search for: da0

...sks during install or the kernel would fail to re-mount the root disk after booting into the new OS. If I used the default layout, or the partition GUI at all (ie; 'manual mode') the new OS wouldn't remount root on boot. I could manually specify the proper root device ie; ufs:/dev/da0p3 and continue booting without issue, so this is an installer thing. I'm sure I could have fixed this in /boot/loader.conf or similar but wanted to try to figure out what was breaking (now I know its something the installer is doing since it doesn't happen when I do it manually). So...

...activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. SMP: AP CPU #1 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: <PLEXTOR DVDR PX-740A 1.01> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at umass-sim0 bus 0 target 0 lun 0 da0: <USB2.0 CF CardReader 9144> Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 1 da1: <USB2.0 CBO CardReader 9144> Removabl...

hail, I partitioned the disk this way: fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=12161 heads=255 sect...

Have the following problems: MBO USB-MultiCardREader 6-in-1 does not read 128MB CF-Card. Oct 3 13:49:23 katrin /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Oct 3 13:49:23 katrin /kernel: da0: <ICSI IC1100 CF 2.5B> Removable Direct Access SCSI-0 device Oct 3 13:49:23 katrin /kernel: da0: 650KB/s transfers Oct 3 13:49:23 katrin /kernel: da0: Attempt to query device size failed: NOT READY, Medium not pre...

...usbus3 umass1: SCSI over Bulk-Only; quirks = 0x0000 umass1:7:1:-1: Attached to scbus7 cd1 at umass-sim0 bus 0 scbus6 target 0 lun 0 cd1: <HUAWEI Mass Storage 2.31> Removable CD-ROM SCSI-2 device cd1: 1.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present da0 at umass-sim1 bus 1 scbus7 target 0 lun 0 da0: <HUAWEI SD Storage 2.31> Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present o Time Elapses....many packets passed, no da0 or cd1 used. o USB Modem d...

...lt;EHCI (generic) USB 2.0 controller> on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered When I plug my digital camera in, I get this report: umass0: HEWLETT-PACKARD HP PhotoSmart R607, rev 2.00/0.01, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: <HP PhotoSmart R607 A001> Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 24MB (50305 512 byte sectors: 64H 32S/T 24C) Looking at the transfer speed, it only registers as USB 1 device, right? On Windows XP (on different machine)...

...powered port 3 powered port 4 powered port 5 addr 2: high speed, power 250 mA, config 1, Mass Storage Device(0x6362), Generic(0x058f), rev 1.27, device umass0 port 6 powered port 7 powered port 8 powered %camcontrol devlist <QUANTUM ATLAS_V_18_WLS 0230> at scbus1 target 0 lun 0 (da0,pass0) <QUANTUM ATLAS10K3_18_WLS 020W> at scbus1 target 2 lun 0 (da1,pass1) <Generic USB SD Reader 1.00> at scbus2 target 0 lun 0 (da2,pass2) <Generic USB CF Reader 1.01> at scbus2 target 0 lun 1 (da3,pass3) <Generic USB SM Reader 1.02> at scbus2 target...

...ternally on channel 2. During boot, I can see all disks being identified first by the machine itself and then in the early part of the process (something scrolls by talking about BIOS drive numbering). However, the result is not 8 drives but 5 in total in a mix between the channels, see below. da0 at sym0 bus 0 target 0 lun 0 da0: <COMPAQ AB00931B92 3AS8> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da4 at sym1 bus 0 target 4 lun 0 da4: <COMPAQ MAB3091SC 0...

...imed-out.Resetting controller Mar 11 13:06:12 web kernel: mpt0: soft reset failed: ack timeout Mar 11 13:06:12 web kernel: mpt0: WARNING - Failed hard reset! Trying to initialize anyway. Mar 11 13:06:12 web kernel: mpt0: Unhandled Event Notify Frame. Event 0xc086250d. Mar 11 13:06:12 web kernel: (da0:mpt0:0:0:0): WRITE(10). CDB: 2a 0 0 85 95 8f 0 0 20 0 Mar 11 13:06:12 web kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Mar 11 13:06:12 web kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Mar 11 13:06:12 web kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Mar 11 13:06:12 web ker...

...de_id = 0x8000ffc0, non CYCLEMASTER mode Apr 26 09:22:51 chowder /kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) Apr 26 09:22:51 chowder /kernel: firewire0: New S400 device ID:00048302e200995f Apr 26 09:22:51 chowder /kernel: firewire0: Device SBP-II Apr 26 09:22:51 chowder /kernel: da0 at sbp0 bus 0 target 0 lun 0 Apr 26 09:22:51 chowder /kernel: da0: <Oxford 911D 0037> Fixed Simplified Direct Access SCSI-4 device Apr 26 09:22:51 chowder /kernel: da0: 50.000MB/s transfers Apr 26 09:22:51 chowder /kernel: da0: 190734MB (390625000 512 byte sectors: 255H 63S/T 24315C) Would t...

