Re: ata: Mount root failure: 6
It seems Alexander Langer wrote: For the archive of this ml: Some of the commits over the time since I got this error solved the problem silently. I'm now using ata this machine w/o any problem. On another machine that had problems with DMA with the old wd drivers UDMA33 now works ok, too. Nice. Thanks! You're welcome, glad to hear it finally worked for you too... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Warner Losh writes: : : The fstab looks good : : : Is the kernel-config ok? : : I didn't see anything wrong with it, but maybe soren should take a : close look. This stuff definitely works for me on my laptop. Hate to follow up myself, but what boot blocks are you using? Really old ones use the disk label to determine what root device to pass to the kernel, and maybe that's where the problem lies? On any sort of -current system, the loader ignores this and uses the contents of /etc/fstab instead. I still haven't seen the plaintiff actually bother to transcribe the few relevant lines out of his startup log, so I'm not too highly motivated to worry about this in return, however ENXIO definitively means "the device you're trying to mount as root was not probed". Since it works with 'wd', and the 'ad' driver registers a 'wd' device as well, the actual options for dysfunction are pretty small. If and when more information is forthcoming, a diagnosis will be trivial. -- \\ 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: ata: Mount root failure: 6
Thus spake Soren Schmidt ([EMAIL PROTECTED]): I now just build a kernel with the old wd drivers and everything works fine... Have you checked the badsect flags then ?? Yes. It was not set. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Thus spake Warner Losh ([EMAIL PROTECTED]): Hate to follow up myself, but what boot blocks are you using? Really old ones use the disk label to determine what root device to pass to the kernel, and maybe that's where the problem lies? Uhm. I don't know, what exactly you want to know, but I think you want to know these: alex:/boot $ ls -l boot* loader -r--r--r-- 1 root wheel 512 17 Dez 16:34 boot0 -r--r--r-- 1 root wheel 512 17 Dez 16:34 boot1 -r--r--r-- 1 root wheel7680 17 Dez 16:34 boot2 -r-xr-xr-x 1 root wheel 143360 17 Dez 16:34 loader* They are build on Dez, 17th, together with the make world. Or what do you mean? Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Thus spake Mike Smith ([EMAIL PROTECTED]): I still haven't seen the plaintiff actually bother to transcribe the few relevant lines out of his startup log, so I'm not too highly motivated to worry about this in return, however ENXIO definitively means "the device you're trying to mount as root was not probed". Since it works with 'wd', and the 'ad' driver registers a 'wd' device as well, the actual options for dysfunction are pretty small. Ok, I scrolled up and wrote the stuff down by hand (args! :) Here are the messages regarding ata and hdd's: ata-pci0: VIA 82C586 ATA controller 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 ... ad0: IBM-DHEA-36481/HP6OA20C ATA-3 disk at ata0 as master ad0: 6197 MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 HTH, Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Sun, 19 Dec 1999, Mike Smith wrote: On any sort of -current system, the loader ignores this and uses the contents of /etc/fstab instead. which /etc/fstab? our systems always have 2 root partitions :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Sun, 19 Dec 1999, Mike Smith wrote: On any sort of -current system, the loader ignores this and uses the contents of /etc/fstab instead. which /etc/fstab? our systems always have 2 root partitions :-) Unless overridden, the one on the same filesystem the kernel was read from. -- \\ 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: ata: Mount root failure: 6
On Fri, Dec 17, 1999 at 11:31:01AM -0700, Warner Losh wrote: BTW, what does your /etc/fstab look like? # DeviceMountpoint FStype Options DumpPass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /usrufs rw 2 2 proc/proc procfs rw 0 0 Is the kernel-config ok? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Fri, Dec 17, 1999 at 12:14:44PM -0800, Dave Truesdell wrote: Try this: running an old/working kernel, run disklabel on all your disks/slices and make sure the "badsect" flag is NOT set. I ran into this a couple of nights ago, updating a machine (my laptop) to a current "-current". Hmm. NO. There is no flag set for any slice/disk. What were your problems? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Thus spake Dave Truesdell ([EMAIL PROTECTED]): Try this: running an old/working kernel, run disklabel on all your disks/slices and make sure the "badsect" flag is NOT set. I ran into this a couple of nights ago, updating a machine (my laptop) to a current "-current". I now just build a kernel with the old wd drivers and everything works fine... Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
It seems Alexander Langer wrote: Thus spake Dave Truesdell ([EMAIL PROTECTED]): Try this: running an old/working kernel, run disklabel on all your disks/slices and make sure the "badsect" flag is NOT set. I ran into this a couple of nights ago, updating a machine (my laptop) to a current "-current". I now just build a kernel with the old wd drivers and everything works fine... Have you checked the badsect flags then ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
The fstab looks good : Is the kernel-config ok? I didn't see anything wrong with it, but maybe soren should take a close look. This stuff definitely works for me on my laptop. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Warner Losh writes: : : The fstab looks good : : : Is the kernel-config ok? : : I didn't see anything wrong with it, but maybe soren should take a : close look. This stuff definitely works for me on my laptop. Hate to follow up myself, but what boot blocks are you using? Really old ones use the disk label to determine what root device to pass to the kernel, and maybe that's where the problem lies? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
In message [EMAIL PROTECTED] Alexander Langer writes: : When I boot my new kernel, I get : root mount failure: 6 This is ENXIO, Device Not Configured. What is the name of the device that it is trying to mount? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Fri, Dec 17, 1999 at 10:17:33AM -0700, Warner Losh wrote: : When I boot my new kernel, I get : root mount failure: 6 This is ENXIO, Device Not Configured. What is the name of the device that it is trying to mount? ad0s1a an IDE drive with the new ata-drivers. Also, the same for wd0s1a and rwd0s1a Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
In message [EMAIL PROTECTED] Alexander Langer writes: : ad0s1a : an IDE drive with the new ata-drivers. : Also, the same for wd0s1a and rwd0s1a That looks good. Can you send the config file and the boot messages, at least those related to ata/ad? And a ls -l /dev/ad0* might not hurt either. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Fri, Dec 17, 1999 at 10:24:19AM -0700, Warner Losh wrote: That looks good. Can you send the config file and the boot messages, at least those related to ata/ad? And a ls -l /dev/ad0* might not hurt either. Unfortunately, I cant send the boot-messages, because they aren`t logged and I have no serial console. But there seems to be no error. The disk is detected correctly with UDMA33 and no errors appear. But I can send the other stuff. crw-r- 1 root operator 116, 0x00010002 Dec 17 18:56 /dev/ad0 crw-r- 1 root operator 116, 0 Dec 17 18:56 /dev/ad0a crw-r- 1 root operator 116, 1 Dec 17 18:56 /dev/ad0b crw-r- 1 root operator 116, 2 Dec 17 18:56 /dev/ad0c crw-r- 1 root operator 116, 3 Dec 17 18:56 /dev/ad0d crw-r- 1 root operator 116, 4 Dec 17 18:56 /dev/ad0e crw-r- 1 root operator 116, 5 Dec 17 18:56 /dev/ad0f crw-r- 1 root operator 116, 6 Dec 17 18:56 /dev/ad0g crw-r- 1 root operator 116, 7 Dec 17 18:56 /dev/ad0h crw-r- 1 root operator 116, 0x00020002 Dec 17 18:56 /dev/ad0s1 crw-r- 1 root operator 116, 0x0002 Dec 17 18:56 /dev/ad0s1a crw-r- 1 root operator 116, 0x00020001 Dec 17 18:56 /dev/ad0s1b crw-r- 1 root operator 116, 0x00020002 Dec 17 18:56 /dev/ad0s1c crw-r- 1 root operator 116, 0x00020003 Dec 17 18:56 /dev/ad0s1d crw-r- 1 root operator 116, 0x00020004 Dec 17 18:56 /dev/ad0s1e crw-r- 1 root operator 116, 0x00020005 Dec 17 18:56 /dev/ad0s1f crw-r- 1 root operator 116, 0x00020006 Dec 17 18:56 /dev/ad0s1g crw-r- 1 root operator 116, 0x00020007 Dec 17 18:56 /dev/ad0s1h crw-r- 1 root operator 116, 0x00030002 Dec 17 18:56 /dev/ad0s2 crw-r- 1 root operator 116, 0x00040002 Dec 17 18:56 /dev/ad0s3 crw-r- 1 root operator 116, 0x00050002 Dec 17 18:56 /dev/ad0s4 crw-r- 1 root operator 116, 0x0001000a Dec 17 18:56 /dev/ad1 crw-r- 1 root operator 116, 8 Dec 17 18:56 /dev/ad1a crw-r- 1 root operator 116, 9 Dec 17 18:56 /dev/ad1b crw-r- 1 root operator 116, 10 Dec 17 18:56 /dev/ad1c crw-r- 1 root operator 116, 11 Dec 17 18:56 /dev/ad1d crw-r- 1 root operator 116, 12 Dec 17 18:56 /dev/ad1e crw-r- 1 root operator 116, 13 Dec 17 18:56 /dev/ad1f crw-r- 1 root operator 116, 14 Dec 17 18:56 /dev/ad1g crw-r- 1 root operator 116, 15 Dec 17 18:56 /dev/ad1h crw-r- 1 root operator 116, 0x0002000a Dec 17 18:56 /dev/ad1s1 crw-r- 1 root operator 116, 0x0003000a Dec 17 18:56 /dev/ad1s2 crw-r- 1 root operator 116, 0x00030008 Dec 17 17:24 /dev/ad1s2a crw-r- 1 root operator 116, 0x00030009 Dec 17 17:24 /dev/ad1s2b crw-r- 1 root operator 116, 0x0003000a Dec 17 17:24 /dev/ad1s2c crw-r- 1 root operator 116, 0x0003000b Dec 17 17:24 /dev/ad1s2d crw-r- 1 root operator 116, 0x0003000c Dec 17 17:24 /dev/ad1s2e crw-r- 1 root operator 116, 0x0003000d Dec 17 17:24 /dev/ad1s2f crw-r- 1 root operator 116, 0x0003000e Dec 17 17:24 /dev/ad1s2g crw-r- 1 root operator 116, 0x0003000f Dec 17 17:24 /dev/ad1s2h crw-r- 1 root operator 116, 0x0004000a Dec 17 18:56 /dev/ad1s3 crw-r- 1 root operator 116, 0x0005000a Dec 17 18:56 /dev/ad1s4 crw-r- 1 root operator 116, 0x00010012 Dec 17 18:56 /dev/ad2 crw-r- 1 root operator 116, 16 Dec 17 18:56 /dev/ad2a crw-r- 1 root operator 116, 17 Dec 17 18:56 /dev/ad2b crw-r- 1 root operator 116, 18 Dec 17 18:56 /dev/ad2c crw-r- 1 root operator 116, 19 Dec 17 18:56 /dev/ad2d crw-r- 1 root operator 116, 20 Dec 17 18:56 /dev/ad2e crw-r- 1 root operator 116, 21 Dec 17 18:56 /dev/ad2f crw-r- 1 root operator 116, 22 Dec 17 18:56 /dev/ad2g crw-r- 1 root operator 116, 23 Dec 17 18:56 /dev/ad2h crw-r- 1 root operator 116, 0x00020012 Dec 17 18:56 /dev/ad2s1 crw-r- 1 root operator 116, 0x00030012 Dec 17 18:56 /dev/ad2s2 crw-r- 1 root operator 116, 0x00040012 Dec 17 18:56 /dev/ad2s3 crw-r- 1 root operator 116, 0x00050012 Dec 17 18:56 /dev/ad2s4 crw-r- 1 root operator 116, 0x0001001a Dec 17 18:56 /dev/ad3 crw-r- 1 root operator 116, 24 Dec 17 18:56 /dev/ad3a crw-r- 1 root operator 116, 25 Dec 17 18:56 /dev/ad3b crw-r- 1 root operator 116, 26 Dec 17 18:56 /dev/ad3c crw-r- 1 root operator 116, 27 Dec 17 18:56 /dev/ad3d crw-r- 1 root operator 116, 28 Dec 17 18:56 /dev/ad3e crw-r- 1 root operator 116, 29 Dec 17 18:56 /dev/ad3f crw-r- 1 root operator 116, 30 Dec 17 18:56 /dev/ad3g crw-r- 1 root operator 116, 31 Dec 17 18:56 /dev/ad3h crw-r- 1 root operator 116, 0x0002001a Dec 17 18:56 /dev/ad3s1 crw-r- 1 root operator 116, 0x0003001a Dec 17 18:56 /dev/ad3s2 crw-r- 1 root operator 116, 0x0004001a Dec 17 18:56 /dev/ad3s3 crw-r- 1 root operator 116, 0x0005001a Dec 17 18:56 /dev/ad3s4 Attached is the config-file.
Re: ata: Mount root failure: 6
In message [EMAIL PROTECTED] Alexander Langer writes: : crw-r- 1 root operator 116, 0x00010002 Dec 17 18:56 /dev/ad0 You didn't copy MAKEDEV from a current source tree before making these devices. The major number of ad is 30, not 116. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
In message [EMAIL PROTECTED] Warner Losh writes: : You didn't copy MAKEDEV from a current source tree before making these : devices. The major number of ad is 30, not 116. Actually, this is wrong. I didn't update MY MAKEDEV before looking. 30 is the old major bdev number... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Fri, Dec 17, 1999 at 10:53:01AM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Alexander Langer writes: : crw-r- 1 root operator 116, 0x00010002 Dec 17 18:56 /dev/ad0 You didn't copy MAKEDEV from a current source tree before making these devices. The major number of ad is 30, not 116. My latest -current tree has the following MAKEDEV and MAKEDEV.local: /usr/src/etc/MAKEDEV:# $FreeBSD: src/etc/MAKEDEV,v 1.226 1999/12/14 22:36:03 joerg Exp $ /usr/src/etc/MAKEDEV.local:# $FreeBSD: src/etc/MAKEDEV.local,v 1.3 1999/08/27 23:23:40 peter Exp $ That are the ones I used. Are these the right ones? If so, why does it fail for me (incorrect major number) but not for you? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Fri, Dec 17, 1999 at 11:18:05AM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Alexander Langer writes: : That are the ones I used. Are these the right ones? Turns out those are the right ones. : If so, why does it fail for me (incorrect major number) but not for you? Don't know. Still doesn't work, btw, also with major num of 30. BTW: The MAKEDEV _really_ does include 116 as major num. If this an error - could one _please_ correct this? Thank you. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Try this: running an old/working kernel, run disklabel on all your disks/slices and make sure the "badsect" flag is NOT set. I ran into this a couple of nights ago, updating a machine (my laptop) to a current "-current". -- T.T.F.N., Dave Truesdell / [EMAIL PROTECTED][EMAIL PROTECTED] / UNIX system administrator To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
