Kernel Configuration Problem.
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. |
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. |
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:
:hattip: |
now there's a problem on mounting my device, i checked if my device is mounted by using fdisk -l and i got
Quote:
Quote:
Quote:
|
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 Code:
#ls /slacktemp/var/log/packages | grep kernel |
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:
|
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 suggest that you do not try anything else. Please wait and see whether someone with more experience than me can offer some advice. |
Hi,
Post 4: That is not the output of 'fdisk -l'; Quote:
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'. :hattip: |
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 :) |
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.
|
i followed the post 3 steps and after i rebooted i got a 0x01 error .
|
Hi,
Quote:
Quote:
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. |
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:
|
All times are GMT -5. The time now is 11:19 AM. |