[SOLVED] Kernel Configuration Problem.

blackl1nux · 10-23-2011, 03:14 AM

i was fetching the new updates from Slackware, using slackpg upgrade-all, then suddenly my laptop turned off due to overheat and interrupted my update, it was in the part where the kernel updates were being fetched.

then after that i rebooted my Slack and after the part where the lilo loads Linux, it reboots..

is there a way to fix my kernel configuration?

or is there a way to access my hard drive files because i need to get some files there before i recompile my Slackware again.

thanks.

ReaperX7 · 10-23-2011, 04:56 AM

You can try booting using the Slackware install DVD.

It should have instructions on the DVD menu boot page. Once you get into your system just rerun the updater and rerun lilo afterwards and it SHOULD work.

onebuck · 10-23-2011, 02:39 PM

Hi,

The easiest way would be to use Slackware install media to boot the system as if you were going to install.

After you get to the login then from the cli (command line);

Code:

 
 ~#mkdir /slacktemp                                 #temporary mount point
  ~#mount /dev/your_device /slacktemp  #device you installed to
  ~#chroot /slacktemp                                #change to yours
  ~#cd /slacktemp/etc                                 #change to directory with lilo.conf   
  ~#vi lilo.conf                                            #edit lilo.conf, if need be
  ~#lilo -v -t -b /dev/your_device             #sda, hda this will only test   
  ~#lilo -v -b /dev/your_device                 #this will write to your boot device

You can 'man commands' in the above example to get a full understanding of the commands and options. Once lilo has been updated then reboot.

blackl1nux · 10-23-2011, 11:43 PM

now there's a problem on mounting my device, i checked if my device is mounted by using fdisk -l and i got

Quote:

/dev/sda1 * 53123512bytes 82 Linux
/dev/sda2 4323235 bytes 83 Linux swap

but when i try to mount it, it says :

Quote:

wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

then i tried using the dmesg | tail command and got :

Quote:

can't find ext4 filesystem

thanks in advance.

allend · 10-24-2011, 12:18 AM

It would help to know some more about your setup.
Were you using the generic kernel with an initrd prior to attempting the upgrade?
If so, it is possible that you have upgraded the kernel but not the associated kernel modules.
Or, it is possible that you have installed the kernel-modules package but have not built the initrd to suit.

Can you boot from the install disk, get to the login and mount the Slackware partition?

Code:

#mkdir /slacktemp
#mount /dev/sda1 /slacktemp

If so, please post the output from

Code:

#ls /slacktemp/var/log/packages | grep kernel

blackl1nux · 10-24-2011, 12:47 AM

i can boot to my install cd but i can't mount my device, it says that wrong fs type, bad superblock, bad option etc.

i tried to fsck.ext4 to fix my bad superblock but it says:

Quote:

fsck.ext4 not found

allend · 10-24-2011, 01:11 AM

Yikes! This is looking like more than a misconfiguration.
If the disk file system was intact, there should be no problem mounting the ext4 partition using the install disk.

I am wondering about corruption of the partition table.
The sizes in post #4 look wrong. A Slackware install in 50MB with a 4MB swap? I do not think so.

Quote:

i tried to fsck.ext4 to fix my bad superblock ...

Probably just as well that it failed as altering the drive may compromise your ability to recover any files.

I suggest that you do not try anything else. Please wait and see whether someone with more experience than me can offer some advice.

onebuck · 10-24-2011, 08:12 AM

Hi,

Post 4: That is not the output of 'fdisk -l';

Quote:

sample output for 'fdisk -l'
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xfdc4297b

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 5125 41164800 7 HPFS/NTFS
/dev/sdb2 5126 5386 2096482+ 82 Linux swap
/dev/sdb3 5387 5781 3172837+ 83 Linux

I believe the OP typed the sample output and transposed the blocks count for 'bytes'. To the OP, notice the disk information at the top of the output for the 'fdisk -l'. Then look at the start & end with the Blocks count.

My suggestion for the OP would be restore from backup. What no backup? If the install is new then possibly gamble and attempt a repair by using the install disk then perform a 'fsck' on the filesystem for '/dev/sda1'.

blackl1nux · 10-24-2011, 11:24 PM

oh pardon, my hard disk size is 60 gigabytes, i allotted 5gig for my swap..

actually i resolved the conflict, my hard disk was corrupted due to power interruption because of overheat so i red some articles about the ext4 super block backup and restore it.

thanks for the help

..

now my problem is how can i reconfigure or roll back my old kernel?..

because every time i reboot without my install cd.. it just reboots.

i'm booting using my install cd kernel configuration. ( hugemsmp.s root=/dev/sda1 rdinit= ro)..

thanks for everyone

allend · 10-25-2011, 07:27 AM

If you are confident that the hard disk file system is OK, then follow onebuck's instructions in post#3. This should get you to being to able to boot from the hard disk. Then you can rerun slackpkg.

blackl1nux · 10-25-2011, 10:21 PM

i followed the post 3 steps and after i rebooted i got a 0x01 error .

onebuck · 10-25-2011, 11:23 PM

Hi,

Quote:

Originally Posted by blackl1nux

i followed the post 3 steps and after i rebooted i got a 0x01 error .

Quote:

excerpt from LILO (boot loader) - Wikipedia 0x01 Illegal Command

This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS. Definitely check to see if the disk is seen by the BIOS first (and that the BIOS detail is complete).

As noted above, check your BIOS to see if indeed the drive(s) are recognized.

Boot using the Install disk then please post the un-edited output for 'fdisk -l' (lower case l not 1(one).
Also post your 'lilo.conf' file.

blackl1nux · 10-25-2011, 11:36 PM

thanks for everyone participation, i solved all of the problems.

i solved the 0x01 error by reinstalling my lilo by booting in my install cd and using some commands:

Quote:

mkdir /foo
mount /dev/sda1 /foo
mount --bind /proc /foo/proc
mount --bind /sys /foo/sys
mount --bind /dev /foo/dev
chroot foo
vi lilo.conf
lilo
exit
reboot

thanks for everyone help.