[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
|
steph.p.foster wrote: > To: list@xxxxxxxxxxxxx > Subject: Re: [LUG] Accessing C: drive from Jaunty > > michael graaf wrote: > > Greetings from a chronic lurker - > > > > I recently converted an XP box to dual-boot with Jaunty, after which > > any attempt to boot into Windows abort saying "file \system32\hal.dll > > missing or corrupt". Google reveals a thread in Ubuntu Forum > > (http://ubuntuforums.org/showthread.php?p=7279426#post7279426) which > > fits the case: > > > > "...as you installed Ubuntu, ... the actual partition location of the > > windows boot disk has moved. Thus the windows boot loader cannot find > > hal.dll on the right hard drive partition... One cool thing to think > > about here is that grub, the Linux boot loader is working and knows > > where the windows boot partition is... the way to fix this problem is > > to boot up into Linux, 7.10 or better and this product automounts the > > various windows partitions... open a terminal and you will find these > > various hard drive partitions in the directory /media. One of these > > will have a lot of "window dressing", say for instance, a directory > > called Windows or WINDOWS (depends :^). In the root of this directory > > you will find a file called boot.ini..."[the writer describes remedial > > steps] > > > > So after years as a GUI-only Ubuntero, I plunged into a terminal and > > was promptly stumped by: > > "/media$ vdir > > total 4 > > lrwxrwxrwx 1 root root 6 2009-05-04 15:51 cdrom -> cdrom0 > > drwxr-xr-x 2 root root 4096 2009-05-04 15:51 cdrom0" > The /media directory only contains a link to cdrom0 > > Usually hard drive partitions will appear to Linux ad /dev/hda or > /dev/sda devices > > try cat'ing the fstab with "cat /etc/fstab" to show lists of filesystems > that may be mountable > > alternatively try cat'ing the boot menu file, try "cat /boot/menu.lst" > or "cat /boot/grub/menu.lst" Thank you, the first suggestion yields: "michael@old-laptop:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=8d6fce1e-6d7a-40df-8812-e40199a6b8ad / ext3 relatime,errors=remount-ro 0 1 # /home was on /dev/sda4 during installation UUID=2cd2be0e-aa0e-4c9e-9dc4-d970b9347d2c /home ext3 relatime 0 2 # swap was on /dev/sda3 during installation UUID=7fab348b-f598-460b-9dde-d4333dfa8517 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0" and the second: "michael@old-laptop:~$ cat /boot/menu.lst cat: /boot/menu.lst: No such file or directory" and the third: "michael@old-laptop:~$ cat /boot/grub/menu.lst # menu.lst - See: grub(8), info grub, update-grub(8) # grub-install(8), grub-floppy(8), # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not use 'savedefault' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 10 ## hiddenmenu # Hides the menu by default (press ESC to see the menu) #hiddenmenu # Pretty colours #color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel /vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=8d6fce1e-6d7a-40df-8812-e40199a6b8ad ro ## default grub root device ## e.g. groot=(hd0,0) # groot=8d6fce1e-6d7a-40df-8812-e40199a6b8ad ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=quiet splash ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(recovery) single # altoptions=(recovery mode) single ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## specify if running in Xen domU or have grub detect automatically ## update-grub will ignore non-xen kernels when running in domU and vice versa ## e.g. indomU=detect ## indomU=true ## indomU=false # indomU=detect ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Ubuntu 9.04, kernel 2.6.28-11-generic uuid 8d6fce1e-6d7a-40df-8812-e40199a6b8ad kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=8d6fce1e-6d7a-40df-8812-e40199a6b8ad ro quiet splash initrd /boot/initrd.img-2.6.28-11-generic quiet title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode) uuid 8d6fce1e-6d7a-40df-8812-e40199a6b8ad kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=8d6fce1e-6d7a-40df-8812-e40199a6b8ad ro single initrd /boot/initrd.img-2.6.28-11-generic title Ubuntu 9.04, memtest86+ uuid 8d6fce1e-6d7a-40df-8812-e40199a6b8ad kernel /boot/memtest86+.bin quiet ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda2 title Microsoft Windows XP Home Edition rootnoverify (hd0,1) savedefault makeactive chainloader +1" Being a command-line virgin, it appears to me that the potentially useful information is in the last part, that XP is in /dev/sda2. However this raises the question of whether the remedy described in Ubuntu Forum is still applicable? Thanks again, Michael Get the next generation of Free Windows Live Services Click here! |
-- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html