rvassar
Guru
- Joined
- May 2, 2018
- Messages
- 972
I picked up a Seagate Ironwolf 4Tb ST4000VN008, hoping to rotate the last HGST 2Tb drive (45k hours!) out of my archive pool. I was going to try doing burn-in in a hotswap enclosure on my NAS, but when I insert it, it fails to train in. The console emits:
So I pulled it and put it in a USB 3.0 enclosure and attached it to a Linux machine, and promptly ended up in Seagate ATA / USB passthru purgatory. I can't seem to even label the drive with a partition table. Gparted fails completely. I can however, run "dd if=/dev/zero of=/dev/sdX bs=1M count=1024" against the raw device, and the drive behaves like it's writing data. Running "badblocks -e 1 -v -o -s -w /dev/sdX" however blows up immediately.
On Edit: Forgot to add... It refuses to run a SMART test in the USB enclosure. I do not usually have problems with this USB enclosure, but I also haven't bought a Seagate drive in 15+ years...
I wanted to see if anyone here had any advice, or should I just RMA it immediately.
Code:
(aprobe0:ahcich3:0:0:0): SETFEATURES SET TRANSFER MODE. ACB: ef 03 00 00 00 40 00 00 00 00 46 00 (aprobe0:ahcich3:0:0:0): CAM status: ATA Status Error (aprobe0:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ahcich3:0:0:0): RES: 51 04 00 00 00 40 00 00 00 46 00 (aprobe0:ahcich3:0:0:0): Retrying command (aprobe0:ahcich3:0:0:0): SETFEATURES SET TRANSFER MODE. ACB: ef 03 00 00 00 40 00 00 00 00 46 00 (aprobe0:ahcich3:0:0:0): CAM status: ATA Status Error (aprobe0:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ahcich3:0:0:0): RES: 51 04 00 00 00 40 00 00 00 46 00 (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted
So I pulled it and put it in a USB 3.0 enclosure and attached it to a Linux machine, and promptly ended up in Seagate ATA / USB passthru purgatory. I can't seem to even label the drive with a partition table. Gparted fails completely. I can however, run "dd if=/dev/zero of=/dev/sdX bs=1M count=1024" against the raw device, and the drive behaves like it's writing data. Running "badblocks -e 1 -v -o -s -w /dev/sdX" however blows up immediately.
On Edit: Forgot to add... It refuses to run a SMART test in the USB enclosure. I do not usually have problems with this USB enclosure, but I also haven't bought a Seagate drive in 15+ years...
I wanted to see if anyone here had any advice, or should I just RMA it immediately.
Last edited: