Is there a reason *two* hard drives that were detected/working in my system (Windows 11) might not be detected in someone else's system?
I've sold two and the buyer is having problems detecting them, any advice for us both please? (shipping materials were 100& foam, no moment, arrived in perfect condition physically etc).
I believe he is having problems detecting them in his Lynx/unraid system. Possibly because I was using them in my windows 11 pc?
I don't think he'll mind me posting this technical snippit of our conversation;
"I will try the drives again in the Unraid system tomorrow and capture the specific error reported in the syslog, but as noted, the drives are not detected/initialised correctly. It seems Gen8 micro server at least completes booting for these errors to be displayed in the linux syslog, but I have not been able to boot another system with them attached as they hang trying to initialise the drives.
I cannot get to "disk management" in order to do anything."
I'll troubleshoot with him some more tomorrow.
I'd have thought if his pc boots correctly without them, it wouldn't try to boot from additional drives.
@Armageus No brand new drives, not shucked (well 2 months old, used perfectly in my pc (lightly). Seagate Exos X16 16TB SATA Hard Drive ST16000NM001G.
What's strange is they are the exact same drives he had no issue with last time. Only difference is these ones came from my Windows 11 pc rather than my Unraid Server (same retailer as well).
As the buyer I will add some further information from repeated testing this morning.
The drives appear DOA and are not detected/initalised during boot, Hostile and I seem to be on different lines here as to me the drives are dud, but Hostile's view is that there is something software based
The machines I am attempting to get signs of life with are:
HP Gen 8 microserver (the same that worked fine with the previous 2 drives from Hostile)
HP Gen 7 microserver
Z690 Tomahawk DDR4
B760i Gigabyte Aorus
All for all, the drives are being switched out with existing fully functional drives, and when reverting there are no issues with the existing previous drive. For the microservers I have tried different bays to the same result - these drives in any bay fail to be detected, while any other drive in any bay works fine. So I can't see a cabling issue.
I have tested further this morning, and the behaviour is the same, not detected in the BIOS and then within an OS, subsequently not detected correctly. The 2x more modern Z690/B760i sytems will boot eventually if I am patient, but same issue ultimately.
Code:
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: link online but 1 devices misclassified, retrying
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: link online but 1 devices misclassified, retrying
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: softreset failed (1st FIS failed)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: limiting SATA link speed to 1.5 Gbps
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 16 08:23:07 s-hpms7-unraid kernel: ata1: link online but 1 devices misclassified, device detection might fail
Code:
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: softreset failed (device not ready)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: softreset failed (device not ready)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: softreset failed (1st FIS failed)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: limiting SATA link speed to 3.0 Gbps
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: found unknown device (class 0)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: softreset failed (device not ready)
Jan 16 08:45:15 s-hpms8-unraid kernel: ata1: reset failed, giving up
Within windows (the Z690 machine) something is detected in Disk Management as the dialogue regarding initialising disk appears. Selecting either GPT or MBR as the partition scheme gives the same error "Virtual Disk Manager - A device which does not exist was specified". No sign of the disk drive in Device Manager, in detected or a failed state. Right clicking properties on the drive which appears to need initialising gives details of the previous device in Disk Management.
The drives are not detected correctly at boot, which means they are not detected correctly within an OS, so I can only conclude they are DOA and failed at some point since they worked for Hostile.
I am more than open to ideas on how to get them functioning, but my experience of this kind of behaviour is on DOA drives. @Hostile_18, unless there are ideas which get them working, I will send them back to you tomorrow to pursue a warranty claim as agreed during the sale, or determine a resolution you consider reasonable.
It's incredibly unlikely both items that were working for me the day before, that arrived perfect condition would arrive DOA at the same time. I'd be willing to test and if working send them back at your cost or sell elsewhere and give money to you. If truly dead and knowing 100% I sent working hard drives then I'd chance the retailers warranty for you, but make no claims if they deny it. Any costs with sending them back to retails (abroad) would have to be covered by you.
I appreciate this is a tough situation but I 100% stand by that I sent you working hard drives as I did before and to many other people. The packaging couldn't of been any better ans as you say yourself they were immaculate. I can't be held responsible for installation damage. Sorry.
It is generally considered sensible not to buy quantities of hard drives together, due to the increased chance of multiple failures within the same batch. It isn't beyond the realms of possibility, clearly I didn't follow the same guidance.
I don't think this is really a topic for the general forums now. Given the withdrawal of any support in resolving the situation, and your clear view of zero shared responsibility of the seller, I will decide separately whether to throw good money after bad in returning them to you.
It is generally considered sensible not to buy quantities of hard drives together, due to the increased chance of multiple failures within the same batch. It isn't beyond the realms of possibility, clearly I didn't follow the same guidance.
I don't think this is really a topic for the general forums now. Given the withdrawal of any support in resolving the situation, and your clear view of zero shared responsibility of the seller, I will decide separately whether to throw good money after bad in returning them to you.
It's just beyond the odds of any kind of probability sorry. I am still 99% positive if it's not installation error it's a software issue. Please keep trying that avenue of investigation and hopefully everyone party will be happy.
Thanks everyone. I got the hard drives back, they do have confirmed serious errors now (for whatever reason, its impossible to identify, condition is immaculate). They are been sent back to the retail for warranty.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
