New hard drive problem - GoFlex

[sweetthdevil]

Hello all,

As mentioned in another topic, my previous 2tb hard drive failed. So I ordered a new 2tb hard drive (see link below)

Once received I booted my goflex using a USB key - from made following that topic http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3312&p=19207#p19207 I used that same USB key in the past to sort few error, booting the goflex without the hard drive plugged in and when the light is green I plugged it in.

But now the hard drive doesn't show up once connected through SSH.

See dmesg result below.

Any advice?

$this->bbcode_second_pass_code('', '[ 23.611164] systemd[1]: Started Create Static Device Nodes in /dev.
[ 23.801740] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 23.830019] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[ 23.862263] ata1: SError: { PHYRdyChg DevExch }
[ 23.874221] systemd[1]: Starting udev Kernel Device Manager...
[ 23.890667] ata1: hard resetting link
[ 23.932268] systemd[1]: Reached target Local File Systems (Pre).
[ 23.972379] systemd[1]: Reached target Local File Systems.
[ 24.016525] systemd[1]: Starting Rebuild Journal Catalog...
[ 24.217566] systemd[1]: Started udev Kernel Device Manager.
[ 24.314527] systemd[1]: Started Rebuild Journal Catalog.
[ 24.601416] systemd[1]: Started Journal Service.
[ 24.864668] systemd-journald[100]: Received request to flush runtime journal from PID 1
[ 29.851933] ata1: link is slow to respond, please be patient (ready=0)
[ 33.931964] ata1: SRST failed (errno=-16)
[ 33.936009] ata1: hard resetting link
[ 39.881952] ata1: link is slow to respond, please be patient (ready=0)
[ 41.032434] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 43.254489] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 43.264435] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 43.961936] ata1: SRST failed (errno=-16)
[ 43.965972] ata1: hard resetting link
[ 49.911937] ata1: link is slow to respond, please be patient (ready=0)
[ 79.011933] ata1: SRST failed (errno=-16)
[ 79.015977] ata1: limiting SATA link speed to 1.5 Gbps
[ 79.021135] ata1: hard resetting link
[ 84.071899] ata1: SRST failed (errno=-16)
[ 84.075961] ata1: reset failed, giving up
[ 84.080004] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen t4
[ 84.089526] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00190002
[ 84.097144] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[ 84.103060] ata1: hard resetting link
[ 90.051753] ata1: link is slow to respond, please be patient (ready=0)
[ 94.141515] ata1: SRST failed (errno=-16)
[ 94.145552] ata1: hard resetting link
[ 100.091097] ata1: link is slow to respond, please be patient (ready=0)
[ 104.170742] ata1: SRST failed (errno=-16)
[ 104.174781] ata1: hard resetting link
[ 110.120143] ata1: link is slow to respond, please be patient (ready=0)
[ 139.215757] ata1: SRST failed (errno=-16)
[ 139.219799] ata1: limiting SATA link speed to 1.5 Gbps
[ 139.224956] ata1: hard resetting link
[ 144.274737] ata1: SRST failed (errno=-16)
[ 144.278795] ata1: reset failed, giving up
[ 144.282840] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen t3
[ 144.292343] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00190002
[ 144.299756] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[ 144.305716] ata1: hard resetting link
[ 150.253445] ata1: link is slow to respond, please be patient (ready=0)
[ 154.332513] ata1: SRST failed (errno=-16)
[ 154.336554] ata1: hard resetting link
[ 160.281041] ata1: link is slow to respond, please be patient (ready=0)
[ 164.359969] ata1: SRST failed (errno=-16)
[ 164.364006] ata1: hard resetting link
[ 170.308302] ata1: link is slow to respond, please be patient (ready=0)
[ 199.408234] ata1: SRST failed (errno=-16)
[ 199.412277] ata1: limiting SATA link speed to 1.5 Gbps
[ 199.417442] ata1: hard resetting link
[ 204.466120] ata1: SRST failed (errno=-16)
[ 204.470184] ata1: reset failed, giving up
[ 204.474227] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen t2
[ 204.484630] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00190002
[ 204.492037] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[ 204.497976] ata1: hard resetting link
[ 210.443549] ata1: link is slow to respond, please be patient (ready=0)
[ 214.521707] ata1: SRST failed (errno=-16)
[ 214.525744] ata1: hard resetting link
[ 220.468905] ata1: link is slow to respond, please be patient (ready=0)
[ 224.546927] ata1: SRST failed (errno=-16)
[ 224.550963] ata1: hard resetting link
[ 230.493940] ata1: link is slow to respond, please be patient (ready=0)
[ 259.577804] ata1: SRST failed (errno=-16)
[ 259.581846] ata1: limiting SATA link speed to 1.5 Gbps
[ 259.587003] ata1: hard resetting link
[ 264.634929] ata1: SRST failed (errno=-16)
[ 264.638986] ata1: reset failed, giving up
[ 264.643029] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen t1
[ 264.652486] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00190002
[ 264.660007] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[ 264.665969] ata1: hard resetting link
[ 270.611601] ata1: link is slow to respond, please be patient (ready=0)
[ 274.689364] ata1: SRST failed (errno=-16)
[ 274.693404] ata1: hard resetting link
[ 280.636149] ata1: link is slow to respond, please be patient (ready=0)
[ 284.713970] ata1: SRST failed (errno=-16)
[ 284.718012] ata1: hard resetting link
[ 290.660804] ata1: link is slow to respond, please be patient (ready=0)
[ 319.546188] EXT4-fs (sda1): error count since last fsck: 37
[ 319.551795] EXT4-fs (sda1): initial error at time 1438507937: ext4_iget:4053: inode 640
[ 319.559848] EXT4-fs (sda1): last error at time 1439922203: ext4_iget:4077: inode 639
[ 319.756104] ata1: SRST failed (errno=-16)
[ 319.760143] ata1: limiting SATA link speed to 1.5 Gbps
[ 319.765301] ata1: hard resetting link
[ 324.813747] ata1: SRST failed (errno=-16)
[ 324.817808] ata1: reset failed, giving up
[ 324.821841] ata1: EH pending after 5 tries, giving up
[ 324.827225] ata1: EH complete
')

