You are not logged in.

Pages: 1

#1 2017-04-16 16:48:21

moesi
Member
Registered: 2014-02-27
Posts: 48

Problem with /home partition - cant access files after some minutes

Hi there!

I have some weird problem after logging in to my xfce session. After some time, when i open the filemanager i get the following error: 

Failed to open directory "user".
Error when getting information for file '/home/user'   Input/output error.

Can this be a problem with the ssd? The home partition is on the 2nd ssd in my Dell Xps15 (early2016).
I tried a disk test: 

sudo smartctl -t short /dev/sda

i get this error: 

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

and with -T permissive i get this output:

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.8-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Short INQUIRY response, skip product id
Short Background Self Test has begun
Use smartctl -X to abort test

Maybe someone can help me with this?

greetings Moesi

Last edited by moesi (2017-04-17 10:50:59)

Offline

#2 2017-04-18 13:01:59

subwaypassenger
Member
Registered: 2017-04-18
Posts: 9

Re: Problem with /home partition - cant access files after some minutes

What says 'lsblk' about your /home? (/dev/sda is the 1st disk, not the 2nd.)
What says 'dmesg' after the error?
What says 'smartctl --all /dev/sdb'? (the disk where /home is)

Offline

#3 2017-04-18 13:48:41

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

I have the root partition on nvme, and my /home on the sda. wink
I currently have not auto-mounted the ssd on startup so i created my home-folder on the nvme-disk.

After manual mounting the ssd, and now about 15minutes later i am able to fully access all directories and no error until now...

FYI:  The first time the error occured, when i booted the system after a backup with "BackInTime"... Could it be possible that there went something wrong?

lsblk /dev/sda:

NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0  477G  0 disk 
└─sda1   8:1    0  477G  0 part

smartctl --all /dev/sda: (unmounted again for the test)

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.9-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron MX100/MX200/M5x0/M600 Client SSDs
Device Model:     Crucial_CT512MX100SSD1
Serial Number:    14400D6E0D76
LU WWN Device Id: 5 00a075 10d6e0d76
Firmware Version: MU01
User Capacity:    512,110,190,592 bytes [512 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Apr 18 13:29:07 2017 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:  (0x80)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		( 2380) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					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: 	 (   6) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x0035)	SCT Status 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     0x002f   100   100   000    Pre-fail  Always       -       0
  5 Reallocate_NAND_Blk_Cnt 0x0033   100   100   000    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       3715
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1595
171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 Ave_Block-Erase_Count   0x0032   100   100   000    Old_age   Always       -       19
174 Unexpect_Power_Loss_Ct  0x0032   100   100   000    Old_age   Always       -       114
180 Unused_Reserve_NAND_Blk 0x0033   000   000   000    Pre-fail  Always       -       4403
183 SATA_Interfac_Downshift 0x0032   100   100   000    Old_age   Always       -       1
184 Error_Correction_Count  0x0032   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   056   050   000    Old_age   Always       -       44 (Min/Max 10/50)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       26
202 Percent_Lifetime_Used   0x0031   100   100   000    Pre-fail  Offline      -       0
206 Write_Error_Rate        0x000e   100   100   000    Old_age   Always       -       0
210 Success_RAIN_Recov_Cnt  0x0032   100   100   000    Old_age   Always       -       0
246 Total_Host_Sector_Write 0x0032   100   100   000    Old_age   Always       -       9450945688
247 Host_Program_Page_Count 0x0032   100   100   000    Old_age   Always       -       297684157
248 Bckgnd_Program_Page_Cnt 0x0032   100   100   000    Old_age   Always       -       335578485

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  Vendor (0xff)       Completed without error       00%      3578         -
# 2  Vendor (0xff)       Completed without error       00%      3546         -
# 3  Vendor (0xff)       Completed without error       00%      3521         -
# 4  Vendor (0xff)       Completed without error       00%      3463         -
# 5  Short offline       Completed without error       00%      3355         -
# 6  Vendor (0xff)       Completed without error       00%      3022         -
# 7  Vendor (0xff)       Completed without error       00%      2460         -
# 8  Vendor (0xff)       Completed without error       00%      2271         -
# 9  Vendor (0xff)       Completed without error       00%      2250         -
#10  Vendor (0xff)       Completed without error       00%      1871         -
#11  Vendor (0xff)       Completed without error       00%      1815         -
#12  Vendor (0xff)       Completed without error       00%      1780         -
#13  Vendor (0xff)       Completed without error       00%      1763         -
#14  Vendor (0xff)       Completed without error       00%      1687         -
#15  Vendor (0xff)       Completed without error       00%      1619         -
#16  Vendor (0xff)       Completed without error       00%      1560         -
#17  Extended offline    Completed without error       00%      1428         -
#18  Short offline       Completed without error       00%      1428         -

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.

