grub errors and read-only

Donal Farrell vmlinuz101 at gmail.com
Fri Aug 5 03:38:21 PDT 2005


Hi there. I'm having serious problems since I put FC4 on my system which
already has (B)LFS 6.0 and SuSE 9.1. I can't boot into SuSE or LFS at
present. Actually, FC4 might not be the problem. I tried to put Sarge
on /dev/hda which was a primary partition I made. I'm using the
linuxformat dvd, so I had to disable my cdrom and enable the dvd-rw in
the bios. This is all very well until the debian base package tries to
install where it looks for the cd drive. I tried to mount debian
on /boot in /dev/hda2. Prior to this, suse was mounted on / on /dev/hda1
and lfs on / on /dev/hda4 with a swap on /dev/hda3. After I aborted the
debian install to try make iso cds instead of the dvd, I got stuck when
trying to boot into suse. using the suse rescue disk, i did a
fsck.reiserfs which repaired any errors on /dev/hda1. grub however
failed to recover, pointing to a mount error on /dev/hda2 (????) I tried
booting the installed system using the rescue cd (i.e. to boot suse on /
on /dev/hda1) the result was my root directory mounted read-only and a
fsck.reiserfs showing error 6 for /dev/hda2 

I installed FC4 to get a working system. Fine. FC4 is mounted on /
on /dev/hda2 (ext3) I then mounted suse to mount (i.e.
mount /dev/hda1 /mnt) I still have everything here, which is fine. Also,
I can mount LFS (mount /dev/hda4 /mnt) and everything is fine here also.
I tried to get a backup menu.lst from /var/log/messages and
from /boot/grub/menu.lst~old ->nothing 

Here is a console output of SuSE's filesystem from inside /mnt on FC4

[root at localhost mnt]# ls -la
total 223
drwxr-xr-x   22 root root    560 Aug  4  2005 .
drwxr-xr-x   23 root root   4096 Aug  4 12:02 ..
drwxr-xr-x    2 root root   2888 Aug  4  2005 bin
drwxr-xr-x    3 root root   1544 Aug  4  2005 boot
drwxr-xr-x   35 root root 180800 Aug  4  2005 dev
drwxr-xr-x   95 root root   8880 Aug  4  2005 etc
drwxr-xr-x    2 root root     96 Sep 22  2004 games
drwxr-xr-x    5 root root    120 Jun  4 11:45 home
drwxr-xr-x   12 root root   3384 Aug 20  2004 lib
drwxr-xr-x    8 root root    320 Jun 30 19:43 media
drwxr-xr-x    3 root root     72 Apr  5 17:05 mnt
drwxr-xr-x   11 root root    296 Dec 17  2004 opt
drwxr-xr-x    2 root root     48 Aug 20  2004 proc
drwx------  128 root root   7264 Aug  4  2005 root
drwxr-xr-x    3 root root   8720 Aug  4  2005 sbin
drwxr-xr-x    5 root root    120 Dec 17  2004 srv
-rw-r--r--    1 root root      0 Aug  4  2005 success
drwxr-xr-x    2 root root     48 Aug 20  2004 sys
drwxrwxrwt  117 root root   7200 Aug  4  2005 tmp
lrwxrwxrwx    1 root root     14 Apr  5 17:10 tools -> /mnt/lfs/tools
drwxr-xr-x   12 root root    344 Jan 26  2005 usr
drwxr-xr-x   15 root root    384 Aug 20  2004 var


Also, and sorry about the message length, here is my /etc/fstab for SuSE

devpts               /dev/pts             devpts     mode=0620,gid=5
0 0
proc                 /proc                proc       defaults
0 0
usbfs                /proc/bus/usb        usbfs      noauto
0 0
sysfs                /sys                 sysfs      noauto
0 0
/dev/hdb4            /media/zip           auto       noauto,user
0 0
/dev/cdrecorder      /media/cdrecorder    subfs
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/cdrom           /media/cdrom         subfs
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0

/dev/hda3            swap                 swap       pri=42
0 0
/dev/hda1            /mnt/lfs             reiserfs   defaults 		   0 0	
/dev/hda2            /boot                reiserfs   acl,user_xattr
1 2

This seems strange. The /boot mount point for debian still exists. Even
though fdisk shows 
/dev/hda1              96       62523    31463302+  83  Linux (suse)
/dev/hda2   *       62524       93731    15728832   83  Linux (fedora)
/dev/hda3           93732       95812     1048824   82  Linux swap 
/dev/hda4           95813      127020    15728832   83  Linux (This is
lfs)

So what should I do now to get suse and lfs back running? Thanks in
advance



More information about the blfs-support mailing list