I can't use Slackware any more !!!!!!!!!!!!!! Help
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't use Slackware any more !!!!!!!!!!!!!! Help
When i start my computer after it loads everything it starts checking my hard disk for errors. On 93% stops and says that there is at error and restarts. Every time i start my computer it does it and i can't use my computer now. Please help!!! Any ideas how to fix it??? Very urgent. need help!!!
Distribution: Windows 8.1. Attempting to get Slack 14.1 working.
Posts: 147
Rep:
when it stops, do you get a message saying that you have to login as root and run a few commands to fix the issue? Or does it just automatically reboot the machine once it reaches the 93%?
Yes it says to run something like fsck -v p <partition> it restarts too quickly to read it. And how do you boot from live cd and what commands to use???
Thank you for the responces
To run a live cd, you download the ISO image and burn it to a CD. RIP (Recovery Is Possible) should work for you. Once you have it on CD, you just insert it into the afflicted machine, make sure that the BIOS knows to boot from CD and turn it on.
Once you are in the Linux environment from that CD, a plain old 'fsck <partition>' should be a good starting point.
To run a live cd, you download the ISO image and burn it to a CD. RIP (Recovery Is Possible) should work for you. Once you have it on CD, you just insert it into the afflicted machine, make sure that the BIOS knows to boot from CD and turn it on.
Once you are in the Linux environment from that CD, a plain old 'fsck <partition>' should be a good starting point.
As has been mentioned many times on this forum, you don't need a "Live CD" because you can boot with your Slackware Install cd.
I'm glad you have a solution to your problem, but it would be good if you posted your resolution. Did you do what kav said? Please contribute to the forum by saying how it was solved.
I just followed the advice given above using the CD to go in Linux environment and use fdisk
I think you meant 'fsck'. Do a 'man fsck' to understand the command.
Code:
excrpt from 'man fsck'
NAME
fsck - check and repair a Linux file system
SYNOPSIS
fsck [ -sAVRTNP ] [ -C [ fd ] ] [ -t fstype ] [filesys ... ] [--] [ fs-
specific-options ]
DESCRIPTION
fsck is used to check and optionally repair one or more Linux file sys-
tems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a
mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier
(e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Nor-
mally, the fsck program will try to handle filesystems on different
physical disk drives in parallel to reduce the total amount of time
needed to check all of the filesystems.
If no filesystems are specified on the command line, and the -A option
is not specified, fsck will default to checking filesystems in
/etc/fstab serially. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following conditions:
0 - No errors
1 - File system errors corrected
2 - System should be rebooted
4 - File system errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - Fsck canceled by user request
128 - Shared library error
The exit code returned when multiple file systems are checked is the
bit-wise OR of the exit codes for each file system that is checked.
In actuality, fsck is simply a front-end for the various file system
checkers (fsck.fstype) available under Linux. The file system-specific
checker is searched for in /sbin first, then in /etc/fs and /etc, and
finally in the directories listed in the PATH environment variable.
Please see the file system-specific checker manual pages for further
details.
You should check the options!
edit: You could have used the single option to boot. Then you would be allowed to perform the maintenance. As stated if you need a boot cd, use the Slackware 12 install cd1 instead of a livecd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.