Re: LMDE update, now have boot error
On Fri, 27 Sep 2013 17:54:27 +1000, Jay Amorin <jeeyessos@gmail.com> wrote:
Yes. If your boot partition is in sda1. So root (hd0,0) if second partition root (hd0,1). How does it goes?
Not too good, see below.
On Fri, Sep 27, 2013 at 1:17 PM, Terry Duell <tduell@iinet.net.au> wrote:
On Fri, 27 Sep 2013 14:25:50 +1000, Jay Amorin <jeeyessos@gmail.com> wrote:
You're almost there. Try to mount all your partition under /mnt and run
chroot
# mount -t proc none /mnt/proc # mount -o bind /dev /mnt/dev # chroot /mnt /bin/bash
this results in... "chroot: failed to run command '/bin/bash': no such file or directory" So, it would seem that I'm missing something. When you said "Try to mount all your partition under /mnt and run chroot" did you imply some other things needed to be done that you didn't list? As I said I am using Knoppix live, which is a 32 bit version. The system I'm trying to rescue is 64 bit. Is that an issue? In an attempt to see if I could get a bit further I booted a 64 bit system in rescue mode, but that doesn't provide grub. Cheers, -- Regards, Terry Duell
Terry Duell <tduell@iinet.net.au> wrote:
When you said "Try to mount all your partition under /mnt and run chroot" did you imply some other things needed to be done that you didn't list?
This usually means: mount the root partition under /mnt, then other partitions at the appropriate mount points under /mnt/whatever, e.g., /mnt/user, /mnt/home, depending on your partitioning scheme.
As I said I am using Knoppix live, which is a 32 bit version. The system I'm trying to rescue is 64 bit. Is that an issue?
Yes it is if you're trying to run programs from the installed system within a chroot, which you won't be able to do as they are 64-bit executables. I would recommend a 64-bit version of the rescue disk.
In an attempt to see if I could get a bit further I booted a 64 bit system in rescue mode, but that doesn't provide grub.
64-bit Knoppix or similar would be better, I think.
On Sat, 28 Sep 2013 09:50:00 +1000, Jason White <jason@jasonjgw.net> wrote:
Terry Duell <tduell@iinet.net.au> wrote:
When you said "Try to mount all your partition under /mnt and run chroot" did you imply some other things needed to be done that you didn't list?
This usually means: mount the root partition under /mnt, then other partitions at the appropriate mount points under /mnt/whatever, e.g., /mnt/user, /mnt/home, depending on your partitioning scheme.
As I said I am using Knoppix live, which is a 32 bit version. The system I'm trying to rescue is 64 bit. Is that an issue?
Yes it is if you're trying to run programs from the installed system within a chroot, which you won't be able to do as they are 64-bit executables.
I would recommend a 64-bit version of the rescue disk.
In an attempt to see if I could get a bit further I booted a 64 bit system in rescue mode, but that doesn't provide grub.
64-bit Knoppix or similar would be better, I think.
I couldn't find a 64-bit Knoppix disc, but did have a Fedora x86_64 live disc, so tried that. Also a bit more research turned up a similar story resulting from an update of LMDE, which describes the solution thus... Boot a live disc su - mount /dev/sda2 /mnt mount --bind /dev /mnt/dev mount --bind /sys /mnt/sys mount --bind /proc /mnt/proc chroot /mnt update-grub2 So followed that prescription but mounted /dev/sda1. Running SystemRescue and gparted shows two partitions and swap. If I remember correctly sda1 is system and sda2 is extended, with sda5, which is my user space. A reboot (using any of the grub menu items) still results in "error: no such partition". So, it would seem that I am not tacking this correctly. Anyone have any other suggestions as what I can try? Cheers, -- Regards, Terry Duell
Terry Duell <tduell@iinet.net.au> wrote:
So followed that prescription but mounted /dev/sda1. Running SystemRescue and gparted shows two partitions and swap. If I remember correctly sda1 is system and sda2 is extended, with sda5, which is my user space.
A reboot (using any of the grub menu items) still results in "error: no such partition". So, it would seem that I am not tacking this correctly.
Anyone have any other suggestions as what I can try?
You might need to re-install Grub. Before doing that, however, have a look at the configuration file (/boot/grub/grub.cfg) just in case there are obvious issues, e.g., not loading the correct modules or not referring to the right partitions.
Hello Jason, On Sat, 28 Sep 2013 11:00:25 +1000, Jason White <jason@jasonjgw.net> wrote:
Terry Duell <tduell@iinet.net.au> wrote:
So followed that prescription but mounted /dev/sda1. Running SystemRescue and gparted shows two partitions and swap. If I remember correctly sda1 is system and sda2 is extended, with sda5, which is my user space.
A reboot (using any of the grub menu items) still results in "error: no such partition". So, it would seem that I am not tacking this correctly.
Anyone have any other suggestions as what I can try?
You might need to re-install Grub. Before doing that, however, have a look at the configuration file (/boot/grub/grub.cfg) just in case there are obvious issues, e.g., not loading the correct modules or not referring to the right partitions.
I had a look at the grub.cfg and it looked OK, but I don't have any experience in this. I tried to re-install grub... grub-install /dev/sda which gave the response that /boot/grub/stage1 file not read correctly. If I look at /etc/fstab and /etc/mtab I note there is no /boot, but I really don't know if that matters. What info do I need to get that will give (someone who knows about this stuff) a clear picture of what has to be done to fix this ? Cheers, -- Regards, Terry Duell
Terry Duell <tduell@iinet.net.au> wrote:
I tried to re-install grub...
grub-install /dev/sda
which gave the response that /boot/grub/stage1 file not read correctly.
I don't have that file, but I'm reasonably sure it existed under Grub 1. Perhaps you are running grub-install from Grub legacy (i.e., Grub 1) whereas you're trying to install Grub 2. This could in fact be your problem if Grub 2 didn't get installed to the boot sector of the drive as it should have been. Make sure you're running grub-install from Grub 2.0. If you invoke it from within the chroot environment, you'll need to have bind mounted /dev into the chroot (you've already quoted instructions for doing that). Otherwise, if you're running grub-install from the "live CD", be sure it's the correct version, and you'll probably have to specify the location of the boot directory with the --boot-directory option, e.g., grub-install --boot-directory=/mnt/boot /dev/sda I hope this is helpful. Just don't mix Grub 1 and Grub 2.
Hello Jason, On Sat, 28 Sep 2013 12:52:32 +1000, Jason White <jason@jasonjgw.net> wrote:
Terry Duell <tduell@iinet.net.au> wrote:
I tried to re-install grub...
grub-install /dev/sda
which gave the response that /boot/grub/stage1 file not read correctly.
I don't have that file, but I'm reasonably sure it existed under Grub 1. Perhaps you are running grub-install from Grub legacy (i.e., Grub 1) whereas you're trying to install Grub 2. This could in fact be your problem if Grub 2 didn't get installed to the boot sector of the drive as it should have been.
Make sure you're running grub-install from Grub 2.0. If you invoke it from within the chroot environment, you'll need to have bind mounted /dev into the chroot (you've already quoted instructions for doing that).
Otherwise, if you're running grub-install from the "live CD", be sure it's the correct version, and you'll probably have to specify the location of the boot directory with the --boot-directory option, e.g., grub-install --boot-directory=/mnt/boot /dev/sda
I hope this is helpful. Just don't mix Grub 1 and Grub 2.
Yes, it is. You are right, when I tried to run grub the system said grub wasn't installed and gave instructions to install grub-legacy. Is there a way that I can ensure that grub-install I run is in fact installing grub2? Cheers, -- Regards, Terry Duell
On Sat, 28 Sep 2013 13:07:58 +1000, Terry Duell <tduell@iinet.net.au> wrote:
correct version, and you'll probably have to specify the location of the boot directory with the --boot-directory option, e.g., grub-install --boot-directory=/mnt/boot /dev/sda
I hope this is helpful. Just don't mix Grub 1 and Grub 2.
Decided to press on; OK, into the live boot, and chroot... I bravely try; grub-install --boot-directory=/mnt/boot /dev/sda and I get the message..."unrecognized option `--boot-directory=/mnt/boot' " A look at grub-install options says " --root-directory=DIR", so I subsitute "root" for "boot" in the above command and get; "mkdir: cannot create directory '/mnt/boot/boot': no such file or directory" "grub-install -v" returns grub-install (GNU GRUB 0.97), doesn't look like grub2, but maybe it announces itself this way? Cheers, -- Regards, Terry Duell
Decided to press on; OK, into the live boot, and chroot... I bravely try; grub-install --boot-directory=/mnt/boot /dev/sda and I get the message..."unrecognized option `--boot-directory=/mnt/boot' " A look at grub-install options says " --root-directory=DIR", so I subsitute "root" for "boot" in the above command and get; "mkdir: cannot create directory '/mnt/boot/boot': no such file or directory" Hi Terry I think you are almost there. If you have mounted /boot on /mnt then specify root-directory=/mnt No need to put boot. Cheers Nic
On 28/09/13 13:43, Nic Baxter wrote:
Decided to press on; OK, into the live boot, and chroot...
I bravely try; grub-install --boot-directory=/mnt/boot /dev/sda and I get the message..."unrecognized option `--boot-directory=/mnt/boot' " A look at grub-install options says " --root-directory=DIR", so I subsitute "root" for "boot" in the above command and get; "mkdir: cannot create directory '/mnt/boot/boot': no such file or directory" Hi Terry I think you are almost there. If you have mounted /boot on /mnt then specify root-directory=/mnt No need to put boot. Cheers
Nic
Sorry reword that. If you have mount / on /mnt then that is the root directory. so use root-directory=/mnt.
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
On Sat, 28 Sep 2013 13:47:46 +1000, Nic Baxter <nic@nicbaxter.com.au> wrote:
On 28/09/13 13:43, Nic Baxter wrote:
Decided to press on; OK, into the live boot, and chroot...
I bravely try; grub-install --boot-directory=/mnt/boot /dev/sda and I get the message..."unrecognized option `--boot-directory=/mnt/boot' " A look at grub-install options says " --root-directory=DIR", so I subsitute "root" for "boot" in the above command and get; "mkdir: cannot create directory '/mnt/boot/boot': no such file or directory" Hi Terry I think you are almost there. If you have mounted /boot on /mnt then specify root-directory=/mnt No need to put boot. Cheers
Nic
Sorry reword that. If you have mount / on /mnt then that is the root directory. so use root-directory=/mnt.
OK, been through hoops yet again, after "chroot /mnt" I ran "grub-install --root-directory=/mnt /dev/sda" (and checked it was grub2) which reported no errors. A reboot of the LMDE system ends up giving me "grub>", no boot menu, nothing but "grub>" ! Am I getting warmer, or moving further out into the cold? Cheers, -- Regards, Terry Duell
Hello Nic, On Sat, 28 Sep 2013 13:43:22 +1000, Nic Baxter <nic@nicbaxter.com.au> wrote:
Decided to press on; OK, into the live boot, and chroot...
I bravely try; grub-install --boot-directory=/mnt/boot /dev/sda and I get the message..."unrecognized option `--boot-directory=/mnt/boot' " A look at grub-install options says " --root-directory=DIR", so I subsitute "root" for "boot" in the above command and get; "mkdir: cannot create directory '/mnt/boot/boot': no such file or directory" Hi Terry I think you are almost there. If you have mounted /boot on /mnt then specify root-directory=/mnt No need to put boot.
This saga must make exciting reading :-) I haven't explicitly mounted /boot on /mnt, as previous advice never mentioned this. I have established that the grub available to me was in fact Not grub2, so installed grub-pc, then ran... grub-install --boot-directory=/mnt/boot /dev/sda which said there were no errors, however a reboot doesn't give a grub menu, just provides a grub prompt ie "grub>". ...almost, almost there, maybe. Cheers, -- Regards, Terry Duell
On 28/09/2013 1:56 PM, Terry Duell wrote:
Hello Nic,
On Sat, 28 Sep 2013 13:43:22 +1000, Nic Baxter <nic@nicbaxter.com.au> wrote:
Decided to press on; OK, into the live boot, and chroot...
I bravely try; grub-install --boot-directory=/mnt/boot /dev/sda and I get the message..."unrecognized option `--boot-directory=/mnt/boot' " A look at grub-install options says " --root-directory=DIR", so I subsitute "root" for "boot" in the above command and get; "mkdir: cannot create directory '/mnt/boot/boot': no such file or directory" Hi Terry I think you are almost there. If you have mounted /boot on /mnt then specify root-directory=/mnt No need to put boot.
This saga must make exciting reading :-)
Might not be exciting but's it's fascinating, I'm enjoying watching from the sidelines, learning much as it unfolds. -- Regards, Colin.
OK start from the beginning. The football is ordinary so I dug out the netbook and nuked the MBR. I run Mageia 3 dual boot with windows xp sudo fdisk -l Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 * 63 102398309 51199123+ 7 HPFS/NTFS/exFAT /dev/sda2 102402027 312576704 105087339 5 Extended /dev/sda5 102402048 127588229 12593091 83 Linux /dev/sda6 127590400 135765314 4087457+ 82 Linux swap / Solaris /dev/sda7 135768064 312576704 88404320+ 83 Linux Boot with usbdrive (Mageia 3 install) to rescue console. mount /dev/sda5 /mnt/ grub-install --root-directory=/mnt/ /dev/sda grub installed with out error and booted correctly see how you go. Cheers Nic
On Sat, 28 Sep 2013 17:03:24 +1000, Nic Baxter <nic@nicbaxter.com.au> wrote:
OK start from the beginning. The football is ordinary so I dug out the netbook and nuked the MBR. I run Mageia 3 dual boot with windows xp
sudo fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/sda1 * 63 102398309 51199123+ 7 HPFS/NTFS/exFAT /dev/sda2 102402027 312576704 105087339 5 Extended /dev/sda5 102402048 127588229 12593091 83 Linux /dev/sda6 127590400 135765314 4087457+ 82 Linux swap / Solaris /dev/sda7 135768064 312576704 88404320+ 83 Linux
Boot with usbdrive (Mageia 3 install) to rescue console.
mount /dev/sda5 /mnt/
grub-install --root-directory=/mnt/ /dev/sda
grub installed with out error and booted correctly
see how you go.
I have been using "mount /dev/sda1 /mnt " and it has been booting into "grub2>" thus far. My approach has been pretty much as you have done. Here is the result of "fdisk -l" on my LMDE system localhost grub # fdisk -l Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0008d876 Device Boot Start End Blocks Id System /dev/sda1 2048 40962047 20480000 83 Linux /dev/sda2 40962048 229378047 94208000 5 Extended /dev/sda3 229378048 234440703 2531328 82 Linux swap / Solaris /dev/sda5 40964096 229378047 94206976 83 Linux Disk /dev/mapper/live-rw: 4294 MB, 4294967296 bytes 255 heads, 63 sectors/track, 522 cylinders, total 8388608 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/live-rw doesn't contain a valid partition table Disk /dev/mapper/live-osimg-min: 4294 MB, 4294967296 bytes 255 heads, 63 sectors/track, 522 cylinders, total 8388608 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/live-osimg-min doesn't contain a valid partition table Note that is has nothing is identified under "Boot". Does this provide any clues Cheers, -- Regards, Terry Duell
On Sat, Sep 28, 2013 at 01:56:16PM +1000, Terry Duell wrote:
I haven't explicitly mounted /boot on /mnt, as previous advice never mentioned this.
this may be where you are going wrong. if you are trying to reinstall grub, then it needs access to not only your root filesystem, but your /boot directory as well. if /boot is just a directory on / then mounting / alone as /mnt will be sufficient. if /boot is a separate partition, then it must also be mounted, as /mnt/boot. for example, if your rootfs (/) is /dev/sda1 and your /boot is /dev/sda2 then to get to a good, working chroot environment for fixing a broken grub you'd do something a lot like this: 1. boot a live cd and get a root shell. if your installed distro is 64-bit then your live-cd must also be 64-bit otherwise you will not be able to chroot into it. i tend to use clonezilla because it has 64 and 32 bit versions and has every repair tool you might ever need. sometimes i use gparted. 2. run the following commands: mount /dev/sda1 /mnt mount /dev/sda2 /mnt/boot for i in proc dev sys dev/pts ; do mount -o bind /$i /mnt/$i ; done chroot /mnt 3. now you can fix your system. e.g. by installing and/or configuring grub2. running 'grub-install /dev/sda' may be sufficient. if your grub config is completely hosed, you may find it better/easier to just purge all currently installed grub packages and start from scratch: dpkg --force-depends --purge $(dpkg -l '*grub*' | awk '/^[hi]/ {print $2}') apt-get install grub note, though, that this scorched-earth purge and reinstall will only work if you either still have the downloaded grub packages in your /var/cache/apt/archives directory, a convenient debian-installer CD/DVD to get the packages from, or if you have a working internet connection from your live CD. 4. anyway, when you have finished fixing your grub configuration, you need to unmount the filesystems (in the reverse order you mounted them) and then reboot. exit # exit from the chroot. for i in dev/pts sys dev proc /boot / ; do umount /mnt/$i ; done sync shutdown -r now BTW, the above is tested and known to work for many boot problems - i've done repairs like this so many times on so many different systems now (both real and vm) i can do it entirely from memory (although i have helper aliases defined in my PXE-bootable clonezilla). steps 1, 2 and 4 are the basis of pretty nearly every rescue/repair operation. step 3 varies according to the nature of the problem.
which said there were no errors, however a reboot doesn't give a grub menu, just provides a grub prompt ie "grub>".
that sounds like grub without a config file. which is about what you'd expect if you didn't have /boot mounted when you ran update-grub or grub-install. craig -- craig sanders <cas@taz.net.au>
On Sat, 28 Sep 2013 18:42:32 +1000, Craig Sanders <cas@taz.net.au> wrote:
On Sat, Sep 28, 2013 at 01:56:16PM +1000, Terry Duell wrote:
I haven't explicitly mounted /boot on /mnt, as previous advice never mentioned this.
this may be where you are going wrong.
if you are trying to reinstall grub, then it needs access to not only your root filesystem, but your /boot directory as well. if /boot is just a directory on / then mounting / alone as /mnt will be sufficient. if /boot is a separate partition, then it must also be mounted, as /mnt/boot.
for example, if your rootfs (/) is /dev/sda1 and your /boot is /dev/sda2 then to get to a good, working chroot environment for fixing a broken grub you'd do something a lot like this:
1. boot a live cd and get a root shell. if your installed distro is 64-bit then your live-cd must also be 64-bit otherwise you will not be able to chroot into it. i tend to use clonezilla because it has 64 and 32 bit versions and has every repair tool you might ever need. sometimes i use gparted.
2. run the following commands:
mount /dev/sda1 /mnt mount /dev/sda2 /mnt/boot for i in proc dev sys dev/pts ; do mount -o bind /$i /mnt/$i ; done chroot /mnt
It was always my understanding that /boot was just a directory in /. here is the disc layout Device Boot Start End Blocks Id System /dev/sda1 2048 40962047 20480000 83 Linux /dev/sda2 40962048 229378047 94208000 5 Extended /dev/sda3 229378048 234440703 2531328 82 Linux swap / Solaris /dev/sda5 40964096 229378047 94206976 83 Linux I thought I'd try "mount /dev/sda2 /mnt/boot" just to see what happens, and when I do I get... "mount: you must specify the filesystem type" , so thought it best to not separately mount /mnt/boot
3. now you can fix your system. e.g. by installing and/or configuring grub2.
running 'grub-install /dev/sda' may be sufficient.
if your grub config is completely hosed, you may find it better/easier to just purge all currently installed grub packages and start from scratch:
dpkg --force-depends --purge $(dpkg -l '*grub*' | awk '/^[hi]/ {print $2}') apt-get install grub
note, though, that this scorched-earth purge and reinstall will only work if you either still have the downloaded grub packages in your /var/cache/apt/archives directory, a convenient debian-installer CD/DVD to get the packages from, or if you have a working internet connection from your live CD.
4. anyway, when you have finished fixing your grub configuration, you need to unmount the filesystems (in the reverse order you mounted them) and then reboot.
exit # exit from the chroot. for i in dev/pts sys dev proc /boot / ; do umount /mnt/$i ; done sync shutdown -r now
went through the whole process, purged grub and reinstalled. "apt-get install grub" says it is going to install grub-legacy, which doesn't seem right, so installed grub-pc instead, but at the end of the installation it pops up a screen asking if I want grub installed on /dev/sda (and displayed ???) or /dev/sda1 (which it thought was /), neither worked, so I had to try a manual install, which said no errors. On reboot, I have the "grub>" prompt. So, given the disc layout above, which I recall was about 20GB for / and about 90GB for /home, do you still think I should be separately mounting /mnt/boot, and, was it correct to install grub-pc, or should I have installed grub-legacy? Many thanks for your help (and to all the others who have been helping as well), but it seems that we are not there yet. Hopefully some of the above will provide some more clues to those of you with knowledge of these things Cheers, -- Regards, Terry Duell
On Sun, Sep 29, 2013 at 09:00:00AM +1000, Terry Duell wrote:
here is the disc layout Device Boot Start End Blocks Id System /dev/sda1 2048 40962047 20480000 83 Linux /dev/sda2 40962048 229378047 94208000 5 Extended /dev/sda3 229378048 234440703 2531328 82 Linux swap / Solaris /dev/sda5 40964096 229378047 94206976 83 Linux
I thought I'd try "mount /dev/sda2 /mnt/boot" just to see what happens, and when I do I get... "mount: you must specify the filesystem type" , so thought it best to not separately mount /mnt/boot
it looks like your /boot IS just a subdirectory on / but can you post a copy of your /etc/fstab ?
went through the whole process, purged grub and reinstalled. "apt-get install grub" says it is going to install grub-legacy, which doesn't seem right, so installed grub-pc instead, but at the end of the
yep, grub-pc is correct. mint's grub package must be slightly different to debian's, on my debian sid machine it depends on grub-pc rather than grub-legacy. does this computer have a traditional BIOS or is it UEFI? since the disk doesn't have a gpt partition table and you don't have a small FAT32 efi partition on the disk, i'll guess traditional bios...but it's worth confirming that.
installation it pops up a screen asking if I want grub installed on /dev/sda (and displayed ???) or /dev/sda1 (which it thought was /), neither worked, so I had to try a manual install, which said no errors.
installing to /dev/sda is what you want - install into the master boot record (MBR)
On reboot, I have the "grub>" prompt.
can you attach a copy of your /boot/grub/grub.cfg or upload it to a pastebin site ? there are dozens of pastebin sites around. http://bash.nopaste.dk/ or http://pastebin.com/ are two of many.
was it correct to install grub-pc, or should I have installed grub-legacy?
grub-pc the only reason to install grub-legacy is if you already have it installed and really don't want to upgrade for some reason. there's no good technical reason for doing so (in fact, lots of good technical reasons for upgrading to grub2), just personal choice. craig -- craig sanders <cas@taz.net.au>
On 29/09/13 10:34, Craig Sanders wrote:
On Sun, Sep 29, 2013 at 09:00:00AM +1000, Terry Duell wrote:
here is the disc layout Device Boot Start End Blocks Id System /dev/sda1 2048 40962047 20480000 83 Linux /dev/sda2 40962048 229378047 94208000 5 Extended /dev/sda3 229378048 234440703 2531328 82 Linux swap / Solaris /dev/sda5 40964096 229378047 94206976 83 Linux
I thought I'd try "mount /dev/sda2 /mnt/boot" just to see what happens, and when I do I get... "mount: you must specify the filesystem type" , so thought it best to not separately mount /mnt/boot
it looks like your /boot IS just a subdirectory on / but can you post a copy of your /etc/fstab ?
went through the whole process, purged grub and reinstalled. "apt-get install grub" says it is going to install grub-legacy, which doesn't seem right, so installed grub-pc instead, but at the end of the
yep, grub-pc is correct. mint's grub package must be slightly different to debian's, on my debian sid machine it depends on grub-pc rather than grub-legacy.
Terry is using LMDE - Linux Mint Debian Edition. From the LM website LMDE is: - ...a semi-rolling distribution based on Debian Testing. - It’s available in both 32 and 64-bit as a live DVD with MATE or Cinnamon. - The purpose of LMDE is to look identical to the main edition and to provide the same functionality while using Debian as a base. As it happens I'm sending this from a laptop with LMDE on awaiting a number of updates, inc grup-pc but also update to the latest release, UP7. I see in the release notes that it says do not do any updates until you've upgraded the Update Pack to version 7, then do package updates.
On Sun, 29 Sep 2013 15:00:15 +1000, Colin Fee <tfeccles@gmail.com> wrote:
Terry is using LMDE - Linux Mint Debian Edition. From the LM website LMDE is:
- ...a semi-rolling distribution based on Debian Testing. - It’s available in both 32 and 64-bit as a live DVD with MATE or Cinnamon. - The purpose of LMDE is to look identical to the main edition and to provide the same functionality while using Debian as a base.
As it happens I'm sending this from a laptop with LMDE on awaiting a number of updates, inc grup-pc but also update to the latest release, UP7. I see in the release notes that it says do not do any updates until you've upgraded the Update Pack to version 7, then do package updates.
Yes, I'm using LMDE, and simply followed the advice of the system which said "updates available...etc". It would seem that I need to be more careful. So, does this imply that my system is all bu##ered up, and there is no way out? Not sure if it's possible to update the system now, from a live distro boot and a chroot. Cheers, -- Regards, Terry Duell
On Sunday, 29 September 2013, Terry Duell wrote:
On Sun, 29 Sep 2013 15:00:15 +1000, Colin Fee <tfeccles@gmail.com<javascript:;>> wrote:
Terry is using LMDE - Linux Mint Debian Edition. From the LM website LMDE is:
- ...a semi-rolling distribution based on Debian Testing. - It’s available in both 32 and 64-bit as a live DVD with MATE or Cinnamon. - The purpose of LMDE is to look identical to the main edition and to provide the same functionality while using Debian as a base.
As it happens I'm sending this from a laptop with LMDE on awaiting a number of updates, inc grup-pc but also update to the latest release, UP7. I see in the release notes that it says do not do any updates until you've upgraded the Update Pack to version 7, then do package updates.
Yes, I'm using LMDE, and simply followed the advice of the system which said "updates available...etc". It would seem that I need to be more careful. So, does this imply that my system is all bu##ered up, and there is no way out? Not sure if it's possible to update the system now, from a live distro boot and a chroot.
Having rechecked the perquisites for the update, I've just kicked off the update on my laptop. I'll see if I have the same issues. Fingers crossed. The two main points the release notes made were one that the you needed to be pointed to a mirror that is at the UP7 level and two that when you check the Update Pack Info section of the update manager that it shows green i.e. no errors. Mine was all good some set it off. They also say I the FAQ that you'll be asked to install grub during the update which by default will install to /dev/sda. -- Colin Fee tfeccles@gmail.com
So that was a big fat failure but not in the same way as Terry's. I left it unattended as it processed, after providing some necessary answers. When I returned to check on process the Update Manager had halted saying processing was stopped due to too many errors. Investigating now. On 29 September 2013 17:13, Colin Fee <tfeccles@gmail.com> wrote:
On Sunday, 29 September 2013, Terry Duell wrote:
On Sun, 29 Sep 2013 15:00:15 +1000, Colin Fee <tfeccles@gmail.com> wrote:
Terry is using LMDE - Linux Mint Debian Edition. From the LM website LMDE is:
- ...a semi-rolling distribution based on Debian Testing. - It’s available in both 32 and 64-bit as a live DVD with MATE or Cinnamon. - The purpose of LMDE is to look identical to the main edition and to provide the same functionality while using Debian as a base.
As it happens I'm sending this from a laptop with LMDE on awaiting a number of updates, inc grup-pc but also update to the latest release, UP7. I see in the release notes that it says do not do any updates until you've upgraded the Update Pack to version 7, then do package updates.
Yes, I'm using LMDE, and simply followed the advice of the system which said "updates available...etc". It would seem that I need to be more careful. So, does this imply that my system is all bu##ered up, and there is no way out? Not sure if it's possible to update the system now, from a live distro boot and a chroot.
Having rechecked the perquisites for the update, I've just kicked off the update on my laptop. I'll see if I have the same issues. Fingers crossed.
The two main points the release notes made were one that the you needed to be pointed to a mirror that is at the UP7 level and two that when you check the Update Pack Info section of the update manager that it shows green i.e. no errors. Mine was all good some set it off.
They also say I the FAQ that you'll be asked to install grub during the update which by default will install to /dev/sda.
-- Colin Fee tfeccles@gmail.com
-- Colin Fee tfeccles@gmail.com
Not sure wha the overall cuse was but I now have a working laptop again with LMDE fully up to date. I used the method as outlined by Craig however I had to battle with the b......y firewire controller first. Seems there's abug in the earlier kernels that causes the system to halt obn boot from live cd/usb when it attempts to active the firewire in this case via firewire_ohci. Despite you telling it to blacklist the module it ignores it and attempts to start it anyway at which point the boot process hangs. I eventually got to a working system using parted magic off the UBCD. Was then able to chroot into the broken system with network available and complete the update. It took an apt-get -f install followed by teo more apt-get update/upgrade rounds. On 29 September 2013 20:50, Colin Fee <tfeccles@gmail.com> wrote:
So that was a big fat failure but not in the same way as Terry's. I left it unattended as it processed, after providing some necessary answers. When I returned to check on process the Update Manager had halted saying processing was stopped due to too many errors. Investigating now.
On 29 September 2013 17:13, Colin Fee <tfeccles@gmail.com> wrote:
On Sunday, 29 September 2013, Terry Duell wrote:
On Sun, 29 Sep 2013 15:00:15 +1000, Colin Fee <tfeccles@gmail.com> wrote:
Terry is using LMDE - Linux Mint Debian Edition. From the LM website LMDE is:
- ...a semi-rolling distribution based on Debian Testing. - It’s available in both 32 and 64-bit as a live DVD with MATE or Cinnamon. - The purpose of LMDE is to look identical to the main edition and to provide the same functionality while using Debian as a base.
As it happens I'm sending this from a laptop with LMDE on awaiting a number of updates, inc grup-pc but also update to the latest release, UP7. I see in the release notes that it says do not do any updates until you've upgraded the Update Pack to version 7, then do package updates.
Yes, I'm using LMDE, and simply followed the advice of the system which said "updates available...etc". It would seem that I need to be more careful. So, does this imply that my system is all bu##ered up, and there is no way out? Not sure if it's possible to update the system now, from a live distro boot and a chroot.
Having rechecked the perquisites for the update, I've just kicked off the update on my laptop. I'll see if I have the same issues. Fingers crossed.
The two main points the release notes made were one that the you needed to be pointed to a mirror that is at the UP7 level and two that when you check the Update Pack Info section of the update manager that it shows green i.e. no errors. Mine was all good some set it off.
They also say I the FAQ that you'll be asked to install grub during the update which by default will install to /dev/sda.
-- Colin Fee tfeccles@gmail.com
-- Colin Fee tfeccles@gmail.com
-- Colin Fee tfeccles@gmail.com
On Sun, 29 Sep 2013 17:13:55 +1000, Colin Fee <tfeccles@gmail.com> wrote:
Having rechecked the perquisites for the update, I've just kicked off the update on my laptop. I'll see if I have the same issues. Fingers crossed.
The two main points the release notes made were one that the you needed to be pointed to a mirror that is at the UP7 level and two that when you check the Update Pack Info section of the update manager that it shows green i.e. no errors. Mine was all good some set it off.
They also say I the FAQ that you'll be asked to install grub during the update which by default will install to /dev/sda.
I read that. I wasn't asked about grub installation. I checked (whilst booted via a live distro and chroot) which mirror the system was currently pointed at, and it was one of in the UP7 list, but can't say if this applied prior to the update. Cheers, -- Regards, Terry Duell
On Sun, 29 Sep 2013 10:34:18 +1000, Craig Sanders <cas@taz.net.au> wrote:
it looks like your /boot IS just a subdirectory on / but can you post a copy of your /etc/fstab ?
[snip]
can you attach a copy of your /boot/grub/grub.cfg or upload it to a pastebin site ?
Here are my /etc/fstab and /boot/grub/grub.cfg Hope is OK to attach them to email. --------------------------------------------------- # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/sda1 UUID=d7740eca-4100-41af-848d-b17aff55fe2d / ext4 rw,errors=remount-ro 0 1 # /dev/sda5 UUID=b6e14f1f-9a5d-4915-b9fd-e44b0203b171 /home ext4 rw,errors=remount-ro 0 0 # /dev/sda3 UUID=f8abfb88-d663-4ddb-8816-f5a92f0855ab swap swap sw 0 0 --------------------------------------------------- localhost grub # more grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="0" if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { true } insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d if loadfont /usr/share/grub/unicode.pf2 ; then set gfxmode=640x480 load_video insmod gfxterm fi terminal_output gfxterm set timeout=5 ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### set menu_color_normal=cyan/blue set menu_color_highlight=white/blue ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/06_mint_theme ### set menu_color_normal=white/black set menu_color_highlight=white/light-gray ### END /etc/grub.d/06_mint_theme ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'LinuxMint GNU/Linux, with Linux 3.10-2-amd64' --class linuxmint --class gnu-linux --class gnu --c lass os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.10-2-amd64 ...' linux /boot/vmlinuz-3.10-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.10-2-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.10-2-amd64 (recovery mode)' --class linuxmint --class gnu-linux --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.10-2-amd64 ...' linux /boot/vmlinuz-3.10-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.10-2-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-4-amd64' --class linuxmint --class gnu-linux --class gnu -- class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-4-amd64 ...' linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-4-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode)' --class linuxmint --class gnu-linu x --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-4-amd64 ...' linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-4-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-2-amd64' --class linuxmint --class gnu-linux --class gnu -- class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-2-amd64 ...' linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-2-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-2-amd64 (recovery mode)' --class linuxmint --class gnu-linu x --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-2-amd64 ...' linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-2-amd64 } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### localhost grub # Cheers, -- Regards, Terry Duell
On Sun, Sep 29, 2013 at 03:53:28PM +1000, Terry Duell wrote:
Here are my /etc/fstab and /boot/grub/grub.cfg Hope is OK to attach them to email.
about the only thing left that i can think of to try is to type in (a simplified version of) one of the boot menu items at the grub prompt. insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --file --set=root /dev/sda1 linux /boot/vmlinuz-3.10-2-amd64 root=/dev/sda1 ro quiet initrd /boot/initrd.img-3.10-2-amd64 if that works, it should get your system booted up - but not fixed. before rebooting again, you should get to a root shell, check that /etc/default/grub is OK, and either run grub-install or update-grub again. it sounds, though, as if there's a bug in the particular version of grub you're running....it doesn't seem to know where to find its configuration (grub.cfg), so re-installing or update-grub may not fix the problem, and you won't know until you try to reboot again. you may have to wait until LMDE releases an updated grub package. or revert to the previous version of grub2 if you still have it available. craig -- craig sanders <cas@taz.net.au>
Hello Craig, On Mon, 30 Sep 2013 08:35:42 +1000, Craig Sanders <cas@taz.net.au> wrote:
On Sun, Sep 29, 2013 at 03:53:28PM +1000, Terry Duell wrote:
Here are my /etc/fstab and /boot/grub/grub.cfg Hope is OK to attach them to email.
about the only thing left that i can think of to try is to type in (a simplified version of) one of the boot menu items at the grub prompt.
insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --file --set=root /dev/sda1 linux /boot/vmlinuz-3.10-2-amd64 root=/dev/sda1 ro quiet initrd /boot/initrd.img-3.10-2-amd64
Well I'm now getting "grub rescue>" when I boot, which reports "error: file not found" at the first command, above. I'll do a bit research on "grub rescue" to see if that leads to anything, otherwise I'll re-try the previous process that you described for me, including purging grub packages, and see if that gets me to the "grub>" prompt, or (faint hope) better. Thanks for taking the time to help with this. Cheers, -- Regards, Terry Duell
On Mon, 30 Sep 2013 09:13:34 +1000, Terry Duell <tduell@iinet.net.au> wrote:
Hello Craig,
On Mon, 30 Sep 2013 08:35:42 +1000, Craig Sanders <cas@taz.net.au> wrote:
On Sun, Sep 29, 2013 at 03:53:28PM +1000, Terry Duell wrote:
Here are my /etc/fstab and /boot/grub/grub.cfg Hope is OK to attach them to email.
about the only thing left that i can think of to try is to type in (a simplified version of) one of the boot menu items at the grub prompt.
insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --file --set=root /dev/sda1 linux /boot/vmlinuz-3.10-2-amd64 root=/dev/sda1 ro quiet initrd /boot/initrd.img-3.10-2-amd64
Well I'm now getting "grub rescue>" when I boot, which reports "error: file not found" at the first command, above. I'll do a bit research on "grub rescue" to see if that leads to anything, otherwise I'll re-try the previous process that you described for me, including purging grub packages, and see if that gets me to the "grub>" prompt, or (faint hope) better.
Not much luck finding any useful info on how to progress from "grub rescue>" prompt. I went through the whole process again, purging grub, and then reinstalling grub-pc. A curious thing, when I try "grub-install /dev/sda" it says grub-install not available, install grub-legacy. If I do that I then end up with all sorts of stuff in /boot/grub from both versions. Maybe I'm assuming too much. Having run "apt-get install grub-pc" ( which then asks me to run "apt-get -f install") is it necessary to run "grub-install" or has that already been done? (the saga lingers on :-) Cheers, -- Regards, Terry Duell
Terry Duell <tduell@iinet.net.au> wrote:
Maybe I'm assuming too much. Having run "apt-get install grub-pc" ( which then asks me to run "apt-get -f install") is it necessary to run "grub-install" or has that already been done?
It usually prompts you to run apt-get -f install because there are broken packages on the system, so it might be worth running it to see what it wants to upgrade/remove/fix. You need both grub-pc (Grub 2.0) and the corresponding version of grub-install, which in Debian is in the grub-common package. Make sure that running grub-install --version gives 2.0 or a later version. Mine is grub-install (GRUB) 2.00-19 You're trying to run an old version of grub-install with Grub 2.0 - that won't work.
Hello Jason, On Mon, 30 Sep 2013 09:55:55 +1000, Jason White <jason@jasonjgw.net> wrote:
Terry Duell <tduell@iinet.net.au> wrote:
Maybe I'm assuming too much. Having run "apt-get install grub-pc" ( which then asks me to run "apt-get -f install") is it necessary to run "grub-install" or has that already been done?
It usually prompts you to run apt-get -f install because there are broken packages on the system, so it might be worth running it to see what it wants to upgrade/remove/fix.
You need both grub-pc (Grub 2.0) and the corresponding version of grub-install, which in Debian is in the grub-common package. Make sure that running grub-install --version gives 2.0 or a later version. Mine is grub-install (GRUB) 2.00-19
You're trying to run an old version of grub-install with Grub 2.0 - that won't work.
Thanks, I'll try again! Cheers, -- Regards, Terry Duell
On 29/09/13 15:53, Terry Duell wrote:
On Sun, 29 Sep 2013 10:34:18 +1000, Craig Sanders <cas@taz.net.au> wrote:
it looks like your /boot IS just a subdirectory on / but can you post a copy of your /etc/fstab ? [snip]
can you attach a copy of your /boot/grub/grub.cfg or upload it to a pastebin site ? Here are my /etc/fstab and /boot/grub/grub.cfg Hope is OK to attach them to email.
--------------------------------------------------- # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/sda1 UUID=d7740eca-4100-41af-848d-b17aff55fe2d / ext4 rw,errors=remount-ro 0 1 # /dev/sda5 UUID=b6e14f1f-9a5d-4915-b9fd-e44b0203b171 /home ext4 rw,errors=remount-ro 0 0 # /dev/sda3 UUID=f8abfb88-d663-4ddb-8816-f5a92f0855ab swap swap sw 0 0
Ok, let's start here. The mount points / and /home are both being mounted via their unique UUID. The first thing to do is to confirm that the UUID and device nodes match up. ls -l /dev/disk/by-uuid should give you a list of UUIDs and show the path to the matching device node (example on next line) lrwxrwxrwx 1 root root 9 Sep 26 23:28 d7740eca-4100-41af-848d-b17aff55fe2d -> ../../sda1
--------------------------------------------------- localhost grub # more grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub #
### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="0" if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi
function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi }
function load_video { true }
insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d if loadfont /usr/share/grub/unicode.pf2 ; then set gfxmode=640x480 load_video insmod gfxterm fi terminal_output gfxterm set timeout=5 ### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ### set menu_color_normal=cyan/blue set menu_color_highlight=white/blue ### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/06_mint_theme ### set menu_color_normal=white/black set menu_color_highlight=white/light-gray ### END /etc/grub.d/06_mint_theme ###
### BEGIN /etc/grub.d/10_linux ### menuentry 'LinuxMint GNU/Linux, with Linux 3.10-2-amd64' --class linuxmint --class gnu-linux --class gnu --c lass os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.10-2-amd64 ...' linux /boot/vmlinuz-3.10-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.10-2-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.10-2-amd64 (recovery mode)' --class linuxmint --class gnu-linux --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.10-2-amd64 ...' linux /boot/vmlinuz-3.10-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.10-2-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-4-amd64' --class linuxmint --class gnu-linux --class gnu -- class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-4-amd64 ...' linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-4-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode)' --class linuxmint --class gnu-linu x --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-4-amd64 ...' linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-4-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-2-amd64' --class linuxmint --class gnu-linux --class gnu -- class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-2-amd64 ...' linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-2-amd64 } menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-2-amd64 (recovery mode)' --class linuxmint --class gnu-linu x --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d7740eca-4100-41af-848d-b17aff55fe2d echo 'Loading Linux 3.2.0-2-amd64 ...' linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=d7740eca-4100-41af-848d-b17aff55fe2d ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-2-amd64 } ### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### localhost grub #
Cheers,
Bingo! This config file is for the newer version of grub You need to install grub2 then run grub-install (grub2 will pull in grub-common and grub-pc) Note that you will need to do so from the chroot to the mounted filesystems, and may find that you need to give the full pathname to grub-install /usr/sbin/grub-install as it may not be in your $PATH Then run update-grub to have it check to see what kernels you have installed as this will regenerate the grub.cfg file based on what it finds. Good luck. Regards, Morrie.
Hello Morrie, On Mon, 30 Sep 2013 10:14:35 +1000, Morrie Wyatt <morrie@morrie.id.au> wrote: [snip]
Ok, let's start here. The mount points / and /home are both being mounted via their unique UUID.
The first thing to do is to confirm that the UUID and device nodes match up.
ls -l /dev/disk/by-uuid should give you a list of UUIDs and show the path to the matching device node (example on next line)
lrwxrwxrwx 1 root root 9 Sep 26 23:28 d7740eca-4100-41af-848d-b17aff55fe2d -> ../../sda1
This is all OK. The UUIDs all match. [snip]
Bingo! This config file is for the newer version of grub
You need to install grub2 then run grub-install (grub2 will pull in grub-common and grub-pc)
Tried that, but had to separately install grub-common and grub-pc. That process gave some feedback that some grub-legacy files existed and asked if I wanted to migrate to grub2, which I did, and then asked which drive to install grub...I chose /dev/sda, and then it went about its business. After going through the umount steps, a reboot gave the right result. My laptop boots. Great leap forward. Many thanks for your help, and to Craig, Nic and Colin for continuing to follow this saga and make helpful contributions. -- Regards, Terry Duell
On 30/09/2013 10:14 AM, Morrie Wyatt wrote:
The first thing to do is to confirm that the UUID and device nodes match up.
ls -l /dev/disk/by-uuid should give you a list of UUIDs and show the path to the matching device node (example on next line)
lrwxrwxrwx 1 root root 9 Sep 26 23:28 d7740eca-4100-41af-848d-b17aff55fe2d -> ../../sda1
An easier way to do that is: blkid -c /dev/null The -c uses a cache of /dev/null, that is, [to the tool/OS] don't rely on what you think you know, go and check it all and report current state of each partition. If there was a mirror [or other mdadm raid device] involved, then it would need to be made active to see it's UUID details. Similar for activation of lvm2. Cheers A.
Terry Duell <tduell@iinet.net.au> wrote:
"grub-install -v" returns grub-install (GNU GRUB 0.97), doesn't look like grub2, but maybe it announces itself this way?
No, that's definitely Grub-legacy. If you have boot/grub/grub.cfg (a Grub 2 configuration file) and grub-install 0.99 installed, something is seriously amiss with the package upgrade. What package management system is your distribution using? If it's Debian-based, make sure that grub-pc is installed (on the system, not the live CD that is).
participants (7)
-
Andrew McGlashan -
Colin Fee -
Craig Sanders -
Jason White -
Morrie Wyatt -
Nic Baxter -
Terry Duell