LinuxQuestions.org
Visit Jeremy's Blog.
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-04-2009, 09:21 AM   #1
netpumber
Member
 
Registered: Sep 2007
Location: In My Box
Distribution: Arch Linux
Posts: 423

Rep: Reputation: 33
crc error --system halted


Halo my friends...!

ten minutes ago i come back from university in my home and i press the power button to open my pc (slackware 12.2)

the message i get back is :
Quote:
Loading Linux.......................
BIOS data check successful
Probing EDD (edd=off to disable)... ok

Decompressing Linux

crc error

--System halted
Whats happen ? I ll try to google it and many people talk about format..
What you say..? Can i make it work again ? If not Can i take back up with a live cd or not ?

Thanks ..!!
 
Old 11-04-2009, 09:41 AM   #2
netpumber
Member
 
Registered: Sep 2007
Location: In My Box
Distribution: Arch Linux
Posts: 423

Original Poster
Rep: Reputation: 33
Now i restart my pc and returns me this :

Quote:
Loading Linux ......
Error 0x01
boot: Linux [here i press enter]
Loading Linux ....
boot: Linux
and so on ...:P

As i can understand something gong wrong with linux image...

:s
 
Old 11-04-2009, 10:38 AM   #3
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 224Reputation: 224Reputation: 224
Sounds like a failing/failed hard drive. Test the drive with smart-tools and the manufactorers testing tools. Most offer a live CD for download.

An easy way is to use SystemRescueCD and fsarchiver. link fsarchiver copies/restores on the file level, and handles per file corruptions. Rather than a big tar-ball that won't handle single file corruptions.

I recently had to do this with an old failing 20gb IDE drive. Attempted the tar-gzip entire mount point from the Slackware install disc. This failed because of some file corruptions. Fsarchiver was able to backup, and then later restore to a new hard disk. I was lucky because the only bad files where located in /usr/share and /usr/doc. I made note of which files had problems and reinstalled these apps.

Run your file system's fsck on the drive before you backup. If there is any corruption, this might fix some of it. To restore to a new hard drive, boot with SystemRescueCD using fsarchiver to restore the partition. You'll have to chroot into the new hard disk to reinstall lilo.

If you don't want a complete backup/restore of everything, mount your hard disk from a live cd, and tar-gzip the files/directories you want.

Last edited by disturbed1; 11-04-2009 at 10:43 AM. Reason: syntax
 
Old 11-04-2009, 11:42 AM   #4
netpumber
Member
 
Registered: Sep 2007
Location: In My Box
Distribution: Arch Linux
Posts: 423

Original Poster
Rep: Reputation: 33
So.. lets take it easy...

1st i boot up with a live cd.
2nd i download and burn into a disc the SystemRescueCd
3nd download and install from live cd the smart tools.

Then i ll check the disks with smart tools and in the end i will back up the system with SystemRescueCd .

Am i right with this ? Or you said something else and i didnt understand?
 
Old 11-04-2009, 12:29 PM   #5
netpumber
Member
 
Registered: Sep 2007
Location: In My Box
Distribution: Arch Linux
Posts: 423

Original Poster
Rep: Reputation: 33
OMG... i had the hirens boot cd . i boot with it then i check my drive with a WesternDigital Tool . The results said that no errors found.. Anyway.. i restart my pc and then .. slackware 12.2 boot up normally...


What the hell is happening ?

No i ll check my disks and take backups..

Any ideas for the best way to check my disk ?

Thanks..!!
 
Old 11-04-2009, 12:37 PM   #6
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 224Reputation: 224Reputation: 224
If you have a Western Digital drive - grab Data Lifeguard Tools ( http://support.wdc.com/product/download.asp ) run the long test.

You can also use smartctl as root smartctl --test=long /dev/hda wait awhile for the test to complete (there is no progress printout) then smartctl --all /dev/hda Substitute /dev/hda for you hard disk.

Use fsck as well.
 
Old 11-04-2009, 01:11 PM   #7
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Indeed it's strange behavior. It could be an HDD problem, so you can still run a long test with either smartctl or the western digital program above. However, I would also encourage you also run memtest86, which is usually found on live CDs anyway. Bad RAM can also cause such errors to show up.
 
Old 11-04-2009, 02:41 PM   #8
netpumber
Member
 
Registered: Sep 2007
Location: In My Box
Distribution: Arch Linux
Posts: 423

Original Poster
Rep: Reputation: 33
Ok guyz Thanks .. i ll try them out...!!
 
Old 11-04-2009, 05:02 PM   #9
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,

One other thing is maintenance on the system. When was the last time the box was opened and maintenance performed (PMS-Preventative Maintenance Schedule)?

You should clean the system on a schedule so as to prevent problems (I do mine on a yearly/quarterly basis relative too environment). With the power off and disconnected you can use canned dry air to blow the system out. At this time you should check the peripheral connectors. I like to prep mine at least once per year.

For my edge connectors and cards I will prep on the same time frame unless needed before hand. I've covered these techniques on the forums several times so a search will get you some information. I do perform diagnostic tests on my system(s) at the time of PMS unless otherwise dictated by problems.

You will find the 'SystemRescueCD' and 'UBCD' to be valuable whenever you come up a against a brickwall or performing PMS on your system(s).



The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!
 
  


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
crc error system halted prabush5 Linux - Newbie 7 02-27-2009 09:33 AM
crc error system halted srasiroslayer Linux - Software 2 12-06-2004 10:06 AM
crc error system halted some_person64 Linux - General 2 09-13-2004 09:59 PM
CRC error --System Halted !!! nuwanguy Linux - Newbie 3 09-02-2003 02:59 AM
CRC error --System Halted occurs occasionally quinnculator Linux - General 4 06-19-2003 11:46 AM

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

All times are GMT -5. The time now is 08:53 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