What i can remember in the output from dmesg were many input/output errors...

greetings

Offline

#4 2017-04-18 14:57:26

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

Re: Problem with /home partition - cant access files after some minutes

You probably want to update the firmware of your SSD to version MU02 as it seems to contain many important fixes (although crucial says the update is optional).

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#5 2017-04-18 18:49:58

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: Problem with /home partition - cant access files after some minutes

In that SMART table you show, there's a number of "UDMA_CRC_Error_Count" events getting recorded. On a desktop PC, that can mean that you should try using a different SATA data cable. I don't know what you're supposed to do with a laptop.

Offline

#6 2017-04-19 10:51:04

seth
Member
Registered: 2012-09-03
Posts: 51,053

Re: Problem with /home partition - cant access files after some minutes

Drive going idle/power saving and fails to wake up?

Try to keep it alive

while true; do stat /home/user/.config; sleep 5m; done

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

Offline

#7 2017-04-19 11:41:57

subwaypassenger
Member
Registered: 2017-04-18
Posts: 9

Re: Problem with /home partition - cant access files after some minutes

moesi wrote:

lsblk /dev/sda:

NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0  477G  0 disk 
└─sda1   8:1    0  477G  0 part

It is not mounted.

Offline

#8 2017-04-19 16:19:02

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

subwaypassenger wrote:
moesi wrote:

lsblk /dev/sda:

NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0  477G  0 disk 
└─sda1   8:1    0  477G  0 part

It is not mounted.

Yes it isn't, i made the commands before i manually mounted them.

seth wrote:

Drive going idle/power saving and fails to wake up?

Try to keep it alive

while true; do stat /home/user/.config; sleep 5m; done

well actually i dont think that the drive goes to sleep or idle, firefox writes to the cache in my home directory, or am i wrong? If it goes to sleep in less then 30 seconds, wouldnt it mean that the ssd had to go to idle/sleep also when manually mounted?


Anyway, i am a little busy with other things and i will backup again the harddisk and try to update the firmware... I will let you know if something happens. hmm

Thanks for now! wink

Offline

#9 2017-04-27 09:21:57

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

So, i have updated the firmware. But right now i have the same problem again. (SSD is not mounted as /home! it was mounted manually)

Yesterday - when i only read data from it (ssd) to make a backup - it ran about 3 hours (with no problem), until i shut down the notebook.
Just some minutes ago, i wanted to reconfigure my fstab to mount the ssd again to my /home. So i copied some files from my home (of the root nvme partition) to the ssd, then it happend again.

dmesg:

[  323.912984] ata2.00: exception Emask 0x0 SAct 0x40000000 SErr 0x50000 action 0x6 frozen
[  323.912993] ata2: SError: { PHYRdyChg CommWake }
[  323.912999] ata2.00: failed command: READ FPDMA QUEUED
[  323.913008] ata2.00: cmd 60/08:f0:70:00:40/00:00:01:00:00/40 tag 30 ncq dma 4096 in
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[  323.913012] ata2.00: status: { DRDY }
[  323.913018] ata2: hard resetting link
[  329.266289] ata2: link is slow to respond, please be patient (ready=0)
[  333.969631] ata2: COMRESET failed (errno=-16)
[  333.969646] ata2: hard resetting link
[  339.322967] ata2: link is slow to respond, please be patient (ready=0)
[  343.982963] ata2: COMRESET failed (errno=-16)
[  343.982971] ata2: hard resetting link
[  349.342985] ata2: link is slow to respond, please be patient (ready=0)
[  379.009622] ata2: COMRESET failed (errno=-16)
[  379.009638] ata2: limiting SATA link speed to 3.0 Gbps
[  379.009641] ata2: hard resetting link
[  384.022959] ata2: COMRESET failed (errno=-16)
[  384.022981] ata2: reset failed, giving up
[  384.022985] ata2.00: disabled
[  384.023024] ata2: EH complete
[  384.023047] sd 1:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023052] sd 1:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 01 40 00 70 00 00 08 00
[  384.023055] blk_update_request: I/O error, dev sda, sector 20971632
[  384.023075] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 89, block_bitmap = 2621449
[  384.023131] sd 1:0:0:0: [sda] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023136] sd 1:0:0:0: [sda] tag#2 CDB: opcode=0x2a 2a 00 00 00 00 28 00 00 08 00
[  384.023139] blk_update_request: I/O error, dev sda, sector 40
[  384.023145] blk_update_request: I/O error, dev sda, sector 40
[  384.023150] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023231] sd 1:0:0:0: [sda] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023236] sd 1:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 01 40 00 78 00 00 08 00
[  384.023239] blk_update_request: I/O error, dev sda, sector 20971640
[  384.023261] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 90, block_bitmap = 2621450
[  384.023271] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023314] sd 1:0:0:0: [sda] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023319] sd 1:0:0:0: [sda] tag#4 CDB: opcode=0x2a 2a 00 00 00 00 28 00 00 08 00
[  384.023322] blk_update_request: I/O error, dev sda, sector 40
[  384.023328] blk_update_request: I/O error, dev sda, sector 40
[  384.023332] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023388] sd 1:0:0:0: [sda] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023392] sd 1:0:0:0: [sda] tag#5 CDB: opcode=0x28 28 00 01 40 00 80 00 00 08 00
[  384.023394] blk_update_request: I/O error, dev sda, sector 20971648
[  384.023414] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 91, block_bitmap = 2621451
[  384.023421] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023455] sd 1:0:0:0: [sda] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023458] sd 1:0:0:0: [sda] tag#6 CDB: opcode=0x2a 2a 00 00 00 00 28 00 00 08 00
[  384.023460] blk_update_request: I/O error, dev sda, sector 40
[  384.023464] blk_update_request: I/O error, dev sda, sector 40
[  384.023468] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023525] sd 1:0:0:0: [sda] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023529] sd 1:0:0:0: [sda] tag#7 CDB: opcode=0x28 28 00 01 40 00 88 00 00 08 00
[  384.023532] blk_update_request: I/O error, dev sda, sector 20971656
[  384.023551] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 92, block_bitmap = 2621452
[  384.023557] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023589] sd 1:0:0:0: [sda] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023593] sd 1:0:0:0: [sda] tag#8 CDB: opcode=0x2a 2a 00 00 00 00 28 00 00 08 00
[  384.023598] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023655] sd 1:0:0:0: [sda] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023659] sd 1:0:0:0: [sda] tag#9 CDB: opcode=0x28 28 00 01 40 00 90 00 00 08 00
[  384.023670] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 93, block_bitmap = 2621453
[  384.023675] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023695] sd 1:0:0:0: [sda] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  384.023698] sd 1:0:0:0: [sda] tag#10 CDB: opcode=0x2a 2a 00 00 00 00 28 00 00 08 00
[  384.023701] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023744] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 94, block_bitmap = 2621454
[  384.023749] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023768] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023808] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 95, block_bitmap = 2621455
[  384.023812] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023829] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023869] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 96, block_bitmap = 3145728
[  384.023873] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023890] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023927] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 97, block_bitmap = 3145729
[  384.023932] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.023948] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.023988] EXT4-fs error (device sda1): ext4_wait_block_bitmap:503: comm kworker/u16:4: Cannot read block bitmap - block_group = 98, block_bitmap = 3145730
[  384.023993] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.024009] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  384.024045] EXT4-fs (sda1): previous I/O error to superblock detected
[  384.027646] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 4198400 starting block 5439749)
[  384.027650] Buffer I/O error on device sda1, logical block 5439488
[  384.027659] Buffer I/O error on device sda1, logical block 5439489
[  384.027662] Buffer I/O error on device sda1, logical block 5439490
[  384.027666] Buffer I/O error on device sda1, logical block 5439491
[  384.027669] Buffer I/O error on device sda1, logical block 5439492
[  384.027672] Buffer I/O error on device sda1, logical block 5439493
[  384.027675] Buffer I/O error on device sda1, logical block 5439494
[  384.027679] Buffer I/O error on device sda1, logical block 5439495
[  384.027682] Buffer I/O error on device sda1, logical block 5439496
[  384.027685] Buffer I/O error on device sda1, logical block 5439497
[  384.027938] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 4198400 starting block 5440005)
[  384.028270] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 4198400 starting block 5440261)
[  384.029866] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 8388608 starting block 5440517)
[  384.030121] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 8388608 starting block 5440773)
[  384.030412] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 8388608 starting block 5441029)
[  384.030658] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 8388608 starting block 5441285)
[  384.031843] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 0 size 8388608 starting block 5441541)
[  384.032707] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 8388608 size 2101248 starting block 5441797)
[  384.033632] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 5783785 (offset 8388608 size 3149824 starting block 5442053)
[  384.042426] JBD2: Detected IO errors while flushing file data on sda1-8
[  384.042429] Aborting journal on device sda1-8.
[  384.042444] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  384.042465] JBD2: Detected IO errors while flushing file data on sda1-8
[  386.193030] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal

Offline

#10 2017-04-27 11:44:05

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: Problem with /home partition - cant access files after some minutes

moesi wrote:

Yesterday - when i only read data from it (ssd) to make a backup - it ran about 3 hours (with no problem), until i shut down the notebook.
Just some minutes ago, i wanted to reconfigure my fstab to mount the ssd again to my /home. So i copied some files from my home (of the root nvme partition) to the ssd, then it happend again.

Maybe it doesn't like being written to? smile In any case, it looks like the disk just decides it doesn't want to talk to you anymore.

You can try silly tweaks like disabling NCQ or limiting speed to 1.5G. If possible, test it in other machine or try some other disk in this machine.

I heard that some SSDs can also be allergic to TRIM. Are you sure the partition is not mounted with -o discard?

Last edited by mich41 (2017-04-27 11:45:28)

Offline

#11 2017-04-27 12:19:07

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

mh.. And this behaviour can occur after nearly 1 year trouble-free usage? I am just wondering. hmm

my fstab entry:

#/dev/sda1              /home           ext4            rw,relatime,data=ordered        0 2

Well i can format it and try it in my gaming Windows pc. I will post it here, when i have time for testing this sad

Offline

#12 2017-04-27 12:30:47

seth
Member
Registered: 2012-09-03
Posts: 51,053

Re: Problem with /home partition - cant access files after some minutes

There's no need to "format" it and certainly not before you tested changing the connection (ie. cable and plugs, apparently it is changeable)

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

Offline

#13 2017-04-27 15:54:21

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

its a notebook. i think if i order the spare part it will take some weeks. By the other hand, i am not shure if i am able to get them anyway... sad
So but you think its more likely that the cable is broken? but why its only when i write to the ssd? any glue for that?

Maybe it would be better to get in contact with Dell.

Last edited by moesi (2017-04-27 15:57:43)

Offline

#14 2017-04-27 18:45:52

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: Problem with /home partition - cant access files after some minutes

moesi wrote:

but why its only when i write to the ssd?

Why do you think it fails on writing and not, say, on Thursdays, Fridays and Mondays but not Wednesdays? Because some random guy on the Internet said so? tongue (In fact, note that I only suggested it as a possibility).

But this actually might be a good idea - check if you can reliably trigger the problem by copying something to the disk. If this works, at least we will have a way to quickly test whether any potential solution actually helps without waiting to the next Thursday wink

