You are not logged in.

#1 2016-10-22 09:17:58

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

filesystem check failed. run fsck manually

Hi guys,
after a crash I rebooted the PC and when I turn on it says:

/dev/sda3 contains a file system with errors, check forced.
         ...
         ...
/dev/sda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
ERROR: Bailing out. Run ' fsck dev/sda3' manually

********** FULESYSTEM CHECK FAILED **********
Please run fsck manually. After leaving this maintenance shell, the system will reboot automatically.
********************************************

sh: can't access tty: job control turned off

If I do

fsck /dev/sda3

, I have this loop in output:

ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:70:30:18:10/00:00:05:00:00/40 tag 14 ncq 4096 in
             res 51/40:08:33:18:10/00:00:05:00:00/40 Emask 0x409(media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: {UNC }
blk_update_request: I/O error, dev sda, sector 84940851
Buffer I/O error on dev sda3, logical block 8389126, async page read
Error reading block 8389126 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan
Ignore error<y>?yes
Force rewrite<y>?yes 

and the loop starts..

can you help me?
thank you

Offline

#2 2016-10-22 09:23:09

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: filesystem check failed. run fsck manually

DarkPassenger wrote:

blk_update_request: I/O error, dev sda, sector 84940851
Buffer I/O error on dev sda3, logical block 8389126, async page read
Error reading block 8389126 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan

The above looks like a hardware error - perhaps your disk is on it's way out.

You should try booting from a usb/cd boot disk to run a smartctl test - see...
https://wiki.archlinux.org/index.php/S.M.A.R.T..

Last edited by paulkerry (2016-10-22 09:24:43)

Offline

#3 2016-10-22 12:24:29

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

ok, I-m running Kali linux and this is the output of a smartctl test:

martctl -H /dev/sda3
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.6.0-kali1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

thank you very much

Offline

#4 2016-10-23 15:59:22

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: filesystem check failed. run fsck manually

You want to run some tests as it mentions on the above link - in your case of /dev/sda

smartctl -t short /dev/sda

and/or

smartctl -t long /dev/sda

and then review and post here the full output of

smartctl -a /dev/sda

paying particular attention to the lower areas of the output where the SMART logs sections are given.


BTW - I'm unsure in what way you are using "Kali linux" (perhaps as a rescue medium?), but note that Arch Linux is the only O/S supported within these forums.

Offline

#5 2016-10-24 15:41:14

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

paulkerry wrote:

You want to run some tests as it mentions on the above link - in your case of /dev/sda

smartctl -t short /dev/sda

and/or

smartctl -t long /dev/sda

and then review and post here the full output of

smartctl -a /dev/sda

paying particular attention to the lower areas of the output where the SMART logs sections are given.


BTW - I'm unsure in what way you are using "Kali linux" (perhaps as a rescue medium?), but note that Arch Linux is the only O/S supported within these forums.

hi, I am using Kali because it is the only distro I have on DVD to use  as LIVE DVD.
this is the output of:

smartctl -a -T permissive /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.6.0-kali1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Short INQUIRY response, skip product id

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Read defect list: asked for grown list but didn't get it
Error Counter logging not supported

Device does not support Self Test logging

thank you very much

Offline

#6 2016-10-24 20:31:55

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: filesystem check failed. run fsck manually

OK about the Kali bit, but the command you have posted above is different to those what I suggested. When you do the "-t short" or "-t long", smartctl will tell you how long the test will take, after which run the "-a" and post the full output.

Offline

#7 2016-10-25 11:02:03

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

paulkerry wrote:

OK about the Kali bit, but the command you have posted above is different to those what I suggested. When you do the "-t short" or "-t long", smartctl will tell you how long the test will take, after which run the "-a" and post the full output.

ok, now I understand..this is the output>

smartctl -t short /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.6.0-kali1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Tue Oct 25 10:51:28 2016

Use smartctl -X to abort test.
root@kali:~# smartctl -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.6.0-kali1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Travelstar 5K500.B
Device Model:     Hitachi HTS545050B9A300
Serial Number:    111209PBN408P7H4KL6E
LU WWN Device Id: 5 000cca 6add02b02
Firmware Version: PB4OC64G
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Tue Oct 25 10:54:59 2016 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(  645) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 158) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   095   095   062    Pre-fail  Always       -       327691
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   180   180   033    Pre-fail  Always       -       2
  4 Start_Stop_Count        0x0012   098   098   000    Old_age   Always       -       4148
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   084   084   000    Old_age   Always       -       7196
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       3754
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       156
193 Load_Cycle_Count        0x0012   085   085   000    Old_age   Always       -       156319
194 Temperature_Celsius     0x0002   196   196   000    Old_age   Always       -       28 (Min/Max 11/43)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       50
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       42
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      7196         195720205
# 2  Extended offline    Completed: read failure       90%      7194         88465345
# 3  Short offline       Completed: read failure       80%      7194         140698270

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 

thank you

Offline

#8 2016-10-25 18:29:28

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: filesystem check failed. run fsck manually

DarkPassenger wrote:

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      7196         195720205
# 2  Extended offline    Completed: read failure       90%      7194         88465345
# 3  Short offline       Completed: read failure       80%      7194         140698270

