On Mon, Aug 2, 2010 at 1:21 AM, Tomas Lund <tlund@xxxxxx> wrote: > On Sun, 1 Aug 2010, Robert Hancock wrote: > >> The output above shows that the drive has security enabled and locked, so >> it seems that must be the case, and it won't be accessible unless it's >> unlocked. hdparm should be able to disable it, though it seems you may need >> a valid password to do it.. > > There is something I did not mention in any of my earlier posts, and that is > the fact that the server also has had a 3ware controller installed (removed > as part of fault isolation) and some of the disks has been attached to that > controller. In the case of the samsung 1tb disk, it was attached to the > 3ware conroller after it was successfully tested on the motherboard > sata-controller. > > Some googling and testing found that yes, the 3ware controller does indeed > lock the drives, even if they are just automatically exported as "JBOD". > > The following command successfully unlocked my devices: > > hdparm --user-master u --security-disable "3wareUserPassword " > /dev/sdb > > I have unlocked and tested a total of 4 disks now, both the samsung 1TB and > 3 of the WDC 2TB disks. Thank you very much! Left to do: test that > everything is working with the PMP aswell. Good to hear. > Question: Would it be unreasonable to request that the kernel would issue > the apropriate ATA-commands to a disk as soon as it is detected, and not try > to read from it if it is locked? It would have been really, really nice to > just get the error message "drive is locked". It should be possible to indicate that, yes. I'll look into it when I get a chance, if someone doesn't beat me to it.. -- 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
