Seagate ST2000DL003?

Printers, HDDs, USB/eSATA drives, 3rd-party programs

Re: Seagate ST2000DL003?

Postby shelter » Tue Jul 26, 2011 9:46 pm

I have witnessed the ST2000DL003 drop at startup a couple of times albeit not since upgrading to 3.4.4 althugh also very few reboots since then.

But I did yesterday experience a drop of disk 2 during operation with message "disk read/write error" as also described by UkPaolo. I believe load was minimal. The unit immediately started rebuilding with the hotspare. Two warning emails were correctly sent (Warning: RAID device in degraded mode, and Error: Drive 2 failed). As in UkPaolo's case, removing and re-adding the drive did not change the drive status, but a Bad Blocks Scan did (thanks for the tip, UkPaolo!). SMART tests reveal no problems with the drive, and I'm feeling lucky so haven't bothered with SeaTools.

I have only had this drop during operation happen once so far, fortunately. Could very well be coincidence but did come relatively soon after upgrading to 3.4.4 for me. Pure speculation, sorry. One feature request, though: a 'Reset Disk' button alternative to the 6 hours Bad Blocks Scan would be great :-)

Regards,
Kenneth
QNAP 419P+ fw4.0.2 Build 20130726 with 3 x 3TB Seagate ST3000DM001-1CH1CC24 in RAID5
shelter
New here
 
Posts: 4
Joined: Tue Jul 26, 2011 1:49 pm
Model: TS-419P+

Re: Seagate ST2000DL003?

Postby fuentesa » Tue Jul 26, 2011 10:44 pm

I haven't had any drive failures since I upgraded to 3.4.4 (about 2 weeks now). I did experience dropouts like once a month with 3.4.3, so I'm sure they will happen again sooner or later after reading the posts. Apparently they fixed the reboot problem but the dropout problem (which is the one that I was more concern about) is still there. You can control and minimize the reboots, and you could be prepared in case of a disk failure in reboots, but with dropouts, that's a different story. They happen randomly, without load, with medium load, etc.

After each drop out you need to initiate a scan for bad blocks and rebuild. The total process could take around 20 hours. At least I never had two dropouts at the same time.

Is Qnap looking at this problem? I will probably change the disks with another model, but command Qnap you listed these drives as recommended. I made an investment based on your recommendations.
fuentesa
New here
 
Posts: 5
Joined: Wed Jun 08, 2011 7:42 am
Model: TS-212

Re: Seagate ST2000DL003?

Postby gkchamp » Wed Jul 27, 2011 10:06 am

Just got back from holidays and have upgraded to the latest firmware.

I've had this dropout problem for months which is exactly as ukPaulo has described. I was getting the issue on power up but worked around it by leaving the NAS constantly online. It's the dropouts during normal use that is the most concerning.

QnapAlex's reply concerns me. Have Qnap not even been looking at both issues?
gkchamp
Getting the hang of things
 
Posts: 76
Joined: Fri Feb 04, 2011 10:32 pm
Model: TS-259 Pro+

Re: Seagate ST2000DL003?

Postby EnJayt6 » Wed Jul 27, 2011 3:47 pm

Hi guys, I am experiencing the same problem, with 3.4.4. At start up Disk 1 has a Read/Write error ad Raid 5 is in degraded mode. I just bought my TS-419+ one week ago.
I did a bad blocks check, but that came out fine. The check now option does not appear in my Raid Management.
And just now did a complete reset, but that dis not help either...

What is also strange that if I remove the disk and reinsert it, the light goes to green, only the error is still there and of course the red light is blinking.

I am a little bit lost what to do now what to do...
EnJayt6
New here
 
Posts: 5
Joined: Fri Jul 22, 2011 6:56 pm
Model: TS-219P+

Re: Seagate ST2000DL003?

Postby schumaku » Wed Jul 27, 2011 4:47 pm

If one or some HDD(s) is/are not detected after boottime, you need to get a special "uboot" update version from QNAP support, specifically for the TS-x19+ NAS models. Appears QNAP Support does not readily know about this fix - so insist they should challenge the product management departement FMI.
User avatar
schumaku
Guru
 
