LinkBack URL
About LinkBacks
Got a bizarre problem with this configuration.
Got 3 drives (SD17) firmware.
When first built one Seagate was DOA, it was swapped. (CC1H firmware)
Upgraded other two to SD1A firmware.
Built the 3800 no problems. RAID 5, 128K stripe.
Replacement Seagate gets 5 "reallocated sectors" (RS), RAID rebuilds. Then gets 9, but no rebuild.
One of originals get 1 RS, no rebuild.
Disk in bay 1 has 0 RS.
Works perfectly for 4 weeks. When I add more and more (over 1TB)
Replacement disk jumps to 10 RS.
RAID is HEALTHY but all applications report NO RAID. Nothing works, no service folders, nothing. Disk appear fine under shutdown and bootup, M3800 reports SATA fine, RAID Healthy but I can't get to anything.
Thecus log in and send me this...a fault log on the disk in TRAY 1
---------------------------------------
ata3: EH complete
sd 2:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
sd 2:0:0:0: [sda] THECUS real size: sdp->tray_id: 1, dkp->capacity: 2930277168, sector_size: 512
sd 2:0:0:0: [sda] THECUS align 128M: sdp->tray_id: 1, dkp->capacity: 2930245632, sector_size: 512
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
res 51/04:00:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
ata3.00: Host Protected Area detected:
current size: 2930277168 sectors
native size: -1364690128 sectors
ata3.00: Host Protected Area detected:
current size: 2930277168 sectors
native size: -1364690128 sectors
ata3.00: configured for UDMA/100
---------------------
A Host Area Protection detected. Notice the -136... this is a signed value >2^32 and is wrapping. A bug in the Linux they are using? A known issue in several unix versions last September, known as the "false Host Area detection bug"
I remove HD1, DOS SeaTools (Windows version fails to see drive at all ) says nothing wrong. HD Capacity tools says no "volume reduction" detected, disk at full capacity.
I trash all partitions, Windows likes the drive. I trash that partition.
Replace in the M3800 which says "new drive", rebuilding RAID. 660 minutes later. RAID HEALTHY. But it will still not mount although the GUI says SATA OK, RAID OK. The OS can see the drives to rebuild but not mount them. That does not sound like a hardware fault to me.
Also why does the DEGRADED RAID not mount if HD1 was the problem?
Anybody any ideas? I think their Linux is broken and can't handle big drives consistently. This "bug" apparently only manifests when timeouts occur, not all the time.
Anyhow I am sat here with a healthy RAID 5 setup with 1.2TB of data on it and can't get to it, although I can remove and replace drives and it works perfectly rebuilding each time!!!
charker
