2Big Network 2, Hard disk 2 failed

[manelppa]

The best is to save as a text file which I dificulty succeeded. Check if this is ok (as file)

[Jocko]

Yes a file is possible.

Currently I see two hardware issues :
-either disk2 is a damaged disk (so just need to buy another one)
-or an issue on the sata port what would be a very bad new

[manelppa]

last page of the dmesg command

Code: Select all

[ 9399.015342] ata2.15: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 9399.022676] ata2.00: hard resetting link
[ 9399.515379] ata2.00: configured for UDMA/33
[ 9399.519797] ata2: EH complete
[ 9429.780881] ata2.00: failed to read SCR 1 (Emask=0x40)
[ 9429.786064] ata2.00: failed to read SCR 0 (Emask=0x40)
[ 9429.791195] ata2.01: failed to read SCR 1 (Emask=0x40)
[ 9429.796356] ata2.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9429.803401] ata2.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9429.810628] ata2.00: failed command: WRITE DMA EXT
[ 9429.815444] ata2.00: cmd 35/00:80:a2:69:08/00:03:00:00:00/e0 tag 0 dma 458752 out
[ 9429.815444]          res 40/00:01:a8:50:22/00:00:00:00:00/e0 Emask 0x4 (timeout)
[ 9429.830271] ata2.00: status: { DRDY }
[ 9429.833942] ata2.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9429.841178] ata2.15: hard resetting link
[ 9430.885351] ata2.15: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 9430.892706] ata2.00: hard resetting link
[ 9431.286054] ata2.01: hard resetting link
[ 9436.935361] ata2.00: qc timeout (cmd 0xec)
[ 9436.939475] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 9436.945580] ata2.00: revalidation failed (errno=-5)
[ 9436.950461] ata2.15: hard resetting link
[ 9437.995354] ata2.15: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 9438.002708] ata2.00: hard resetting link
[ 9438.495388] ata2.00: configured for UDMA/33
[ 9438.499820] ata2: EH complete
[ 9468.820875] ata2.00: failed to read SCR 1 (Emask=0x40)
[ 9468.826053] ata2.00: failed to read SCR 0 (Emask=0x40)
[ 9468.831190] ata2.01: failed to read SCR 1 (Emask=0x40)
[ 9468.836350] ata2.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9468.843387] ata2.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9468.850614] ata2.00: failed command: WRITE DMA EXT
[ 9468.855431] ata2.00: cmd 35/00:80:a2:69:08/00:03:00:00:00/e0 tag 0 dma 458752 out
[ 9468.855431]          res 40/00:01:a8:50:22/00:00:00:00:00/e0 Emask 0x4 (timeout)
[ 9468.870258] ata2.00: status: { DRDY }
[ 9468.873928] ata2.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9468.881161] ata2.15: hard resetting link
[ 9469.925358] ata2.15: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 9469.932705] ata2.00: hard resetting link
[ 9470.326063] ata2.01: hard resetting link
[ 9471.015394] ata2.00: configured for UDMA/33
[ 9471.019827] sd 1:0:0:0: [sdb] 
[ 9471.022974] Result: hostbyte=0x00 driverbyte=0x08
[ 9471.027697] sd 1:0:0:0: [sdb] 
[ 9471.030841] Sense Key : 0xb [current] [descriptor]
[ 9471.035713] Descriptor sense data with sense descriptors (in hex):
[ 9471.041886]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 9471.048540]         00 22 50 a8
[ 9471.051855] sd 1:0:0:0: [sdb] 
[ 9471.054989] ASC=0x0 ASCQ=0x0
[ 9471.057914] sd 1:0:0:0: [sdb] CDB:
[ 9471.061399] cdb[0]=0x2a: 2a 00 00 08 69 a2 00 03 80 00
[ 9471.066767] end_request: I/O error, dev sdb, sector 551330
[ 9471.073239] ata2: EH complete
[ 9471.625423] RAID1 conf printout:
[ 9471.625436]  --- wd:1 rd:2
[ 9471.625447]  disk 0, wo:0, o:1, dev:sda8
[ 9471.625456]  disk 1, wo:1, o:0, dev:sdb8
[ 9471.665345] RAID1 conf printout:
[ 9471.665355]  --- wd:1 rd:2
[ 9471.665365]  disk 0, wo:0, o:1, dev:sda8
root@fvdw-sta-kirkwood:/ #

[manelppa]

I have another 2Tb hard disk but exactely the same model.
The actual disk inside the NAS are WD 2.0TB SATA 64MB Cache (model WD20EARX).
The new I own and can replace the faulty one is WD 2.0TB SATA 32MB Cache WD20EADS

Do you think it's ok to add the new model for Disk II and recreate the partition as you sent me ?

[Jocko]

hummm

That seems to be a sata port issue

Code: Select all

[ 9437.995354] ata2.15: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 9438.002708] ata2.00: hard resetting link
[ 9438.495388] ata2.00: configured for UDMA/33
[ 9438.499820] ata2: EH complete
[ 9468.820875] ata2.00: failed to read SCR 1 (Emask=0x40)
[ 9468.826053] ata2.00: failed to read SCR 0 (Emask=0x40)
[ 9468.831190] ata2.01: failed to read SCR 1 (Emask=0x40)
[ 9468.836350] ata2.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9468.843387] ata2.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9468.850614] ata2.00: failed command: WRITE DMA EXT
[ 9468.855431] ata2.00: cmd 35/00:80:a2:69:08/00:03:00:00:00/e0 tag 0 dma 458752 out
[ 9468.855431]          res 40/00:01:a8:50:22/00:00:00:00:00/e0 Emask 0x4 (timeout)
[ 9468.870258] ata2.00: status: { DRDY }

fvdw is more competent on these hardware issues.

So wait what he will say :?

[Jocko]

The new I own and can replace the faulty one is WD 2.0TB SATA 32MB Cache WD20EADS

According to WD this disk should not be using on NAS.

But it may be used to confirm if it is a sata port issue or disk issue.

[manelppa]

Anyway, thanks so much for all your time you spent today. I will recreate the partitionning according a tuto on this topic (add new firmware on LaCie 2 BIG 2).

I would also request you (if you agree) to list all command we have used because I would like to recreate the new disk 2 (sdb) to check if it's a port problem or disk.
is it ok ?

[Jocko]

Yes you can

[manelppa]

Hello Jocko,
will you be available for checking what I have and what should I do ?
I've created a new disk II but not sure about the status with mdadm --examine sda or sdb. I've different values than yesterday...
Do you think I should go for a new box NAS 2BIG v2 ? I can see some few on internet

I THINK I FOUND ONE OF THE PROBLEM : when I type mdadm --examine /dev/sdb[25789], this is the left blue led of the disk that flashes to get the info....
If I do the same for the SDA disk, then this is the right blue led that flashes (left =disk 1, right = Disk2).
Is it normal ?


Kind regards,
Renaud F.

[Jocko]

Hi manelppa,

I think you should not take care of the LED behaviour as the standalone kernel version is not compiled to handle them rightly.

Anyhow we go to deepen this:
after booting the nas with the fvdw-sl console, post the outputs of

Code: Select all

dmesg
cat /proc/partitions
ls -l /dev/sd[ab][0-9]*
cat /sys/block/sda/device/model
cat /sys/block/sdb/device/model