You are not logged in.

Pages: 1

#1 2017-07-21 19:41:27

Marvix
Member
Registered: 2013-10-08
Posts: 146

[SOLVED] File system check errors all the time on every new start

Hello to the community.

Since an clean installation on a new machine I get always file system check errors and promts me to solve these with the fsck sometime with destructive results.

Now with a new installation I get a new one with

[DEPEND] Dependency failed to /home
[DEPEND] Dependency failed for Local File Systems

and suggests me to run the below and I get after

systecmctl status "systemd-fsck@dev-disk-by\\x2duuid-b3fb6ad7\\x2d52bd\\x2d431c\\x2d98bc\\x2da5fdab6db86.service"
Loaded:error (Reason:Invalid argument)
Active:Inactive (dead)
Docs: man:systemd-fsck@.service(8)

21 21:39:29 systemd /usr/lib/system/systemd-fsck@.service:9:failed to resolve init specifiers on File System Check on %f: ignoring:Invalid argument
21 21:39:29 systemd /usr/lib/system/systemd-fsck@.service:9:failed to resolve init specifiers on File System Check on %f: No such file or directory
21 21:39:29 systemd-fsck@dev-disk-by\\x2duuid-b3fb6ad7\\x2d52bd\\x2d431c\\x2d98bc\\x2da5fdab6db86.service: service lacks both ExecStart= and ExecStop=

and I cannot get prompted to login.

What can I do, where to get started?

I use OpenBox with startx for login.

For now I'm on live session on Kali.

Thank you.

Last edited by Marvix (2017-11-02 17:08:36)

Offline

#2 2017-07-21 21:29:20

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] File system check errors all the time on every new start

I would start by ruling out a hardware problem, check disk health, if cpu is not overheating, if cabling is all well connected, and do a memtest.

Which filesystem type are we talking about here?

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#3 2017-07-21 21:42:20

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

Memtest showed no problem.

About the hard disk and CPU i'm sure as I checked, but they seem fine.

I have installed ext4 filesystem.

Offline

#4 2017-07-21 22:00:56

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [SOLVED] File system check errors all the time on every new start

https://bbs.archlinux.org/viewtopic.php?id=195102 ?

ls /dev/disk/by-uuid
lsblk -f
cat /etc/fstab # of the installed system, can you mount the disk from kali?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2017-07-21 22:25:46

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

As from kali I can mount the disk and partitions both root and home from Kali's file manager and terminal.

I will try to check the fstab and rebuild it as you suggested and return with the results.

Offline

#6 2017-07-22 18:48:32

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

I didn't try anything as I shut down my computer and went to sleep.

When I started the pc in the moring, I had a delayed boot for about one minute and now throws me to emergency mode after I have to give the root password. I did login and run fsck and prompted to use e2fck -b 8193 or 32768 which repaired two problem on the Pass 1 checking inodes, blocks, and use.

From Kali linux which I use as live system, now I can't mount to /home partition from file manager by from terminal gives me the message 

mount: /dev/sdb2: can't read superblock

as I did before.
From GParted shows me the filesystem as unknown and from the information I get

Unable to detect file system! Possible reasons are:
- The file system is damaged
- The file system is unknown to GParted
- There is no file system available (unformatted)
- The device entry /dev/sdb2 is missing

The /dev/sdb1 root partition is intact.
The /dev/sdb2 home partition is the one with errors.

I will try to see the fstab from chroot.

Could you suggest me any checking tools for CPU and Hard Drive so I can use them in Kali to avoid boot and have to wait the delayed boot?

Offline

#7 2017-07-22 19:22:23

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED] File system check errors all the time on every new start

https://wiki.archlinux.org/index.php/S.M.A.R.T.

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#8 2017-07-22 19:34:54

adesh
Member
Registered: 2016-10-05
Posts: 167

Re: [SOLVED] File system check errors all the time on every new start

Correct link: https://wiki.archlinux.org/index.php/S.M.A.R.T.
(Fixed the trailing dot)

Offline

#9 2017-07-22 19:40:13

loqs
Member
Registered: 2014-03-06
Posts: 17,314

Re: [SOLVED] File system check errors all the time on every new start

Do you have backups of all the data on that device?  You might want to consider imaging the device then working on an overlay on top of the the image
as after using fsck the situation appears to have deteriorated instead of improved and working on an overlay on top of the image all changes do not affect the original device and are reversible.

