Hi,
On Wed, Mar 5, 2008 at 1:55 PM, Lev Olshvang <[EMAIL PROTECTED]> wrote:
>
>
> It had finished successfully and required the reboot.
> After reboot I got blank screen filled with "7777" and so I used the SCD
> rescue to reinstall grub.
So I assume you installed grub correctly at this time?
>
> Several strange things happened :
>
> 1. fsck on / runs only e2fsk although I know my / is ext3
Not strange. Ext3 is only an extension to ext2. (not exactly, but close
enough) There is no problem to mount ext3 filesystem as ext2. fsck is only
one of a bunch of tools referred to with the no. 2. (resize2fs is another
example)
On Kubuntu, e2fsck and fsck.ext3 are hard links for the same inode (check it
using 'ls -li')
> 2. when boot from Hard Disk, grub does not see /boot/vmlinuz (my boot
> partition is on thirst slice of HD),
> but it sees it as /vmlinuz
> The same with initrd
That's correct. grub looks for the kernel and the initrd relatively to the
boot partition.
Also, a file called /boot/grub/device.map defines the mapping between grubs
aliasing (hd0 is an example for an alias) and the physical devices.
So, you can see in the menu.lst (grub.conf in redhat based distros) that the
"root" line is "hd0,0" (the second 0 refers to the first partition of hd0,
which is /boot on your case)
3. When grub finally boot the system
> fsck error on / and was thrown into maintanence shell:
> fsck 1.40.2 (12-Jul-2007)
> fsck.ext3: symbol lookup error: fsck.ext3: undefined symbol:
> et_ext2_error_table
> fsck.ext3: symbol lookup error: fsck.ext3: undefined symbol:
> et_ext2_error_table
> fsck died with exit status 127
>
Your upgrade did not finish cleanly and completely and there is a missing
dependency for the fsck tool.
> Since / is mounted read-only
Try remounting the filesystem r/w ("mount -o remount,rw /")
> I tried to boot from SCD and fix
> filesystem but SCD thinks it is ext2 and OK
Try mounting the filesystem and specify ext3 explicitly (-t ext3).
good luck.
- Noam
