| 1 |
I boot-strap the system from CD and run: |
| 2 |
fsck /dev/sda5 |
| 3 |
|
| 4 |
got bunch of errors eg.: |
| 5 |
Directories count wrong for group #1567 (1, counted=0). |
| 6 |
Fix? yes |
| 7 |
|
| 8 |
Free inodes count wrong for group #1568 (8073, counted=8192). |
| 9 |
Fix? yes |
| 10 |
|
| 11 |
Directories count wrong for group #1568 (1, counted=0). |
| 12 |
Fix? yes |
| 13 |
|
| 14 |
Free inodes count wrong for group #1569 (8103, counted=8192). |
| 15 |
Fix? yes |
| 16 |
|
| 17 |
Directories count wrong for group #1569 (7, counted=0). |
| 18 |
Fix? yes |
| 19 |
|
| 20 |
Now when try to run it again I get: |
| 21 |
fsck /dev/sda5 |
| 22 |
Segmentation fault |
| 23 |
|
| 24 |
Is this partition/drive gone? |
| 25 |
|
| 26 |
Joseph |
| 27 |
On 12/31/2017 12:22 AM, mad.scientist.at.large@××××××××.com wrote: |
| 28 |
> that would most likely be a failing/failed hard drive or a bad connection/cable. I'd suggest carefully checking the cable and then boot off a cd and back up anything you care about on the drive, you might check the SMART status of the drive. In any case back it up first, worry about understanding it/finding the bug later. Once everything is backed up you can run the drives self test routines. Back it up before you do anything else, the next time it mounts may be the last (i've used a lot of very old drives from tivo's that were thrown out, you may or may not get it to mount again and may or may not be able to recover your' data). |
| 29 |
> |
| 30 |
> good luck. |
| 31 |
> |
| 32 |
> mad.scientist.at.large (a good madscientist) |
| 33 |
> -- |
| 34 |
> God bless the rich, the greedy and the corrupt politicians they have put into office. God bless them for helping me do the right thing by giving the rich my little pile of cash. After all, the rich know what to do with money. |
| 35 |
> |
| 36 |
> |
| 37 |
> 30. Dec 2017 23:32 by thelma@×××××××××××.com: |
| 38 |
> |
| 39 |
> |
| 40 |
>> I'm getting a strange error trying to boot my system. |
| 41 |
>> |
| 42 |
>> init id c5 response too fast disabled for 5 min |
| 43 |
>> |
| 44 |
>> the error appears right after when it to start mysql at boot. |
| 45 |
>> In addition when the system starts I see: |
| 46 |
>> |
| 47 |
>> ata4.00 failed command read DMA |
| 48 |
>> |
| 49 |
>> It is hart to post any information as I can not even boot the system. I |
| 50 |
>> just took a video trying to see if I can read any relevant information. |
| 51 |
>> Though, I can boot strap the system via CD |
| 52 |
>> |
| 53 |
>> -- |
| 54 |
>> Joseph |
Archives