LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-16-2007, 09:43 AM   #1
BULPulse
Member
 
Registered: Nov 2007
Location: UK
Distribution: Slackware 13
Posts: 60

Rep: Reputation: 15
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!!!
 
Old 11-16-2007, 09:47 AM   #2
Unr3a164
Member
 
Registered: Apr 2007
Distribution: Windows 8.1. Attempting to get Slack 14.1 working.
Posts: 147

Rep: Reputation: 16
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%?
 
Old 11-16-2007, 02:18 PM   #3
juergen
Member
 
Registered: Sep 2001
Posts: 40

Rep: Reputation: 16
LiveCD's are the answer to everything.
In this case, boot from one of them and run a fsck on the partition in question by hand.

Good luck!
 
Old 11-16-2007, 02:37 PM   #4
BULPulse
Member
 
Registered: Nov 2007
Location: UK
Distribution: Slackware 13
Posts: 60

Original Poster
Rep: Reputation: 15
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
 
Old 11-16-2007, 02:52 PM   #5
juergen
Member
 
Registered: Sep 2001
Posts: 40

Rep: Reputation: 16
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.
 
Old 11-16-2007, 02:57 PM   #6
kav
Member
 
Registered: May 2006
Location: USA
Distribution: FreeBSD Ubuntu Debian
Posts: 137

Rep: Reputation: 15
Do a fdisk -l to list your partitions

Code:
# fdisk -l

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000800bd

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1           6       48163+  83  Linux

If this was your system you would then type
Code:
# fsck /dev/sda1
 
Old 11-16-2007, 04:07 PM   #7
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639

Rep: Reputation: Disabled
Quote:
Originally Posted by juergen View Post
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.

Brian
 
Old 11-16-2007, 04:10 PM   #8
BULPulse
Member
 
Registered: Nov 2007
Location: UK
Distribution: Slackware 13
Posts: 60

Original Poster
Rep: Reputation: 15
Thanks for all the help!!! The problem is solved
 
Old 11-16-2007, 04:18 PM   #9
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639

Rep: Reputation: Disabled
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.

Brian
 
Old 11-16-2007, 04:23 PM   #10
BULPulse
Member
 
Registered: Nov 2007
Location: UK
Distribution: Slackware 13
Posts: 60

Original Poster
Rep: Reputation: 15
I just followed the advice given above using the CD to go in Linux environment and use fsck

Last edited by BULPulse; 06-10-2009 at 12:20 PM.
 
Old 11-16-2007, 05:26 PM   #11
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Hi,

Quote:
Originally Posted by BULPulse View Post
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.

Last edited by onebuck; 11-16-2007 at 05:28 PM.
 
Old 11-16-2007, 05:27 PM   #12
BULPulse
Member
 
Registered: Nov 2007
Location: UK
Distribution: Slackware 13
Posts: 60

Original Poster
Rep: Reputation: 15
Thanks for the info
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
About Slackware 9.1 boot disk?? ftp://ftp.kpn.be/pub/linux/slackware/slackware-9.1-is AL3OMDAH Slackware 4 04-18-2007 09:54 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:39 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration