TS-419P smbd and flush-9:0 acting up

Questions about SNMP, Power, System, Logs, disk, & RAID.
ivox
Starting out
Posts: 32
Joined: Tue Dec 14, 2010 1:02 pm

Re: TS-419P smbd and flush-9:0 acting up

Post by ivox »

ivox wrote:Same problem!
TS-419P, dead slow speed to write, via FTP, or AFP, or SMBD either!
System: TS-419P, 2T x4 as RAID5, has been Working perfectly for more than half years!
This problem came recently.
dead slow writing to NAS, while the HDD1 led flashes more fast than the others!
RAID error? I guess all the HDD leds will flash in same speed, will thy?
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: TS-419P smbd and flush-9:0 acting up

Post by schumaku »

@ivox: Check disk healtht (SMART), dmesg for any ATA disk eror correction and block replacement messages, /proc/mdstat , ...
ivox
Starting out
Posts: 32
Joined: Tue Dec 14, 2010 1:02 pm

Re: TS-419P smbd and flush-9:0 acting up

Post by ivox »

schumaku wrote:@ivox: Check disk healtht (SMART), dmesg for any ATA disk eror correction and block replacement messages, /proc/mdstat , ...
thank schumaku!
I had done all those. all disks seem good.
and, FW 4.3.3 bings no good news for me, eigher.
ivox
Starting out
Posts: 32
Joined: Tue Dec 14, 2010 1:02 pm

Re: TS-419P smbd and flush-9:0 acting up

Post by ivox »

schumaku wrote:@ivox: Check disk healtht (SMART), dmesg for any ATA disk eror correction and block replacement messages, /proc/mdstat , ...

Code: Select all

# dmesg | grep ata
EXT3-fs (sda1): mounted filesystem with writeback data mode
EXT3-fs (sdb1): mounted filesystem with writeback data mode
EXT3-fs (sdc1): mounted filesystem with writeback data mode
EXT3-fs (sdd1): mounted filesystem with writeback data mode
EXT3-fs (md9): mounted filesystem with writeback data mode
EXT3-fs (md9): mounted filesystem with writeback data mode
EXT3-fs (md9): mounted filesystem with writeback data mode
EXT3-fs (md13): mounted filesystem with writeback data mode
EXT3-fs (md9): mounted filesystem with writeback data mode
EXT4-fs (md0): mounted filesystem with ordered data mode
what's the message meaning? thanks
ivox
Starting out
Posts: 32
Joined: Tue Dec 14, 2010 1:02 pm

Re: TS-419P smbd and flush-9:0 acting up

Post by ivox »

and this

Code: Select all

# dmesg | grep disk
sd 4:0:0:0: [sdc] Attached SCSI disk
sd 5:0:0:0: [sdd] Attached SCSI disk
sd 3:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: [sda] Attached SCSI disk
md9: bitmap initialized from disk: read 5/5 pages, set 1 bits
md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
 disk 0, wo:0, o:1, dev:sda2
 disk 1, wo:1, o:1, dev:sdb2
md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
 disk 0, wo:0, o:1, dev:sda2
 disk 1, wo:0, o:1, dev:sdb2
raid5: device sda3 operational as raid disk 0
raid5: device sdd3 operational as raid disk 3
raid5: device sdc3 operational as raid disk 2
raid5: device sdb3 operational as raid disk 1
 disk 0, o:1, dev:sda3
 disk 1, o:1, dev:sdb3
 disk 2, o:1, dev:sdc3
 disk 3, o:1, dev:sdd3
ivox
Starting out
Posts: 32
Joined: Tue Dec 14, 2010 1:02 pm

Re: TS-419P smbd and flush-9:0 acting up

Post by ivox »

and this:

Code: Select all

# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [raid0] [raid10] 
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
      5855836800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      
md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0]
      530048 blocks [2/2] [UU]
      
md13 : active raid1 sdc4[0] sda4[3] sdd4[2] sdb4[1]
      458880 blocks [4/4] [UUUU]
      bitmap: 1/57 pages [4KB], 4KB chunk

md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
      530048 blocks [4/4] [UUUU]
      bitmap: 0/65 pages [0KB], 4KB chunk

unused devices: <none>
User avatar
joelang1699
Easy as a breeze
Posts: 400
Joined: Tue Feb 03, 2009 11:33 am

Re: TS-419P smbd and flush-9:0 acting up

Post by joelang1699 »

Tried to run SMART health scan today. Disk 1 dropped out of the array. Tried to add it again, the NAS refuses to rebuild the array so im going to wipe the disk in question using a windows pc and try again to add the disk.

This is really bad news so ive shut my NAS down until the disk is wiped as i'm scared to death of loosing everything.
Regards
Joe


TVS-EC1080 32Gb Ram 10x WD60EFRX Raid 6

TS-1079 Pro 16Gb Ram 10x WD60EFRX Raid 6

TS-879 Pro 2Gb Ram 3 X WD60EFRX Raid 5

TVS-863 4Gb Ram 3 X WD60EFRX Raid 5
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: TS-419P smbd and flush-9:0 acting up

Post by schumaku »

