SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
my slack is on hda2
and when he load it says that there is some problem with the partition couse is on read-only format, and will be batter if i type: e2fsck -n <device>
when i type: e2fsck -n /dev/hda2 on the root screen it says that he is not able to continue couse is not able to find superblock (or something like that.. i,m not able to make screenshot there) and will be batter to type: e2fsck -b 8391 <device> to use alternate superblock.
When i type it... it says will be batter if i type: e2fsck -n <device>
and so, and so on...
however... i fount the way to boot my slack. with bootable diskate and command mount root=/dev/hda2 rw
everything loads fine... but i see somewhere in loading screen error with filesystem and to fix it i need to change a lilo.conf file in /etc/ to add the line read-only and that will fix the problem... but when i open it, i see that this line was here all the time...
This seems like a Slackware specific issue, or at least, I think it is.
I honestly have almost no idea what you are trying to say here other than there is some file system error which is preventing you from booting the machine, and you are trying to get it started and resolved.
Im not overly sure either about what it is you want, but here is my take:
Linux mounts the root file system read-only, its safe, but realistically, you need it to be read/write (and going that you used the "rw" option to mount, i think thats what you want). The solution, in this case, is that your distros boot scripts (if you even have any) fail to remount the root file system with read/write, issue the command
mount -o remount -rw /
as root, that will give you a read/write root filesystem.
The part about not finding a superblock doesn't sound good, thought I'm not sure as I've never run into that. Check /etc/fstab to make sure you're mounting hda2 rw. Initially on boot-up it's supposed to be mounted ro, but then it gets remounted as rw(along with any other options you've got in /etc/fstab). So check that file and if you're not sure post it up here.
I ran into this before, and it was fstab related.
I had mistakenly put in etc/fstab to mount device '/dev/hda' instead of '/dev/hda5' for example.
I forgot to specify the partition, and the result was identical to the problem the original poster is having.
Took a few close looks before noticing the typo. After that correction, all was perfect.
Distribution: Debian. (Formerly Slackware, Gentoo, RHEL, and Suse)
I think I have the same problem as the original poster. The problem only exists when I try to start a 2.6 kernel. The 2.4 kernel is fine, and all disks are fine when booting huge26.s from the cd.
everything looks good during boot, all disks are detected, until e2fsck posts an error: No such device or address while trying to open /dev/hda2. Which I notice happens when fstab has invalid entries.
I'm given the option to login to reboot. I can login with hda2's root password, and I'm given hda2 which I can remount rw and write to the disk, but I cannot mount any other volumes nor open disks with fdisk. It's as if the devices are not connected and I'm very confused.