-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/27/2015 6:03 PM, Nuno Magalhães wrote: > Since i've heard the problem could be the PSU, i did some research > and ended up (layman-ly) concluding that a 500W PSU is sufficient > for all 4 disks. Still, i wanted to try and enable PUIS on the WDs, > maybe it could work (the PSU isn't new, wouldn't be as stressed on > boot, etc). Yea, a power supply issue is extremely unlikely. Also if the PSU is overloaded, it simply shuts down. It is easy enough to verify the output voltage with a $10 radio shack multimeter. > As for the WDs... > > I went and tried hdparm -s1 --yes-i-know-what-i-am-doing Yes, WDs require a hardware jumper to enable PUiS, though doing so isn't going to help you; I mentioned it because when it already IS enabled, the results of the IDENTIFY_DEVICE command look like swiss cheese until the drive is forced to spin up by a specific command, that the kernel knows to issue on boot or resume. > [ 12.824479] ata4.00: failed to IDENTIFY (SPINUP failed, > err_mask=0x4) > > which i took as a good sign since i didn't want it spinning up. Well, you *do* want it spinning up of course, so you can access it. Looking at your dmesg, I noticed this: [ 1806.776781] ata2.00: ATA-9: WDC WD10EFRX-68PJCN0, 01.01A01, max UDMA/133 [ 1806.776785] ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 1806.784760] ata2.00: n_sectors mismatch 1953525168 != 268435455 [ 1806.784768] ata2.00: revalidation failed (errno=-19) [ 1806.784780] ata2: limiting SATA link speed to 1.5 Gbps [ 1806.784787] ata2.00: limiting speed to UDMA/133:PIO3 [ 1811.768094] ata2: hard resetting link [ 1811.768103] ata2: nv: skipping hardreset on occupied port [ 1812.236126] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) THIS appears to be your problem. It looks like the drive is changing its mind on its size, indicating some spectacularly broken firmware. I also notice that it fails to reset the link and lower the speed... is this controller set to IDE mode in the bios? If so you might have better luck in proper AHCI mode. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJUyOyiAAoJENRVrw2cjl5ROpUIAJ9eHjTUDhBhKjcBVQHIKhP9 hIi00ySdjy/+0ZcPak7FCb/iXVmBlxfDvlvRo2/XCjrdMgWn6z6NhoYtoO4zC8uT BoENSznq+jFfhk6eN2/uCWVRY4jwwd6VlpCIXOOl/dDoA+7QLRzIMB+vqzZ0WEmj qc6ucL1b7zP8Rj36tBQATV+K9sO4J6wqO0i3RiTnBe93h1hjsyFVn6Y0CnI5sQM/ VwzSILac4yQaFKgTCtJiSN5Zuaq8kDgaBCbloOiuu5TLiwvEduBoQE6NOVUl73bh tbErHPwrkA7jWjdMektfH9Tzja1tbTWxH1pCUmLQRvOM4IOxD2qKkWDJSkJFP2g= =uOZ9 -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
