Thomas Klausner <tk%giga.or.at@localhost> writes: > When I plug in a new disk I bought recently, I get: > > umass1 at uhub4 port 8 configuration 1 interface 0 > umass1: Samsung D3 Station, rev 2.10/2.02, addr 5 > umass1: using SCSI over Bulk-Only > scsibus1 at umass1: 2 targets, 1 lun per target > inquire: addlen=71, not retrying > sd5 at scsibus1 target 0 lun 0: <Samsung, D3 Station, 0202> disk fixed > sd5(umass1:0:0:0): Check Condition on CDB: 0x00 00 00 00 00 00 > SENSE KEY: Not Ready > ASC/ASCQ: Logical Unit Is in Process Of Becoming Ready > > sd5: drive offline > sd5: unable to open device, error = 5 > sd5: fabricating a geometry > > but then I get no further devices. > > I was able to add a GPT table, and "gpt list /dev/sd5" works, so I can > manually create wedges using dkctl. It'd be nicer if it was done > automatically, like usual, though... I wonder if the disk is returning a "Not Ready" to some operation, which should be interpreted as "wait a few seconds and try again" rather than erroring out. You could try putting in a wait loop to retry every 1s for 30s, or something like that. I wonder if this disk returns this until it's fully spun up, rather than just haing the first operation that actually needs it spun up take a long time.
Attachment:
pgptJi53yK6Ia.pgp
Description: PGP signature