Offline

#10 2017-07-22 19:43:01

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [SOLVED] File system check errors all the time on every new start

You might be able to rescue data from your /home partition using https://wiki.archlinux.org/index.php/Fi … d_PhotoRec
No need to chroot and probably neither to inspect your fstab. The superblock apparently was ok before the reboot but is no longer - that's a severe problem.

You ran " e2fsck -b 8193 or 32768" on sdb2? Do you understand what this means?
What *excatly* did you run? The numbers are not arbitrary but depend on the blocksize of the actual filesystem.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2017-07-22 19:55:15

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

I have backup, not no worries.

for the e2fsck i didn't understand.

I run e2fsc -b 32768 repaired 2 isusses in Part1 and on the final part shows 5 digit numbers.

Can you please explain?

Should I reinstall?

Offline

#12 2017-07-22 20:06:40

loqs
Member
Registered: 2014-03-06
Posts: 17,314

Re: [SOLVED] File system check errors all the time on every new start

Has the device passed a SMART long self test?
Without knowing why the filesystem on the device became corrupted there is no way to know how likely further corruption is to occur.

Offline

#13 2017-07-22 20:08:59

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [SOLVED] File system check errors all the time on every new start

This command says to use the backup superblock on a 4k blocksize filesystem for reparation.
You may try likewise on /dev/sdb2 (assuming it's ext4 created w/ the same parameters) - this may restore superblock and filesystem, but the incident is a bad sign, so ensure to run the smart tests, maybe badblocks (but that's destructive!) to test the disk.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2017-07-22 20:10:12

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

Sorry it did. Here's the result

root@kali:/# smartctl -l selftest /dev/sdb2
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-kali3-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
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%     11861         4572472
# 2  Short offline       Completed: read failure       90%     11860         4572472
# 3  Offline             Completed without error       00%         0         -
# 4  Offline             Completed without error       00%         0

Offline

#15 2017-07-22 20:14:49

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [SOLVED] File system check errors all the time on every new start

https://wiki.archlinux.org/index.php/Badblocks

But don't trust the disk anymore. If badblocks does without error, you can use it as media tank and attach it to your TV or so, but do no longer trust the disk.
Also check "smartctl -x /dev/sdb" for a general health status.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2017-07-22 20:26:16

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

Worst news ever for the hard drive


Here the smartctl -x /dev/sdb2

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-kali3-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Samsung SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2SMJ9GD537594
LU WWN Device Id: 5 0004cf 20a6695af
Firmware Version: 2AR20002
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes 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 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Jul 22 20:17:53 2017 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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: 		(12480) 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: 	 ( 208) minutes.
SCT capabilities: 	       (0x003f)	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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   100   051    -    22114
  2 Throughput_Performance  -OS--K   252   252   000    -    0
  3 Spin_Up_Time            PO---K   090   088   025    -    3060
  4 Start_Stop_Count        -O--CK   094   094   000    -    6529
  5 Reallocated_Sector_Ct   PO--CK   252   252   010    -    0
  7 Seek_Error_Rate         -OSR-K   252   252   051    -    0
  8 Seek_Time_Performance   --S--K   252   252   015    -    0
  9 Power_On_Hours          -O--CK   100   100   000    -    11861
 10 Spin_Retry_Count        -O--CK   252   252   051    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    13
 12 Power_Cycle_Count       -O--CK   094   094   000    -    6256
