View previous topic :: View next topic |
Author |
Message |
Thomas H. Oliver n00b
Joined: 08 Jun 2002 Posts: 34 Location: St. Paul, MN
|
Posted: Wed Jun 12, 2002 5:07 am Post subject: Booting from NTFS volume with GRUB |
|
|
Is there some way to turn off filesystem verification in GRUB? I'm attempting to boot Win2K from an NTFS partition on a SCSI disk. This partition is the only one on the particular disk. GRUB checks the filesystem before chainloading and bombs when it can't recognize NTFS. This seem unnecessary since the filesystem type is irrelevant to the bootblock, which is read physically. The menu.lst file for GRUB looks like this:
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=Gentoo Linux Mk. I
root (hd0,3)
kernel /boot/bzImage root=/dev/hda9
title=Windows 2000 Pro
root (hd1,0)
chainloader +1
title=Windows 98
root (hd0,0)
chainloader +1
Linux and Win98 are both booted properly. (Incidentally, is hd1 the proper id for the SCSI disk? I tried sd0 but GRUB didn't recognize it. I scoured the Net looking for comments about booting from a SCSI disk and eventually found a narrative mentioning hdx as a SCSI boot device.) |
|
Back to top |
|
|
huw Apprentice
Joined: 13 May 2002 Posts: 220 Location: UK
|
|
Back to top |
|
|
huw Apprentice
Joined: 13 May 2002 Posts: 220 Location: UK
|
Posted: Wed Jun 12, 2002 8:37 am Post subject: |
|
|
as for SCSI naming convention - to quote from the GRUB manual: Quote: | Note that GRUB does not distinguish IDE from SCSI - it simply counts the drive numbers from zero, regardless of their type. Normally, any IDE drive number is less than any SCSI drive number, although that is not true if you change the boot sequence by swapping IDE and SCSI drives in your BIOS. |
|
|
Back to top |
|
|
Thomas H. Oliver n00b
Joined: 08 Jun 2002 Posts: 34 Location: St. Paul, MN
|
Posted: Wed Jun 12, 2002 11:14 am Post subject: |
|
|
Excellent, thank you very much! I looked through the GRUB manual last night but am afraid I missed what you've pointed out. Okay, it was late, I was frustrated, etc. etc. Anyway, thanks again. |
|
Back to top |
|
|
Thomas H. Oliver n00b
Joined: 08 Jun 2002 Posts: 34 Location: St. Paul, MN
|
Posted: Wed Jun 12, 2002 12:38 pm Post subject: |
|
|
I changed the "root (hd1,0)" command to "rootnoverify (hd1,0)" and attempted to boot to Win2K and was able to get through to the "chainloader +1" command. The chainloader command was printed to the console following which the system hung. A suggestion in the GRUB manual was to turn off INT 13 extensions but my BIOS doesn't seem to have such a switch. |
|
Back to top |
|
|
Thomas H. Oliver n00b
Joined: 08 Jun 2002 Posts: 34 Location: St. Paul, MN
|
Posted: Wed Jun 12, 2002 5:41 pm Post subject: |
|
|
You know the old adage "When in doubt, read the manual"? I finally took the time to read the GRUB manual carefully, and guess what I found?
If you have installed DOS (or Windows) on a non-first hard disk, you have to use the disk swapping technique, because that OS cannot boot from any disks but the first one. The workaround used in GRUB is the command map (see map), like this:
grub> map (hd0) (hd1)
grub> map (hd1) (hd0)
This performs a virtual swap between your first and second hard drive.
So.... Here's the reworked Win2K section of my menu.lst:
title=Windows 2000 Pro
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
Works like a charm. Thanks very much for your advice, I'd probably still be spinning my wheels otherwise. |
|
Back to top |
|
|
klieber Bodhisattva
Joined: 17 Apr 2002 Posts: 3657 Location: San Francisco, CA
|
Posted: Wed Jun 12, 2002 6:05 pm Post subject: |
|
|
Thomas --
Thanks for posting the solution. I've mirrored your post over in the tips & tricks forum in case others run into the same problem.
--kurt _________________ The problem with political jokes is that they get elected |
|
Back to top |
|
|
|