Posts: 31277
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Model: TS-x79 Pro

Re: Seagate ST2000DL003?

Postby schumaku » Wed Jul 27, 2011 6:18 pm

Here we go: viewtopic.php?f=160&t=47468

Ignore the U-Boot screen views - users will never see these, lack of a serial console adapter :roll:
User avatar
schumaku
Guru
 
Posts: 31277
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Model: TS-x79 Pro

Re: Seagate ST2000DL003?

Postby EnJayt6 » Wed Jul 27, 2011 8:24 pm

I think I out of troubles. Switched HDD1 with HDD2. And seems to work fine. Restarted 2 times without troubles.... fingers crossed.
EnJayt6
New here
 
Posts: 5
Joined: Fri Jul 22, 2011 6:56 pm
Model: TS-219P+

Re: Seagate ST2000DL003?

Postby schumaku » Wed Jul 27, 2011 8:27 pm

EnJayt6 wrote:I think I out of troubles. ... fingers crossed.
U-Boot firmwae update installed?
User avatar
schumaku
Guru
 
Posts: 31277
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Model: TS-x79 Pro

Re: Seagate ST2000DL003?

Postby Lorenz0 » Thu Jul 28, 2011 2:42 am

So, to summarize, there seem to be two distinct issues with this HDs:

1. Disks randomly fail at startup ("Disk Read/Write Error"), but SMART parameters seem OK and bad block tests reveal nothing:

1a. No notification Email gets sent, even if Test-Email arrives

2. Disks get randomly disconnected while running.
----------
Luckily, I have experienced only problems 1 and 1a, see pic
Image
(HD Firmware is the current version CC32, QNAP-Firmware 3.4.4 Build 0718T)

