Re: Grub demage my boot loader
On Fri, Mar 26, 2010 at 3:56 PM, Jindřich Káňa jindr...@kana.at wrote: Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Looks like you are not that fluent in dual/multiple boot schemes. I would suggest that you buy another sata disk and install FBSD in one and Linux on the other and boot selection with your BIOS. Either that, or RTFM on multiple boot systems, whether it's booting FBSD from Linux (grub) or the other way around. You could start by Googling this: dual boot linux freebsd there are many references on the list archives on the subject and many other references as well. Best, Alejandro Imass Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Grub demage my boot loader
I love the RTFM - who came up with that anyway? That said Jindřich, your English is more than passable! Have a good weekend! G -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Alejandro Imass Sent: Friday, March 26, 2010 4:46 PM To: freebsd-questions@freebsd.org Subject: Re: Grub demage my boot loader On Fri, Mar 26, 2010 at 3:56 PM, Jindřich Káňa jindr...@kana.at wrote: Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Looks like you are not that fluent in dual/multiple boot schemes. I would suggest that you buy another sata disk and install FBSD in one and Linux on the other and boot selection with your BIOS. Either that, or RTFM on multiple boot systems, whether it's booting FBSD from Linux (grub) or the other way around. You could start by Googling this: dual boot linux freebsd there are many references on the list archives on the subject and many other references as well. Best, Alejandro Imass Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Unga [EMAIL PROTECTED] wrote: From: Unga [EMAIL PROTECTED] Subject: GRUB: Filesystem type unknown (ufs2) To: freebsd-questions@FreeBSD.org Date: Thursday, November 13, 2008, 6:24 PM Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Ok, found the problem. Its the newfs. The problem is GRUB cannot recognize ufs2 file systems created by newfs. The GRUB can recognize ufs2 file systems created by sysinstall. I have even tried newfs -O 2 -U /dev/ad2s1a, the GRUB still cannot recognize ufs2 file systems. Now the question is, how to properly create a ufs2 file system manually? Is it by newfs? Also appreciate if someone could let me know where does it create ufs2 file systems in sysinstall. Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thursday 13 November 2008, Unga wrote: --- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Yes, the root was UFS2. I don't know which version I used at the time. When I get home from work, I'll give it a try. -- Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 02:24:33AM -0800, Unga wrote: Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Do others experience this issue? Do I need to patch the Grub to recognize ufs2 file systems? Your reply is very much appreciated. How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. ftp://alpha.gnu.org/gnu/grub/ -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). It would be really cool if since you're working on getting GRUB2 working, you could make a port for it, e.g. sysutils/grub2. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thursday 13 November 2008, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: GRUB: Filesystem type unknown (ufs2) To: Unga [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Thursday, November 13, 2008, 7:21 PM On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). Well, I thought FreeBSD guys use GRUB. Its easy to communicate with those who use FreeBSD rather than those who use Linux and discuss mostly on a theoretical basis. I mostly wanted to know does GRUB works for other FreeBSD users. If so, I could investigate what went wrong on mine. Btw, I did not use the port, its straight away compiled from sources. That I mentioned as the first line in my original post. Regards Unga I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. -- Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: GRUB: Filesystem type unknown (ufs2) To: Unga [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Thursday, November 13, 2008, 7:21 PM On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). Well, I thought FreeBSD guys use GRUB. Its easy to communicate with those who use FreeBSD rather than those who use Linux and discuss mostly on a theoretical basis. I mostly wanted to know does GRUB works for other FreeBSD users. If so, I could investigate what went wrong on mine. Btw, I did not use the port, its straight away compiled from sources. That I mentioned as the first line in my original post. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
I'm using GRUB and it has no problem recognizing UFS2 slices. Same version than you, GRUB 0.97. Regards Ezequiel R. Aguerre 2008/11/13 Unga [EMAIL PROTECTED] --- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB / boot easy problems w / USB stick
Some thoughts: 1. bsdlabel -Brw /dev/da0s1 - What is the option r? - bsdlabel is supposed to create standard label which probably means creating da0s1a partition (can you call bsdlabel /dev/da0s1 to see what was created?) So your next command should be newfs /dev/da0s1a rather than newfs /dev/da0s1. And commands after that will need to be adjusted as well. 2. boot0cfg -B -s 1 -t -v 182 /dev/da0 It should be -v -t 182 rather than -t -v 182. Not sure if it matters though. Hope this helps. Andrey Thanks Andrey, great news! placing newfs on /dev/da0s1a instead of /dev/da0s1 really helped. Now GRUB recognizes the filesystem on my usb partition. Here's what's new. #I placed 1 UFS2 partition on my USB key at #/dev/da0s1a. mount /dev/da0s1a /usb mkdir -p /usb/boot/grub #copied all files from /boot to /usb/boot and all files #from /boot/grub to /usb/boot/grub (I know I can make #it smaller but just copying all for now). Next I #invoked the grub shell and did the following: grub root (hd1,0,a) Filesystem type is ufs2, partition type is 0xa5. grub setup (hd1) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd1)... 16 sectors are embedded. Succeeded Running install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0,a)/boot/grub/stage2 /boot/grub/menu.lst... Succeeded Done. #I reboot, and am excited to see the grub menu I've set #up. Here is my menu.lst: default=0 timeout=30 title NewOS root (hd0,0,a) kernel /boot/loader #You might notice I made root hd0. This is actually #helpful for anyone setting GRUB up for the first time. #You see when setting up grub from the shell within #your computer, your first hard drive is always hd0, #and your usb stick can be anything after that (in my #case hd1). You can test this by placing an oddly #named text file in each of your grub directories (1 in #hard drive, 1 in usb stick), then using find from the #grub shell to indicate where that oddly named file is #located: grub find /boot/grub/weirdfile (hd0,0,a) #The main point is that when you reboot to your USB #key, because it's now the first drive, it's probably #going to be hd0, instead of hdx, thus my menu.lst. # Anyway, back to the menu selection. When I choose the 'NewOS', this is what I get: Booting 'NewOS' root (hd0,0,a) Filesystem type is ufs2, partition type is 0xa5 kernel /boot/loader [FreeBSD-a.out, loadaddr=0x20, text=0x1000, data=0x32000, bss=0x0, entry=0x20] BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 631kB/980480kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (root @barney.msu.edu, Sun May 8 03:20:03 UTC 2006) #This is the last line, and if I wait about five #minutes it prints these additional lines: can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK _ #Again I'm pretty sure I must have the right 'hd' #addressing. I tested this by changing the root #location to (hd1,0,a) which found the boot loader off #of my hard drive and booted. I tested this by moving #the loader from my hard drive out of /boot, and #rebooting, where upon it couldn't find loader anymore. Alright I'll leave it there. (Starving for that little morsel of knowledge out there that will unlock this!) -Fred (p.s. I'm new to the mailing lists, and can't find the charter for any of the groups, anyone have a link? :) Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=listsid=396546091 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB / boot easy problems w / USB stick
It seems like this thread isn't getting updated when I post for some reason. This will be the last one I try until I figure out what's wrong. #I've done some more tests. In my last post I had booted # from the usb key. the results of lsdev from the boot #loader prompt were: OK lsdev cd devices: disk devices: disk0: BIOS drive C: disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS # If I booted from the hard drive first I got: cd devices: disk devices: disk0: BIOS Drive C: disk0s1a: FFS disk0s1b: swap disk1s1d: FFS disk1L BIOS Drive D: #So it's clear that which ever drive is booted from #first between the hard drive and the usb key drive is #going to show up as disk0: BIOS Drive C, but I was #wondering why the disk slices/partition letters for #the USB key don't #show up when I boot from it. Or #even when I boot from the HD and use the loader #prompt? # Again just to quickly restate the problem, when # booting from the USB key, the BTX loader hangs, and # after about 5 minutes I get the loader prompt. The # loader apparently can't find the kernel. When #booting normally I have double checked that the #bsdlabels, filesystems, and required files are at #least present on the key. # I'll keep learning the intimate details of various #config files, and loader commands, and post back if I #find a solution. Thanks again for any bits of know #how you send my way. -Fred Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB / boot easy problems w / USB stick
On 6/2/07, Fred Davidson [EMAIL PROTECTED] wrote: I am looking for some help to enable booting from a USB stick. After weeks of reading, and attempting I am at a total loss. This all began while I was trying to follow the many excellent tutorials on encrypting whole laptop disks with GELI[1]. These tutorials were great except they didn't really cover how to make the sticks bootable. Here is some of the many things I have tried. Background: My laptop BIOS allows me to pick the boot order from 7 devices, I set them as follows: (1) USB Key (2) USB HDD (3) USB CDROM (4) USB FDC (5) IDE CD (6) IDE HDD (7) PCI BEV Attempt 1: FreeBSD Boot Manager # created a dedicated slice on my 512MB stick with a #UFS2 filesystem. (after fdisk) bsdlabel -Brw /dev/da0s1 newfs /dev/da0s1 # Copied over boot files to usb filesystem. mount /dev/da0s1 /usb mkdir /usb/boot cd /boot cp -Rpv * /usb/boot # Placed FreeBSD boot manager on MBR of USB stick. boot0cfg -B -s 1 -t -v 182 /dev/da0 Problem: When I reboot the laptop keyboard won't allow me to select a partition with the F keys. Attempt 2: GRUB # make install grub from the ports collection. copy #over the files from #/usr/local/share/grub/i386-freebsd/* to /boot/grub. #My understanding was that Grub can read write UFS2 #because of patches since version 0.94. So on my first #attempt I made a single UFS2 partition. mount /dev/da0s1 /usb mkdir -p /usb/boot/grub cd /boot cp -Rpv * /usb/boot cd /boot/grub cp -Rpv * /usb/boot/grub #I invoke the grub shell. There are two devices in my #device map: (hd0) /dev/ad0 (hd1) /dev/da0 # Now if I try to set root in the following ways I'll #get the following: grub root (hd0,0,a) Filesystem type is ufs2, partition type 0xa5 grub root (hd1,0) Filesystem type is unknown, partition type 0xa5 # now before you say it, I also tried (hd1,0,a) but #this is even worse in some situations. Basically I #can't get grub to read or write to the USB stick with #a UFS2 filesystem. Yet it will read write to the #UFS2 filesystem of the native disk. Does anyone know #why? I have tried grub-install which apparently is #successful, but once I attempt to reboot, it hangs #with the word, GRUB printed. Attempt 3: Chainloading GRUB #This time I though I had it. I created S1 FAT #partition and S2 UFS2 partition on the stick. I # was able to use setup from the grub shell to setup #the FAT slice as the location for stage2. On the #ufs2 partition I set up the proper /boot setup above. #I read on an old post and someone mentioned that #boot2 does something stupid, and won't work with a #chainload scenario. I tried it anyways, and it didn't #work. I had heard that it might work if you bounce #boot0 to the beginning of the slice instead of the #disk MBR so I did. boot0cfg -B -s 2 -t 182 -v /dev/da0s2 #seemed to go well. I rebooted, and got as far as #the F key menu, but again nothing worked, and I #couldn't boot. Just to add, I also tried the whole booting FreeBSD from a FAT partition but that just plain doesn't work [2]. Well that's where I am. I can't tell you how much you will rock my world if you can show me how to fix this. These are some ideas I have, but don't know enough to do anything about: (1) BIOS issues; from what I understand each computer manufacturer takes a base bios (phoenix in my case) and proprietories it up. I'm dreading that maybe my BIOS will prevent any of this from working. Doesn't seem to be documentation anywhere on my manufac's site. (2) Bootblocks; Maybe there's some easy modifications or config files for boot blocks I don't know about? Maybe there are some alternatives? (3) GRUB patches; I've been downloading ports from another PC (no network yet)burning to CD, then making. done it twice now. Is there some wonderful patch to GRUB that makes it work with FreeBSD I don't know about? Do any of you have it working? if so , can I copy how you built exactly? Alright, that's all. I'm sorry for the length of this post, it's my first one, and I have seriously dredged pretty hard on my own for a solution. Thanks again. Fred [1] http://www.proportion.ch/index.php?page=31 http://www.daimi.au.dk/~u063592/ http://www.bsdforums.org/forums/showthread.php?threadid=43796 [2] http://docs.FreeBSD.org/cgi/mid.cgi?2002003159.A46044 Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Some thoughts: 1. bsdlabel -Brw /dev/da0s1 - What is the option r? - bsdlabel is supposed to create standard label which probably means creating da0s1a partition (can you call
Re: grub
In the last episode (May 29), Richard Knebel said: I had freebsd installed on my 1st hardrive withour difficuties. I then installed Debian Linux on my 2nd hard drive and the grub bootloader overwrote my mbr and now I can only boot debian. How can I get my freebsd back ? Assuming grub is functional, you might want to just keep it and add another entry like this: title FreeBSD root (hd1,1,a) kernel /boot/loader savedefault replacing (hd1,1,a) with whatever find /boot/loader at the grub CLI returns. If your grub doesn't have UFS support, then the find and kernel commands won't work, and you'll have to chainload to the FreeBSD slice's bootblock instead of using the kernel command. If you really want booteasy back, boot into FreeBSD and run boot0cfg -B /dev/ad0 (or whatever your 1st hardrive's device is) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub
On 5/30/07, Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (May 29), Richard Knebel said: I had freebsd installed on my 1st hardrive withour difficuties. I then installed Debian Linux on my 2nd hard drive and the grub bootloader overwrote my mbr and now I can only boot debian. How can I get my freebsd back ? Assuming grub is functional, you might want to just keep it and add another entry like this: title FreeBSD root (hd1,1,a) kernel /boot/loader savedefault replacing (hd1,1,a) with whatever find /boot/loader at the grub CLI returns. If your grub doesn't have UFS support, then the find and kernel commands won't work, and you'll have to chainload to the FreeBSD slice's bootblock instead of using the kernel command. If you really want booteasy back, boot into FreeBSD and run boot0cfg -B /dev/ad0 (or whatever your 1st hardrive's device is) -- Dan Nelson [EMAIL PROTECTED] Boot into your linux box, edit /boot/grub/menu.lst And add the following lines: title FreeBSD root (hd0,1)# this changes based on where on the partition/drive the FreeBSD is installed. chainloader +1 savedefault run, # grub-install /dev/hda # sda if sata disk reboot. this should help to solve your problem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
On Aug 21, 2006, at 6:41 PM, backyard wrote: --- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian Ok, it seems like your installation process at least is ok; perhaps the location of the installed grub is incorrect though. Could you do the following? 1. Run fdisk and verify that the partition you actually have your root installed on is the first one. 2. Replace all references to just / (root) in all partition names to the proper device name, plus root, e.g.: root (hd0,0,a) kernel (hd0,0,a)/boot/loader I know it seems a bit redundant, but it's saved me from some issues with installing grub on my linux box. 3. Remove the splashedimage reference. It's referring to your floppy and if the floppy isn't there I could see some possible issues occurring with booting grub, as you mentioned earlier in the email. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
--- Garrett Cooper [EMAIL PROTECTED] wrote: On Aug 21, 2006, at 6:41 PM, backyard wrote: --- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian Ok, it seems like your installation process at least is ok; perhaps the location of the installed grub is incorrect though. Could you do the following? 1.Run fdisk and verify that the partition you actually have your root installed on is the first one. 2.Replace all references to just / (root) in all partition names to the proper device name, plus root, e.g.: root (hd0,0,a) kernel (hd0,0,a)/boot/loader I know it seems a bit redundant, but it's saved me from some issues with installing grub on my linux box. 3.Remove the splashedimage reference. It's referring to your floppy and if the floppy isn't there I could see some possible issues occurring with booting grub, as you mentioned earlier in the email. -Garrett I'll give this a whirl and report back as to what happens, but I think I just have one of the machines that grub just doesn't like very much. Its just a good thing it happened to be the one machine I have that will never see anything but BSD on it. Like I said GRUB was just to put an inappropriate splash screen up to tick off my friends should they ever turn the thing on with a monitor plugged into it... That being said it's still annoying when things don't work out the way you want. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
--- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garret #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub on FreeBSD
Nikolas Britton [EMAIL PROTECTED] writes: IIRC grub can't see UFS2, only UFS. I belive there is a work around though. google for it GRUB has been able to read UFS2 filesystems for a long time. That doesn't help Ask with his particular problem though. -- Christian Laursen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub on FreeBSD
On Mon, 29 May 2006, Ask Bj?rn Hansen wrote: Hi, I am trying to use grub instead of the usual boot0 thing on a Compact Flash card I use in Soekris and PC Engines WRAP systems. I installed grub from ports/sysutils/grub and put the package on my nanobsd system on the CF card. Booting on a Soekris box and running grub, I get this: grub root (hd0,1) Filesystem type unknown, partition type 0xa5 grub root (hd0,1,a) Filesystem type unknown, partition type 0xa5 It seems like it can't read the ufs filesystem? Any ideas? Did you copy the stage1, stage2, and ufs2_stage1_5 files to /boot/grub on the CF card? As I understand it, grub needs these files to understand UFS2. Just a guess. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub on FreeBSD
On 5/29/06, Ask Bjørn Hansen [EMAIL PROTECTED] wrote: Hi, I am trying to use grub instead of the usual boot0 thing on a Compact Flash card I use in Soekris and PC Engines WRAP systems. I installed grub from ports/sysutils/grub and put the package on my nanobsd system on the CF card. Booting on a Soekris box and running grub, I get this: grub root (hd0,1) Filesystem type unknown, partition type 0xa5 grub root (hd0,1,a) Filesystem type unknown, partition type 0xa5 It seems like it can't read the ufs filesystem? Any ideas? IIRC grub can't see UFS2, only UFS. I belive there is a work around though. google for it -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub+freebsd
+++ serge [freebsd] [28-01-06 15:53 +0300]: | Hi | | Help to install please grub-0.95 on FreeBSD-5.4. | At attempt to install grub the following message is deduced: Error 29: Disk write error | | | Part Mount Size Newfs | - - - - | ad0s1none 30003MB DOS | ad0s2a /256MB UFS2 Y | ad0s2b SWAP 1006MBSWAP | ad0s2d /var 256MB UFS2+S Y | ad0s2e /tmp 256MB UFS2+S Y | ad0s2f /usr 6383MBUFS2+S Y | | | offset SizeEndName PTypeDesc Sutype | -- --- - -- | 0 63 62 - 12 unused0 | 63 6144761761447679 ad0s1 7fat 12 | 61447680 1670760078155279 ad0s2 165 freebsd 165 | 78155280 10080 78165359 - 12 unused0 | | | # grub | grub root (hd0,1,a) | File system type is ufs2, partition type 0xa5 | grub kernel /boot/loader | [FreeBSD-a .out, loadaddr=0x2,text=0x1000, data=0x32000, bss=0x0, | entry=0x20] | grubboot | # | | And another: | | #grub-install /dev/hd0 | grub root (hd0,1,a) | File system type is ufs2, partition type 0xa5 | grubsetup --stage2=/boot/grub/stage2 --prefix=/boot/grub (hd0) | Checking if /boot/grub/stage1exists.yes | Checking if /boot/grub/stage2exists.yes | Checking if /boot/grub/ufs2_stage1_5..exists.yes | Running embed /boot/grub/ufs2_stage1_5 (hd0)...failed (this is not fatal) | Running embed /boot/grub/ufs2_stage1_5 (hd0,1,a)...failed (this is not fatal) | Running install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) | /boot/grub/stage2 p /boot/grub.lst...failed | | ***Error 29: Disk write error | | grubquite | # | | In what here a problem, prompt please. IIRC, you need to change sysctl setting of 'kern.geom.debugflags' from 0 to 16. Shantanoo pgpH2ZgSvDfnj.pgp Description: PGP signature
Re: grub doesn't know ufs filesystem
On Wednesday 14 December 2005 21:42, Micah wrote: I used chainloading for a while until I wanted multiple installs of FreeBSD on the same drive. Using chainloading from grub always booted the first FreeBSD regardless of which slice was specified in menu.lst. Changing it to use /boot/loader allowed me to actually have more than one FreeBSD on the same drive. I pretty sure you did something wrong, I've chainloaded multiple FreeBSD slices on the same drive using Lilo and other bootloaders. Also, grub places some files on a host filesystem. It may be more convenient to have those files stored on UFS rather than FAT or EXT. ... In that case, if you use grub (rather than FreeBSD's manager), you'd have to make a partition solely for grub. But is it a good idea for a bootloader to require external files at boot-time? I assume there are cases were grub does things that other loaders can't, but it seems to me that for most people booting FreeBSD it's an overcomplicated and awkward solution. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
Hi Micah and Harley, Thanks for your answer. Humm.. I don't have any other grub on my path, and running which returns: # which grub /usr/local/sbin/grub The ports were updated quite recently.. in occasion of last update world. I did some more testing.. the strange thing is that I use the same grub boot floppy and the results are ok on the newly installed freebsd boxes, while on the two that are already installed the results are bad.. test 1: === - made a grub floppy - boot the existing FreeBSD boxes (2 boxes) from grub floppy result -- grub doesn't know the ufs filesystem test 2: === - installed a brand new FreeBSD 5-3-RELEASE with default partitioning on the whole disk on a separate pc - boot with grub floppy result -- grub recognizes the ufs filesystem test 3: === - same as test2, but / root has now soft-updates option - boot with grub floppy result -- grub recognizes the ufs filesystem test 4: === - same as test2, but partitioning done with partition magic as was done on the computers of test1 - boot with grub floppy result -- grub recognizes the ufs filesystem All that seams to point out that there's something wrong with the existing FreeBSD boxes.. but What? I must say that both boxes had all filesystem dumped and restored after repartitioning for permitting the use of dumping software such as ghost (that didn't like the partitioning done by freebsd during installation..) Any more ideas? Harley D. Eades III wrote: On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not, issue /usr/local/sbin/grub from a command prompt and duplicate your test. If that's broken, make sure your ports tree is up to date, make sure /usr/ports/devel/autoconf259 /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date (grub's build dependancies) then deinstall, clean, and reintsall the grub port. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I can second this, I use grub all the time, as well as test grub2 on FreeBSD and both work great for me. --Harley -BEGIN GEEK CODE BLOCK- G: GCS-- d- a? C B- E+++ W+++ N++ w--- X+++ b++ G e* r x+ z+ --END GEEK CODE BLOCK-- -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To
Re: grub doesn't know ufs filesystem
One more note.. let's call 'bad' the pc that grub doesn't like and ok the others.. and note that the two pc have identical disk drives.. so.. bad# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 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=29777 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 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ok# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 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=29777 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 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 3/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED as you can see, there's a difference in the end head.. bad says end head is 254, while ok says end head is 3 Could that be a source of trouble? bad# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 1048576 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15728644.2BSD 2048 16384 32776 e: 524288 20971524.2BSD 2048 16384 32776 f: 27387917 26214404.2BSD 2048 16384 28552 ok# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 996992 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15212804.2BSD 2048 16384 32776 e: 524288 20455684.2BSD 2048 16384 32776 f: 27387917 25698564.2BSD 2048 16384 28552 the disklabel is essentialy the same.. apart from the size of the swap and consequently the offset of the rest of the internal partitions.. Again.. any ideas? -- Robi Harley D. Eades III wrote: On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not,
Re: grub doesn't know ufs filesystem
Roberto Nunnari wrote: One more note.. let's call 'bad' the pc that grub doesn't like and ok the others.. and note that the two pc have identical disk drives.. so.. bad# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 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=29777 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 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ok# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 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=29777 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 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 3/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED as you can see, there's a difference in the end head.. bad says end head is 254, while ok says end head is 3 Could that be a source of trouble? bad# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 1048576 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15728644.2BSD 2048 16384 32776 e: 524288 20971524.2BSD 2048 16384 32776 f: 27387917 26214404.2BSD 2048 16384 28552 ok# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 996992 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15212804.2BSD 2048 16384 32776 e: 524288 20455684.2BSD 2048 16384 32776 f: 27387917 25698564.2BSD 2048 16384 28552 the disklabel is essentialy the same.. apart from the size of the swap and consequently the offset of the rest of the internal partitions.. Again.. any ideas? -- Robi Harley D. Eades III wrote: On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get
Re: grub doesn't know ufs filesystem
On Wed, Dec 14, 2005 at 03:52:33PM +0100, Roberto Nunnari wrote: grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader You are correct. Old versions of grub don't know about UFS2 filesystem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not, issue /usr/local/sbin/grub from a command prompt and duplicate your test. If that's broken, make sure your ports tree is up to date, make sure /usr/ports/devel/autoconf259 /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date (grub's build dependancies) then deinstall, clean, and reintsall the grub port. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not, issue /usr/local/sbin/grub from a command prompt and duplicate your test. If that's broken, make sure your ports tree is up to date, make sure /usr/ports/devel/autoconf259 /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date (grub's build dependancies) then deinstall, clean, and reintsall the grub port. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I can second this, I use grub all the time, as well as test grub2 on FreeBSD and both work great for me. --Harley -BEGIN GEEK CODE BLOCK- G: GCS-- d- a? C B- E+++ W+++ N++ w--- X+++ b++ G e* r x+ z+ --END GEEK CODE BLOCK-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
On Wednesday 14 December 2005 16:36, Micah wrote: Some of the grubs that ship with Linux distros do not support ufs. I'm curious as to why people care about this so much. There are numerous threads about whether or not particular bootloaders support UFS. A bootloader needs to understand Linux filesystems to boot Linux off a logical partition, but BSDs slices are always on primary partitions. Is there really any advantage to going directly to /boot/loader, rather than simply chaining? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
RW wrote: On Wednesday 14 December 2005 16:36, Micah wrote: Some of the grubs that ship with Linux distros do not support ufs. I'm curious as to why people care about this so much. There are numerous threads about whether or not particular bootloaders support UFS. A bootloader needs to understand Linux filesystems to boot Linux off a logical partition, but BSDs slices are always on primary partitions. Is there really any advantage to going directly to /boot/loader, rather than simply chaining? I used chainloading for a while until I wanted multiple installs of FreeBSD on the same drive. Using chainloading from grub always booted the first FreeBSD regardless of which slice was specified in menu.lst. Changing it to use /boot/loader allowed me to actually have more than one FreeBSD on the same drive. Also, grub places some files on a host filesystem. It may be more convenient to have those files stored on UFS rather than FAT or EXT. Or you may have a system that consists only of multiple FreeBSD installs. In that case, if you use grub (rather than FreeBSD's manager), you'd have to make a partition solely for grub. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub not working
In the last episode (Jul 28), Gary W. Swearingen said: Benjamin Lutz [EMAIL PROTECTED] writes: Two guesses: - You can't write to a disks MBR while it's being used. I've seen this myself, but I'm not exactly why this is, or how it can be circumvented (other than booting from another device). Yes. It wasn't always this way. It's easy to turn off, though, and is even documented in grub's pkg-message file: To install GRUB on the master boot record of your hard drive use 'grub-install drive-to-install' command. NOTE: Don't forget to run 'sysctl kern.geom.debugflags=16' on 5.x and -CURRENT to enable writing in hard disk system areas. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub not working
Valerio daelli wrote: I am trying to install grub as a boot loader on my disk. I installed it from ports. When I try to install it on the MBR I get the error [...] Error 29: Disk write error Two guesses: - You can't write to a disks MBR while it's being used. I've seen this myself, but I'm not exactly why this is, or how it can be circumvented (other than booting from another device). - You have MBR protection (Virus Protection) in your BIOS enabled. Cheers Benjamin signature.asc Description: OpenPGP digital signature
Re: Grub not working
Benjamin Lutz [EMAIL PROTECTED] writes: Two guesses: - You can't write to a disks MBR while it's being used. I've seen this myself, but I'm not exactly why this is, or how it can be circumvented (other than booting from another device). Yes. It wasn't always this way. You can make a gruby boot floppy and from its command line, install to the MBR. You might have to mess around with storing the grub files in /boot/boot/grub instead of /boot/grub or something; see the grub info or just try it both ways. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub and NTFS
RdBSD wrote: Dear all, Can I use grub to boot windows 2003 server with ntfs file system ? The FreeBSD boot loader will boot windows/ntfs. There are lots of mentions of grub in the archives so probably it will. Why not google for the grub home page? --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub and NTFS
On Wednesday 15 June 2005 02:38, RdBSD wrote: Can I use grub to boot windows 2003 server with ntfs file system ? My understanding is that Windows is always installed on a standard bootable primary partition, so the bootmanager doesn't need to understand the filesystem or the details of the OS's boot process. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB problems
In the last episode (Apr 27), Michael Thaler said: Hello, I just installed PC-BSD which is based on FreeBSD5.3, but comes with a graphical installer. I already have Windows XP and Debian Linux installed on my computer, so I could not install PC-BSD in a primary partition at the beginning of the disk. Instead I created a new primary partition at the end of the disk. I now have the following disk layout: hda3 PrimaryFreeBSD I have the following two entries in /boot/grub/menu.lst: title PC-BSD root (hd0,2,a) kernel /boot/loader With both entries I cannot boot. I get the following error messages: Entry 2: Filesystem type unknown, partition type 0xa5 kernel /boot/loader Error 17: cannot mount selected partition Is there anything I can do to get this working? You probably don't have ufs support built into grub. I find it easier to just chain to the bootblock instead: root(hd0,2) chainloader +1 -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB problems
On Wednesday 27 April 2005 21:54, Dan Nelson wrote: You probably don't have ufs support built into grub. I find it easier to just chain to the bootblock instead: root(hd0,2) chainloader +1 That did the trick! Thank you very much! So far I am quite pleased with PC-BSD. The installation took me less than half an hour, the graphical installation is quite nice (even though it should mention somewhere that you MUST install FreeBSD on a primary partition) and PC-BSD booted fine, recognized my soundcard and came up with a nice KDE3.4. The only thing I had to do was change the resolution and the driver (vesa is not a good idea if you have an ATI card) in XF86Config. The next thing I have to do is to get the network working (actually I have an ISDN router, so this should not be a big deal). And then I should probably start reading the nice handbook:-) Greetings, Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB problems
Michael Thaler wrote: (even though it should mention somewhere that you MUST install FreeBSD on a primary partition) Hello, read http://www.freebsd.org/doc/de/books/handbook/disk-organization.html The slice/partition issue is one of the most confusing things for beginners. Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub and FreeBSD
In the last episode (Nov 04), Briggaman, Jason said: I'm trying to get Grub running on 5.3-rc2 but I keep getting Error 29: Disk write error. I'm trying to install it directly to the MBR. I can't use the floppy method because there is one. I can use the FreeBSD loader but I'd like to use grub. This is the only OS on the laptop. If anyone has any suggestions I'd appreciate it. I always make a grub boot disk, then install onto the hard drive from that. I don't trust the userland grub CLI to get my devicenames right. But if you have only one OS, there's no need for grub at all.. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
On Sun, Jul 04, 2004 at 12:19:23AM -0400, Bruce Hunter wrote: Hey, Thanks for you help. I figured out my problem. I was trying to install grub to (hd0) while running gnome. I read some more of the manual for grub and realized that I had to create a floppy disk to do the installation. So, I created the floppy and rebooted and ran the commands again and everything went well. Hm, then I think Grub cannot write to your HD when it is mounted. Or something like that. Anyway, that step has to be performed just once. You can always change your configfile, Grub will read it in at boot time. The only thing is. It doesn't use grub.conf, it uses menu.lst to create the menu. Ok. Then grub.conf was used in older versions. I thought it was the other way around, but I always just symlinked one to the other. Would I be able to use the installation of RedHat Core 2's grub, to make my grub look pretty? I also, noticed that RedHat has a pretty little thing or gui when booting up. How would I integrate that to FreeBSD? The difference is in their configfile, it probably uses colors and some background. Try grub bootsplash on Google and you'll find plenty of howto's. Thanks man, Bruce Happy to help you, GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
On Sat, Jul 03, 2004 at 03:01:07PM -0400, Bruce Hunter wrote: Happy 4th! okay, now that's out of the way. I am bored with freebsds' boot loader and want to install Grub from the ports collection. My question is: When grub installs, will it find my partitions and set everything up for me? So, when I reboot grub is working. Here is my hard drive setup Partition 0 ) 5g: Windows 2k Partition 1 ) 35g: Freebsd 5.2.1 Thanks guys, Bruce No, when you install Grub from ports, it will only install some commandline-tool, nothing will be changed to your configuration. You will need this commandline-tool to install Grub into your MBR. If you want a menu at boot, you will also have to create a textfile describing the various menu-items (different OS'es or just different kernels for example). All this may seem rather complicated, but once you get it, it's pretty easy. It's also very powerful. Just checkout the documentation (it's very well documented). If you have installed Grub from ports, just do info grub and you'll get all you need to know, with lots of examples too. (Remember you don't have to be afraid to install Grub from the ports, as it will change nothing to your system automatically.) GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
title FreeBSD 5.2.1 root (hd0,2,a) kernel /boot/loader Sorry, this should be (hd0,1,a) ! The first slice (windows) is (hd0,0) and the second is (hd0,1), and you want the root-partition within that (hd0,1,a). GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
On Sat, 2004-07-03 at 16:17, Geert Hendrickx wrote: title FreeBSD 5.2.1 root (hd0,2,a) kernel /boot/loader Sorry, this should be (hd0,1,a) ! The first slice (windows) is (hd0,0) and the second is (hd0,1), and you want the root-partition within that (hd0,1,a). GH ___ I have read a few instructions from info grub. I am a little confuzed. There are so many different ways to do this. One way is grub-install /dev/hd0 or stages. except hd0 is not a device under freebsd. I am trying to install it to the mbr. At least I think that's where I should install it. i believe ad0s1 is windows and ad0s2 is freebsd --- [EMAIL PROTECTED] grub-install /dev/ad0/ Probing devices to guess BIOS drives. This may take a long time. /dev/ad0/: Not found or not a block device. [EMAIL PROTECTED] grub-install /dev/hd0 /dev/hd0: Not found or not a block device. [EMAIL PROTECTED] grub-install /dev/ad0 /dev/ad0 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s1 /dev/ad0s1 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s1 /dev/ad0s1 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s2 /dev/ad0s2 does not have any corresponding BIOS drive. -- just a little confuzed.. :o/ Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
On Sat, Jul 03, 2004 at 05:35:35PM -0400, Bruce Hunter wrote: On Sat, 2004-07-03 at 16:17, Geert Hendrickx wrote: title FreeBSD 5.2.1 root (hd0,2,a) kernel /boot/loader Sorry, this should be (hd0,1,a) ! The first slice (windows) is (hd0,0) and the second is (hd0,1), and you want the root-partition within that (hd0,1,a). GH ___ I have read a few instructions from info grub. I am a little confuzed. There are so many different ways to do this. One way is grub-install /dev/hd0 or stages. except hd0 is not a device under freebsd. I am trying to install it to the mbr. At least I think that's where I should install it. i believe ad0s1 is windows and ad0s2 is freebsd --- [EMAIL PROTECTED] grub-install /dev/ad0/ Probing devices to guess BIOS drives. This may take a long time. /dev/ad0/: Not found or not a block device. [EMAIL PROTECTED] grub-install /dev/hd0 /dev/hd0: Not found or not a block device. [EMAIL PROTECTED] grub-install /dev/ad0 /dev/ad0 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s1 /dev/ad0s1 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s1 /dev/ad0s1 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s2 /dev/ad0s2 does not have any corresponding BIOS drive. -- just a little confuzed.. :o/ Bruce The easiest way (in my opinion) to install Grub is with the interactive tool. Just run grub from the commandline, and you'll be dropped in the same interactive environment you will enter upon booting when you have no grub.conf (or grub cannot find it). The commands you can enter here, are the same as in the grub.conf. The first thing you have to do is copy the stagefiles from /usr/local/share/grub/i386-freebsd/ to a directory called /boot in either of your partitions (Grub can read many filesystems, including UFS, FAT and NTFS). Also put your grub.conf in that directory. Then start grub from the commandline, so you'll get the Grub-prompt. If your boot-directory is on your Windows-drive (C:\BOOT), then you must enter root (hd0,0) (the Windows-slice), if it is on FreeBSD, then use root (hd0,1,a) (your root-partition on FreeBSD). Grub will then check if the necessary files are there, and tell you if not. If the files are indeed there, you can install the stage1 into the MBR with setup (hd0). Stage1 is just a pointer to stage2 (which actually contains Grub), but that one is too big to fit inside the MBR, so it must be on one of your filesystems (in the /boot directory, so that the stage1 can find it). You could also install Grub into a partition (e.g. setup (hd0,1)), but that way Grub will not show up at boot, only when you explicitly chainload that partition (using another bootloader e.g. FreeBSD's). P.S. 1: the grub.conf file is completely optional, so Grub will not complain if it's not there, you will simply be dropped at the Grub- commandline at your next reboot. There you could enter the exact same commands as in the config-file, e.g. root (hd0,1,a) and kernel /boot/loader to boot FreeBSD. But you'll have to confirm with the command boot. P.S. 2: The Grub-commandline provides tab-completion for both devices and files. So, to see all your partitions (and their filesystem-types), you could enter ( + Tab. GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
On Sat, 2004-07-03 at 18:02, Geert Hendrickx wrote: On Sat, Jul 03, 2004 at 05:35:35PM -0400, Bruce Hunter wrote: On Sat, 2004-07-03 at 16:17, Geert Hendrickx wrote: title FreeBSD 5.2.1 root (hd0,2,a) kernel /boot/loader Sorry, this should be (hd0,1,a) ! The first slice (windows) is (hd0,0) and the second is (hd0,1), and you want the root-partition within that (hd0,1,a). GH ___ I have read a few instructions from info grub. I am a little confuzed. There are so many different ways to do this. One way is grub-install /dev/hd0 or stages. except hd0 is not a device under freebsd. I am trying to install it to the mbr. At least I think that's where I should install it. i believe ad0s1 is windows and ad0s2 is freebsd --- [EMAIL PROTECTED] grub-install /dev/ad0/ Probing devices to guess BIOS drives. This may take a long time. /dev/ad0/: Not found or not a block device. [EMAIL PROTECTED] grub-install /dev/hd0 /dev/hd0: Not found or not a block device. [EMAIL PROTECTED] grub-install /dev/ad0 /dev/ad0 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s1 /dev/ad0s1 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s1 /dev/ad0s1 does not have any corresponding BIOS drive. [EMAIL PROTECTED] grub-install /dev/ad0s2 /dev/ad0s2 does not have any corresponding BIOS drive. -- just a little confuzed.. :o/ Bruce The easiest way (in my opinion) to install Grub is with the interactive tool. Just run grub from the commandline, and you'll be dropped in the same interactive environment you will enter upon booting when you have no grub.conf (or grub cannot find it). The commands you can enter here, are the same as in the grub.conf. The first thing you have to do is copy the stagefiles from /usr/local/share/grub/i386-freebsd/ to a directory called /boot in either of your partitions (Grub can read many filesystems, including UFS, FAT and NTFS). Also put your grub.conf in that directory. Then start grub from the commandline, so you'll get the Grub-prompt. If your boot-directory is on your Windows-drive (C:\BOOT), then you must enter root (hd0,0) (the Windows-slice), if it is on FreeBSD, then use root (hd0,1,a) (your root-partition on FreeBSD). Grub will then check if the necessary files are there, and tell you if not. If the files are indeed there, you can install the stage1 into the MBR with setup (hd0). Stage1 is just a pointer to stage2 (which actually contains Grub), but that one is too big to fit inside the MBR, so it must be on one of your filesystems (in the /boot directory, so that the stage1 can find it). You could also install Grub into a partition (e.g. setup (hd0,1)), but that way Grub will not show up at boot, only when you explicitly chainload that partition (using another bootloader e.g. FreeBSD's). P.S. 1: the grub.conf file is completely optional, so Grub will not complain if it's not there, you will simply be dropped at the Grub- commandline at your next reboot. There you could enter the exact same commands as in the config-file, e.g. root (hd0,1,a) and kernel /boot/loader to boot FreeBSD. But you'll have to confirm with the command boot. P.S. 2: The Grub-commandline provides tab-completion for both devices and files. So, to see all your partitions (and their filesystem-types), you could enter ( + Tab. GH Thanks for the help, I think I will be able to get it working now, after that information. The only question I have or comment is. Shouldn't I have the stages and grub.conf in /boot/grub ? You said /boot. Just wondering which it is. Thanks again.. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
Thanks for the help, I think I will be able to get it working now, after that information. The only question I have or comment is. Shouldn't I have the stages and grub.conf in /boot/grub ? You said /boot. Just wondering which it is. Thanks again.. Bruce I'm sorry, you're right. (I don't use Grub with FreeBSD, I used it with Linux all the time, but it's been a while...) GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
I moved all the files and ran the commands that you said. I am having this problem. GNU GRUB version 0.95 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,1,a) Filesystem type is ufs2, partition type 0xa5 grub setup (hd0) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd0)... failed (this is not fatal) Running embed /boot/grub/ufs2_stage1_5 (hd0,1,a)... failed (this is not fata l) Running install /boot/grub/stage1 (hd0) /boot/grub/stage2 p /boot/grub/menu.l st ... failed Error 29: Disk write error grub Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
Seems as you don't have write permission for /dev/ad0. Did you run grub as root? GH On Sat, Jul 03, 2004 at 07:21:45PM -0400, Bruce Hunter wrote: I moved all the files and ran the commands that you said. I am having this problem. GNU GRUB version 0.95 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,1,a) Filesystem type is ufs2, partition type 0xa5 grub setup (hd0) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd0)... failed (this is not fatal) Running embed /boot/grub/ufs2_stage1_5 (hd0,1,a)... failed (this is not fata l) Running install /boot/grub/stage1 (hd0) /boot/grub/stage2 p /boot/grub/menu.l st ... failed Error 29: Disk write error grub Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub installation from the ports collection vs. Freebsd boot loader
Hmm.. I'm root I even tried changing the permissions on /dev/ad0 the device has read and write access.. wierd. Maybe instead of setup (hd0) it should be setup (ad0) But device.map sets the hd0 pointer to /dev/ad0 any other ideas? Bruce On Sat, 2004-07-03 at 19:31, Geert Hendrickx wrote: Seems as you don't have write permission for /dev/ad0. Did you run grub as root? GH On Sat, Jul 03, 2004 at 07:21:45PM -0400, Bruce Hunter wrote: I moved all the files and ran the commands that you said. I am having this problem. GNU GRUB version 0.95 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,1,a) Filesystem type is ufs2, partition type 0xa5 grub setup (hd0) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd0)... failed (this is not fatal) Running embed /boot/grub/ufs2_stage1_5 (hd0,1,a)... failed (this is not fata l) Running install /boot/grub/stage1 (hd0) /boot/grub/stage2 p /boot/grub/menu.l st ... failed Error 29: Disk write error grub Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub problem
Errors on the root will still occur. Grub does that. With BSD, you can set the menu option such as : root (hd0,2) chainloader +1 And it will load the MBR from the BSD partition, which will load the loader, which will load the kernel (the best way, really). Joe Robert Storey wrote: Use the chainloader command to start FBSD, like this: root (hd0,2,a) chainloader +1 boot best regards, Robert On Mon, 02 Feb 2004 01:42:02 -0300 Roy Fokker [EMAIL PROTECTED] wrote: Hi, i have installed in my computer FBSD 5.1, and RH9. The thing is, when i try to get GRUB to boot FBSD, i get the following error message: root (hd0,2,a) Filesystem type unknown, partition type 0xa5 Then, in the GRUB-shell, i get this from auto-completion. Partition num: 2, [BSD sub-partitions immediately follow] BSD Partition num:'a', Filesystem type unknown, partition type 0xa5 BSD Partition num:'b', Filesystem type unknown, partition type 0xa5 BSD Partition num:'d', Filesystem type unknown, partition type 0xa5 BSD Partition num:'e', Filesystem type unknown, partition type 0xa5 BSD Partition num:'f', Filesystem type unknown, partition type 0xa5 And i'm guessing that it is because of this, it then grub kernel /boot/loader ro root=/dev/hda3 Error 17: Cannot mount selected partition This is an extract of my grub.conf. I looked for info about this, and found no other reference. title FreeBSD 5.1 Release root (hd0,2,a) kernel/boot/loader ro root=/dev/hda3 I will appreciate any input. Thanks. Alejandro, from BA, Argentina. _ Nuevo MSN Messenger [1]Una forma rápida y divertida de enviar mensajes References 1. http://g.msn.com/8HMBESAR/2728??PS= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub problem
Use the chainloader command to start FBSD, like this: root (hd0,2,a) chainloader +1 boot best regards, Robert On Mon, 02 Feb 2004 01:42:02 -0300 Roy Fokker [EMAIL PROTECTED] wrote: Hi, i have installed in my computer FBSD 5.1, and RH9. The thing is, when i try to get GRUB to boot FBSD, i get the following error message: root (hd0,2,a) Filesystem type unknown, partition type 0xa5 Then, in the GRUB-shell, i get this from auto-completion. Partition num: 2, [BSD sub-partitions immediately follow] BSD Partition num:'a', Filesystem type unknown, partition type 0xa5 BSD Partition num:'b', Filesystem type unknown, partition type 0xa5 BSD Partition num:'d', Filesystem type unknown, partition type 0xa5 BSD Partition num:'e', Filesystem type unknown, partition type 0xa5 BSD Partition num:'f', Filesystem type unknown, partition type 0xa5 And i'm guessing that it is because of this, it then grub kernel /boot/loader ro root=/dev/hda3 Error 17: Cannot mount selected partition This is an extract of my grub.conf. I looked for info about this, and found no other reference. title FreeBSD 5.1 Release root (hd0,2,a) kernel/boot/loader ro root=/dev/hda3 I will appreciate any input. Thanks. Alejandro, from BA, Argentina. _ Nuevo MSN Messenger [1]Una forma rápida y divertida de enviar mensajes References 1. http://g.msn.com/8HMBESAR/2728??PS= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub
This is the config: root (hd1,3,a) kernel /boot/loader I'm running release 5.1. Is there something other to do ?? Thanks for your help. mess-mate Grub does not support UFS2 currently. The solution is to use UFS1 for the root partition, then everything works fine. IIRC to achive you have to select Custom Options while creating the partitions and replace -02 with -01. Bye Stefan Or you can just use the following: title FreeBSD RELEASE 5.1 rootnoverify (hd1,3) chainloader +1 Don't know if there are any practical differences.. -- Herculano de Lima Einloft Neto [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub
Hi Stefan, a little : makeactive chainloader +1 and there we go !! A debian-user give me the tip. A+ mess-mate On Sun, 31 Aug 2003 23:25:14 +0200 Stefan Malte Schumacher [EMAIL PROTECTED] wrote: | On Sun, Aug 31, 2003 at 22:47:00 +0200, mess-mate wrote: | Hi list, | Can't boot FreeBSD from the grub bootloader. | Error 17 : can't mount selected . | This is the config: | root (hd1,3,a) | kernel /boot/loader | I'm running release 5.1. | Is there something other to do ?? | Thanks for your help. | mess-mate | | Grub does not support UFS2 currently. The solution is to use UFS1 for the | root partition, then everything works fine. IIRC to achive you have to | select Custom Options while creating the partitions and replace -02 with | -01. | | Bye | Stefan | ___ | [EMAIL PROTECTED] mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-questions | To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub
mess-mate [EMAIL PROTECTED] writes: Can't boot FreeBSD from the grub bootloader. [...] I'm running release 5.1. Try to boot it the way you do it for Windows. Frank ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB 0.92 on FreeBSD 5.x
On Sun, Jun 08, 2003 at 01:59:11PM +0100 or thereabouts, leon j. breedt seemed to write: hi, is it a new feature of 5.x disallowing direct writes to the device nodes /dev/ad*? getting weird behaviour trying to use the GRUB 0.92 port on all versions of 5.x i've used so far (currently on 5.1-RELEASE). the problem being that i can't see any disks in the 'grub' shell. the 'device' command works, and then a subsequent command like 'root' still fails with No such disk. i've tracked down the problem to a call in the GRUB source where its trying to open(2) the device node /dev/ad0 with O_RDWR which fails with EPERM, which causes GRUB to delete the drive from its device map without any warning, just silent failure. i am running the 'grub' executable as root though. when i patch that section of the source file (asmstub.c, function get_diskinfo()) to accept EPERM and only open in read-only mode, suddenly i can see my drives. but obviously anything wanting to modify the drive, like 'setup', fails. is my only recourse to install GRUB from floppy when using it from FreeBSD? I think so. GEOM makes it impossible to write to disks that are currently in use. Best bet is to boot from a floppy. -- Josh please cc me on replies, i'm not subscribed to -questions. thanks leon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Grub 0.92 fails to recognise disks on FBSD5
Hi all, I'm fighting with the same problem and found that grub *does* recognize the disks if started with '--read-only'... That fits perfectly to the following paragraph found in the 5.0-RELEASE Errata: The geom(4)-based disk partitioning code in the kernel will not allow an open partition to be overwritten. This usually prevents the use of disklabel -B to update the boot blocks on a disk because the a partition overlaps the space where the boot blocks are stored. A suggested workaround is to boot from an alternate disk, a CDROM, or a fixit floppy. I can happily boot -current with grub - booting isn't the problem, installing it is the problem. And I installed grub from my 4.7-STABLE installation... (happy to have one :-) Grub seems to open disks/slices r/w and refuses to know them if that's not possible. I, personally, would say that's a bug of grub but that doesn't help here. It even doesn't help, if you run 5.0/-current on your base disk because you can't write the MBR anyway. My question to 'phk' is, if he (or anybody else) has or at least could imagine a solution for this problem. Nothing against 'booteasy', it does the job - but it looks ugly :-) And I can't imagine that the majority of FreeBSD-Users all have a bunch of disks in their systems - especially if I think of the giant sizes of HDs nowadays... -- Ciao/BSD - Matthias Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Grub 0.92 fails to recognise disks on FBSD5
On Sun, Feb 09, 2003 at 06:14:30PM +0100, Matthias Schuendehuette wrote: Nothing against 'booteasy', it does the job - but it looks ugly :-) If that is the only reason to use grub, try osbsbeta.exe that is in the tools directory of your CDROM or ftp.freebsd.org. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Grub 0.92 fails to recognise disks on FBSD5
Rumours go that on Monday 03 February 2003 05:33, Jud spoke the following words: On Sun, 2 Feb 2003 14:02:17 + (GMT), William Palfreman [EMAIL PROTECTED] wrote: snip a lot That's what it says at one point in the docs. At another point it explains that no, the 1 isn't extra, and it uses what Chris has in its example FreeBSD section for the menu.lst file. (I used a similar config with GRUB, no problems.) i tried both ways to no avail. The info page actually says the (hd0,a) notation is a short-cut for (hd0,1,a), so they should be equivalent. I found in some mailing list archive some comments about the bios not providing the right hints... tho i think i can rule that out since i've been running grub for about three years on this machine both with FBSD4.5, 4.6 and several linuxes... Also, how new are you to FreeBSD? You sound quite new. not that new :) I came from Mandrake Linux, i've been using FBSD from the release of 4.5 until last september. Then i switched to gentoo linux, and when FBSD5 was released i thought to give it a shot. If I were you I would use FreeBSD 4.7 instead of 5.0 - I'd only use 5.0 if I were an OS developer or there was some feature on 5.0 that I desperately needed - like maybe I had a machine with more than 2 CPUs. I personally have no intention of going near 5.x until it is the -stable branch *and* everyone else has used it long enough to get the problems out. in general, i agree with your statement: if i had a machine depending on stability, i wouldn't switch :) my gateway still safely runs 4.7... but trying new things is kinda exiting, so... :) Dang! I missed that. GRUB may not recognize FreeBSD 5.0 disks - does anyone know for sure one way or the other? It looks like running FBSD5 is the only difference between my machine now and the machine when i ran 4.6 with grub... does someone know if and how i can determine this 100%? In any case, thanks all who have replied. If i find a solution, i'll make sure to post it, in the mean time, i'll be googling until evey piece of info on grub is on my pc :P regards, Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Grub 0.92 fails to recognise disks on FBSD5
On Sat, 1 Feb 2003, Chris Delnooz wrote: Hi all, i'm experiencing problems with the installation of the GRUB bootloader. I have installed the port (grub version 0.92) and created the /boot/grub directory with the files from /usr/local/share/grub/i381-freebsd. Next I created a menu.lst file in /boot/grub and thought to install GRUB in the mbr, so I launch the grub shell. My fbsd install is on ad0s2 with / on partition a. If i am correct that should be (hd0,1,a) for grub, right? well this is what i get: grub root (hd0,1,a) Error 21: Selected disk does not exist Probably because you've got an extra 1. This is what the grub info file says: -- GRUB can load the kernel directly, either in ELF or a.out format. But this is not recommended, since FreeBSD's bootstrap interface sometimes changes heavily, so GRUB can't guarantee to pass kernel parameters correctly. Thus, we'd recommend loading the very flexible loader `/boot/loader' instead. See this example: grub root (hd0,a) grub kernel /boot/loader grub boot - Anyway, note that Grub is pointing to /boot/loader - you might as well use that instead of grub. It is a better bootloader IMO and its the default. It configures itself at run time, examining the disk to see what OSes are available. Use /stand/sysinstall to put it back on the MBR (if you have lost it), or if you want to use the slightly harder way, read the manpage for disklabel. I never use grub (or lilo) on any multiboot system when I have the FreeBSD loader available. Also, how new are you to FreeBSD? You sound quite new. If I were you I would use FreeBSD 4.7 instead of 5.0 - I'd only use 5.0 if I were an OS developer or there was some feature on 5.0 that I desperately needed - like maybe I had a machine with more than 2 CPUs. I personally have no intention of going near 5.x until it is the -stable branch *and* everyone else has used it long enough to get the problems out. Bill. -- W. Palfreman. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Grub 0.92 fails to recognise disks on FBSD5
On Sun, 2 Feb 2003 14:02:17 + (GMT), William Palfreman [EMAIL PROTECTED] wrote: On Sat, 1 Feb 2003, Chris Delnooz wrote: Hi all, i'm experiencing problems with the installation of the GRUB bootloader. I have installed the port (grub version 0.92) and created the /boot/grub directory with the files from /usr/local/share/grub/i381-freebsd. Next I created a menu.lst file in /boot/grub and thought to install GRUB in the mbr, so I launch the grub shell. My fbsd install is on ad0s2 with / on partition a. If i am correct that should be (hd0,1,a) for grub, right? well this is what i get: grub root (hd0,1,a) Error 21: Selected disk does not exist Probably because you've got an extra 1. This is what the grub info file says: -- GRUB can load the kernel directly, either in ELF or a.out format. But this is not recommended, since FreeBSD's bootstrap interface sometimes changes heavily, so GRUB can't guarantee to pass kernel parameters correctly. Thus, we'd recommend loading the very flexible loader `/boot/loader' instead. See this example: grub root (hd0,a) grub kernel /boot/loader grub boot - That's what it says at one point in the docs. At another point it explains that no, the 1 isn't extra, and it uses what Chris has in its example FreeBSD section for the menu.lst file. (I used a similar config with GRUB, no problems.) Also, how new are you to FreeBSD? You sound quite new. If I were you I would use FreeBSD 4.7 instead of 5.0 - I'd only use 5.0 if I were an OS developer or there was some feature on 5.0 that I desperately needed - like maybe I had a machine with more than 2 CPUs. I personally have no intention of going near 5.x until it is the -stable branch *and* everyone else has used it long enough to get the problems out. Dang! I missed that. GRUB may not recognize FreeBSD 5.0 disks - does anyone know for sure one way or the other? Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Grub 0.92 fails to recognise disks on FBSD5
On Sat, 1 Feb 2003 21:19:02 +0100, Chris Delnooz [EMAIL PROTECTED] said: Hi all, i'm experiencing problems with the installation of the GRUB bootloader. I have installed the port (grub version 0.92) and created the /boot/grub directory with the files from /usr/local/share/grub/i381-freebsd. Next I created a menu.lst file in /boot/grub and thought to install GRUB in the mbr, so I launch the grub shell. My fbsd install is on ad0s2 with / on partition a. If i am correct that should be (hd0,1,a) for grub, right? well this is what i get: grub root (hd0,1,a) Error 21: Selected disk does not exist I looked up the error in the manual and it says: This error is returned if the device part of a device- or full filename refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system. which doesn't help me much i'm afraid... dmesg shows my disk as follows: ad0: 39266MB IC35L040AVVN07-0 [79780/16/63] at ata0-master UDMA100 does anyone have a clue what's going on here? Two ideas, though you may want to wait to see if others more knowledgeable weigh in. Try the steps outlined in the manual regarding installing from a floppy disk. If that also runs into problems, try the device command to tell GRUB what hd0 is. Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: grub boot loader or freebsd boot loader
Gary W. Swearingen [EMAIL PROTECTED] wrote: Nobody said the kernel would be considered a derivative of any bootloader, but a CD which contains both is a derivative of both. Which is not a violation of the GPL. You can distribute GPL and non-GPL software on the same CD, or put it on the same FTP site, or whatever. That's what everyone does. We do it, Sun does it, etc. The problem with the GPL arises as soon as you merge code from GPL software with other code, e.g. by taking parts of its source and compiling it together to produce one object file or executable, or by linking them together (unless it is only LGPL and not real GPL). And remember that you may boot FreeBSD from the NT boot loader, but you'd better not publish a CD containing both. If you've got a license for the NT boot loader to do so, there's no problem to do that. (Nobody says there's a legal problem with using a GPL'd loader locally, but making it part of the core of the distributed OS is too risky.) Certainly not. A boot manager is as separates as it can be from the rest of the system. It's running in real mode. It does not share or merge _any_ code with the rest of the system. And it is optional -- you can boot FreeBSD without it. Think about gcc in our base system. Or GNU-awk, GNU-tar, cvs, groff, gzip, send-pr, and many others. Just as an example, take awk (which is GPL, not even LGPL). It is linked against our (non-GPL) libc. Sure, you can install a different (slightly incompatible) version of awk from the ports collection, such as bawk, but the question is if we are even allowed to link gnu-awk with our libc. Why is that not mere aggregation, and allowed by the GPL? No, that's exactly the reason why the LPGL exists. (Seeing your TLD, I wonder how software license issues are complicated by the fact that many of the owners of open source software offer their license under non-USA law. And whether the local laws of the licensee AND licensor are involved. Arggh...) Of course they are involved. I wouldn't be surprised if some of the GPL clauses are invalid in Germany (and also possibly in other countries). I'm not a lawyer, though. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: grub boot loader or freebsd boot loader
Gary W. Swearingen [EMAIL PROTECTED] wrote: I would like to see people support and develop the FreeBSD boot loader or some other loader with a decent license. The combination of the GPL'd GRUB (or GAG) boot loader and the kernel is too likely to be considerd by some judge or jury as a derivative of both parts which is sufficiently unworthy of any of the GPL's nebulous excape clauses to avoid partial or even total infection. (Especially when a dangerously-dedicated-disk install is considered.) Why would you want to install a bootmanager on a dangerously- dedicated disk? Apart from that, dangerously-dedicated has been deprecated, AFAIK. The kernel can certainly not be considered a derivative of any bootloader; they don't have anything in common, neither do they share any code. Remember that you can boot FreeBSD from the NT boot loader, for example, which isn't even open source and certainly has a more restrictive license than GRUB. (Microsoft certainly didn't have supporting Linux or BSD in mind when they created their boot loader, while FreeBSD is even mentioned in the GRUB documentation, IIRC). I'd be much more concerned about other GPL'ed parts of the base system. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: grub boot loader or freebsd boot loader
I have been using AiR-BOOT and it works great, is free, and loads in mbr/floppy. By far the best one I have used over the years. Mike ps- please don't use lilo ;) I have and use: FreeBSD 4.6, OS/2 Warp3 4, OpenBSD3.1, Mandrake 8.1,SuSE 7.3, Win3.1 - 2000Pro ICQ# 54186124 bp40mm --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.394 / Virus Database: 224 - Release Date: 10/3/2002
Re: grub boot loader or freebsd boot loader
Guess I could leave the URL for air-boot ;) http://en.ecomstation.ru/kiewitzsoft/air-boot.php I have and use: FreeBSD 4.6, OS/2 Warp3 4, OpenBSD3.1, Mandrake 8.1,SuSE 7.3, Win3.1 - 2000Pro ICQ# 54186124 bp40mm --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.394 / Virus Database: 224 - Release Date: 10/3/2002
Re: grub boot loader or freebsd boot loader
Oliver Fromme [EMAIL PROTECTED] writes: Why would you want to install a bootmanager on a dangerously- dedicated disk? Apart from that, dangerously-dedicated has been deprecated, AFAIK. The second sentence is not relevant as DD is still supported, but I shouldn't have added my parenthetical mention of DD. If you're using GRUB or GAG to boot, then you'll need a partition table, so you won't have a DD disk, by definition. (Make it a one-slice install, then.) The kernel can certainly not be considered a derivative of any bootloader; they don't have anything in common, neither do they share any code. Remember that you can boot FreeBSD from the NT boot loader, for example, which isn't even open source and certainly has a more restrictive license than GRUB. (Microsoft certainly didn't have supporting Linux or BSD in mind when they created their boot loader, while FreeBSD is even mentioned in the GRUB documentation, IIRC). Nobody said the kernel would be considered a derivative of any bootloader, but a CD which contains both is a derivative of both. The question is under what conditions the GPL infects the other parts of that derivative CD (or .tgz, etc.), making the publishing of it illegal. (The real question is how confident we are about how certain people might answer the previous question.) There is no question that the loader+kernel forms derivative work; the problem is that people don't/ can't understand what the GPL has to say about escape clauses for particular derivatives works, especially when they use linking, and especially because it makes some kind of sense to find that the loader and kernel are not independent since the GPL uses the word loosely. And remember that you may boot FreeBSD from the NT boot loader, but you'd better not publish a CD containing both. (Nobody says there's a legal problem with using a GPL'd loader locally, but making it part of the core of the distributed OS is too risky.) I'd be much more concerned about other GPL'ed parts of the base system. Why is that not mere aggregation, and allowed by the GPL? (And if you are concerned about that, you shouldn't find it hard to believe that others will be concerned about the loader, even if in error.) (Seeing your TLD, I wonder how software license issues are complicated by the fact that many of the owners of open source software offer their license under non-USA law. And whether the local laws of the licensee AND licensor are involved. Arggh...) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: grub boot loader or freebsd boot loader
Grub is very powerful. (I would like to see it as the default boot loader on FreeBSD.) But it is not so easy to configure, a bit a steep learning curve. However, if you dig in, you'll be greatly rewarded with flexibility. I suggest you give it a shot. Cheers, Kurt On Thu, Oct 03, 2002 at 04:58:25PM -0500, SweeTLeaF wrote: Primary Master: 40gig Primary Slave: 20 gig I want to install XP on the first 20gig of the Master, Redhat 8.0 on the remaining 20gig of the Master and FreeBSD on the entire 20gig of the Slave. What would be my best options for being able to boot all 3. I heard grub had issues booting BSD so i just wanted to know my best approach before starting. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: grub boot loader or freebsd boot loader
[EMAIL PROTECTED] writes: Grub is very powerful. (I would like to see it as the default boot loader on FreeBSD.) But it is not so easy to configure, a bit a steep learning I would like to see people support and develop the FreeBSD boot loader or some other loader with a decent license. The combination of the GPL'd GRUB (or GAG) boot loader and the kernel is too likely to be considerd by some judge or jury as a derivative of both parts which is sufficiently unworthy of any of the GPL's nebulous excape clauses to avoid partial or even total infection. (Especially when a dangerously-dedicated-disk install is considered.) At least, the FreeBSD core leaders won't take the risk anytime soon, I hope. I'd prefer to not waste time arguing about the true level of risk as it is only the core leaders' feelings about the risk that matters much and we can trust that they'll be copyleft-averse for a good long time. (You should be able to find the subject debated in the archives.) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: grub boot loader or freebsd boot loader
I have been using gag for quite some time now. I think it is the best boot loader out there. I boot Redhat, OpenBSD, FreeBSD, and Windows 2000. with it. It displays a graphical menu, has password security, allows you to set a default OS with a boot timer, makes a backup of your boot configuration on floppy, It does not require any drive space outside of the MBR, and it was *very* easy to set up. http://raster.cibermillennium.com/gageng.htm - Original Message - From: SweeTLeaF [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 03, 2002 4:58 PM Subject: grub boot loader or freebsd boot loader OK, my system has two hds: Primary Master: 40gig Primary Slave: 20 gig I want to install XP on the first 20gig of the Master, Redhat 8.0 on the remaining 20gig of the Master and FreeBSD on the entire 20gig of the Slave. What would be my best options for being able to boot all 3. I heard grub had issues booting BSD so i just wanted to know my best approach before starting. Ps. Have they said when the 4.7 release is coming rescheduled to? -- Best regards, SweeTLeaF mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
