Re: [gentoo-user] init id c5 response too fast disabled for 5 min

[mad.scientist.at.large]

please see  for 
information on using the drives built in test.  please run the short test 
followed by conveyance and then the long test (can be over an hour)  and show 
us the output if it complains.  it could be a normal aging bad sector, which 
will be remapped the next time it's written to (hopefully).  if the drive 
passes all the smart test you can probably reformat the flakey partition (or 
possibly just run fsck until it doesn't have problems).  The original error 
message about the interrupt line however suggest a problem somewhere.

mad.scientist.at.large (a good madscientist)
--
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.


31. Dec 2017 00:28 by the...@sys-concept.com:


> I boot-strap the system from CD and run:
> fsck /dev/sda5
>
> got bunch of errors eg.:
> Directories count wrong for group #1567 (1, counted=0).
> Fix? yes
>
> Free inodes count wrong for group #1568 (8073, counted=8192).
> Fix? yes
>
> Directories count wrong for group #1568 (1, counted=0).
> Fix? yes
>
> Free inodes count wrong for group #1569 (8103, counted=8192).
> Fix? yes
>
> Directories count wrong for group #1569 (7, counted=0).
> Fix? yes
>
> Now when try to run it again I get:
> fsck /dev/sda5
> Segmentation fault
>
> Is this partition/drive gone?
> <<>
> Joseph
>
>>
>>
>> 30. Dec 2017 23:32 by >> the...@sys-concept.com>> :
>>
>>
>>> I'm getting a strange error trying to boot my system.
>>>
>>> init id c5 response too fast disabled for 5 min
>>>
>>> the error appears right after when it to start mysql at boot.
>>> In addition when the system starts I see:
>>>
>>> ata4.00 failed command read DMA
>>>
>>> It is hart to post any information as I can not even boot the system.  I
>>> just took a video trying to see if I can read any relevant information.
>>> Though, I can boot strap the system via CD
>>>
>>> -- 
>>> Joseph

Re: [gentoo-user] init id c5 response too fast disabled for 5 min

[thelma]

The CD boots OK.
Other partition are working OK on this disk I only have problem with
/dev/ada5

I can boot strap the drive and mount /dev/sda5 manually but I don't know
if it can be fixed.
The cable is OK as other partition are working correctly.

Joseph
On 12/31/2017 12:52 AM, mad.scientist.at.la...@tutanota.com wrote:
> with the seg fault, you may have other problems.  you might want to unplug 
> the hard drive (so you aren't spinning it) and run whatever diagnostics you 
> can on the machine, just to make sure it's not failing/loosing it's little 
> silicon mind.   
> 
> seg fault shouldn't happen (from drive issues) i don't think, but i suppose 
> if fsck gets confused enough it might.  or it might be a more general i/o or 
> system problem.
> 
> there is definately some problem reading the drive but it could be some other 
> part of the system failing causing read issues.  does the cd boot normally or 
> do you notice any odd behavior booting off other media?
> 
> mad.scientist.at.large (a good madscientist)
> --
> 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.
> 
> 
> 31. Dec 2017 00:44 by mad.scientist.at.la...@tutanota.com:
> 
> 
>> likely dying soon, or if you are lucky a key sector went out, if not the 
>> drive may be getting worse with every rotation.  If the drive is badly 
>> corrupted fsck can damage what is left.   definately DO NOT run fsck without 
>> knowing if the hardware has serious problems, also if part of it won't read 
>> don't try to long, drive electronics retrain themselves to some extent, 
>> trying to recover lost data can cause it to misadjust itself and work worse. 
>>  at least it's spinning, it's when the motor electronics suddendly die that 
>> you have real problems.  hopefully it's not a samsung drive (they have a 
>> classic tendency to die this way, i.e. spindle motor electronics die so 
>> platters don't spin).
>>
>> again however it could be the drive data/power cable.  anything else happen 
>> to it recently, i.e. new hardware added or swapped out?  is it an ata or a 
>> sata drive?  old/new drive/system?   hopefully it doesn't live near the heat 
>> vent..  if it's hotter than normal in the room it could be heat.  low 
>> humidity can also cause strange static related problems but they usually 
>> happen when you touch or stop touching the keyboard/mouse.  
>>
>> if it's dry, definately humidify before working on the machine, worse case 
>> you can boil a couple of gallons of water on the stove to humidify it 
>> temporarily.   under dry conditions i've lost a mother board just from 
>> touching the power switch, in a room without carpeting, i was not happy.   
>> also when doing electronics, try not to wear synthetics or other materials 
>> known for static (wool is way bad, as are things like silk, if it doesn't 
>> get wet easily (won't soak up water) it probably isn't static friendly).
>>
>> mad.scientist.at.large (a good madscientist)
>> --
>> 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.
>>
>>
>> 31. Dec 2017 00:28 by > the...@sys-concept.com> :
>>
>>
>>> I boot-strap the system from CD and run:
>>> fsck /dev/sda5
>>>
>>> got bunch of errors eg.:
>>> Directories count wrong for group #1567 (1, counted=0).
>>> Fix? yes
>>>
>>> Free inodes count wrong for group #1568 (8073, counted=8192).
>>> Fix? yes
>>>
>>> Directories count wrong for group #1568 (1, counted=0).
>>> Fix? yes
>>>
>>> Free inodes count wrong for group #1569 (8103, counted=8192).
>>> Fix? yes
>>>
>>> Directories count wrong for group #1569 (7, counted=0).
>>> Fix? yes
>>>
>>> Now when try to run it again I get:
>>> fsck /dev/sda5
>>> Segmentation fault
>>>
>>> Is this partition/drive gone?
>>>
>>> Joseph
>>> On 12/31/2017 12:22 AM, >> mad.scientist.at.la...@tutanota.com>>  wrote:
 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).

 good luck.

 mad.scientist.at.large (a good madscientist)
 --
 God bless the rich, the greedy and the corrupt politicians 

Re: [gentoo-user] init id c5 response too fast disabled for 5 min

[mad.scientist.at.large]

with the seg fault, you may have other problems.  you might want to unplug the 
hard drive (so you aren't spinning it) and run whatever diagnostics you can on 
the machine, just to make sure it's not failing/loosing it's little silicon 
mind.   

seg fault shouldn't happen (from drive issues) i don't think, but i suppose if 
fsck gets confused enough it might.  or it might be a more general i/o or 
system problem.

there is definately some problem reading the drive but it could be some other 
part of the system failing causing read issues.  does the cd boot normally or 
do you notice any odd behavior booting off other media?

mad.scientist.at.large (a good madscientist)
--
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.


31. Dec 2017 00:44 by mad.scientist.at.la...@tutanota.com:


> likely dying soon, or if you are lucky a key sector went out, if not the 
> drive may be getting worse with every rotation.  If the drive is badly 
> corrupted fsck can damage what is left.   definately DO NOT run fsck without 
> knowing if the hardware has serious problems, also if part of it won't read 
> don't try to long, drive electronics retrain themselves to some extent, 
> trying to recover lost data can cause it to misadjust itself and work worse.  
> at least it's spinning, it's when the motor electronics suddendly die that 
> you have real problems.  hopefully it's not a samsung drive (they have a 
> classic tendency to die this way, i.e. spindle motor electronics die so 
> platters don't spin).
>
> again however it could be the drive data/power cable.  anything else happen 
> to it recently, i.e. new hardware added or swapped out?  is it an ata or a 
> sata drive?  old/new drive/system?   hopefully it doesn't live near the heat 
> vent..  if it's hotter than normal in the room it could be heat.  low 
> humidity can also cause strange static related problems but they usually 
> happen when you touch or stop touching the keyboard/mouse.  
>
> if it's dry, definately humidify before working on the machine, worse case 
> you can boil a couple of gallons of water on the stove to humidify it 
> temporarily.   under dry conditions i've lost a mother board just from 
> touching the power switch, in a room without carpeting, i was not happy.   
> also when doing electronics, try not to wear synthetics or other materials 
> known for static (wool is way bad, as are things like silk, if it doesn't get 
> wet easily (won't soak up water) it probably isn't static friendly).
>
> mad.scientist.at.large (a good madscientist)
> --
> 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.
>
>
> 31. Dec 2017 00:28 by > the...@sys-concept.com> :
>
>
>> I boot-strap the system from CD and run:
>> fsck /dev/sda5
>>
>> got bunch of errors eg.:
>> Directories count wrong for group #1567 (1, counted=0).
>> Fix? yes
>>
>> Free inodes count wrong for group #1568 (8073, counted=8192).
>> Fix? yes
>>
>> Directories count wrong for group #1568 (1, counted=0).
>> Fix? yes
>>
>> Free inodes count wrong for group #1569 (8103, counted=8192).
>> Fix? yes
>>
>> Directories count wrong for group #1569 (7, counted=0).
>> Fix? yes
>>
>> Now when try to run it again I get:
>> fsck /dev/sda5
>> Segmentation fault
>>
>> Is this partition/drive gone?
>>
>> Joseph
>> On 12/31/2017 12:22 AM, >> mad.scientist.at.la...@tutanota.com>>  wrote:
>>> 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).
>>>
>>> good luck.
>>>
>>> mad.scientist.at.large (a good madscientist)
>>> --
>>> 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.
>>>
>>>
>>> 30. Dec 2017 23:32 by >>> the...@sys-concept.com>>> :
>>>
>>>
 I'm getting a strange error trying to boot my system.

 init id c5 response too fast disabled for 5 min

 the error appears right after when it to start mysql at boot.

Re: [gentoo-user] init id c5 response too fast disabled for 5 min

[mad.scientist.at.large]

likely dying soon, or if you are lucky a key sector went out, if not the drive 
may be getting worse with every rotation.  If the drive is badly corrupted fsck 
can damage what is left.   definately DO NOT run fsck without knowing if the 
hardware has serious problems, also if part of it won't read don't try to long, 
drive electronics retrain themselves to some extent, trying to recover lost 
data can cause it to misadjust itself and work worse.  at least it's spinning, 
it's when the motor electronics suddendly die that you have real problems.  
hopefully it's not a samsung drive (they have a classic tendency to die this 
way, i.e. spindle motor electronics die so platters don't spin).

again however it could be the drive data/power cable.  anything else happen to 
it recently, i.e. new hardware added or swapped out?  is it an ata or a sata 
drive?  old/new drive/system?   hopefully it doesn't live near the heat 
vent..  if it's hotter than normal in the room it could be heat.  low 
humidity can also cause strange static related problems but they usually happen 
when you touch or stop touching the keyboard/mouse.  

if it's dry, definately humidify before working on the machine, worse case you 
can boil a couple of gallons of water on the stove to humidify it temporarily.  
 under dry conditions i've lost a mother board just from touching the power 
switch, in a room without carpeting, i was not happy.   also when doing 
electronics, try not to wear synthetics or other materials known for static 
(wool is way bad, as are things like silk, if it doesn't get wet easily (won't 
soak up water) it probably isn't static friendly).

mad.scientist.at.large (a good madscientist)
--
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.


31. Dec 2017 00:28 by the...@sys-concept.com:


> I boot-strap the system from CD and run:
> fsck /dev/sda5
>
> got bunch of errors eg.:
> Directories count wrong for group #1567 (1, counted=0).
> Fix? yes
>
> Free inodes count wrong for group #1568 (8073, counted=8192).
> Fix? yes
>
> Directories count wrong for group #1568 (1, counted=0).
> Fix? yes
>
> Free inodes count wrong for group #1569 (8103, counted=8192).
> Fix? yes
>
> Directories count wrong for group #1569 (7, counted=0).
> Fix? yes
>
> Now when try to run it again I get:
> fsck /dev/sda5
> Segmentation fault
>
> Is this partition/drive gone?
>
> Joseph
> On 12/31/2017 12:22 AM, > mad.scientist.at.la...@tutanota.com>  wrote:
>> 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).
>>
>> good luck.
>>
>> mad.scientist.at.large (a good madscientist)
>> --
>> 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.
>>
>>
>> 30. Dec 2017 23:32 by >> the...@sys-concept.com>> :
>>
>>
>>> I'm getting a strange error trying to boot my system.
>>>
>>> init id c5 response too fast disabled for 5 min
>>>
>>> the error appears right after when it to start mysql at boot.
>>> In addition when the system starts I see:
>>>
>>> ata4.00 failed command read DMA
>>>
>>> It is hart to post any information as I can not even boot the system.  I
>>> just took a video trying to see if I can read any relevant information.
>>> Though, I can boot strap the system via CD
>>>
>>> -- 
>>> Joseph

Re: [gentoo-user] init id c5 response too fast disabled for 5 min

[thelma]

I boot-strap the system from CD and run:
fsck /dev/sda5

got bunch of errors eg.:
Directories count wrong for group #1567 (1, counted=0).
Fix? yes

Free inodes count wrong for group #1568 (8073, counted=8192).
Fix? yes

Directories count wrong for group #1568 (1, counted=0).
Fix? yes

Free inodes count wrong for group #1569 (8103, counted=8192).
Fix? yes

Directories count wrong for group #1569 (7, counted=0).
Fix? yes

Now when try to run it again I get:
fsck /dev/sda5
Segmentation fault

Is this partition/drive gone?

Joseph
On 12/31/2017 12:22 AM, mad.scientist.at.la...@tutanota.com wrote:
> 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).
> 
> good luck.
> 
> mad.scientist.at.large (a good madscientist)
> --
> 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.
> 
> 
> 30. Dec 2017 23:32 by the...@sys-concept.com:
> 
> 
>> I'm getting a strange error trying to boot my system.
>>
>> init id c5 response too fast disabled for 5 min
>>
>> the error appears right after when it to start mysql at boot.
>> In addition when the system starts I see:
>>
>> ata4.00 failed command read DMA
>>
>> It is hart to post any information as I can not even boot the system.  I
>> just took a video trying to see if I can read any relevant information.
>> Though, I can boot strap the system via CD
>>
>> -- 
>> Joseph

Re: [gentoo-user] init id c5 response too fast disabled for 5 min

[mad.scientist.at.large]

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).

good luck.

mad.scientist.at.large (a good madscientist)
--
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.


30. Dec 2017 23:32 by the...@sys-concept.com:


> I'm getting a strange error trying to boot my system.
>
> init id c5 response too fast disabled for 5 min
>
> the error appears right after when it to start mysql at boot.
> In addition when the system starts I see:
>
> ata4.00 failed command read DMA
>
> It is hart to post any information as I can not even boot the system.  I
> just took a video trying to see if I can read any relevant information.
> Though, I can boot strap the system via CD
>
> -- 
> Joseph

[gentoo-user] init id c5 response too fast disabled for 5 min

[thelma]

I'm getting a strange error trying to boot my system.

init id c5 response too fast disabled for 5 min

the error appears right after when it to start mysql at boot.
In addition when the system starts I see:

ata4.00 failed command read DMA

It is hart to post any information as I can not even boot the system.  I
just took a video trying to see if I can read any relevant information.
Though, I can boot strap the system via CD

-- 
Joseph