After installing the new FW I rebooted twice and got twice those issues :(

Since I don't reboot often it's no major issue, I just have to type (given that in my case it's always disk 3 or sdc that has these issues:)
Code: Select all
mdadm /dev/md0 --re-add /dev/sdc3
mdadm /dev/md9 --re-add /dev/sdc1

That way I don't have to unplug the HD, but the LED above disk 3 remains red.
Lorenz0
Starting out
 
Posts: 11
Joined: Sat Apr 09, 2011 12:40 am
Model: TS-212

Re: Seagate ST2000DL003?

Postby schumaku » Thu Jul 28, 2011 2:55 am

There must be evidence of the read/write errors in dmesg as well as in /mnt/HDA_ROOT/.logs/kmsg - likely with more information what goes mad with one of four drives on your NAS.
User avatar
schumaku
Guru
 
Posts: 31277
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Model: TS-x79 Pro

Re: Seagate ST2000DL003?

Postby Lorenz0 » Thu Jul 28, 2011 4:58 am

Here is my dmesg:
Code: Select all
isk: read 5/5 pages, set 81501 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<sda4>
md: bind<sdd4>
md: bind<sdc4>
md: bind<sdb4>
raid1: raid set md13 active with 4 out of 4 mirrors
md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
created bitmap (57 pages) for device md13
md13: detected capacity change from 0 to 469893120
 md13: unknown partition table
scsi 6:0:0:0: Direct-Access     WD       Ext HDD 1021     2021 PQ: 0 ANSI: 4
sd 6:0:0:0: Attached scsi generic sg8 type 0
sd 6:0:0:0: [sdi] 3907024896 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 6:0:0:0: [sdi] Write Protect is off
sd 6:0:0:0: [sdi] Mode Sense: 17 00 10 08
sd 6:0:0:0: [sdi] Assuming drive cache: write through
sd 6:0:0:0: [sdi] Assuming drive cache: write through
 sdi:
scsi 7:0:0:0: Direct-Access     BUFFALO  External HDD     0000 PQ: 0 ANSI: 3
sd 7:0:0:0: Attached scsi generic sg20 type 0
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
sd 7:0:0:0: [sdu] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 7:0:0:0: [sdu] Write Protect is off
sd 7:0:0:0: [sdu] Mode Sense: 3b 00 00 00
sd 7:0:0:0: [sdu] Assuming drive cache: write through
sd 7:0:0:0: [sdu] Assuming drive cache: write through
 sdu: sdu1
sd 7:0:0:0: [sdu] Assuming drive cache: write through
sd 7:0:0:0: [sdu] Attached SCSI disk
fuse init (API version 7.13)
 sdi1
sd 6:0:0:0: [sdi] Assuming drive cache: write through
sd 6:0:0:0: [sdi] Attached SCSI disk
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 (Jul 18 2011 07:40:05)  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: started
eth0: stopped
eth0: mac address changed
eth0: started
eth1: stopped
eth1: mac address changed
eth1: started
eth0: 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<sda2>
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<sdb2>
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:sda2
 disk 1, wo:1, o:1, dev:sdb2
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
md: md4: recovery done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda2
 disk 1, wo:0, o:1, dev:sdb2
md: md0 stopped.
md: md0 stopped.
md: bind<sdb3>
md: bind<sdc3>
md: bind<sdd3>
md: bind<sda3>
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
raid5: allocated 67488kB for md0
0: 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
1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
raid5: raid level 5 set md0 active with 4 out of 4 devices, algorithm 2
RAID5 conf printout:
 --- rd:4 wd:4
 disk 0, o:1, dev:sda3
 disk 1, o:1, dev:sdb3
 disk 2, o:1, dev:sdc3
 disk 3, o:1, dev:sdd3
md0: bitmap initialized from disk: read 30/30 pages, set 42 bits
created bitmap (466 pages) for device md0
md0: detected capacity change from 0 to 5996376686592
 md0: unknown partition table
raid5: Disk failure on sdc3, disabling device. <===
raid5: Operation continuing on 3 devices.
RAID5 conf printout:
 --- rd:4 wd:3
 disk 0, o:1, dev:sda3
 disk 1, o:1, dev:sdb3
 disk 2, o:0, dev:sdc3
 disk 3, o:1, dev:sdd3
RAID5 conf printout:
 --- rd:4 wd:3
 disk 0, o:1, dev:sda3
 disk 1, o:1, dev:sdb3
 disk 3, o:1, dev:sdd3
md: unbind<sdc3>
md: export_rdev(sdc3)
EXT4-fs (md0): mounted filesystem with ordered data mode
eth1: stopped
eth0: stopped
eth1: started
eth0: link down
eth0: started
eth0: link up, full duplex, speed 1 Gbps
active port 0 :139
active port 1 :445
active port 2 :20
EXT4-fs (sdu1): mounted filesystem with ordered data mode
active port 0 :139
active port 1 :445
active port 2 :20
ufsd: sdi1 without journal
warning: process `storage_boot_in' used the deprecated sysctl system call with 8.1.2.
active port 0 :139
active port 1 :445
active port 2 :20
 Set Adpater:port=1:0 standby to 241 (1800 secs).
 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=0
Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)


And here is kmesg
Code: Select all
rce kw_clocksource
<6>NET: Registered protocol family 2
<6>IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>TCP established hash table entries: 8192 (order: 4, 65536 bytes)
<6>TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
<6>TCP: Hash tables configured (established 8192 bind 8192)
<6>TCP reno registered
<6>UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>NET: Registered protocol family 1
<6>RPC: Registered udp transport module.
<6>RPC: Registered tcp transport module.
<6>RPC: Registered tcp NFSv4.1 backchannel transport module.
<7>PCI: CLS 32 bytes, default 32
<6>Trying to unpack rootfs image as initramfs...
<6>rootfs image is not initramfs (no cpio magic); looks like an initrd
<6>Freeing initrd memory: 9216K
<4>QNAP RTC initializing....
<4>Initializing RTC is completed.
<6>rtc kw_rtc: rtc core: registered kw-rtc as rtc0
<4>RTC registered
<4>watchdog_init: succeed to register misc device
<4>Init WDT and Active SYSREST if WDT timeout
<6>XOR registered 4 channels
<6>XOR 2nd invalidate WA enabled
<5>MV Buttons Driver Load
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>audit: initializing netlink socket (disabled)
<5>type=2000 audit(1311792069.000:1): initialized
<5>VFS: Disk quotas dquot_6.5.2
<4>Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
<6>Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
<6>msgmni has been set to 499
<6>alg: No test for stdrng (krng)
<6>io scheduler noop registered
<6>io scheduler deadline registered
<6>io scheduler cfq registered (default)
<6>Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
<6>serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
<6>serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
<6>brd: module loaded
<6>loop: module loaded
<4>serial8250_PIC_init..uartclk = 200000000,baudDivisor = 651,irq = 34
<4>qnap_pic_init: succeed to register misc device
<4>tsinfo: create proc systemp successfully
<4>tsinfo: create proc systemp successfully
<4>Integrated Sata device found
<4>IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
<4>Spin up ...(0:0)
<4>Spin up ...(0:1)
<4>Spin up all...
<4>[0 0]: Waiting for channel initialization.
<4>[0 1]: Waiting for channel initialization.
<6>scsi0 : Marvell SCSI to SATA adapter
<6>scsi1 : Marvell SCSI to SATA adapter
<4>PCI: enabling device 0000:00:01.0 (0140 -> 0143)
<4>IRQ 9/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
<4>Spin up ...(1:0)
<4>Spin up ...(1:1)
<4>Spin up ...(1:2)
<4>Spin up ...(1:3)
<4>Spin up all...
<4>[1 0]: Waiting for channel initialization.
<4>[1 1]: Waiting for channel initialization.
<4>[1 2]: Waiting for channel initialization.
<4>[1 3]: Waiting for channel initialization.
<4> Wait 0 seconds to initialize scsi 0.
<6>scsi2 : Marvell SCSI to SATA adapter
<4> Wait 0 seconds to initialize scsi 1.
<6>scsi3 : Marvell SCSI to SATA adapter
<4> Wait 5 seconds to initialize scsi 2.
<6>scsi4 : Marvell SCSI to SATA adapter
<4> Wait 5 seconds to initialize scsi 3.
<6>scsi5 : Marvell SCSI to SATA adapter
<4>ENABLE_WRITE_CACHE (current: enabled).
<4>ENABLE_WRITE_CACHE (current: enabled).
<4>ENABLE_WRITE_CACHE (current: enabled).
<4>ENABLE_WRITE_CACHE (current: enabled).
<5>scsi 2:0:0:0: Direct-Access     Seagate  ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
<5>scsi 3:0:0:0: Direct-Access     Seagate  ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
<5>scsi 4:0:0:0: Direct-Access     Seagate  ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
<5>scsi 5:0:0:0: Direct-Access     Seagate  ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
<4>Check proc_name[mvSata].
<4>Check proc_name[mvSata].
<4>Check proc_name[mvSata].
<5>sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512.
<5>sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
<5>sd 2:0:0:0: [sda] 0-byte physical blocks
<4>Check proc_name[mvSata].
<5>sd 2:0:0:0: [sda] Write Protect is off
<7>sd 2:0:0:0: [sda] Mode Sense: 23 00 10 00
<5>sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512.
<5>sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
<5>sd 3:0:0:0: [sdb] 0-byte physical blocks
<5>sd 3:0:0:0: [sdb] Write Protect is off
<7>sd 3:0:0:0: [sdb] Mode Sense: 23 00 10 00
<5>sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512.
<5>sd 4:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
<5>sd 4:0:0:0: [sdc] 0-byte physical blocks
<5>sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
<5>sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512.
<5>sd 4:0:0:0: [sdc] Write Protect is off
<7>sd 4:0:0:0: [sdc] Mode Sense: 23 00 10 00
<5>sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
<5>sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512.
<5>sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512.
<5>sd 5:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
<5>sd 5:0:0:0: [sdd] 0-byte physical blocks
<6> sda:
<5>sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
<5>sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512.
<5>sd 5:0:0:0: [sdd] Write Protect is off
<7>sd 5:0:0:0: [sdd] Mode Sense: 23 00 10 00
<4>Check proc_name[mvSata].
<6> sdb:
<5>sd 2:0:0:0: Attached scsi generic sg0 type 0
<4>Check proc_name[mvSata].
<5>sd 3:0:0:0: Attached scsi generic sg1 type 0
<4>Check proc_name[mvSata].
<5>sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
<5>sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512.
<6> sdc:
<5>sd 4:0:0:0: Attached scsi generic sg2 type 0
<4>Check proc_name[mvSata].
<5>sd 5:0:0:0: Attached scsi generic sg3 type 0
<4>SPI Serial flash detected @ 0xf4000000, 16384KB (64sec x 256KB)
<5>Creating 6 MTD partitions on "spi_flash":
<5>0x000000000000-0x000000080000 : "U-Boot"
<6> sdd:
<5>0x000000200000-0x000000400000 : "Kernel"
<5>0x000000400000-0x000000d00000 : "RootFS"
<5>0x000000d00000-0x000001000000 : "RootFS2"
<5>0x000000080000-0x0000000c0000 : "U-Boot Config"
<5>0x0000000c0000-0x000000200000 : "NAS Config"
<4>Loading Marvell Ethernet Driver:
<4>  o Cached descriptors in DRAM
<4>  o DRAM SW cache-coherency
<4>  o 2 Giga ports supported
<4>  o Single RX Queue support - ETH_DEF_RXQ=0
<4>  o Single TX Queue support - ETH_DEF_TXQ=0
<4>  o TCP segmentation offload (TSO) supported
<4>  o Large Receive offload (LRO) supported
<4>  o Receive checksum offload supported
<4>  o Transmit checksum offload supported
<4>  o Network Fast Processing (Routing) supported - (Disabled)
<4>  o Proc tool API enabled
<4>  o SKB Reuse supported - (Disabled)
<4>  o SKB Recycle supported - (Disabled)
<4>  o Rx descripors: q0=128
<4>  o Tx descripors: q0=532
<4>  o Loading network interface(s):
<4>    o  register under mv88fx_eth platform
<4> sda1 sda2 sda3 sda4
<4> sdc1 sdc2 sdc3 sdc4
<4> sdd1 sdd2 sdd3 sdd4
<5>sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512.
<5>sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512.
<5>sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512.
<4>    o eth0, ifindex = 2, GbE port = 0
<4> sdb1 sdb2 sdb3 sdb4
<5>sd 2:0:0:0: [sda] Attached SCSI disk
<5>sd 4:0:0:0: [sdc] Attached SCSI disk
<5>sd 5:0:0:0: [sdd] Attached SCSI disk
<5>sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512.
<4>    o eth1, ifindex = 3, GbE port = 1
<4>
<4>mvFpRuleDb (00000010): 0 entries, 0 bytes
<4>Marvell debug tracing is on
<6>ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>orion-ehci orion-ehci.0: Marvell Orion EHCI
<6>orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
<5>sd 3:0:0:0: [sdb] Attached SCSI disk
<6>orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
<6>orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<4>usb: create proc systemp successfully
<4>usb: create proc systemp successfully
<6>mice: PS/2 mouse device common for all mice
<6>md: raid1 personality registered for level 1
<6>md: raid6 personality registered for level 6
<6>md: raid5 personality registered for level 5
<6>md: raid4 personality registered for level 4
<6>TCP cubic registered
<6>NET: Registered protocol family 17
<6>rtc kw_rtc: setting system clock to 2011-07-27 18:41:51 UTC (1311792111)
<6>md: Waiting for all devices to be available before autodetect
<6>md: If you don't use raid, use raid=noautodetect
<6>md: Autodetecting RAID arrays.
<6>md: Scanned 0 and added 0 devices.
<6>md: autorun ...
<6>md: ... autorun DONE.
<5>RAMDISK: gzip image found at block 0
<6>usb 1-1: new high speed USB device using orion-ehci and address 2
<6>hub 1-1:1.0: USB hub found
<6>hub 1-1:1.0: 4 ports detected
<6>usb 1-1.1: new high speed USB device using orion-ehci and address 3
<6>scsi6 : usb-storage 1-1.1:1.0
<6>usb 1-1.4: new high speed USB device using orion-ehci and address 4
<4>VFS: Mounted root (ext2 filesystem) on device 1:0.
<6>Freeing init memory: 136K
<6>scsi7 : usb-storage 1-1.4:1.0
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (sda1): mounted filesystem with writeback data mode
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (sdb1): mounted filesystem with writeback data mode
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (sdc1): mounted filesystem with writeback data mode
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (sdd1): mounted filesystem with writeback data mode
<6>md: md9 stopped.
<6>md: bind<sdb1>
<6>md: bind<sdd1>
<6>md: bind<sda1>
<6>raid1: raid set md9 active with 3 out of 4 mirrors                      <===
<6>md9: bitmap initialized from disk: read 5/5 pages, set 81501 bits
<6>created bitmap (65 pages) for device md9
<6>md9: detected capacity change from 0 to 542769152
<6> md9: unknown partition table
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (md9): using internal journal
<6>EXT3-fs (md9): mounted filesystem with writeback data mode
<6>md: md13 stopped.
<6>md: bind<sda4>
<6>md: bind<sdd4>
<6>md: bind<sdc4>
<6>md: bind<sdb4>
<6>raid1: raid set md13 active with 4 out of 4 mirrors
<6>md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
<6>created bitmap (57 pages) for device md13
<6>md13: detected capacity change from 0 to 469893120
<6> md13: unknown partition table
<5>scsi 6:0:0:0: Direct-Access     WD       Ext HDD 1021     2021 PQ: 0 ANSI: 4
<5>sd 6:0:0:0: Attached scsi generic sg8 type 0
<5>sd 6:0:0:0: [sdi] 3907024896 512-byte logical blocks: (2.00 TB/1.81 TiB)
<5>sd 6:0:0:0: [sdi] Write Protect is off
<7>sd 6:0:0:0: [sdi] Mode Sense: 17 00 10 08
<3>sd 6:0:0:0: [sdi] Assuming drive cache: write through
<3>sd 6:0:0:0: [sdi] Assuming drive cache: write through
<6> sdi:
<5>scsi 7:0:0:0: Direct-Access     BUFFALO  External HDD     0000 PQ: 0 ANSI: 3
<5>sd 7:0:0:0: Attached scsi generic sg20 type 0
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (md9): using internal journal
<6>EXT3-fs (md9): mounted filesystem with writeback data mode
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (md9): using internal journal
<6>EXT3-fs (md9): mounted filesystem with writeback data mode
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (md13): using internal journal
<6>EXT3-fs (md13): mounted filesystem with writeback data mode
<5>sd 7:0:0:0: [sdu] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
<5>sd 7:0:0:0: [sdu] Write Protect is off
<7>sd 7:0:0:0: [sdu] Mode Sense: 3b 00 00 00
<3>sd 7:0:0:0: [sdu] Assuming drive cache: write through
<3>sd 7:0:0:0: [sdu] Assuming drive cache: write through
<6> sdu: sdu1
<3>sd 7:0:0:0: [sdu] Assuming drive cache: write through
<5>sd 7:0:0:0: [sdu] Attached SCSI disk
<6>fuse init (API version 7.13)
<4> sdi1
<3>sd 6:0:0:0: [sdi] Assuming drive cache: write through
<5>sd 6:0:0:0: [sdi] Attached SCSI disk
<6>NET: Registered protocol family 5
<6>md: linear personality registered for level -1
<6>md: raid0 personality registered for level 0
<6>md: raid10 personality registered for level 10
<6>device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver
<6>usbcore: registered new interface driver usblp
<6>sysinfo: Module loaded.
<4>ufsd: module license 'Commercial product' taints kernel.
<4>Disabling lock debugging due to kernel taint
<5>ufsd: driver U82 (Jul 18 2011 07:40:05)  LBD=OFF with ioctl loaded at bf18a000
<5>NTFS read/write support included
<5>Hfs+/HfsX read/write support included
<5>Slow work thread pool: Starting up
<5>Slow work thread pool: Ready
<6>lib80211: common routines for IEEE802.11 drivers
<7>lib80211_crypt: registered algorithm 'NULL'
<6>cfg80211: Calling CRDA to update world regulatory domain
<4>Enable WDT...
<6>usbcore: registered new interface driver snd-usb-audio
<6>usbcore: registered new interface driver snd-usb-caiaq
<5>eth0: link down
<5>eth0: started
<5>eth1: started
<5>eth0: stopped
<5>eth0: mac address changed
<5>eth0: started
<5>eth1: stopped
<5>eth1: mac address changed
<5>eth1: started
<5>eth0: link up, full duplex, speed 1 Gbps
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (md9): using internal journal
<6>EXT3-fs (md9): mounted filesystem with writeback data mode
<6>md: bind<sda2>
<6>raid1: raid set md4 active with 1 out of 1 mirrors
<6>md4: detected capacity change from 0 to 542769152
<6> md4: unknown partition table
<6>Adding 530040k swap on /dev/md4.  Priority:-1 extents:1 across:530040k
<6>md: bind<sdb2>
<4>RAID1 conf printout:
<4> --- wd:1 rd:2
<4> disk 0, wo:0, o:1, dev:sda2
<4> disk 1, wo:1, o:1, dev:sdb2
<6>md: recovery of RAID array md4
<6>md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
<6>md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
<6>md: using 128k window, over a total of 530048 blocks.
<6>md: bind<sdd2>
<4>active port 0 :139
<4>active port 1 :445
<4>active port 2 :20
<6>md: md4: recovery done.
<4>RAID1 conf printout:
<4> --- wd:2 rd:2
<4> disk 0, wo:0, o:1, dev:sda2
<4> disk 1, wo:0, o:1, dev:sdb2
<6>md: md0 stopped.
<6>md: md0 stopped.
<6>md: bind<sdb3>
<6>md: bind<sdc3>
<6>md: bind<sdd3>
<6>md: bind<sda3>
<6>raid5: device sda3 operational as raid disk 0
<6>raid5: device sdd3 operational as raid disk 3
<6>raid5: device sdc3 operational as raid disk 2
<6>raid5: device sdb3 operational as raid disk 1
<6>raid5: allocated 67488kB for md0
<4>0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
<4>3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
<4>2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
<4>1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
<4>raid5: raid level 5 set md0 active with 4 out of 4 devices, algorithm 2
<4>RAID5 conf printout:
<4> --- rd:4 wd:4
<4> disk 0, o:1, dev:sda3
<4> disk 1, o:1, dev:sdb3
<4> disk 2, o:1, dev:sdc3
<4> disk 3, o:1, dev:sdd3
<6>md0: bitmap initialized from disk: read 30/30 pages, set 42 bits
<6>created bitmap (466 pages) for device md0
<6>md0: detected capacity change from 0 to 5996376686592
<6> md0: unknown partition table
<1>raid5: Disk failure on sdc3, disabling device.                               <===
<1>raid5: Operation continuing on 3 devices.
<4>RAID5 conf printout:
<4> --- rd:4 wd:3
<4> disk 0, o:1, dev:sda3
<4> disk 1, o:1, dev:sdb3
<4> disk 2, o:0, dev:sdc3
<4> disk 3, o:1, dev:sdd3
<4>RAID5 conf printout:
<4> --- rd:4 wd:3
<4> disk 0, o:1, dev:sda3
<4> disk 1, o:1, dev:sdb3
<4> disk 3, o:1, dev:sdd3
<6>md: unbind<sdc3>
<6>md: export_rdev(sdc3)
<6>EXT4-fs (md0): mounted filesystem with ordered data mode
<5>eth1: stopped
<5>eth0: stopped
<5>eth1: started
<5>eth0: link down
<5>eth0: started
<5>eth0: link up, full duplex, speed 1 Gbps
<4>active port 0 :139
<4>active port 1 :445
<4>active port 2 :20
<6>EXT4-fs (sdu1): mounted filesystem with ordered data mode
<4>active port 0 :139
<4>active port 1 :445
<4>active port 2 :20
<5>ufsd: sdi1 without journal
<6>warning: process `storage_boot_in' used the deprecated sysctl system call with 8.1.2.
<4>active port 0 :139
<4>active port 1 :445
<4>active port 2 :20
<4> Set Adpater:port=1:0 standby to 241 (1800 secs).
<4> Set Adpater:port=1:1 standby to 241 (1800 secs).
<4> Set Adpater:port=1:2 standby to 241 (1800 secs).
<4> Set Adpater:port=1:3 standby to 241 (1800 secs).
<4>rule type=2, num=0
<6>Loading iSCSI transport class v2.0-871.
<5>iscsi: registered transport (tcp)


"Disk failure on sdc3, disabling device." Not very enlightening, eh? :?
Lorenz0
Starting out
 
Posts: 11
Joined: Sat Apr 09, 2011 12:40 am
Model: TS-212

Re: Seagate ST2000DL003?

Postby fk8 » Fri Jul 29, 2011 12:52 am

I can confirm drops on my TS-209 Pro with a newly installed ST2000DL003. I'm running firmware 3.3.0 Build 0924T.

Same issue as reported above. No errors reported under testing and drive works perfectly under any other Linux.


I'm in the process migrating to bigger drives but if this is how it will be I'm considering just getting a new NAS and be rid of this issues. Seems Synology NAS works good with these Seagate drives.
fk8
Starting out
 
Posts: 13
Joined: Fri Jul 29, 2011 12:34 am
Model: TS-109/209

Re: Seagate ST2000DL003?

Postby fk8 » Fri Jul 29, 2011 8:48 am

Interesting:

Code: Select all
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10]
md5 : active raid1 sdb2[1] sda2[0]
      530048 blocks [2/2] [UU]

md13 : active raid1 sda4[0] sdb4[1]
      71808 blocks [2/2] [UU]

md9 : active raid1 sdb1[1] sda1[0]
      530048 blocks [2/2] [UU]

md0 : active raid1 sdb3[1] sda3[0]
      487243328 blocks [2/2] [UU]

unused devices: <none>


Code: Select all
   2011-07-28   20:23:56   System   127.0.0.1   localhost   [Mirror Disk Volume: Drive 1 2] Rebuilding done.
   2011-07-28   17:15:35   System   127.0.0.1   localhost   [Mirror Disk Volume: Drive 1 2] Start rebuilding.


Also SMART status is good.

But QNAP administration interface refuse to cooperate. Anyone know where the interface gets its status from??

I'll try to rebuilld the RAID but it seems the interface refuse to let go of the status. The software under is not reporting problems, only QNAP software it seems.
fk8
Starting out
 
Posts: 13
Joined: Fri Jul 29, 2011 12:34 am
Model: TS-109/209

Re: Seagate ST2000DL003?

Postby fk8 » Fri Jul 29, 2011 9:06 am

Still getting the "Disk Read/Write Error" even after manually taking the disk out of the array, restarting the NAS, and re-fitting it.

So it seems QNAP software tries to be smart. saves the fail information on the drive and gives a rats ** about what is reported by the system and linux raid software. Brilliant.
fk8
Starting out
 
Posts: 13
Joined: Fri Jul 29, 2011 12:34 am
Model: TS-109/209

Re: Seagate ST2000DL003?

Postby UkPaolo » Fri Jul 29, 2011 3:43 pm

fk8 wrote:Still getting the "Disk Read/Write Error" even after manually taking the disk out of the array, restarting the NAS, and re-fitting it.

So it seems QNAP software tries to be smart. saves the fail information on the drive and gives a rats ** about what is reported by the system and linux raid software. Brilliant.


Try running a bad blocks scan - it'll take a few hours and find no problems, but at the end the NAS seems to wake up and realise that the drive is OK after all and initiate a RAID rebuild. Takes far longer than it should but it's the only way I've found that works...
UkPaolo
Starting out
 
Posts: 11
Joined: Mon Apr 04, 2011 4:10 am
Model: TS-401T

PreviousNext

Return to Hardware & Software Compatibility

Who is online

Users browsing this forum: No registered users and 5 guests