| View previous topic :: View next topic |
| Author |
Message |
eltech
Guru
Joined: 05 Nov 2002
Posts: 582
Location: New York
|
 Posted: Thu Sep 21, 2006 4:49 pm Post subject: [SOLVED] odd boot up after a normal kernel upgrade |
 |
|
Greetings...
Today I upgraded the kernel on my gentoo box to vanilla-sources-2.4.32 and on rebbot i received..
| Code: | Checking root filesystem...
fsck.ext2: No such file or directory while trying to open /dev/sda1
/dev/sda1:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Filesystem couldn't be fixed :(
Give root password for maintenance (or type Control-D to continue) |
So I tried the e2fsck -b 8193 /dev/sda1, but it says it failed cause there isnt any such device.
All my configs are ok .. see below..
| Code: | /dev/sda1 /boot ext2 noauto,noatime 1 1
/dev/sda3 / reiserfs noatime 0 0
/dev/sda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
|
my grub config is below also ..
| Code: | default 0
timeout 10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=PCNS
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/sda3
|
My kernel upgrade steps are below and I have been using them for about 3 years now..
| Code: | # cd /usr/src/linux
# cp .config ~/
# rm /usr/src/linux
# ln -s /usr/src/linux-2.4.XX /usr/src/linux
# ls -al /usr/src/linux (TO CHECK CORRECT LINKING)
# cd /usr/src/linux
# make mrproper
# cp ~/.config .
# make menuconfig
# make dep && make clean bzImage modules modules_install
# mv /boot/bzImage /boot/bzImage.bak
# ls -al /boot (TO CHECK CORRECT LINKING)
# cp /usr/src/linux/arch/i386/boot/bzImage /boot
# umount /boot |
CTRL+D boots up fine, no errors and all works well, this is a box running lots of other stuff and in spite of these errors; all is well ..
But where did this go wrong? I have always upgraded kernels manually.. so I know I did this right.. Where can i start to troubleshoot this problem?
Thanks
Last edited by eltech on Mon Oct 30, 2006 12:48 pm; edited 1 time in total |
|
| Back to top |
|
 |
gentoome
Tux's lil' helper
Joined: 18 Jul 2005
Posts: 78
|
| Posted: Fri Sep 22, 2006 11:56 am Post subject: |
|
|
Hi,
I do not quite understand. Let's see if I get this roght first :
The kernel gets loaded, from sda1 no less (which means that at least the grub sees the partition), and then, the init process complains that sda1 does not exist. Really weird indeed.
However, the steps you use to configure your kernel mean that you start from scratch everytime (make mrproper). Is it not possible that you have overlooked an option this time (for example ext2 support) ?
Another explaination would be that the module in charge of the SCSI/SATA interface gets loaded later. Hence, you would not have access to /dev/sda1 at first, but would eventually get access to it. You should include it in the kernel if that's not already done.
Last, there might be a bug in the SCSI/SATA interface detection routine of the new kernel. What does happen when you revert back to your old kernel ?
Those are only my two cents.
HTH,
Cheers,
John
P.S : I can't help but notice that you don't copy/link System.map in /boot. |
|
| Back to top |
|
|
eltech
Guru
Joined: 05 Nov 2002
Posts: 582
Location: New York
|
| Posted: Fri Sep 22, 2006 3:58 pm Post subject: |
|
|
gentoome thanks for the help... yes i do a make mrproper, but also notice..
| Code: | [b]# cp .config ~/[/b]
# rm /usr/src/linux
# ln -s /usr/src/linux-2.4.XX /usr/src/linux
# ls -al /usr/src/linux (TO CHECK CORRECT LINKING)
# cd /usr/src/linux
# [b]make mrproper[/b]
# [b]cp ~/.config . [/b] |
Now the megaraid module is loaded into the kernel not as a module.. but just as you said its quite odd ..
anyoen else? |
|
| Back to top |
|
|
eltech
Guru
Joined: 05 Nov 2002
Posts: 582
Location: New York
|
| Posted: Mon Oct 30, 2006 12:48 pm Post subject: |
|
|
Upgraded to 2.6.X kernel and problems gone..
Thanks everyone.. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
