Re: Dual-boot does not work with GRUB
On 23 Dec 2003 20:24:34 +0100, Jaroslaw Nozderko <[EMAIL PROTECTED]> wrote: Hi Jud, Tillman, Bill, On Mon, 22 Dec 2003 18:58:16 -0600, Tillman Hodgson <[EMAIL PROTECTED]> wrote: > On Tue, Dec 23, 2003 at 01:52:46AM +0100, Jaroslaw Nozderko wrote: >> I've got the following error: >> >> Filesystem type unknown, partition type 0xa5 >> Error 17: Cannot mount selected partition >> >> Does GRUB have some problems with FreeBSD partition ? > > I recently ran into the same problem - I found the solution in an > archived posting to the bug-grub@ mailing list (from Sergey Matveychuk > on Sep 25 2003, if you're interested). > > Try this: > > rootnoverify (hd0,1) > chainloader +1 Is your root partition UFS2? GRUB does not understand UFS2 yet as far as I know, so you may need to chainload as in the above example. Jud Yes, it's UFS2, so probably that was a reason. rootnoverify (hd0,1) fails: Error 13: Invalid or unsupported executable format Fortunately, rootnoverify (hd0,2) chainloader +1 finally works ! Slices are: swap 1 GBad0s3b /home1 1 GBad0s3d / 28 GBad0s3a Why 2, not 1 ? I'm a little bit confused. Because (hd0,1) is only an example. For your setup on ad0s3, (hd0,2) is correct (I think, or should it be (hd0,3)?). Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual-boot does not work with GRUB
Hi Jud, Tillman, Bill, > On Mon, 22 Dec 2003 18:58:16 -0600, Tillman Hodgson > <[EMAIL PROTECTED]> wrote: > > > On Tue, Dec 23, 2003 at 01:52:46AM +0100, Jaroslaw Nozderko wrote: > >> I've got the following error: > >> > >> Filesystem type unknown, partition type 0xa5 > >> Error 17: Cannot mount selected partition > >> > >> Does GRUB have some problems with FreeBSD partition ? > > > > I recently ran into the same problem - I found the solution in an > > archived posting to the bug-grub@ mailing list (from Sergey Matveychuk > > on Sep 25 2003, if you're interested). > > > > Try this: > > > > rootnoverify (hd0,1) > > chainloader +1 > > Is your root partition UFS2? GRUB does not understand UFS2 yet as far as > I know, so you may need to chainload as in the above example. > > Jud Yes, it's UFS2, so probably that was a reason. rootnoverify (hd0,1) fails: Error 13: Invalid or unsupported executable format Fortunately, rootnoverify (hd0,2) chainloader +1 finally works ! Slices are: swap 1 GBad0s3b /home1 1 GBad0s3d / 28 GBad0s3a Why 2, not 1 ? I'm a little bit confused. Anyway, thanks a lot for your help. Regards, Jarek ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual-boot does not work with GRUB
At Tue, 23 Dec 2003 it looks like Jaroslaw Nozderko composed: >Device BootStart EndBlocks Id System > /dev/hda1 165522081 83 Linux > /dev/hda266 3889 30716280 83 Linux > /dev/hda3 * 3890 7713 30716280 a5 FreeBSD > /dev/hda4 7714 14593 55263600f Win95 Ext'd (LBA) > /dev/hda5 7714 10263 20482843+ 83 Linux > /dev/hda6 10264 11793 12289693+ 83 Linux > /dev/hda7 11794 13068 10241406 83 Linux > /dev/hda8 13069 14088 8193118+ 83 Linux > /dev/hda9 14089 14219 1052226 82 Linux swap > /dev/hda1014220 14350 1052226 83 Linux > > FreeBSD partition is visible as hda3 under Linux and ad0s3 under > FreeBSD. It has 3 slices: > > swap 1 GBad0s3b > /home1 1 GBad0s3d > / 28 GBad0s3a > > After reading GRUB documentation, I've prepared the following > entry in grub.conf: > > # FreeBSD > title FreeBSD 5.1-RELEASE > root (hd0,2,a) > kernel /boot/loader > Hello, I experienced some problems with GRUB back with Linux in an earlier release where it actually started counting at 1, not 0. Try setting root to hd0,3,a I hope this helps. -- |<--"Word-Wrap-At-72-Please"-->| Bill Schoolcraft PO Box 210076 -o) San Francisco CA 94121 /\ "UNIX, A Way Of Life."_\_v ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual-boot does not work with GRUB
On Mon, 22 Dec 2003 18:58:16 -0600, Tillman Hodgson <[EMAIL PROTECTED]> wrote: On Tue, Dec 23, 2003 at 01:52:46AM +0100, Jaroslaw Nozderko wrote: I've got the following error: Filesystem type unknown, partition type 0xa5 Error 17: Cannot mount selected partition Does GRUB have some problems with FreeBSD partition ? I recently ran into the same problem - I found the solution in an archived posting to the bug-grub@ mailing list (from Sergey Matveychuk on Sep 25 2003, if you're interested). Try this: rootnoverify (hd0,1) chainloader +1 Is your root partition UFS2? GRUB does not understand UFS2 yet as far as I know, so you may need to chainload as in the above example. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual-boot does not work with GRUB
On Tue, Dec 23, 2003 at 01:52:46AM +0100, Jaroslaw Nozderko wrote: > I've got the following error: > > Filesystem type unknown, partition type 0xa5 > Error 17: Cannot mount selected partition > > Does GRUB have some problems with FreeBSD partition ? I recently ran into the same problem - I found the solution in an archived posting to the bug-grub@ mailing list (from Sergey Matveychuk on Sep 25 2003, if you're interested). Try this: rootnoverify (hd0,1) chainloader +1 -T -- "There is a time in the life of every problem when it is big enough to see, yet small enough to solve." - Mike Leavitt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual-boot does not work with GRUB
FreeBSD 5.1-RELEASE RedHat Linux 9.0 Hi, I have such problem: RedHat Linux 9.0 (Shrike) and FreeBSD 5.1-RELEASE together. I'd like to have working dual-boot with GRUB. # fdisk -l Disk /dev/hda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device BootStart EndBlocks Id System /dev/hda1 165522081 83 Linux /dev/hda266 3889 30716280 83 Linux /dev/hda3 * 3890 7713 30716280 a5 FreeBSD /dev/hda4 7714 14593 55263600f Win95 Ext'd (LBA) /dev/hda5 7714 10263 20482843+ 83 Linux /dev/hda6 10264 11793 12289693+ 83 Linux /dev/hda7 11794 13068 10241406 83 Linux /dev/hda8 13069 14088 8193118+ 83 Linux /dev/hda9 14089 14219 1052226 82 Linux swap /dev/hda1014220 14350 1052226 83 Linux FreeBSD partition is visible as hda3 under Linux and ad0s3 under FreeBSD. It has 3 slices: swap 1 GBad0s3b /home1 1 GBad0s3d / 28 GBad0s3a After reading GRUB documentation, I've prepared the following entry in grub.conf: # FreeBSD title FreeBSD 5.1-RELEASE root (hd0,2,a) kernel /boot/loader Despite GRUB doc, I'm not sure I understand this format. According to http://www.gnu.org/software/grub/manual/html_node/Configuration.html#Configuration (hd0,2,a) means "partition of the third PC slice of the first hard disk". Is "a" a slice symbol and "2" is a partition number (starting with 0) on hd0 ? I've got the following error: Filesystem type unknown, partition type 0xa5 Error 17: Cannot mount selected partition Does GRUB have some problems with FreeBSD partition ? This is probably some stupid mistake. Could anyone give me some advice ? Thanks for any help, Jarek -Original Message- Hi, I to have a multi boot system with linux and freebsd and windows. GRUB is my boot loader. I did not chain load FreeBSD. This is my menu file for GRUB default=1 timeout=10 splashimage=(hd0,4)/grub/splash.xpm.gz title Red Hat Linux 9 (2.4.20-8) root (hd0,4) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ initrd /initrd-2.4.20-8.img title Windows 2000 rootnoverify (hd0,0) chainloader +1 title FreeBSD 4.8 root (hd0,3,a) kernel /boot/loader And my fdisk -l Device BootStart EndBlocks Id System /dev/hda1 1 892 7164958+ 7 HPFS/NTFS /dev/hda2 893 956514080b Win95 FAT32 /dev/hda3 957 2522 125788955 Extended /dev/hda4 * 2523 4865 18820147+ a5 FreeBSD /dev/hda5 957 969104391 83 Linux /dev/hda6 970 2457 11952328+ 83 Linux /dev/hda7 2458 2522522081 82 Linux swap This works fine for me. I to am a beginner and still gathering info Hope it helps -sundeep ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Dual-boot does not work with GRUB
Hi, I to have a multi boot system with linux and freebsd and windows. GRUB is my boot loader. I did not chain load FreeBSD. This is my menu file for GRUB default=1 timeout=10 splashimage=(hd0,4)/grub/splash.xpm.gz title Red Hat Linux 9 (2.4.20-8) root (hd0,4) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ initrd /initrd-2.4.20-8.img title Windows 2000 rootnoverify (hd0,0) chainloader +1 title FreeBSD 4.8 root (hd0,3,a) kernel /boot/loader And my fdisk -l Device BootStart EndBlocks Id System /dev/hda1 1 892 7164958+ 7 HPFS/NTFS /dev/hda2 893 956514080b Win95 FAT32 /dev/hda3 957 2522 125788955 Extended /dev/hda4 * 2523 4865 18820147+ a5 FreeBSD /dev/hda5 957 969104391 83 Linux /dev/hda6 970 2457 11952328+ 83 Linux /dev/hda7 2458 2522522081 82 Linux swap This works fine for me. I to am a beginner and still gathering info Hope it helps -sundeep -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Loren M. Lang Sent: Monday, December 08, 2003 7:26 AM To: [EMAIL PROTECTED] Subject: Dual-boot does not work with GRUB I've been trying to setup a dual boot Linux/FreeBSD system so I can tryout freebsd and compare it to linux, my current main os. I had the freebsd easyboot bootloader installed, but I couldn't get it to boot linux so I reinstalled GRUB as lilo doesn't even load properly on my system. I can now boot into linux and use the freebsd install disk to boot into freebsd. I've tried to get grub to boot freebsd directly, but it's not working. I've had it chainloader the first sector of the slice with freebsd on it and chainload /boot/boot1 directly, both just print a - in the upper left corner and stop, like it loaded boot1 successfully but boot1 couldn't find boot2. Chainloading /boot/boot0 does a similar result, with that boot loader. Using grub to try and load /boot/loader and /kernel with the kernel command doesn't do much either. Any suggestions. Also, in my short experience with freebsd, it seems relatively fast, but when there is massive i/o in the background, like untarring a massive tarball, the system becomes rather unresponsive with certain things, is something misconfigured on my system? Harddrive dma is turned on according to sysctl. On linux there is also an option to unmask irqs while handling a disk interrupt, is there a similar option in freebsd and will it help? -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
