Multiple grub menu.lst?

Charlie Zender zender at uci.edu
Sat May 3 21:32:41 UTC 2008


>>> And just for kicks, what happens when you try to mount boot?
>>> sudo mount /boot
>> zender at virga:~$  sudo mount /boot
>> sudo: unable to resolve host virga
>> mount: /dev/sda1 already mounted or /boot busy
> 
> Hey Charlie, sorry this is taking so long and has so much back an
> forth..  Here is what I think has happened.
> 
> At some point prior to your upgrade to Hardy, the system became unable
> to mount the /boot partition.  Consequently, when the update to hardy
> was done, any files that get written to /boot are not going into the
> partition that Grub needs to start up, so only old files from your
> previous install are ever available to the boot process.

I agree with your diagnosis.

> What I do not understand, from the error message, is why you cannot
> mount /boot from the command line.  Clearly the UUID in your fstab is
> resolving to the correct location.

It bothers me that the only UUID points to sda1.
I thought each partition is supposed to have its own UUID.
Or is it only one UUID per disk?
If not, why does sda1 report, and sda2 and sda5 not report, UUIDs?

> But before we fix that, first we need to grab a copy of the /boot you
> currently see, (with the hardy files), so that when the partition is
> finally mounted, you will be able to copy the files into it.
> 
> mkdir ~/boot_backup
> sudo cp -a /boot/ /boot_backup

done

> Then we can try to mount /boot.  make sure you have no files in /boot
> open, and that none of your command shells are currently in /boot
> 
> Then try a sudo mount /boot again.

fails as before with

zender at virga:~$ sudo mount /boot
sudo: unable to resolve host virga
mount: /dev/sda1 already mounted or /boot busy

> If it still fails, type dmesg and see if any of the more recent messages
> are errors relating to /dev/sda1.  

dmesg reports seemingly normal results:

zender at virga:~$ dmesg | grep sda
[    5.876000] sd 0:0:0:0: [sda] 192426570 512-byte hardware sectors 
(98522 MB)
[    5.876000] sd 0:0:0:0: [sda] Write Protect is off
[    5.876000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    5.876000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[    5.876000] sd 0:0:0:0: [sda] 192426570 512-byte hardware sectors 
(98522 MB)
[    5.876000] sd 0:0:0:0: [sda] Write Protect is off
[    5.876000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    5.876000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[    5.876000]  sda: sda1 sda2 < sda5 >
[    5.904000] sd 0:0:0:0: [sda] Attached SCSI disk

> Also, try to run sudo fuser /boot to
> see if any processes are listed as accessing /boot

This returns nothing

zender at virga:~$ sudo fuser /boot
sudo: unable to resolve host virga
zender at virga:~$


-- 
Charlie Zender, Department of Earth System Science, UC Irvine
Sab. at CNRS/LGGE-Grenoble until 20080815 :) 011+33+476+824236
Laboratoire de Glaciologie et Géophysique de l'Environnement
54 rue Molière BP 96, 38402 Saint Martin d'Hères Cedex, France




More information about the ubuntu-users mailing list