Re: Among the ATA casualties...
On Sun, Dec 12, 1999 at 11:08:24PM -0800, Mike Smith wrote: You'll need to take this up with Soren; I suspect though that the simplest answer for you is going to be to stick with 'wd' until you get yourself a less-broken disk, or manage to analyse the problem in greater depth. Ideally I (we?) would fix the problem in code. Even with the odd error messages emitted by wd everything is quite solid, so I know there's a "better" solution than buying another drive for no reason... I'll wallow around the code tomorrow night and post the results. On Mon, Dec 13, 1999 at 08:14:34AM +0100, Soren Schmidt wrote: Have you update your /dev with MAKEDEV from usr/src/etc recently? I rebuilt and fresh MAKEDEVved at about 11AM PST with exactly the same results... -Adam Wight To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Among the ATA casualties...
Against my better judgment, I've been running -current on, among other machines, a Dell Latitude XP 475C... The wd driver manages to deal with the inevitable cruft quite nicely, but the ata driver refuses to mount the root partition. To the best of my knowledge the chipset is the Western Digital 8110. I can supply any other information required, of course. -Adam Wight boot -v output using the wd driver follows: That's not very helpful; we know it works. How about some information on the problem? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Among the ATA casualties...
boot -v output using the wd driver follows: That's not very helpful; we know it works. How about some information on the problem? Well... I'd sure like to send a boot -v for a kernel using ata... I don't have the right hardware here to use a serial console, however. Here are the relevant lines from the boot sequence (paraphrased, of course): ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at port 0x1f0 irq 14 on isa0 BIOS Geometries: 0:03da0f34 0..986=987 cylinders, 0..15=16 heads, 1..52=52 sectors 1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors 0 accounted for Device configuration finished. new masks: bio 40084040, tty 40031092, net 40071092 ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ST9420AG/08.08.01 ATA-? disk at ata0 as master ad0: 401MB (822016 sectors), 988 cyls, 16 heads, 52 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/wd0s1a wd0: invalid primary partition table: no magic Root mount failed: 6 Mounting root from ufs:wd0s1a wd0: invalid primary partition table: no magic Root mount failed: 6 Mounting root from ufs:wd0a wd0: invalid primary partition table: no magic Root mount failed: 22 Manual root filesystem specification To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Among the ATA casualties...
boot -v output using the wd driver follows: That's not very helpful; we know it works. How about some information on the problem? Well... I'd sure like to send a boot -v for a kernel using ata... I don't have the right hardware here to use a serial console, however. That's more your problem than ours though. Here are the relevant lines from the boot sequence (paraphrased, of course): ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ST9420AG/08.08.01 ATA-? disk at ata0 as master Eek. An old laptop drive. ad0: 401MB (822016 sectors), 988 cyls, 16 heads, 52 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/wd0s1a Ultimately you'll want to update /etc/fstab (obviously not yet!) wd0: invalid primary partition table: no magic Ok. It looks like we need more verbose output from the 'ad' driver, since it believes that it's read the primary partition table, but obviously hasn't. This syncs to some degree with the 'wd' driver's complaining about the recal failing. Root mount failed: 6 Mounting root from ufs:wd0s1a wd0: invalid primary partition table: no magic This destroys my original hypothesis (that the first command was being ignored). You'll need to take this up with Soren; I suspect though that the simplest answer for you is going to be to stick with 'wd' until you get yourself a less-broken disk, or manage to analyse the problem in greater depth. The latter would be greatly assisted if you were able to dig into the 'ad' code a little and see what, if anything, is actually failing. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Among the ATA casualties...
It seems Adam Wight wrote: Against my better judgment, I've been running -current on, among other machines, a Dell Latitude XP 475C... The wd driver manages to deal with the inevitable cruft quite nicely, but the ata driver refuses to mount the root partition. To the best of my knowledge the chipset is the Western Digital 8110. I can supply any other information required, of course. Have you update your /dev with MAKEDEV from usr/src/etc recently? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
