Boot stops. Can't find (mount?) partitions. Why?
This is openSuSE 11.0
Bootsplash verbose, excerpt from the output: Code:
... This is the disk from my old box {deceased}. I installed it as second disk in my new box which runs openSuSE 11.3_64. This second disk carries openSuSE 11.2 which I can boot with the same GRUB, openSuSE 11.0 which throws the errors shown above and FreeBSD which breaks off booting ending up in a prompt "mountroot>". I need the old SuSE she has our homebanking program :(. |
As I understand your post, you removed the hard drive containing Opensuse 11.0 and placed it in a drive which has Opensuse 11.3 and 11.2 on it and you are able to successfully boot the latter two using Grub from, 11.3?
Check the menu.lst entry from 11.3 (if you are using its Grub) to see what entry you have for 11.0. Check the /etc/fstab to see what it has. It's looking for the system on partition 7. Is that where it is? I have Opensuse 11.2 and had problems booting a couple of other systems. Using a configfile entry or chainloader in place of the /dev/disk/by-id worked for me. Lazy way out but... If you use the configfile or chainloader you will need the Grub files in 11.0. |
Umm, no and yes ;).
I placed the old drive in a new computer, all unchanged, i.e. the hardware moved over to the new chassis. The old one has 11.0 and 11.2 on it. On boot 11.0 dies with the messages shown in the OP, but I can boot 11.2. (and of course 11.3_64 from my new drive). I made the old drive bootable in the BIOS and I also chainloaded the old GRUB(!) with my latest installation on the new drive resulting in the same failure. And yes, 11.0's "/" is on /dev/sdb7. This is the new /boot/grub menu.lst: Quote:
Quote:
|
When you boot initially, it is using the OS 11.3 bootloader, the one you refer to as the "new" menu.lst, is that correct?
Does the problem occur when selecting 11.0 from this menu? It shows the two standard entries for 11.3, the next title line show 11.2 and 11.0 and I expect that boots 11.2? The title line after that is just for 11.0 which when selected fails? Note the root entries. You have root (hd0,0) for 11.3 and 11.0 and 11.2 shows root (hd1,0). 11.2 and 11.0 are on the same drive, correct? If so, change the 11.0 entry to reflect which partition it is on. If that is not the problem, I mean if you boot from your initial menu.lst on 11.3 and select the 11.2 and 11.0 chainloader entry and then get the problem, the solution would be different. The menu.lst from the old drive is from OS 11.2? If so, and this is where the problem comes up, check its /etc/fstab file. The error complains about not being able to find sdb9, swap partition. Do you have that? The other part of the error is "Could not find /dev/disk/by-id/ata-Maxtor....-part7...". It's looking for partition 7 without success! In the second menu.lst (old) are those the original entries? Posting your partition info might help? |
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Code:
linux-3ppp:/home/me # fdisk -l |
The changes (for now) should just be on the old menu.lst, from 11.2.
Just to clarify, when you select from the new menu.lst the 11.2 chainloader entry, you are able to successfully boot 11.2 off the second menu.lst but booting 11.0 from that menu.lst fails? I would suggest you change the entry for 11.0 from: root (hd1,0) to root (hd1,6). I have Opensuse 11.2 and here is its menu.lst entry. It is on sda8, swap on partition 6: Quote:
You could check the disk by-id to make sure they are correct. I doubt this is the problem though: ls /dev/disk/by-id |
Quote:
Quote:
Quote:
Quote:
Quote:
In the meantime I think that this is a kernel problem. When you re-read my very first post and examine the last line of the "code"-text box it reads: "Not found, exiting to /bin/sh". That's not GRUB's command line that is the shell of the booting kernel I'd say. Any thoughts on this? |
Hello JZL240I-U,
Quote:
Markus |
The old box is dead (doesn't show even the BIOS messages during power-on self test) so I can't run lspci there.
Wait, I re-re-re-read your post: "missing driver for the disk-controller" you wrote. I'm way out of my depth here but if 11.0 should lack the driver for the controller, how can I find out which one it is (i.e. its name) and is there a way to insert it into the existing installation of 11.0? P.S.: I do have a CD with drivers of the Gigabyte board, but I doubt that there is anything for linux. I'll look soonest. |
Well the point is that I know a similar issue when booting a new Gentooinstallation and my selfbuild kernel is missing the SATA-Controller. In your case the point is, that the drivers for your Harddisk must be in the kernel since it would not have been running in your old computer. But there must be a difference in the hardware. So I would look at lspci with a live-CD and then search in the kernels .config file.
Markus Edit: you may use lspci with the other Suse installation. But then it may be easier to compare both .config files. Another (better) idea. Start your Suse 11.3 and chroot into the old Suse, then execute lsmod and find out what the old kernel is missing. |
Quote:
But one can load kernel modules. If I find the correct one, how to insert that during boot? I can boot the new hardware and get a lspci, I'll post it soonest -- only right now I'm not sitting in front of that box. Quote:
|
Well, I see, this is complicated in your case, since a chroot from a 64bit into a 32bit installation is not easy. Read this: http://www.gentoo.de/doc/de/handbook...?part=1&chap=6 and this http://www.gentoo.org/proj/en/base/a...?part=1&chap=2 . You can istead boot with a 32bit live-CD (e.g. slax) and chroot to the old HD. Then you may build a new kernel with the necessary drivers.
Markus |
No no, it is not that problematic at all: I still have the old 11.2 on the same old disk which does boot :). You suggest chroot'ing to the old installation? Hmm, well worth a try. I'll read up on chroot (never used it before).
|
ok, make a directory
Code:
mkdir /mnt/oldsuse Code:
mount /dev/whereureoldSuseis /mnt/oldsuse Markus |
I'll try that tomorrow and report back after that. Thanks for your support :).
|
All times are GMT -5. The time now is 08:19 PM. |