http://www.scan.co.uk/products/2tb-wd-wd20ezrx-green-35-hdd-sata-iii-6gb-s-intellipower-64mb-cache-8ms-oem

[sweetthdevil]

Still no luck,

Tried to monitor udev activity but nothing when I plugged in it.

$this->bbcode_second_pass_code('', '$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent')

It seems that the hard drive doesn't like hot plugging, it works well while plugged on my desktop.

Is there a way to start the GoFlex from the usb key with the hard drive attached?

[sweetthdevil]

A quick question, will sound stupid for sure but just want to be sure.

I had Arch ARM working in the past on the goflex so uboot was installed, if I installed the files nessesary on the drive from my desktop will it boot? Or does uboot works with the hard drive UUID?

[WarheadsSE]

viewtopic.php?f=18&t=3312&p=19207#p19207

[sweetthdevil]

Thank you for your reply, however I already follow that topic to create a bootable usb key.

BUT the new hard drive doesn't show up, so can NOT be mounted to follow the procedure.

To answer my own question, installing the Arch ARM files on the partition and boot the goflex doesn't work.

Any other suggestion?

*Edit* Was searching the forum and came across this topic viewtopic.php?f=55&t=2146#p11512
Will this work in my case? There is no mentioned of goflex in the topic?

[WarheadsSE]

You don't have an oxnas, so no.

If you have this bootable USB key, you can use that to debug why the HDD is not coming up. Since that is the root cause of the problem.

[sweetthdevil]

Ok, but I spend several hours trying to and searching the web so have you got some direction?

That would be greatly appreciated.

Many them

[WarheadsSE]

Have you tried that drive on any other machines? This thing really does not like the GoFlex

[sweetthdevil]

Yes. I plugged the drive on my desktop several times to partitioned it (using archlinux desktop, or windows 8.1)

According to Seagate website, the drive is compatible with Home NAS.

I tried to debug from the USB key, restarting systemctl services, and all the above mentioned also... I am by no mean an linux expert but I have been using it for 15 years on my desktop - but I can't figure out what's wrong there!

[moonman]

I have WD30EZRX which is a 3TB equivalent of yours and it works in the GFH. (By the way I would recommend disabling automatic head parking on this drive before it dies prematurely if it is a system drive).

Try a different known-good drive in the GFH to exclude GFH from being faulty itself.