@Joe: You don't use by accident some of the disks known to have issues that should be addressed in v3.4.4? Executing the SMART tests does not require unmounting the volume or remove a disk from the RAID. Any indication in # demsg of why the disks was dropped from the raid, or why re-adding failed?
User avatar
joelang1699
Easy as a breeze
Posts: 400
Joined: Tue Feb 03, 2009 11:33 am

Re: TS-419P smbd and flush-9:0 acting up

Post by joelang1699 »

I use Seagate st32000542as drives. Im unsure if these drives had issues with 3.4.4. The SMART tests on drive 1 failed and then it just unmounted itself. Ive never used demsg, how do I run it?
Regards
Joe


TVS-EC1080 32Gb Ram 10x WD60EFRX Raid 6

TS-1079 Pro 16Gb Ram 10x WD60EFRX Raid 6

TS-879 Pro 2Gb Ram 3 X WD60EFRX Raid 5

TVS-863 4Gb Ram 3 X WD60EFRX Raid 5
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: TS-419P smbd and flush-9:0 acting up

Post by schumaku »

dmesg is a Linux shell command to retrieve the latest Kernel messages. Checkk of SSH is enabled in the NAS Web UI. Login on the NAS shell using ie. PuTTY from Windows or the OS X Terminal app ( # ssh admin@[NAS-IP] ).
Last edited by schumaku on Thu Jul 21, 2011 4:53 am, edited 1 time in total.
User avatar
joelang1699
Easy as a breeze
Posts: 400
Joined: Tue Feb 03, 2009 11:33 am

Re: TS-419P smbd and flush-9:0 acting up

Post by joelang1699 »

-sh: dedesg: command not found

Am I missing something here?
Regards
Joe


TVS-EC1080 32Gb Ram 10x WD60EFRX Raid 6

TS-1079 Pro 16Gb Ram 10x WD60EFRX Raid 6

TS-879 Pro 2Gb Ram 3 X WD60EFRX Raid 5

TVS-863 4Gb Ram 3 X WD60EFRX Raid 5
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: TS-419P smbd and flush-9:0 acting up

Post by schumaku »

Code: Select all

dmesg
typo, sorry... :roll:
User avatar
joelang1699
Easy as a breeze
Posts: 400
Joined: Tue Feb 03, 2009 11:33 am

Re: TS-419P smbd and flush-9:0 acting up

Post by joelang1699 »

E.
RAMDISK: gzip image found at block 0
usb 1-1: new high speed USB device using orion-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 136K
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdc1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdd1): mounted filesystem with writeback data mode
md: md9 stopped.
md: bind<sdc1>
md: bind<sdd1>
md: bind<sdb1>
raid1: raid set md9 active with 3 out of 4 mirrors
md9: bitmap initialized from disk: read 5/5 pages, set 1218 bits
created bitmap (65 pages) for device md9
md9: detected capacity change from 0 to 542769152
md9: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: md13 stopped.
md: bind<sdc4>
md: bind<sdd4>
md: bind<sdb4>
raid1: raid set md13 active with 3 out of 4 mirrors
md13: bitmap initialized from disk: read 4/4 pages, set 33255 bits
created bitmap (57 pages) for device md13
md13: detected capacity change from 0 to 469893120
md13: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (md13): using internal journal
EXT3-fs (md13): mounted filesystem with writeback data mode
fuse init (API version 7.13)
NET: Registered protocol family 5
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid10 personality registered for level 10
device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver usblp
sysinfo: Module loaded.
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
ufsd: driver U82 (May 20 2011 01:16:45) LBD=OFF with ioctl loaded at bf18a000
NTFS read/write support included
Hfs+/HfsX read/write support included
Slow work thread pool: Starting up
Slow work thread pool: Ready
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
Enable WDT...
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
eth0: link down
eth0: started
eth1: link down
eth1: started
eth0: stopped
eth0: mac address changed
eth0: started
eth1: stopped
eth1: mac address changed
eth1: started
EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
eth0: link up, full duplex, speed 1 Gbps
eth1: link up, full duplex, speed 1 Gbps
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: bind<sdb2>
raid1: raid set md4 active with 1 out of 1 mirrors
md4: detected capacity change from 0 to 542769152
md4: unknown partition table
Adding 530040k swap on /dev/md4. Priority:-1 extents:1 across:530040k
md: bind<sdc2>
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:sdb2
disk 1, wo:1, o:1, dev:sdc2
md: recovery of RAID array md4
md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 128k window, over a total of 530048 blocks.
md: bind<sdd2>
active port 0 :139
active port 1 :445
active port 2 :20
EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
md: md4: recovery done.
RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:sdb2
disk 1, wo:0, o:1, dev:sdc2
md: md0 stopped.
md: md0 stopped.
md: bind<sdc3>
md: bind<sdd3>
md: bind<sdb3>
raid5: device sdb3 operational as raid disk 1
raid5: device sdd3 operational as raid disk 3
raid5: device sdc3 operational as raid disk 2
raid5: allocated 67488kB for md0
1: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2
RAID5 conf printout:
--- rd:4 wd:3
disk 1, o:1, dev:sdb3
disk 2, o:1, dev:sdc3
disk 3, o:1, dev:sdd3
md0: detected capacity change from 0 to 5996376883200
md0: unknown partition table
EXT4-fs (md0): mounted filesystem with ordered data mode
eth1: stopped
eth0: stopped
eth1: link down
eth1: started
eth0: link down
eth0: started
eth1: link up, full duplex, speed 1 Gbps
eth0: link up, full duplex, speed 1 Gbps
active port 0 :139
active port 1 :445
active port 2 :20
warning: `proftpd' uses 32-bit capabilities (legacy support in use)
TARGET_CORE[0]: Loading Generic Kernel Storage Engine: v3.5.0 on Linux/armv5tel on 2.6.33.2
TARGET_CORE[0]: Initialized ConfigFS Fabric Infrastructure: v3.5.0 on Linux/armv5tel on 2.6.33.2
SE_PC[0] - Registered Plugin Class: TRANSPORT
PLUGIN_TRANSPORT[1] - pscsi registered
PLUGIN_TRANSPORT[4] - iblock registered
PLUGIN_TRANSPORT[5] - rd_dr registered
PLUGIN_TRANSPORT[6] - rd_mcp registered
PLUGIN_TRANSPORT[7] - fileio registered
SE_PC[1] - Registered Plugin Class: OBJ
PLUGIN_OBJ[1] - dev registered
CORE_HBA[0] - Linux-iSCSI.org Ramdisk HBA Driver v3.1 on Generic Target Core Stack v3.5.0
CORE_HBA[0] - Attached Ramdisk HBA: 0 to Generic Target Core TCQ Depth: 256 MaxSectors: 1024
CORE_HBA[0] - Attached HBA to Generic Target Core
RAMDISK: Referencing Page Count: 8
CORE_RD[0] - Built Ramdisk Device ID: 0 space of 8 pages in 1 tables
rd_dr: Using SPC_PASSTHROUGH, no reservation emulation
rd_dr: Using SPC_ALUA_PASSTHROUGH, no ALUA emulation
CORE_RD[0] - Activating Device with TCQ: 0 at Ramdisk Device ID: 0
Vendor: QNAP Model: RAMDISK-DR Revision: 3.1
Type: Direct-Access ANSI SCSI revision: 05
T10 VPD Unit Serial Number: 1234567890:0_0
T10 VPD Page Length: 38
T10 VPD Identifer Length: 34
T10 VPD Identifier Association: addressed logical unit
T10 VPD Identifier Type: T10 Vendor ID based
T10 VPD ASCII Device Identifier: QNAP
CORE_RD[0] - Added LIO DIRECT Ramdisk Device ID: 0 of 8 pages in 1 tables, 32768 total bytes
Initiate iscsi target log successfully.
Linux-iSCSI.org iSCSI Target Core Stack v3.5.0 on Linux/armv5tel on 2.6.33.2
<<<<<<<<<<<<<<<<<<<<<< BEGIN FABRIC API >>>>>>>>>>>>>>>>>>>>>>
Initialized struct target_fabric_configfs: cc585200 for iscsi
<<<<<<<<<<<<<<<<<<<<<< END FABRIC API >>>>>>>>>>>>>>>>>>>>>>
LIO_TARGET[0] - Set fabric -> lio_target_fabric_configfs
iscsi_allocate_thread_sets:206: ***OPS*** Spawned 4 thread set(s) (8 total threads).
TARGET_CORE[iSCSI]: Allocated Discovery se_portal_group_t for endpoint: None, Portal Tag: 1
CORE[0] - Allocated Discovery TPG
Loading Complete.
iscsi_log_rcv_msg: get log pid = 3429.
EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2.
Set Adpater:port=1:1 standby to 241 (1800 secs).
Set Adpater:port=1:2 standby to 241 (1800 secs).
Set Adpater:port=1:3 standby to 241 (1800 secs).
rule type=2, num=4
EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
[~] #
Regards
Joe


TVS-EC1080 32Gb Ram 10x WD60EFRX Raid 6

TS-1079 Pro 16Gb Ram 10x WD60EFRX Raid 6

TS-879 Pro 2Gb Ram 3 X WD60EFRX Raid 5

TVS-863 4Gb Ram 3 X WD60EFRX Raid 5
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: TS-419P smbd and flush-9:0 acting up

Post by schumaku »

Nothig wrong here at all.
User avatar
joelang1699
Easy as a breeze
Posts: 400
Joined: Tue Feb 03, 2009 11:33 am

Re: TS-419P smbd and flush-9:0 acting up

Post by joelang1699 »

Strange. A few weeks ago Disk 4 dropped from the array with no explanation. I was able to add the disk again and rebuild the array with no issues. In the meantime I'll run a full scan of Disk 1 on a windows terminal.
Regards
Joe


TVS-EC1080 32Gb Ram 10x WD60EFRX Raid 6

TS-1079 Pro 16Gb Ram 10x WD60EFRX Raid 6

TS-879 Pro 2Gb Ram 3 X WD60EFRX Raid 5

TVS-863 4Gb Ram 3 X WD60EFRX Raid 5
Post Reply

Return to “System & Disk Volume Management”