Hello, Sorry about the late reply. On Tue, Jul 15, 2014 at 12:24:21AM +0100, Nuno Magalhães wrote: > > Can you please try the followings? > > This doesn't happen every-time i boot, only sometimes (about 50/50). > Once i booted and the disk was disabled, i created dmesg1.nodisk > > > 1. After boot is complete, re-trigger device attach by doing > > > > echo - - - > /sys/class/scsi_host/hostN/scan > > Partial dmesg2.reset (i just wanted to see what this output to dmesg, > i didn't reboot) Does this always work? ie. can you do it repeatedly and the device is always detected correctly? Or, if you issue rescanning after the device fails detection during boot, does it always work? > > 2. Boot with libata.force=dump_id and report full dmesg after boot. > > dmesg3.dump_id > > > 3. Boot with libata.force=nohrst and see whether anything changes. > > dmesg4.nohrst > > > Thanks. > > Thank you for your time. > > Both dump_id and nohrst detected the drive the first time i used them. > Should i keep trying one or the other until the disk is dropped again > (or not)? Should i specify both boot options simultaneously? dump_id shouldn't affect anything but should give us more data about the failure. Can you please try to reproduce the problem with dump_id specified? nohrst may make the problem go away. Can you please try to reproduce the issue with the parameter specified. Thanks. -- tejun -- 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
