Re: ATA - Trouble mounting secondary master
In message <[EMAIL PROTECTED]>, Mike Smith writes: >> So I still stick with my statement that the -current bootblocks/loader >> doesn't have the computrons needed to use the ad device (or any non >> wd/da/fd device for that matter) for anything usefull :) > >The loader is fine; the problem is just that Poul never finished fixing >the mountroot code. All the loader does is read /etc/fstab and pass in >the entry for /. It's up to the kernel to work it out from there, and >that's where it's falling down. Excuse me! I fixed boot -a, and you came rushing in and said that the boot code could use the same thing, so obviously I expected you to do that, since the boot code is your baby... I don't even know where to look for the cookies left by the bootcode... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
> So I still stick with my statement that the -current bootblocks/loader > doesn't have the computrons needed to use the ad device (or any non > wd/da/fd device for that matter) for anything usefull :) The loader is fine; the problem is just that Poul never finished fixing the mountroot code. All the loader does is read /etc/fstab and pass in the entry for /. It's up to the kernel to work it out from there, and that's where it's falling down. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
It seems Mike Smith wrote: > > Our boot blocks/loader dont have the needed computrons to use the > > "ad" device name. However I have some patches to boot2 that allows > > to boot off an ad root device, provided you dont use the loader, and > > put the rigth boot string in boot.config. > > This should now be totally redundant as long as your /etc/fstab entry > is correct. Define "correct" then please, it doesn't work for my definition... -Current as of aug 21th... If I have this in my fstab: /dev/ad0a / ufs rw 1 1 /dev/ad0f /usrufs rw 2 2 /dev/ad0e /varufs rw 2 2 And have NO wd* entries in /dev, it says on boot: Changing root device to wd0s1a Changing root device to wd0a ... mount: /dev/ad0a on / special device does not match mounted device. Bummer! If however I have a /dev/wd0a it will mount that and show that in a mount/df command, but then it doesn't fit what it is written in /etc/fstab and that is bogus too... So I still stick with my statement that the -current bootblocks/loader doesn't have the computrons needed to use the ad device (or any non wd/da/fd device for that matter) for anything usefull :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
> It seems Geoff Rehmet wrote: > > Hmm, > > > > My root device still lands up on "wd0" - even though my fstab has > > the root filesystem on ad0s1a. I haven't looked at getting it to > > use the ad dev entries for the root file system. (I'm assuming that > > is still WIP.) > > Our boot blocks/loader dont have the needed computrons to use the > "ad" device name. However I have some patches to boot2 that allows > to boot off an ad root device, provided you dont use the loader, and > put the rigth boot string in boot.config. This should now be totally redundant as long as your /etc/fstab entry is correct. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA - Trouble mounting secondary master
I just rebooted on an August 11 kernel. My system still is happy with the disks. Hmm. I can't remember exactly where my tracing went, before I left off before, but the message you are seeing comes from /sys/i386/isa/diskslice_machdep.c, line 200 (version 1.35). What you will probably find, is that if you put a line that goes: goto reread_mbr instead of "goto done", you will find that, on the second attempt, it reads the mbr successfully. The above is a severe kludge, and that is why I never committed any code to do anything of the sort. I think the error is actually somewhere in the ATA code (sorry Soren). I don't want to patch around a bug. Now somebody remarked that after the probe, a drive status light stayed on - maybe, the probe is not doing something properly for some drives, or there is somethign timing out. > -Original Message- > From: Kevin Street [mailto:[EMAIL PROTECTED]] > Sent: 12 August 1999 03:10 > To: Soren Schmidt > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: ATA - Trouble mounting secondary master > > > Kevin Street <[EMAIL PROTECTED]> writes: > > Soren Schmidt <[EMAIL PROTECTED]> writes: > > > > Hmm, damn, after the problem went away for Geoff I > thought it to be > > > solved since I've never heard of it anywhere else, and I > cant reproduce > > > it here no matter what I try. > > > Does it help eany if you only has the root partition use > the wd dev > > > and have the rest use the prober ad dev entries ?? It > could be some > > > artifact from this... > > > > I tried with the ad dev entries for my problem as well with no > > improvement. I've also tried using: > > dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 > > as the first access to one of the failing drives (ad0). > > The first dd fails with device not configured, but any subsequent > > access works fine. It seems it's left in an odd state by the driver > > start up, but all it takes is a read to get it sorted out again. > > More on this. > I just booted with -v and now when I do the first dd I see: > ad0: invalid primary partition table: no magic > and the same on ad2 when the swapon fails. > > So how do I get the magic back into my relationship with my drives? > > -- > Kevin Street > [EMAIL PROTECTED] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
Kevin Street <[EMAIL PROTECTED]> writes: > Soren Schmidt <[EMAIL PROTECTED]> writes: > > Hmm, damn, after the problem went away for Geoff I thought it to be > > solved since I've never heard of it anywhere else, and I cant reproduce > > it here no matter what I try. > > Does it help eany if you only has the root partition use the wd dev > > and have the rest use the prober ad dev entries ?? It could be some > > artifact from this... > > I tried with the ad dev entries for my problem as well with no > improvement. I've also tried using: > dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 > as the first access to one of the failing drives (ad0). > The first dd fails with device not configured, but any subsequent > access works fine. It seems it's left in an odd state by the driver > start up, but all it takes is a read to get it sorted out again. More on this. I just booted with -v and now when I do the first dd I see: ad0: invalid primary partition table: no magic and the same on ad2 when the swapon fails. So how do I get the magic back into my relationship with my drives? -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
Soren Schmidt <[EMAIL PROTECTED]> writes: > It seems Geoff Rehmet wrote: > > Brian McGroarty writes : > > > In using the ATA driver, I'm unable to automatically mount a > > > partition on a master drive on the secondary controller. fsck > > > complains that device rwd2s1e isn't configured and exists. > > > Immediately mounting by hand works perfectly. > > I had exactly the same problem, although it manifested itself with a > > secondary master or slave. It went away a few weeks ago, and I > > was never able to make any sensible progress in tracking the problem > > down. > > Hmm, damn, after the problem went away for Geoff I thought it to be > solved since I've never heard of it anywhere else, and I cant reproduce > it here no matter what I try. > Does it help eany if you only has the root partition use the wd dev > and have the rest use the prober ad dev entries ?? It could be some > artifact from this... I tried with the ad dev entries for my problem as well with no improvement. I've also tried using: dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 as the first access to one of the failing drives (ad0). The first dd fails with device not configured, but any subsequent access works fine. It seems it's left in an odd state by the driver start up, but all it takes is a read to get it sorted out again. Any thoughts on how we can help debug this? -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA - Trouble mounting secondary master
FWIW, I am running a July 30th kernel. let me see if the problem comes back with a new CVSup. > -Original Message- > From: Brian McGroarty [mailto:[EMAIL PROTECTED]] > Sent: 11 August 1999 01:41 > To: Soren Schmidt; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: ATA - Trouble mounting secondary master > > > I've just tried and coming in via wd and ad produce the same > problem. > > Note my previous comment - the access light is a steady on for > this particular drive. It's left that way when devices are > probed during startup. > > My configuration FWIW - > > (Note that the devclass_alloc_unit messages are new as of > yesterday's cvsup and, presumably, unrelated.) > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #7: Tue Aug 10 22:13:10 CDT 1999 > Timecounter "i8254" frequency 1193182 Hz > CPU: Celeron (686-class CPU) > Origin = "GenuineIntel" Id = 0x665 Stepping = 5 > > Features=0x183fbff ,MTRR,PGE,MCA,CM > OV,PAT,PSE36,MMX,FXSR> > real memory = 536870912 (524288K bytes) > avail memory = 518422528 (506272K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 > Preloaded elf kernel "kernel" at 0xc028f000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c. > Pentium Pro MTRR support enabled > Probing for PnP devices: > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > npx0: on motherboard > npx0: INT 16 interface > pcib0: on > motherboard > pci0: on pcib0 > WARNING: "bktr" is usurping "bktr"'s cdevsw[] > pcib6: at device > 1.0 on pci0 > pci1: on pcib6 > vga-pci0: irq 16 at > device 0.0 on pci1 > isab0: at device 7.0 on pci0 > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > chip1: at device 7.2 on pci0 > chip2: at device 7.3 > on pci0 > bktr0: irq 16 at device 16.0 on pci0 > iicbb0: on bti2c0 > iicbus0: on iicbb0 master-only > smbus0: on bti2c0 > Hauppauge Model 62471 A > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. > pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1 > irq 16 > pcm0: irq 18 at device 18.0 on pci0 > pcm0: using I/O space register mapping at 0xef00 > fxp0: irq 19 at device > 19.0 on pci0fxp0: Ethernet address 00:90:27:18:a6:fa > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 16 at device 20.0 on > pci0 > xl0: Ethernet address: 00:50:04:01:77:7b > xl0: autoneg complete, link status good (half-duplex, 100Mbps) > devclass_alloc_unit: pci1 already exists, using next available > unit number > pcib1: on motherboard > pci2: on pcib1 > devclass_alloc_unit: pci2 already exists, using next available > unit number > pcib2: on motherboard > pci3: on pcib2 > devclass_alloc_unit: pci3 already exists, using next available > unit number > pcib3: on motherboard > pci4: on pcib3 > devclass_alloc_unit: pci4 already exists, using next available > unit number > pcib4: on motherboard > pci5: on pcib4 > devclass_alloc_unit: pci5 already exists, using next available > unit number > pcib5: on motherboard > pci6: on pcib5 > isa0: on motherboard > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on > isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3b0-0x3df iomem > 0xa-0xb on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > IP packet filtering initialized, divert enabled, rule-based > forwarding disabled, > logging disabled > SMP: AP CPU #1 Launched! > ata0: master: setting up UDMA2 mode on PIIX4 chip OK > ad0: ATA-4 disk at ata0 as master > ad0: 1
Re: ATA - Trouble mounting secondary master
I've just tried and coming in via wd and ad produce the same problem. Note my previous comment - the access light is a steady on for this particular drive. It's left that way when devices are probed during startup. My configuration FWIW - (Note that the devclass_alloc_unit messages are new as of yesterday's cvsup and, presumably, unrelated.) Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #7: Tue Aug 10 22:13:10 CDT 1999 Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 536870912 (524288K bytes) avail memory = 518422528 (506272K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc028f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c. Pentium Pro MTRR support enabled Probing for PnP devices: devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib6: at device 1.0 on pci0 pci1: on pcib6 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: at device 7.2 on pci0 chip2: at device 7.3 on pci0 bktr0: irq 16 at device 16.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 Hauppauge Model 62471 A Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1 irq 16 pcm0: irq 18 at device 18.0 on pci0 pcm0: using I/O space register mapping at 0xef00 fxp0: irq 19 at device 19.0 on pci0fxp0: Ethernet address 00:90:27:18:a6:fa xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 16 at device 20.0 on pci0 xl0: Ethernet address: 00:50:04:01:77:7b xl0: autoneg complete, link status good (half-duplex, 100Mbps) devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci2: on pcib1 devclass_alloc_unit: pci2 already exists, using next available unit number pcib2: on motherboard pci3: on pcib2 devclass_alloc_unit: pci3 already exists, using next available unit number pcib3: on motherboard pci4: on pcib3 devclass_alloc_unit: pci4 already exists, using next available unit number pcib4: on motherboard pci5: on pcib4 devclass_alloc_unit: pci5 already exists, using next available unit number pcib5: on motherboard pci6: on pcib5 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled SMP: AP CPU #1 Launched! ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: ATA-4 disk at ata0 as slave ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 31 depth queue, DMA mode acd0: CDROM drive at ata1 as slave acd0: drive speed 344 - 1034KB/sec, 384KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 128 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked, lock protected changing root device to wd0s1a changing root device to wd0a --- Soren Schmidt <[EMAIL PROTECTED]> wrote: > It seems Geoff Rehmet wrote: > > Brian McGroarty
Re: ATA - Trouble mounting secondary master
It seems Geoff Rehmet wrote: > Hmm, > > My root device still lands up on "wd0" - even though my fstab has > the root filesystem on ad0s1a. I haven't looked at getting it to > use the ad dev entries for the root file system. (I'm assuming that > is still WIP.) Our boot blocks/loader dont have the needed computrons to use the "ad" device name. However I have some patches to boot2 that allows to boot off an ad root device, provided you dont use the loader, and put the rigth boot string in boot.config. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA - Trouble mounting secondary master
Hmm, My root device still lands up on "wd0" - even though my fstab has the root filesystem on ad0s1a. I haven't looked at getting it to use the ad dev entries for the root file system. (I'm assuming that is still WIP.) Geoff. > -Original Message- > From: Soren Schmidt [mailto:[EMAIL PROTECTED]] > Sent: 11 August 1999 08:53 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: ATA - Trouble mounting secondary master > > > It seems Geoff Rehmet wrote: > > Brian McGroarty writes : > > > In using the ATA driver, I'm unable to automatically mount a > > > partition on a master drive on the secondary controller. fsck > > > complains that device rwd2s1e isn't configured and exists. > > > Immediately mounting by hand works perfectly. > > > > > > Compiling the kernel with wd instead of ata eliminates the > > > problem. > > Hmm, > > > > I had exactly the same problem, although it manifested itself with a > > secondary master or slave. It went away a few weeks ago, and I > > was never able to make any sensible progress in tracking the problem > > down. > > Hmm, damn, after the problem went away for Geoff I thought it to be > solved since I've never heard of it anywhere else, and I cant > reproduce > it here no matter what I try. > Does it help eany if you only has the root partition use the wd dev > and have the rest use the prober ad dev entries ?? It could be some > artifact from this... > > -Søren > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
It seems Geoff Rehmet wrote: > Brian McGroarty writes : > > In using the ATA driver, I'm unable to automatically mount a > > partition on a master drive on the secondary controller. fsck > > complains that device rwd2s1e isn't configured and exists. > > Immediately mounting by hand works perfectly. > > > > Compiling the kernel with wd instead of ata eliminates the > > problem. > Hmm, > > I had exactly the same problem, although it manifested itself with a > secondary master or slave. It went away a few weeks ago, and I > was never able to make any sensible progress in tracking the problem > down. Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
Brian McGroarty writes : > In using the ATA driver, I'm unable to automatically mount a > partition on a master drive on the secondary controller. fsck > complains that device rwd2s1e isn't configured and exists. > Immediately mounting by hand works perfectly. > > Compiling the kernel with wd instead of ata eliminates the > problem. Hmm, I had exactly the same problem, although it manifested itself with a secondary master or slave. It went away a few weeks ago, and I was never able to make any sensible progress in tracking the problem down. It appears to occur when the partition table is read. Something times out, and the real partition table values are not read. The second time you read the disk, everything works. For a while, I had the line disklabel /dev/rad2s1a 2>&1 > /dev/null in my rc file :-). This was enough to kick the disk past the initial problem. (Not the right thing to do, but it allowed me to reboot without hitting single user mode.) Geoff. -- Geoff Rehmet, The Internet Solution [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] tel: +27-83-292-5800 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
Also of interest - I have a seperate access light for each of my drives, as they're in removable bays. I notice the access light for the secondary master remaining on after the kernel driver has done its scanning. The light goes off on this, the failed first access. I believe the light for the primary slave stays on as well, but goes off on the first access to the primary master (which does -not- fail). --- Kevin Street <[EMAIL PROTECTED]> wrote: > Brian McGroarty <[EMAIL PROTECTED]> writes: > > > In using the ATA driver, I'm unable to automatically mount a > > partition on a master drive on the secondary controller. > fsck > > complains that device rwd2s1e isn't configured and exists. > > Immediately mounting by hand works perfectly. > > Nice timing, I was about to send a message with a description > of a > similar (the same?) problem. The first access to any IDE disk > (except > the one I'm booting from - wd1) fails with 'device not > configured'. This > affects swapon for wd2s2b during the boot as well as the first > mount > for wd0 which happens to have only dos partitions on it. So > the > problem is not restricted to ufs partitions or to the > secondary > controller. > > Repeating the swapon or mount command works normally. > > I've been seeing this problem for about a month, but I've been > away on > vacation so am just beginning to look into it. I made changes > to all > my drives and put them in LBA mode at about the same time as I > began > seeing this, but I'm not sure if that is related. > > ata-pci0: at device 4.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > > ata0: master: setting up UDMA2 mode on PIIX4 chip OK > ad0: ATA-4 disk at ata0 as master > ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, > 512 B/S > ad0: piomode=4, dmamode=2, udmamode=2 > ad0: 16 secs/int, 0 depth queue, DMA mode > ata0: slave: setting up UDMA2 mode on PIIX4 chip OK > ad1: ATA-3 disk at ata0 as slave > ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, > 512 B/S > ad1: piomode=4, dmamode=2, udmamode=2 > ad1: 16 secs/int, 0 depth queue, DMA mode > ata1: master: setting up UDMA2 mode on PIIX4 chip OK > ad2: ATA-4 disk at ata1 as master > ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, > 512 B/S > ad2: piomode=4, dmamode=2, udmamode=2 > ad2: 16 secs/int, 0 depth queue, DMA mode > acd0: CDROM drive at ata1 as slave > acd0: drive speed 5515KB/sec, 256KB cache > acd0: supported read types: CD-R, CD-RW, CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked _ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
Brian McGroarty <[EMAIL PROTECTED]> writes: > In using the ATA driver, I'm unable to automatically mount a > partition on a master drive on the secondary controller. fsck > complains that device rwd2s1e isn't configured and exists. > Immediately mounting by hand works perfectly. Nice timing, I was about to send a message with a description of a similar (the same?) problem. The first access to any IDE disk (except the one I'm booting from - wd1) fails with 'device not configured'. This affects swapon for wd2s2b during the boot as well as the first mount for wd0 which happens to have only dos partitions on it. So the problem is not restricted to ufs partitions or to the secondary controller. Repeating the swapon or mount command works normally. I've been seeing this problem for about a month, but I've been away on vacation so am just beginning to look into it. I made changes to all my drives and put them in LBA mode at about the same time as I began seeing this, but I'm not sure if that is related. ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: ATA-3 disk at ata0 as slave ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata1 as slave acd0: drive speed 5515KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
