On Fri, Mar 26, 2010 at 11:30 PM, Douglas Gilbert <dgilbert@xxxxxxxxxxxx> wrote: >> Booting into a minimal userspace environment (for example, with >> init=/bin/bash) might prove this. >> >> No doubt the reason the drive fails to respond is because it can't handle >> these commands and gets fatally confused. > > The ATA commands seem to be: > IDENTIFY DEVICE (via the ATA_12 tunnel) > SET FEATURES (via the ATA_16 tunnel) > IDENTIFY DEVICE (via the ATA_16 tunnel) > > The last one fails but that could be caused by > the second last one. Doesn't look like smartd. > My money would be on udev. Doug was right. I switched into runlevel 1 and connected the drive. Same errors as before. Then, I unplugged it, stopped the udev daemon and plugged it back in. Voila, I was able to manually mount the drive with no issues. Where do we go from here? Does anyone know how to debug udev? -Jonas -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
