NAS326 and NAS452 and ULTRASTAR drives!

gtdaniel · May 2023

Hello!

Is anybody that use WD ULTRASTAR drives on Zxyel NAS?

I have one pair of Western Digital Ultrastar DC HC520 12Tb HUH721212ALE604 0F30146

and i try to use it in my Zxyel NAS (both 326 and 542)…

My disk are identified ok but any attempt to create a volume ends

with nothing…

No error, just operation is canceled and no volume created…

Mijzelf · May 2023

The disk shouldn't matter, SATA is SATA. Having said that, the 512 bytes physical sector size seems unlikely to me for a 12TB disk.

Have you the possibility to test the disk outside the NAS?

gtdaniel · May 2023

Thanks for anwser!

Yes, those drives are manafactured in two variants with 512 and 4096 bytes/sector…

Outside of NAS i tested and is not detected by bios…

Maybe my PC is to old…

After a while appear at Disk Management with no volume and whan i try

to initialize via GPT ends with error: «I/O error» or «Incorect operation»

Disks was new, i open sealed package, and is very unliked both beeing damaged…

Seems more a problem with compatibility…

Mijzelf · May 2023

So you have 3 different systems (two different NASses and a PC) which all recognize the disks (OK, the PC is a bit slow on that) but fail to partitionize it. The PC spawns an I/O error. Maybe the NASses do that too, but unfortunately they don't show low level errors.

My first thought wouldn't be compatibility but defective disk(s). (SATA is SATA, and it's easy to kill a disk. Just drop it from 1 meter, or something like that).

Can you login on the NAS over ssh (enable it in TCP/IP settings), run dmesg to see the last timestamp, try to create a volume on that disk, and then run dmesg again. There might be new log line indicating the problem.

gtdaniel · May 2023

Hello!

I do that and is a lot of error mesages…

[ 533.072989] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 533.079474] ata4.00: irq_stat 0x40000000
[ 533.083411] ata4.00: failed command: READ DMA
[ 533.087799] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 533.087803] res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[ 533.102896] ata4.00: status: { DRDY ERR }
[ 533.106922] ata4.00: error: { ABRT }
[ 533.111053] ata4.00: configured for UDMA/133 (device error ignored)
[ 533.117382] ata4: EH complete
[ 533.120670] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 533.127144] ata4.00: irq_stat 0x40000000
[ 533.131079] ata4.00: failed command: READ DMA
[ 533.135459] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 533.135463] res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[ 533.150556] ata4.00: status: { DRDY ERR }
[ 533.154576] ata4.00: error: { ABRT }
[ 533.158709] ata4.00: configured for UDMA/133 (device error ignored)
[ 533.165018] ata4: EH complete
[ 533.168333] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 533.174793] ata4.00: irq_stat 0x40000000
[ 533.178746] ata4.00: failed command: READ DMA
[ 533.183126] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 533.183130] res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[ 533.198224] ata4.00: status: { DRDY ERR }
[ 533.202248] ata4.00: error: { ABRT }
[ 533.206393] ata4.00: configured for UDMA/133 (device error ignored)
[ 533.212714] ata4: EH complete
[ 533.216021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 533.222501] ata4.00: irq_stat 0x40000000
[ 533.226450] ata4.00: failed command: READ DMA
[ 533.230830] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 533.230834] res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[ 533.245934] ata4.00: status: { DRDY ERR }
[ 533.249960] ata4.00: error: { ABRT }
[ 533.254106] ata4.00: configured for UDMA/133 (device error ignored)
[ 533.260432] ata4: EH complete
[ 533.263723] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 533.270197] ata4.00: irq_stat 0x40000000
[ 533.274133] ata4.00: failed command: READ DMA
[ 533.278523] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 533.278527] res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[ 533.293622] ata4.00: status: { DRDY ERR }
[ 533.297647] ata4.00: error: { ABRT }
[ 533.301787] ata4.00: configured for UDMA/133 (device error ignored)
[ 533.308113] sd 3:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08
[ 533.314498] sd 3:0:0:0: [sdd] Sense Key : 0xb [current] [descriptor]
[ 533.321007] Descriptor sense data with sense descriptors (in hex):
[ 533.327217] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 533.333767] 00 00 00 00
[ 533.337060] sd 3:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
[ 533.341624] sd 3:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[ 533.348920] end_request: I/O error, dev sdd, sector 0
[ 533.354017] ata4: EH complete

Mijzelf · May 2023

[ 533.348920] end_request: I/O error, dev sdd, sector 0

So the NAS is also spawning an I/O error. You can ask the smart values of that disk:

su
smartctl -a /dev/sdd

gtdaniel · May 2023

Ok!

Return this…

~ # smartctl -a /dev/sdd
smartctl 6.3 2014-07-26 r3976 [armv7l-linux-3.2.54] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: HGST HUH721212ALE604
Serial Number: 5QK50V5B
LU WWN Device Id: 5 000cca 2b0ec8f89
Firmware Version: LEGNW9G0
User Capacity: 12,000,138,625,024 bytes [12.0 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA >3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Tue May 30 10:36:45 2023 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error aborted command

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error aborted command
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error aborted command

Read SMART Error Log failed: scsi error aborted command

Read SMART Self-test Log failed: scsi error aborted command

Selective Self-tests/Logging not supported

Mijzelf · May 2023

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error aborted command

Here should have been the table of SMART values. But it failed. So either the disk is dead, or it is seriously incompatible, which should not be possible, AFAIK. Does the other disk fail the same way?

gtdaniel · May 2023

Yes, both disks are the same simptoms…

I run some hdparm commands and i see this status at security…

how new disk are locked status?

even WD Dashboard on PC desktop indicate that both drives are Locked…

i read about this and seems a lot of ATA commands are not permited when drive is in locked state…

Mijzelf, thank you for your time!

Mijzelf · May 2023

Locked? Are you sure the disks are new? That should mean someone put a password on them.

gtdaniel · May 2023

Yes, i just buyed via a reseller, new, in sealed bag.

Myself i cut the plastic bag and put it in NAS.

Drives was packaged in buble foil individualy and next both again packaged in buble foil and put in carton corugated box…

I registered disks on WD and i have waranty of 5 years, expiring in 2028, so i am covered…

NAS326 and NAS452 and ULTRASTAR drives!

All Replies

Categories

Consumer Product Help Center