Re: Problems with booting MBR
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Vittorio De Martino wrote: | # fdisk -B -b /boot/boot0 ad0 | fdisk: cannot open disk /dev/ad0: No such file or directory | | and with | | # fdisk -B -b /boot/boot0 ad1 | fdisk: cannot open disk /dev/ad1: No such file or directory I think this is because you're in multi-user mode and the drives are in use (things mounted). You might have better luck in single-user mode. Stewart, - - - Stewart Morgan MEng MIEE Technical Director, Nameless-UK Phone : +44 870 757 1625| Address: The Production House Fax : +44 870 168 0210| 147a Saint Michael's Hill PGP ID: 0xECD5CE64 | Bristol, BS2 8DB, UK - - --x- PGP Fingerprint: 89DE F8C3 CA14 598C 30DB 504A 3055 DDD7 ECD5 CE64 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFC83oPMFXd1+zVzmQRAnwFAKCnzTn3Ra6V4wZjVkXGOcP5+9AlSQCeKh29 HteCD/v+xHKpYLU6adp2FEo= =wG+l -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with booting MBR
Dear Glenn, even though a bit late here you are the info you suggested to check (still absolutely obscure to me!!): Yes, the / directory for booting is /dev/ad1s2a as in the fstab file. From dmesg: ad0: 9541MB WDC WD100BA/16.13M16 [19386/16/63] at ata0-master UDMA33 ad1: 9541MB WDC WD200EB-11CPF0/06.04G06 [19386/16/63] at ata0-slave UDMA33 vicbsd root# fdisk /dev/ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=19386 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19386 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 19541025 (9541 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED vicbsd root# fdisk /dev/ad1 *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=19386 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19386 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 9179856, size 10361232 (5059 Meg), flag 80 (active) beg: cyl 1023/ head 15/ sector 63; end: cyl 1023/ head 15/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED vicbsd root# bsdlabel /dev/ad1s2 # /dev/ad1s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 9312656 10485764.2BSD 2048 16384 28552 b: 10485760 swap c: 103612320unused0 0 # raw part, don't edit vicbsd root# bsdlabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1433600004.2BSD0 0 0 b: 1084449 18456576 swap c: 195410250unused0 0 # raw part, don't edit d: 524288 143360004.2BSD 2048 16384 32776 e: 524288 148602884.2BSD 2048 16384 32776 f: 3072000 153845764.2BSD 2048 16384 28552 Ciao Vittorio -- Messaggio originale -- Date: Fri, 29 Jul 2005 08:43:10 -0700 To: Vittorio De Martino [EMAIL PROTECTED] From: Glenn Dawson [EMAIL PROTECTED] Subject: Re: Problems with booting MBR At 08:25 AM 7/29/2005, you wrote: Friends, as suggested in the docs in the internet I tried both with # fdisk -B -b /boot/boot0 ad0 fdisk: cannot open disk /dev/ad0: No such file or directory and with # fdisk -B -b /boot/boot0 ad1 fdisk: cannot open disk /dev/ad1: No such file or directory WHILST my working /etc/fstab is, as I mentioned before: # DeviceMountpoint FStype Options Dump Pass# /dev/ad1s2b noneswapsw 0 0 /dev/ad1s2a / ufs rw 1 1 /dev/ad0s1a /usr/local ufs rw 0 0 /dev/ad0s1d /varufs rw 0 0 /dev/ad0s1e /tmpufs rw 0 0 Why FreeBSD 5.4 cannot find /dev/ad0 and ad1? What should I do? How are you booting the system to get to a prompt where you can issue the commands shown above? The first thing you probably need to do is examine dmesg output and see what disk devices are being detected at boot time. Then look in /dev and see if the entries you need are there or not. Also, one thing to keep in mind is that the bootloader only knows how to find the root file system when it's on the 'a' partition. Based on your fstab above, that would be /dev/ad1s2a. Assuming that's correct, what's on ad1s1? It would be helpful to see output from 'fdisk /dev/ad0' and 'fdisk /dev/ad1' if you can get it. Then depending on what slices are there, the corresponding bsdlabel output. Here's a sample from one of my test systems (it boots from /dev/ad4 which has two slices, one with 4.11 and one with 5.4 installed) test54# fdisk /dev/ad4 *** Working on device /dev/ad4 *** parameters extracted from in-core disklabel are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data
Re: Problems with booting MBR
[EMAIL PROTECTED] writes: From dmesg: ad0: 9541MB WDC WD100BA/16.13M16 [19386/16/63] at ata0-master UDMA33 I think you just said that vicbsd root# fdisk /dev/ad0 vicbsd root# bsdlabel /dev/ad0s1 work OK, but that your problem (from a prior msg) is: # fdisk -B -b /boot/boot0 ad0 fdisk: cannot open disk /dev/ad0: No such file or directory That makes no sense. If I understood this right, there's something very wrong and you ought to be filing a PR about it and/or reporting the problem on the mailing list for 5.4 development, freebsd-stable. Also: You might rather use boot0cfg instead of fdisk as the former allows you to configure stuff that the later doesn't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with booting MBR
Alle 11:16, giovedì 28 luglio 2005, [EMAIL PROTECTED] ha scritto: In the first disk ad0 (master) of a computer at office I had installed linux to be used as a postgresql server. Later I installed FreeBSD 5.4 (just to have a go at it) on a partition of the second disk ad1 (slave) to be a postgrresql server too. Linux lilo was the boot loader, booting linux by default and freebsd. Now, convinced of the high quality of the latter I eliminated linux from the first disk unfortunately without modifying lilo, and reshuffled the FreeBSD filesystem as in my latest /etc/fstab using also the first disk: # DeviceMountpoint FStype Options Dump Pass# /dev/ad1s2b noneswapsw 0 0 /dev/ad1s2a / ufs rw 1 1 /dev/ad0s1a /usr/local ufs rw 0 0 /dev/ad0s1d /varufs rw 0 0 /dev/ad0s1e /tmpufs rw 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Now, even though I read the booting procedure in the handbook and somewhere else in the internet, issuing the various fdisk -b B, disklabel -b .., boot0cfg .., I was completely unable to modify the MBR and make this FreeBSD only computer boot directly into this OS. What should I do with the configuration I have? A straightforward and step by step explanation is highly appreciated. P.S. Is it possible that some problems can arise by the fact that I used an a slice (ad0s1a)for mounting /usr/local and freebsd starts from ad1s1a? Friends, as suggested in the docs in the internet I tried both with # fdisk -B -b /boot/boot0 ad0 fdisk: cannot open disk /dev/ad0: No such file or directory and with # fdisk -B -b /boot/boot0 ad1 fdisk: cannot open disk /dev/ad1: No such file or directory WHILST my working /etc/fstab is, as I mentioned before: # DeviceMountpoint FStype Options DumpPass# /dev/ad1s2b noneswapsw 0 0 /dev/ad1s2a / ufs rw 1 1 /dev/ad0s1a /usr/local ufs rw 0 0 /dev/ad0s1d /varufs rw 0 0 /dev/ad0s1e /tmpufs rw 0 0 Why FreeBSD 5.4 cannot find /dev/ad0 and ad1? What should I do? A baffled and frustated Vittorio again ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with booting MBR
In the first disk ad0 (master) of a computer at office I had installed linux to be used as a postgresql server. Later I installed FreeBSD 5.4 (just to have a go at it) on a partition of the second disk ad1 (slave) to be a postgrresql server too. Linux lilo was the boot loader, booting linux by default and freebsd. Now, convinced of the high quality of the latter I eliminated linux from the first disk unfortunately without modifying lilo, and reshuffled the FreeBSD filesystem as in my latest /etc/fstab using also the first disk: # DeviceMountpoint FStype Options DumpPass# /dev/ad1s2b noneswapsw 0 0 /dev/ad1s2a / ufs rw 1 1 /dev/ad0s1a /usr/local ufs rw 0 0 /dev/ad0s1d /varufs rw 0 0 /dev/ad0s1e /tmpufs rw 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Now, even though I read the booting procedure in the handbook and somewhere else in the internet, issuing the various fdisk -b B, disklabel -b .., boot0cfg .., I was completely unable to modify the MBR and make this FreeBSD only computer boot directly into this OS. What should I do with the configuration I have? A straightforward and step by step explanation is highly appreciated. P.S. Is it possible that some problems can arise by the fact that I used an a slice (ad0s1a)for mounting /usr/local and freebsd starts from ad1s1a? Ciao Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with booting MBR
[EMAIL PROTECTED] writes: # DeviceMountpoint FStype Options DumpPass# /dev/ad1s2b noneswapsw 0 0 /dev/ad1s2a / ufs rw 1 1 /dev/ad0s1a /usr/local ufs rw 0 0 /dev/ad0s1d /varufs rw 0 0 /dev/ad0s1e /tmpufs rw 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Now, even though I read the booting procedure in the handbook and somewhere else in the internet, issuing the various fdisk -b B, disklabel -b .., boot0cfg .., I was completely unable to modify the MBR and make this FreeBSD only computer boot directly into this OS. If you're sticking to FreeBSD's boot0 MBR, you'll have to put one on each disk. I don't know if boot0 can remember F5 as the default choice for auto-booting or not. But one way or another the first disk's boot0 needs to use F5 to start the second disk's MBR/boot0 which needs to use F2 by hand or from boot0cfg config. You could also use grub or lilo to do it too, but it's harder to set up. P.S. Is it possible that some problems can arise by the fact that I used an a slice (ad0s1a)for mounting /usr/local and freebsd starts from ad1s1a? Only the easy-to-fix problems that you're having. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with booting MBR
Gary W. Swearingen wrote: If you're sticking to FreeBSD's boot0 MBR, you'll have to put one on each disk. I don't know if boot0 can remember F5 as the default choice for auto-booting or not. But one way or another the first disk's boot0 needs to use F5 to start the second disk's MBR/boot0 which needs to use F2 by hand or from boot0cfg config. Yes, it does. I believe it picks F5 when all the partitions before it are not set to boot. Once you've done the right sequence once, the machine will boot the same until interfered with. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
