Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As it stands, it will only partially boot: It starts to boot and hangs at "waiting for root file system."
After several minutes it says "PCI: Failed to allocate mem resource #6:" and a bunch of numbers. Then "ALERT! /dev/sda1 does not exist. Dropping to a shell!" Then it gives me a BusyBox shell.
While I think that upgrading from 6.06 is a good idea, I don't agree that linux "isn't recognizing your chipset". Instead it appears the boot manager isn't finding your root partition.
If you want to boot from your old drive, you have to tell grub where to look for the root filesystem.
From your other posts, it seems clear that there is some confusion about what drive is where. So, what is your exact drive topology? You have a new SATA drive? Is it sda? Is sdb your old drive? What kind of drive is your old drive? SATA? SCSI?
I suggest you boot with a live CD then run fdisk -l to get a listing of what is connected to your system. Once that is clear, sorting your boot troubles out won't be a big problem.
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
jiml8--
Many thanks.
Here is what I get from fdisk -l: nothing, just another command line prompt.
However, gparted reports these:
/dev/sda 74.53 GiB unallocated
/dev/sdb1 184.89 GiB ext3 / flag is boot
/dev/sdb2 extended 1.42 GiB
/dev/sdb5 linux-swap 1.42 GiB
So sda appears to be the new 80 gig, and sdb the old 200 gig.
Both are SATA Western Digital.
I have tried to boot using sdb1, 2, and 5 and none get me anywhere. It simply tells me that it cannot find sdb1 or 2 or 5.
Oh! Just ran sudo fdisk -l and got this additional info: sda does not contain a valid partition table. Also sdb1 has an Id 83, sdb2 has 5, and sdb5 has 82, if those mean anything. It also shows that sdb1 starts at cylinder 1; 2 starts at 24137, as does 5 (gparted had shown 5 indented under 2).
Thanks for jumping in here with your note of hope!
The boot-loader has done it's job and loaded the kernel - it is the kernel that mounts the root.
To test booting the old drive, merely pull the cable out of the new drive - interface or power, doesn't matter. That way the old drive will be /dev/sda again.
As for my comment, when (if) you use the alternate CD you specify the partition/mountpoint you want assigned. As I suggested, you need to do this if you want "/home" as a separate partition.
If you do this (and use the same user/password), all your old configuration data will be available to you on the new system.
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
As I am writing this, I am on the second download that syg00 suggested. I will try his install after I have had some sleep, unless someone stops me!
Tonight I tried all these things, with these results:
1. with livecd, put fstab and menu.lst back to sda1 from sdb1; next pull data cable on the new drive; reboot: Waiting for root file system. This was a test to see if it would boot without the new drive running. It failed this test.
2. Question: What is that "PCI: Failed to allocate mem resource #6" stuff all about?
3. Rebooted with live cd: sudo gparted shows now just /dev/sda1 with the same info as before for sdb. So this tells me I pulled the cable on the correct one.
4. mkdir /606; mount -t ext3 /dev/sda1 /606; cd /606; sudo chroot /606 /bin/bash; apt-get update; apt-get install udev: already have the latest udev
sudo nano -w /etc/hosts and changed 127.0.0.1 from doug2 to ubuntu; sudo mount -o remount,rw /; sudo /sbin/evms_activate; nano and changed back to doug2; reboot: Waiting for root file system;
tried the two mount and evms_activate commands from the command line after "/dev/sda1 does not exist". mount gave “Cannot read /etc/fstab: No such file or directory”; evms gave: “Engine: Unable to open the control node for Device-Mapper. The Engine will run without Device-Mapper support.” Rebooted: Waiting for root file system.
These tell me that the evms_activate stuff I found on evms.sourceforge did not help.
5. reboot with live cd: mounted the sda1 partition and did du -h: 23G. So there is probably room on the new 80 gig drive for this.
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
syg00--
Quote:
Originally Posted by syg00
Grab a liveCD and copy /home out to a new partition - either disk, doesn't matter, but on the new one makes sense.
Grab the "alternate" CD for gutsy, and install onto the new disk, nominating the /home partition (not to be formatted), and install fresh.
When you say copy /home out, I am guessing you mean to copy /home from the old drive to the new location, not the one from the live cd. Right?
So I would suspect I need to format the new disk to enable the copy. Does gparted handle this? Or can I copy to here without that step and then let the alternate CD handle partitioning, formatting, etc.?
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
jiml8--
Please note that I had edited this to change the first two references to sdb1 (as well as changing the references in /etc/fstab the same way). That did not work--still got Waiting for root filesystem message--and so I put them back.
Code:
# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# default 5
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# 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'.
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## 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=/dev/sda1 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## 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
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) 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
## 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
## ## End Default Options ##
title Ubuntu, kernel 2.6.15-29-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-29-386
savedefault
boot
title Ubuntu, kernel 2.6.15-29-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-29-386
boot
title Ubuntu, kernel 2.6.15-28-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-28-386
savedefault
boot
title Ubuntu, kernel 2.6.15-28-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-28-386
boot
title Ubuntu, kernel 2.6.15-27-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-27-386
savedefault
boot
title Ubuntu, kernel 2.6.15-27-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-27-386
boot
title Ubuntu, kernel 2.6.15-26-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-26-386
savedefault
boot
title Ubuntu, kernel 2.6.15-26-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-26-386
boot
title Ubuntu, kernel 2.6.15-25-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-25-386
savedefault
boot
title Ubuntu, kernel 2.6.15-25-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-25-386
boot
title Ubuntu, kernel 2.6.12-10-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot
title Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.12-10-386
boot
title Ubuntu, kernel 2.6.12-9-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.12-9-386
savedefault
boot
title Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.12-9-386
boot
title Ubuntu, kernel 2.6.10-5-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot
title Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.10-5-386
boot
title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
title Win4Lin
root (hd0,0)
kernel /boot/win4lin root=/dev/sda1 ro quiet splash pci=noacpi ide=reverse
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
You are not booting from drive 0, you are booting from drive 1. So you have to change all references of hd0 to hd1, as well as changing all sda1 to sdb1.
Also take a look at /boot/grub/device.map to make sure you aren't getting some funky drive remapping (you probably aren't).
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
jiml8--
Ahh! I wondered what that hd(0,0) might be for!
Despite all your great help, I am still stuck. Can you help me further?
Here is my menu.lst (I did a search and replace on sda1 and hd0, and I think it got all of them):
Code:
# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# default 5
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# 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'.
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## 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 (hd1,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd1,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=/dev/sdb1 ro
## default grub root device
## e.g. groot=(hd1,0)
# groot=(hd1,0)
## 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
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) 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
## 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
## ## End Default Options ##
title Ubuntu, kernel 2.6.15-29-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro quiet splashinitrd
/boot/initrd.img-2.6.15-29-386
savedefault
boot
title Ubuntu, kernel 2.6.15-29-386 (recovery mode)
# root (hd1,0)
# kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro single
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.15-29-386
boot
title Ubuntu, kernel 2.6.15-28-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-28-386
savedefault
boot
title Ubuntu, kernel 2.6.15-28-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.15-28-386
boot
title Ubuntu, kernel 2.6.15-27-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-27-386
savedefault
boot
title Ubuntu, kernel 2.6.15-27-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.15-27-386
boot
title Ubuntu, kernel 2.6.15-26-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-26-386
savedefault
boot
title Ubuntu, kernel 2.6.15-26-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.15-26-386
boot
title Ubuntu, kernel 2.6.15-25-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-25-386
savedefault
boot
title Ubuntu, kernel 2.6.15-25-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.15-25-386
boot
title Ubuntu, kernel 2.6.12-10-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot
title Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.12-10-386
boot
title Ubuntu, kernel 2.6.12-9-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.12-9-386
savedefault
boot
title Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.12-9-386
boot
title Ubuntu, kernel 2.6.10-5-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot
title Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sdb1 ro single
initrd /boot/initrd.img-2.6.10-5-386
boot
title Ubuntu, memtest86+
root (hd1,0)
kernel /boot/memtest86+.bin
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
title Win4Lin
root (hd1,0)
kernel /boot/win4lin root=/dev/sdb1 ro quiet splash pci=noacpi ide=reverse
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
Here is the device.map file. This one I am not sure of how it should be (I added the second line; I tried it once with the first line commented out, but it did not work that way either):
Code:
(hd0) /dev/sda
(hd1) /dev/sdb
Here is my /etc/fstab file, again changed for sda/b. I am not sure of what the CD should be called, but I suspect that makes no difference for mounting the hdd:
One curious thing: when I choose this kernel in grub, and hit e, it still shows the kernel root line as sda1. It makes no difference if I change it to sdb1 or not: it still hangs at "Waiting for root file system."
It may be important for you to know that I installed 7.10 on the new drive, sda1. Grub gives that as the default choice and lists this kernel as the first of "other file systems."
Are we getting any closer, jiml8? Thanks for all your help. I feel like we are getting closer....
It may be important for you to know that I installed 7.10 on the new drive, sda1. Grub gives that as the default choice and lists this kernel as the first of "other file systems."
I thought that sda was unformatted, per your message 17 above.
Yes, that changes things considerably. What does your menu.lst on that drive say? That is the one being used to boot, apparently.
Also, now tell me what your goal is. You want to boot from the old drive or the new one?
One curious thing: when I choose this kernel in grub, and hit e, it still shows the kernel root line as sda1. It makes no difference if I change it to sdb1 or not: it still hangs at "Waiting for root file system."
You need to run fdisk on sda and toggle the bootable flag (the "a" command") to off. BIOS will then skip that drive and boot from sdb.
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
jiml8--
Here is the menu.lst for sda1:
Code:
# 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=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro
## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## 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
## 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 7.10, kernel 2.6.22-14-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet
title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro single
initrd /boot/initrd.img-2.6.22-14-generic
title Ubuntu 7.10, memtest86+
root (hd0,0)
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 an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-29-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-29-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-29-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-29-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-28-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-28-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-28-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-28-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-27-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-27-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-27-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-27-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-26-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-26-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-26-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-26-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-25-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.15-25-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.15-25-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.15-25-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.12-10-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.12-10-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.12-9-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.12-9-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.12-9-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.12-9-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.10-5-386 (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, kernel 2.6.10-5-386 (recovery mode) (on /dev/sdb1)
root (hd1,0)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Ubuntu, memtest86+ (on /dev/sdb1)
root (hd1,0)
kernel /boot/memtest86+.bin
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title Win4Lin (on /dev/sdb1)
root (hd1,0)
kernel /boot/win4lin root=/dev/sda1 ro quiet splash pci=noacpi ide=reverse
savedefault
boot
So I can see where it is getting the sda1 in there, despite the fact that I changed it on sdb1.
Yes, sda1 was unformatted in message 17; but since this is a production machine, I needed to get it up and running, so I proceeded in line with message 19 and syg00's original post to install 7.10 Gutsy to that drive. My goal is still to get the original drive working again, because I'd feel better with more room in the larger drive.
David1357--
Am trying that now. Will get back to you with the results.
<pause>
Nope, did not go. It did not seem to even get as far. It stopped with an Error 15.
Last edited by dgermann; 12-06-2007 at 07:42 PM.
Reason: update folks after trying a step
It is trying to boot using these entries, which still point at (hd0,0) and use a UUID to identify the boot partition. You need to comment out these lines.
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366
Original Poster
Rep:
David1357--
Those entries you quote are on the new drive, sda, and it had the boot flag removed. When Grub came up, it showed only the Grub entries from sdb.
A day or so ago, I even unplugged the data cable from sda, and still it was the same "Waiting for...."
So will commenting these out on sda help with this Error 15?
(It is getting to be a long thread, so it is hard to keep up with all the things that are in there right now! I could say I am getting confused, but I was to start! So no problem if someone not living with the problem misses what is the current state of things, David!)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