191 G-Sense_Error_Rate      -O---K   100   100   000    -    146
192 Power-Off_Retract_Count -O---K   252   252   000    -    0
194 Temperature_Celsius     -O----   058   043   000    -    42 (Min/Max 15/57)
195 Hardware_ECC_Recovered  -O-RCK   100   100   000    -    0
196 Reallocated_Event_Count -O--CK   252   252   000    -    0
197 Current_Pending_Sector  -O--CK   100   100   000    -    36
198 Offline_Uncorrectable   ----CK   252   252   000    -    0
199 UDMA_CRC_Error_Count    -OS-CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   -O-R-K   100   100   000    -    20053
223 Load_Retry_Count        -O--CK   100   100   000    -    13
225 Load_Cycle_Count        -O--CK   078   078   000    -    224913
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      2  Comprehensive SMART error log
0x03       GPL     R/O      2  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      2  Extended self-test log
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xc0-0xdf  GPL,SL  VS      16  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 19600 (device log contains only the most recent 8 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 19600 [7] occurred at disk power-on lifetime: 11860 hours (494 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:07.995  READ DMA
  c8 00 00 00 08 00 00 00 00 18 00 e0 08     00:00:07.995  READ DMA
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:07.995  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:07.995  IDENTIFY DEVICE
  ef 00 03 00 45 00 00 00 00 00 00 a0 08     00:00:07.995  SET FEATURES [Set transfer mode]

Error 19599 [6] occurred at disk power-on lifetime: 11860 hours (494 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:07.993  READ DMA
  25 00 00 00 08 00 00 74 70 6d a0 e0 08     00:00:07.993  READ DMA EXT
  25 00 00 00 08 00 00 74 70 6d 00 e0 08     00:00:07.993  READ DMA EXT
  c8 00 00 00 68 00 00 00 80 07 88 e2 08     00:00:07.993  READ DMA
  c8 00 00 00 80 00 00 00 80 07 00 e2 08     00:00:07.993  READ DMA

Error 19598 [5] occurred at disk power-on lifetime: 11859 hours (494 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:07.022  READ DMA
  c8 00 00 00 00 00 00 00 80 0d 80 e2 08     00:00:07.022  READ DMA
  c8 00 00 00 00 00 00 00 80 0c 80 e2 08     00:00:07.022  READ DMA
  c8 00 00 00 80 00 00 00 80 0c 00 e2 08     00:00:07.022  READ DMA
  c8 00 00 00 40 00 00 00 80 0b c0 e2 08     00:00:07.022  READ DMA

Error 19597 [4] occurred at disk power-on lifetime: 11859 hours (494 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:07.020  READ DMA
  25 00 00 00 08 00 00 74 70 6d a0 e0 08     00:00:07.020  READ DMA EXT
  25 00 00 00 08 00 00 74 70 6d 00 e0 08     00:00:07.020  READ DMA EXT
  c8 00 00 00 08 00 00 00 82 08 00 e2 08     00:00:07.020  READ DMA
  c8 00 00 00 08 00 00 00 81 08 00 e2 08     00:00:07.020  READ DMA

Error 19596 [3] occurred at disk power-on lifetime: 11859 hours (494 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:06.966  READ DMA
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.966  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:06.966  IDENTIFY DEVICE
  ef 00 03 00 45 00 00 00 00 00 00 a0 08     00:00:06.966  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.966  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 19595 [2] occurred at disk power-on lifetime: 11859 hours (494 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:06.964  READ DMA
  25 00 00 00 08 00 00 74 70 6d a0 e0 08     00:00:06.964  READ DMA EXT
  25 00 00 00 08 00 00 74 70 6d 00 e0 08     00:00:06.964  READ DMA EXT
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.964  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:06.964  IDENTIFY DEVICE

Error 19594 [1] occurred at disk power-on lifetime: 11859 hours (494 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:06.962  READ DMA
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.962  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:06.962  IDENTIFY DEVICE
  ef 00 03 00 45 00 00 00 00 00 00 a0 08     00:00:06.962  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.962  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 19593 [0] occurred at disk power-on lifetime: 11859 hours (494 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 00 80 08 00 e2 00  Error: UNC 8 sectors at LBA = 0x02800800 = 41945088

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  c8 00 00 00 08 00 00 00 80 08 00 e2 08     00:00:06.961  READ DMA
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.961  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:06.961  IDENTIFY DEVICE
  ef 00 03 00 45 00 00 00 00 00 00 a0 08     00:00:06.961  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:06.961  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

SMART Extended Self-test Log Version: 1 (2 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     11861         4572472
# 2  Short offline       Completed: read failure       90%     11860         4572472
# 3  Offline             Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed_read_failure [90% left] (0-65535)
    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.

SCT Status Version:                  2
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    42 Celsius
Power Cycle Min/Max Temperature:     28/45 Celsius
Lifetime    Min/Max Temperature:     15/57 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         5 minutes
Temperature Logging Interval:        5 minutes
Min/Max recommended Temperature:     -5/80 Celsius
Min/Max Temperature Limit:           -10/85 Celsius
Temperature History Size (Index):    128 (107)

Index    Estimated Time   Temperature Celsius
 108    2017-07-22 09:40    42  ***********************
 109    2017-07-22 09:45    51  ********************************
 110    2017-07-22 09:50    52  *********************************
 111    2017-07-22 09:55    53  **********************************
 112    2017-07-22 10:00    52  *********************************
 113    2017-07-22 10:05    52  *********************************
 114    2017-07-22 10:10    52  *********************************
 115    2017-07-22 10:15    53  **********************************
 116    2017-07-22 10:20    53  **********************************
 117    2017-07-22 10:25    54  ***********************************
 118    2017-07-22 10:30    54  ***********************************
 119    2017-07-22 10:35    53  **********************************
 120    2017-07-22 10:40    52  *********************************
 121    2017-07-22 10:45    52  *********************************
 122    2017-07-22 10:50    49  ******************************
 123    2017-07-22 10:55    51  ********************************
 124    2017-07-22 11:00    51  ********************************
 125    2017-07-22 11:05    52  *********************************
 126    2017-07-22 11:10    53  **********************************
 127    2017-07-22 11:15    54  ***********************************
   0    2017-07-22 11:20    54  ***********************************
   1    2017-07-22 11:25    54  ***********************************
   2    2017-07-22 11:30    55  ************************************
   3    2017-07-22 11:35    55  ************************************
   4    2017-07-22 11:40    55  ************************************
   5    2017-07-22 11:45    54  ***********************************
   6    2017-07-22 11:50    54  ***********************************
   7    2017-07-22 11:55    52  *********************************
   8    2017-07-22 12:00    51  ********************************
   9    2017-07-22 12:05    49  ******************************
  10    2017-07-22 12:10    48  *****************************
  11    2017-07-22 12:15    47  ****************************
  12    2017-07-22 12:20    47  ****************************
  13    2017-07-22 12:25    47  ****************************
  14    2017-07-22 12:30    46  ***************************
 ...    ..(  2 skipped).    ..  ***************************
  17    2017-07-22 12:45    46  ***************************
  18    2017-07-22 12:50    45  **************************
  19    2017-07-22 12:55    45  **************************
  20    2017-07-22 13:00    47  ****************************
  21    2017-07-22 13:05    47  ****************************
  22    2017-07-22 13:10    40  *********************
  23    2017-07-22 13:15    41  **********************
  24    2017-07-22 13:20    41  **********************
  25    2017-07-22 13:25    42  ***********************
  26    2017-07-22 13:30    42  ***********************
  27    2017-07-22 13:35    43  ************************
  28    2017-07-22 13:40    44  *************************
  29    2017-07-22 13:45    43  ************************
 ...    ..( 13 skipped).    ..  ************************
  43    2017-07-22 14:55    43  ************************
  44    2017-07-22 15:00    42  ***********************
  45    2017-07-22 15:05    42  ***********************
  46    2017-07-22 15:10    41  **********************
  47    2017-07-22 15:15    41  **********************
  48    2017-07-22 15:20    42  ***********************
  49    2017-07-22 15:25    42  ***********************
  50    2017-07-22 15:30    42  ***********************
  51    2017-07-22 15:35    30  ***********
  52    2017-07-22 15:40    34  ***************
  53    2017-07-22 15:45    37  ******************
  54    2017-07-22 15:50    39  ********************
  55    2017-07-22 15:55    41  **********************
  56    2017-07-22 16:00    42  ***********************
  57    2017-07-22 16:05    42  ***********************
  58    2017-07-22 16:10    41  **********************
 ...    ..(  2 skipped).    ..  **********************
  61    2017-07-22 16:25    41  **********************
  62    2017-07-22 16:30    42  ***********************
  63    2017-07-22 16:35    42  ***********************
  64    2017-07-22 16:40    42  ***********************
  65    2017-07-22 16:45    41  **********************
  66    2017-07-22 16:50    40  *********************
  67    2017-07-22 16:55    40  *********************
  68    2017-07-22 17:00    42  ***********************
  69    2017-07-22 17:05    43  ************************
 ...    ..(  2 skipped).    ..  ************************
  72    2017-07-22 17:20    43  ************************
  73    2017-07-22 17:25    45  **************************
  74    2017-07-22 17:30    44  *************************
  75    2017-07-22 17:35    45  **************************
  76    2017-07-22 17:40    45  **************************
  77    2017-07-22 17:45    44  *************************
  78    2017-07-22 17:50    46  ***************************
  79    2017-07-22 17:55    48  *****************************
  80    2017-07-22 18:00    48  *****************************
  81    2017-07-22 18:05    47  ****************************
  82    2017-07-22 18:10    46  ***************************
  83    2017-07-22 18:15    46  ***************************
  84    2017-07-22 18:20    46  ***************************
  85    2017-07-22 18:25    32  *************
  86    2017-07-22 18:30    35  ****************
  87    2017-07-22 18:35    39  ********************
  88    2017-07-22 18:40    39  ********************
  89    2017-07-22 18:45    41  **********************
  90    2017-07-22 18:50    42  ***********************
  91    2017-07-22 18:55    43  ************************
  92    2017-07-22 19:00    44  *************************
  93    2017-07-22 19:05    44  *************************
  94    2017-07-22 19:10    45  **************************
  95    2017-07-22 19:15    44  *************************
  96    2017-07-22 19:20    44  *************************
  97    2017-07-22 19:25    42  ***********************
  98    2017-07-22 19:30    43  ************************
  99    2017-07-22 19:35    44  *************************
 100    2017-07-22 19:40    43  ************************
 101    2017-07-22 19:45    42  ***********************
 ...    ..(  5 skipped).    ..  ***********************
 107    2017-07-22 20:15    42  ***********************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x0002  4            0  R_ERR response for data FIS
0x0003  4            0  R_ERR response for device-to-host data FIS
0x0004  4            0  R_ERR response for host-to-device data FIS
0x0005  4            0  R_ERR response for non-data FIS
0x0006  4            0  R_ERR response for device-to-host non-data FIS
0x0007  4            0  R_ERR response for host-to-device non-data FIS
0x0008  4            0  Device-to-host non-data FIS retries
0x0009  4            7  Transition from drive PhyRdy to drive PhyNRdy
0x000a  4            7  Device-to-host register FISes sent due to a COMRESET
0x000b  4            0  CRC errors within host-to-device FIS
0x000d  4            0  Non-CRC errors within host-to-device FIS
0x000f  4            0  R_ERR response for host-to-device data FIS, CRC
0x0010  4            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  4            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  4            0  R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00  4            0  Vendor specific
0x8e01  4            0  Vendor specific
0x8e02  4            0  Vendor specific
0x8e03  4            0  Vendor specific
0x8e04  4            0  Vendor specific
0x8e05  4            0  Vendor specific
0x8e06  4            0  Vendor specific
0x8e07  4            0  Vendor specific
0x8e08  4            0  Vendor specific
0x8e09  4            0  Vendor specific
0x8e0a  4            0  Vendor specific
0x8e0b  4            0  Vendor specific
0x8e0c  4            0  Vendor specific
0x8e0d  4            0  Vendor specific
0x8e0e  4            0  Vendor specific
0x8e0f  4            0  Vendor specific
0x8e10  4            0  Vendor specific
0x8e11  4            0  Vendor specific

Offline

#17 2017-07-22 20:49:46

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [SOLVED] File system check errors all the time on every new start

no reallocations and no Offline Uncorrectable - but the block at 0x02800800 seems wonky. Writing into that block will either "fix" it or get you one re-allocated block.

Since the disk has seen some days and apparently heat - and you've backups - you might want to run badblocks across it (at least in the nondestructive way) to retire weary blocks and see the condition of the disk.
Then run smartctl again.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#18 2017-07-22 22:40:39

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] File system check errors all the time on every new start

I suppose a non destructive test will not work, it needs to be able to read the data to be able to write it again, if it fails to read a sector it doesn't know what to write.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#19 2017-07-22 22:47:24

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [SOLVED] File system check errors all the time on every new start

True.
You'll still get a nice list of sectors to dd into and an idea how broken the disk really is (and the destructive test always takes ages ...)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#20 2017-07-23 15:51:56

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] File system check errors all the time on every new start

Good point there and that gave me another idea, with the sector list in hand one could potentially check which files those sectors belong to (if any). Last time I tried doing it I remember it takes a bit of math to take into account partition start and any offsets introduced by lvm/luks/raid (if using any of those).

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#21 2017-07-27 12:32:57

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] File system check errors all the time on every new start

I have replaced the HDD with a new one and everything are working as they should be.

I don't know if it is related by I had an issue with the CD/DVD drive when was connected with the laptop, the BIOS couldn't see both HDD and CD/DVD drive and couldn't boot. Now I can use the CD/DVD drive as before and laugh when I see it in the lsblk results.

Thank you again for your time and  knowledge.

Offline

Pages: 1

Board footer

Powered by FluxBB