| View previous topic :: View next topic |
| Author |
Message |
drspewfy
Tux's lil' helper
Joined: 13 Dec 2003
Posts: 125
Location: Mexico
|
 Posted: Fri Feb 27, 2004 1:46 am Post subject: My Hard disk is dying!?? how to get my stuff that... |
 |
|
HELP!!
yeah my hard drive is dying, actually iu cant enter to GDM, gnome,
i just get a console, but without almost any command,,,
just the basics ones, "ls" shutdown"cd"pwd"...
but "fsck" to fix the hard disk i dont have it,, EMERGE neither..
all the programs, nothing!!, /home says that i dont have any USEr....
what too do1!???
i need to get my stufff to back up1!!!!
Here is the errors!
| Code: |
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: end_request: I/O error, cmd 0 dev 03:09 (hda), sector 2515824
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: ide0: reset: success
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 21:26:27 la-machine kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Feb 25 21:26:27 la-machine kernel: ide0: reset: success
Feb 25 21:30:00 la-machine CRON[2362]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 25 21:45:00 la-machine CRON[2393]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 25 22:00:00 la-machine CRON[2433]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Feb 25 22:00:00 la-machine CRON[2434]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 25 22:15:01 la-machine CRON[2490]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 25 22:30:00 la-machine CRON[2526]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 25 22:45:00 la-machine CRON[2584]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 25 22:58:20 la-machine gdm[1396]: gdm_child_action: Master halting...
Feb 25 22:58:22 la-machine init: Switching to runlevel: 0
Feb 25 22:58:31 la-machine proftpd[1202]: la-machine - ProFTPD killed (signal 15)
Feb 25 22:58:31 la-machine proftpd[1202]: la-machine - ProFTPD 1.2.9rc2 standalone mode SHUTDOWN
Feb 25 22:58:33 la-machine rc-scripts: Error stopping gdm.
Feb 25 22:58:33 la-machine exiting on signal 15
|
so what can i do1!??
backup and get a new Hard disk!?? or how could i fix it!??
HELP guuys 
thanks in advance!! |
|
| Back to top |
|
 |
drspewfy
Tux's lil' helper
Joined: 13 Dec 2003
Posts: 125
Location: Mexico
|
| Posted: Fri Feb 27, 2004 1:50 am Post subject: |
|
|
and is a LAPTOP!
=( |
|
| Back to top |
|
|
secondshadow
Guru
Joined: 23 Jun 2003
Posts: 362
|
| Posted: Fri Feb 27, 2004 4:08 am Post subject: |
|
|
| errrr....I've actually had those errors before...try turning off DMA for the drive before jumping to any conclusions. I had an old ATA33 drive thats pretty old and when I connected it to my Promise ATA controller it acted really wierd (gave those same errors) if ATA were enabled. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
