Re: Vinum issue with USB CompactFlash reader.
On Friday, 28 December 2001 at 14:48:54 -0600, Jim Bryant wrote: I know this is probably a minor issue, as it is only an annoyance, and doesn't impact operation or performance, but still.. Ever since I concatenated some old drives to make a more reasonable capacity out of them, I have been noticing the following whenever vinum is loaded at startup [Note: The dmesg output doesn't show it, but before the check condition errors, vinum is loaded. Also this occurs when no CF card is present in the reader, seems to do well when booted with a card in place.]: Could vinum not be detecting that this is a removable media device? This has nothing to do with Vinum. The errors are at the device driver level, and they appear to relate only to the compact flash adaptor. Does it work when Vinum is not loaded? Was there in fact a CF card in the adaptor? Greg Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: HP C1533A 9608 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at ahc1 bus 0 target 0 lun 0 da0: COMPAQ ST15150W 6213 Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 15 lun 0 da1: COMPAQ ST15150W 6215 Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/ad0s1a cd1 at ahc0 bus 0 target 3 lun 0 cd1: TOSHIBA CD-ROM XM-6401TA 1009 Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 0 da3: eUSB Compact Flash \\0001 Removable Direct Access SCSI-2 device da3: 150KB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present cd2 at ahc0 bus 0 target 4 lun 0 cd2: NEC CD-ROM DRIVE:841 1.0 Removable CD-ROM SCSI-2 device cd2: 3.300MB/s transfers cd2: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: SEAGATE ST32550N 0022 Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: NEC CD-ROM DRIVE:466 1.06 Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum issue with USB CompactFlash reader.
On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote: On Friday, 28 December 2001 at 14:48:54 -0600, Jim Bryant wrote: I know this is probably a minor issue, as it is only an annoyance, and doesn't impact operation or performance, but still.. Ever since I concatenated some old drives to make a more reasonable capacity out of them, I have been noticing the following whenever vinum is loaded at startup [Note: The dmesg output doesn't show it, but before the check condition errors, vinum is loaded. Also this occurs when no CF card is present in the reader, seems to do well when booted with a card in place.]: Could vinum not be detecting that this is a removable media device? There are valid reasons to run vinum on removeable media so it should not exclude them. This has nothing to do with Vinum. The errors are at the device driver level, and they appear to relate only to the compact flash adaptor. Does it work when Vinum is not loaded? Was there in fact a CF card in the adaptor? vinums read_drive_label triggers this. It tries to read the label and produces the given errors if the drive is not ready - nothing wrong IMHO. I see the same messages for an MO drive if there is no media inserted. And I see these errors for a fixed drive with media errors. It is just unavoidable to have a single error for each drive and I don't know for shure why it happens several times - maybe vinum probes for multiple partitions. Greg Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: HP C1533A 9608 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at ahc1 bus 0 target 0 lun 0 da0: COMPAQ ST15150W 6213 Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 15 lun 0 da1: COMPAQ ST15150W 6215 Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/ad0s1a cd1 at ahc0 bus 0 target 3 lun 0 cd1: TOSHIBA CD-ROM XM-6401TA 1009 Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 0 da3: eUSB Compact Flash \\0001 Removable Direct Access SCSI-2 device da3: 150KB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present cd2 at ahc0 bus 0 target 4 lun 0 cd2: NEC CD-ROM DRIVE:841 1.0 Removable CD-ROM SCSI-2 device cd2: 3.300MB/s transfers cd2: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: SEAGATE ST32550N 0022 Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: NEC CD-ROM DRIVE:466 1.06 Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum issue with USB CompactFlash reader.
On Saturday, 29 December 2001 at 6:21:29 +0100, Bernd Walter wrote: On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote: This has nothing to do with Vinum. The errors are at the device driver level, and they appear to relate only to the compact flash adaptor. Does it work when Vinum is not loaded? Was there in fact a CF card in the adaptor? vinums read_drive_label triggers this. It tries to read the label and produces the given errors if the drive is not ready - nothing wrong IMHO. This would assume that Vinum was started after the adaptor was inserted. I see the same messages for an MO drive if there is no media inserted. And I see these errors for a fixed drive with media errors. It is just unavoidable to have a single error for each drive and I don't know for shure why it happens several times - maybe vinum probes for multiple partitions. Yes, Vinum probes for up to 35 partitions. First it tries each partition in each slice. If that doesn't work, it tries the compatibility slice. In each case, it ignores partition c. I suppose it would be possible to recognize conditions like medium not present and stop after the first attempt. But I can't see how to handle this without at least one error message. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum issue with USB CompactFlash reader.
On Sat, Dec 29, 2001 at 04:03:40PM +1030, Greg Lehey wrote: On Saturday, 29 December 2001 at 6:21:29 +0100, Bernd Walter wrote: On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote: This has nothing to do with Vinum. The errors are at the device driver level, and they appear to relate only to the compact flash adaptor. Does it work when Vinum is not loaded? Was there in fact a CF card in the adaptor? vinums read_drive_label triggers this. It tries to read the label and produces the given errors if the drive is not ready - nothing wrong IMHO. This would assume that Vinum was started after the adaptor was inserted. You can see from the bootlog that the adapter was probed and detected during booting - it was even printed before some scsi harddisks. I see the same messages for an MO drive if there is no media inserted. And I see these errors for a fixed drive with media errors. It is just unavoidable to have a single error for each drive and I don't know for shure why it happens several times - maybe vinum probes for multiple partitions. Yes, Vinum probes for up to 35 partitions. First it tries each partition in each slice. If that doesn't work, it tries the compatibility slice. In each case, it ignores partition c. I suppose it would be possible to recognize conditions like medium not present and stop after the first attempt. But I can't see how to handle this without at least one error message. I'm not shure that you see this error inside vinum. From what I understood it's that reading the disklabel failed and vinum might only get ENXIO. I don't know the disklabel code but maybe there is something possible to have one call and get all available partitions. Nevertheless the errors are just telling why this drive was not succesfully scanned and have a valid reason to be there. You can alway tell vinum which partitions to probe. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