...a cheapo memory stick, simply plugging it in and taking it out a couple of times is a guaranteed panic. I use only one USB device, a cheapo USB memory stick, which I recently bought on a whim. When things work, it identifies as: umass0: IMGSYS-3 Security X-Disk V1.02 , rev 1.10/2.01, addr 3 da0 at umass-sim0 bus 0 target 0 lun 0 da0: <GENERIC USB FLASH DISK 0201> Removable Direct Access SCSI-0 device da0: 650KB/s transfers da0: 15MB (32000 512 byte sectors: 64H 32S/T 15C) I tried it on a 4.7 machine and although it probes and attaches OK, it can't be read (returns EIO) and the...

...:umass-sim0:0:0:0): SCSI status: Check Condition Jul 4 14:40:27 twinhead kernel: (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) Jul 4 14:40:27 twinhead kernel: (probe0:umass-sim0:0:0:0): Error 22, Unretryable error Jul 4 14:40:27 twinhead kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 Jul 4 14:40:27 twinhead kernel: da0: <Hitachi HTS542520K9SA00 BBDO> Fixed Direct Access SCSI-5 device Jul 4 14:40:27 twinhead kernel: da0: 400.000MB/s transfers Jul 4 14:40:27 twinhead kernel: da0: 190782MB (390721968 512 byte sectors: 255H 63S/T...

Hi all, I would like to knwon if with ZFS it''s possible to do something like that : http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html meaning : I have a zpool with 48 disks with 4 raidz2 (12 disk). Inside those 48 disk I''ve 36x 3T and 12 x 2T. Can I buy new 12x4 To disk put in the server, add in the zpool, ask zpool to migrate all data on those 12 old disk on the new and

...controller> on uhci1 Aug 5 12:53:58 goshik /kernel: usb1: USB revision 1.0 Aug 5 12:53:58 goshik /kernel: uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Aug 5 12:53:58 goshik /kernel: uhub2: 2 ports with 2 removable, self powered [...] Aug 5 12:53:58 goshik /kernel: Creating DISK da0 Aug 5 12:53:58 goshik /kernel: pass0 at umass-sim0 bus 0 target 0 lun 0 Aug 5 12:53:58 goshik /kernel: pass0: <A-DATA Flash 2.0 P1.0> Removable Direct Access SCSI-0 device Aug 5 12:53:58 goshik /kernel: pass0: Serial Number Aug 5 12:53:58 goshik /kernel: pass0: 650KB/s transfers Aug 5 1...

...pi0: <Parallel I/O> on ppbus0 ad0: 58644MB <Maxtor 6Y060L0> [119150/16/63] at ata0-master UDMA133 acd0: DVD-ROM <DV-516E> at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a uscanner0: EPSON EPSON Scanner, rev 1.10/1.00, addr 2 umass0: ICSI IC1100 V2.5B, rev 1.10/2.5b, addr 3 da0 at umass-sim0 bus 0 target 0 lun 0 da0: <ICSI IC1100 CF 2.5B> Removable Direct Access SCSI-0 device da0: 650KB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NO...

Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic way to recover the data? Most of the data is mirrored over da0 & da1, but I...

...activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. SMP: AP CPU #1 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: <PLEXTOR DVDR PX-740A 1.01> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at umass-sim0 bus 0 target 0 lun 0 da0: <USB2.0 CF CardReader 9144> Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 1 da1: <USB2.0 CBO CardReader 9144> Removabl...

If you have any of the devices listed below, please test with a recent -stable or -current. They will stop working in 4.9 and 5.2 although old behavior can _temporarily_ be enabled by adding "options DA_OLD_QUIRKS" to your kernel config. If I don't hear from anyone, they'll be going away permanently after the releases. -Nate #ifdef DA_OLD_QUIRKS /* Below a list of

...or that chipset (c60X) was recently added via the isci driver. Ok, great, that explains why 8.2-R and 9.0-R didn't see the drives. So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, booted it up, and sure enough, as the dmesg scrolls I see it now properly recognizes da0 and da1, as it should (the memstick is da2). It sees the disks fine at this point, everything looks good. However, once the system finishes booting and loads into sysinstall, and I go to partition the drives, I get "No disks found! Please verify that your disk controller is being properly...

...ec usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: <Intel> at usbus0 uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0 ugen1.1: <Intel> at usbus1 uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 ada0 at ahcich0 bus 0 scbus1 target 0 lun 0 ada0: <INTEL SSDSA2CT040G3 4PC10362> ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at a...