these lines show that your disk is failing or has failed around those LBA areas, which is more than likely the reason why your fsck is looping.

If you need files from the disk, you could try a rescue with something like ddrescue ( https://www.archlinux.org/packages/?q=ddrescue )

If it's still under warranty, it should be replaced due to those errors otherwise you'll just have to get a replacement.

Offline

#9 2016-10-25 19:55:27

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

paulkerry wrote:
DarkPassenger wrote:

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      7196         195720205
# 2  Extended offline    Completed: read failure       90%      7194         88465345
# 3  Short offline       Completed: read failure       80%      7194         140698270

these lines show that your disk is failing or has failed around those LBA areas, which is more than likely the reason why your fsck is looping.

If you need files from the disk, you could try a rescue with something like ddrescue ( https://www.archlinux.org/packages/?q=ddrescue )

If it's still under warranty, it should be replaced due to those errors otherwise you'll just have to get a replacement.

sorry, you're saying that the hard disk is burned?

Offline

#10 2016-10-25 21:07:10

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: filesystem check failed. run fsck manually

Yes. Secure your data. Now.
Preferably from some life system (kali), NOT booting from the broken device, NOR chroot into it. Just use it as some data source and copy everything relevant to some other medium.

>  9 Power_On_Hours          0x0012   084   084   000    Old_age   Always       -       7196
And if you didn't smash it or something, that should still be on warranty?

Offline

#11 2016-10-25 21:47:38

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

all my revelant files are on cloud, so I tryed to format it but it gives me an error.
I tryed to install kali also but it gives me errors.
so I can say I must change hard disk.
it is not on warranty so I have to buy new one..
is there some other thing Can I try?

PS: what means the string you posted?

Last edited by DarkPassenger (2016-10-25 21:47:53)

Offline

#12 2016-10-25 21:58:12

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: filesystem check failed. run fsck manually

It has been on power only for 7196 hours so far. That's not too much. (But of course if you only use the system occasionally, this can mean 10 years ;-)

Offline

#13 2016-10-25 22:06:46

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

seth wrote:

It has been on power only for 7196 hours so far. That's not too much. (But of course if you only use the system occasionally, this can mean 10 years ;-)

no, I use PC 10-20 hours at day..
it is impossible..mmm...
I changed my HDD 2 years ago..
is it possible that the timer went to 0 when I formatted HDD before installing archlinux last time?

Offline

#14 2016-10-25 22:08:33

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: filesystem check failed. run fsck manually

7196 hours is 300 full days - fits your description.

Offline

#15 2016-10-25 23:44:20

ukhippo
Member
From: Non-paged pool
Registered: 2014-02-21
Posts: 366

Re: filesystem check failed. run fsck manually

Depending on where you bought it, model and manufacturer, the drive may still be in warranty. Check the manufacturer's support website - some provide a warranty checker.

Offline

#16 2016-10-26 18:47:12

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: filesystem check failed. run fsck manually

DarkPassenger wrote:

I tryed to format it but it gives me an error.
I tryed to install kali also but it gives me errors.

Formatting normally works on devices without errors in the disk structure, which is why you were having problems when trying to install kali as well as having the initial problem of fsck. There is the option to check for bad blocks, but if you go ahead and use that you are asking for real trouble further down the road.

DarkPassenger wrote:

is it possible that the timer went to 0 when I formatted HDD before installing archlinux last time?

No that is not possible.

Offline

#17 2016-10-26 21:19:45

DarkPassenger
Member
Registered: 2014-11-10
Posts: 58

Re: filesystem check failed. run fsck manually

Ok, the strangest thing is that now I installed Windows 10 without problems. The installation was slow but all is gone well.
Now I am updating windows.
Mmm, I cannot explain to myself this thing  and why

Offline

#18 2016-10-26 21:27:13

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: filesystem check failed. run fsck manually

Here's a kind advice: do not store anything important on the disk and prepend for the OS to do weird things.

The hardware is done. Ignoring that means to beg for trouble.
S.M.A.R.T. is a feature of the HDD. You can read it with windows tools as well and they will tell you that  the device is done.
Good luck and all the best, but it will bite you nevertheless.

Offline

#19 2016-10-27 18:13:52

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: filesystem check failed. run fsck manually

Maybe windows hasn't come across those bad areas yet.

I agree with @seth: you are really asking for trouble here installing anything on this disk. It's time to get the wallet out and buy a replacement.

Please remember to prepend "[SOLVED]" to your first post.

Offline

#20 2016-10-29 06:00:40

kevdog
Member
Registered: 2013-01-26
Posts: 102

Re: filesystem check failed. run fsck manually

I had a similar error once -- totally ignored it although I knew it was the wrong thing to do.  The drive kept working partially for like another 3 months and then totally crapped out.  The hard drive is dying.  I know its relatively new, however some crappy hard drives do this.  I've had them before myself and it pisses me off to no end since they are a lot of money.  However there isn't any alternative.  The drive is dying.  Nothing is going to save it.

Offline

Board footer

Powered by FluxBB