And just for kicks, maybe run the long SMART self-test. It probably won't find anything, but if it does, there is no point trying other things.

Do you remember when exactly it started? Theoretically it may be a kernel bug, brought in by some recent system update. It won't hurt to temporarily downgrade the kernel to some version you used before it started and see what happens.

edit:

I see somebody noticed nonzero UDMA_CRC_Error_Count in SMART data. Does this counter keep increasing every time it happens?

Last edited by mich41 (2017-04-27 18:50:29)

Offline

#15 2017-04-27 20:27:32

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

mich41 wrote:
moesi wrote:

but why its only when i write to the ssd?

Why do you think it fails on writing and not, say, on Thursdays, Fridays and Mondays but not Wednesdays? Because some random guy on the Internet said so? tongue (In fact, note that I only suggested it as a possibility).

But this actually might be a good idea - check if you can reliably trigger the problem by copying something to the disk. If this works, at least we will have a way to quickly test whether any potential solution actually helps without waiting to the next Thursday wink

And just for kicks, maybe run the long SMART self-test. It probably won't find anything, but if it does, there is no point trying other things.

Do you remember when exactly it started? Theoretically it may be a kernel bug, brought in by some recent system update. It won't hurt to temporarily downgrade the kernel to some version you used before it started and see what happens.

edit:

I see somebody noticed nonzero UDMA_CRC_Error_Count in SMART data. Does this counter keep increasing every time it happens?


Well i tried some time since my last post to trigger the error, but with no luck. sad
I then changed the fstab and boom, after restart and starting firefox it crashed again. I found an old 2.5" hdd and changed it with the ssd. I hope the error occurs with this setup too... Just to know thats it is not the ssd. hmm
But as i said, i couldnt trigger the event... sad

Last edited by moesi (2017-04-27 20:28:03)

Offline

#16 2017-04-27 20:49:40

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: Problem with /home partition - cant access files after some minutes

What's "smartctl -a" showing for the drive right now? In your post from April 18, the entry "199 UDMA_CRC_Error_Count" had a count of "26". Did that increase since then?

Offline

#17 2017-04-27 21:11:08

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

Actually with the old hdd.. 0.

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.9-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Travelstar 7K100
Device Model:     HTS721080G9SA00
Serial Number:    MPDDN7Y4HBTHJL
Firmware Version: MC4OC12V
User Capacity:    80,026,361,856 bytes [80.0 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 T13/1532D revision 1
Local Time is:    Thu Apr 27 20:59:47 2017 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:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
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: 	 (  45) minutes.

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   100   099   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   114   100   040    Pre-fail  Offline      -       3471
  3 Spin_Up_Time            0x0007   217   100   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   098   098   000    Old_age   Always       -       4565
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       60 (0 7)
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   116   100   040    Pre-fail  Offline      -       38
  9 Power_On_Hours          0x0012   086   086   000    Old_age   Always       -       6249
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       3770
191 G-Sense_Error_Rate      0x000a   100   094   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   096   096   000    Old_age   Always       -       2229029
193 Load_Cycle_Count        0x0012   073   073   000    Old_age   Always       -       271090
194 Temperature_Celsius     0x0002   152   090   000    Old_age   Always       -       36 (Min/Max 19/61)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       8
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
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.

If you want i will again check with the ssd tomorrow wink

Last edited by moesi (2017-04-27 21:11:47)

Offline

#18 2017-04-28 08:20:50

moesi
Member
Registered: 2014-02-27
Posts: 48

Re: Problem with /home partition - cant access files after some minutes

I replaced again the hdd (the error didn't occured with it) with the ssd, and - as i expected it - it crashed...
UDMA_CRC_Error_Count is still 26

How can i reduce the speed of the sata connection? Maybe i try it this way...

Offline

#19 2017-04-28 14:07:09

seth
Member
Registered: 2012-09-03
Posts: 51,053

Re: Problem with /home partition - cant access files after some minutes

pass "libata.force=1.5G" to the kernel parameters (preferably from the grub commandline, not permanent settings - until you're sure this is good to go)

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

Offline

Pages: 1

Board footer

Powered by FluxBB