Xfce Desktop crashes periodically

mintvx · 09-28-2014, 07:29 PM

Debian Wheezy on SSD, crached when I browsed with Midori, several tab been opened and few .txt docs opened, no other apps. When I opened Tunar File Manager, the folders are missed in the right pane. Recycle Bin on Desktop has missing icon, the other folders also looks different. Also, when try Log out, error shown

Code:

"Failed to execute command Xfce-4-session-logout.(no such file or directory)"

Same thing when try to open any application. I pressed Power off button on laptop, it than show terminal screen with texts like

Code:

[12055.788372] ETX4-fs error (device sdb2): ext4_find_entry:932: inode # 1572866: comm lightdm: reading iblock 0"

After restarting PC, problem has gone. Which log file store such issue? (log file names are just meaningless).

frankbell · 09-28-2014, 08:56 PM

I don't have Debian running right now, and I might not be 100% correct on the file names, but I'd look first in /var/log/messages or /var/log/system (may be "syslog").

You might also look in /var/log/Xorg.0.log.

mintvx · 09-29-2014, 02:42 PM

I checked these files, but can find anything that tells about the issue

messages line 1235?
syslog
Xorg.0.log
messages1

compare with Windows Event Viewer, where you can find Aplication, Security, Setup, System logs, Linux logs system looks quite confusing, is there a sort of Event Viewer for Linux?

propofol · 09-29-2014, 09:20 PM

That sounds like a disk error. It might be worth booting from a live cd & running fsck.ext4 on the drive. If the drive supports S.M.A.R.T. I would try "smartctl -a /dev/sdx" first.

mintvx · 09-30-2014, 08:26 AM

Quote:

Originally Posted by propofol

That sounds like a disk error. It might be worth booting from a live cd & running fsck.ext4 on the drive. If the drive supports S.M.A.R.T. I would try "smartctl -a /dev/sdx" first.

"smartctl -a /dev/sdX" - this command shows how long a drive has been in use? The SSD drive is almost new, I just recently did a first installation.
Can you specify how to properly use fsck.ext4 from a Live CD? The disk error can be caused by hardware issue or by software error?

rokytnji · 09-30-2014, 09:08 AM

Quote:

Can you specify how to properly use fsck.ext4 from a Live CD?

Live CD>Gparted>right click partition>unmount>check.

mintvx · 09-30-2014, 01:49 PM

here is smartctl results:

Code:

smartctl 6.2 2013-04-20 r3812 [i686-linux-3.9.6] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     KINGSTON SV300S37A60G
Serial Number:    50026B7742002F48
LU WWN Device Id: 5 0026b7 742002f48
Firmware Version: 525ABBF0
User Capacity:    60,022,480,896 bytes [60.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS, ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Tue Sep 30 17:25:20 2014 EDT
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:      (   1)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x79) SMART execute Offline immediate.
					No Auto Offline data collection 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  36) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x0025)	SCT Status supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0033   120   120   050    Pre-fail  Always       -       0/0
  5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always       -       0
  9 Power_On_Hours_and_Msec 0x0032   100   100   000    Old_age   Always       -       25h+24m+35.670s
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       69
171 Program_Fail_Count      0x000a   000   000   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       -       0
174 Unexpect_Power_Loss_Ct  0x0030   000   000   000    Old_age   Offline      -       69
177 Wear_Range_Delta        0x0000   000   000   000    Old_age   Offline      -       1
181 Program_Fail_Count      0x000a   000   000   000    Old_age   Always       -       0
182 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0012   100   100   000    Old_age   Always       -       0
189 Airflow_Temperature_Cel 0x0000   026   031   000    Old_age   Offline      -       26 (Min/Max 17/31)
194 Temperature_Celsius     0x0022   026   031   000    Old_age   Always       -       26 (Min/Max 17/31)
195 ECC_Uncorr_Error_Count  0x001c   120   120   000    Old_age   Offline      -       0/0
196 Reallocated_Event_Count 0x0033   100   100   003    Pre-fail  Always       -       0
201 Unc_Soft_Read_Err_Rate  0x001c   120   120   000    Old_age   Offline      -       0/0
204 Soft_ECC_Correct_Rate   0x001c   120   120   000    Old_age   Offline      -       0/0
230 Life_Curve_Status       0x0013   100   100   000    Pre-fail  Always       -       100
231 SSD_Life_Left           0x0013   100   100   010    Pre-fail  Always       -       0
233 SandForce_Internal      0x0032   000   000   000    Old_age   Always       -       11
234 SandForce_Internal      0x0032   000   000   000    Old_age   Always       -       19
241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always       -       19
242 Lifetime_Reads_GiB      0x0032   000   000   000    Old_age   Always       -       5

SMART Error Log not supported

SMART Self-test Log not supported

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.

fsck result:

Code:

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
BOOT: 240/128000 files (1.3% non-contiguous), 32621/256000 blocks

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
ROOT: 101764/2498560 files (0.2% non-contiguous), 894670/9984000 blocks

propofol · 09-30-2014, 03:51 PM

Quote:

Originally Posted by mintvx

here is smartctl results:

Code:

smartctl 6.2 2013-04-20 r3812 [i686-linux-3.9.6] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     KINGSTON SV300S37A60G
...
SMART overall-health self-assessment test result: PASSED

..
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0033   120   120   050    Pre-fail  Always       -       0/0
  5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always       -       0
  9 Power_On_Hours_and_Msec 0x0032   100   100   000    Old_age   Always       -       25h+24m+35.670s
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       69
171 Program_Fail_Count      0x000a   000   000   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       -       0
174 Unexpect_Power_Loss_Ct  0x0030   000   000   000    Old_age   Offline      -       69
177 Wear_Range_Delta        0x0000   000   000   000    Old_age   Offline      -       1
181 Program_Fail_Count      0x000a   000   000   000    Old_age   Always       -       0
182 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0012   100   100   000    Old_age   Always       -       0
189 Airflow_Temperature_Cel 0x0000   026   031   000    Old_age   Offline      -       26 (Min/Max 17/31)
194 Temperature_Celsius     0x0022   026   031   000    Old_age   Always       -       26 (Min/Max 17/31)
195 ECC_Uncorr_Error_Count  0x001c   120   120   000    Old_age   Offline      -       0/0
196 Reallocated_Event_Count 0x0033   100   100   003    Pre-fail  Always       -       0
201 Unc_Soft_Read_Err_Rate  0x001c   120   120   000    Old_age   Offline      -       0/0
204 Soft_ECC_Correct_Rate   0x001c   120   120   000    Old_age   Offline      -       0/0
230 Life_Curve_Status       0x0013   100   100   000    Pre-fail  Always       -       100
231 SSD_Life_Left           0x0013   100   100   010    Pre-fail  Always       -       0
233 SandForce_Internal      0x0032   000   000   000    Old_age   Always       -       11
234 SandForce_Internal      0x0032   000   000   000    Old_age   Always       -       19
241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always       -       19
242 Lifetime_Reads_GiB      0x0032   000   000   000    Old_age   Always       -       5
...

Seems ok to me. You could do a self check with "smartctl -t long /dev/sdX"

Quote:

Code:

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
BOOT: 240/128000 files (1.3% non-contiguous), 32621/256000 blocks

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
ROOT: 101764/2498560 files (0.2% non-contiguous), 894670/9984000 blocks

Seems fine as well. Did "dmesg" show any other file system errors?

If the drive is working properly the only other suggestion I have would be to try another SATA controller card. I have had issues with this in a cheap HP Slimline PC I bought on a special once. The OSes I had on it (both Windows & Debian) crashed after after a few weeks of use. After swapping drives & operating systems it finally dawned on me it was a hardware problem.

The fastest (if somewhat painful) way to check is to put the ssd in another computer & boot it up there. If you are using a Debian based system, delete the lines with "SUBSYSTEM=="net",..." lines from "/etc/udev/rules.d/70-persistent-net.rules" (or similar) to keep wlan0 & eth0 from being renamed. You would need to edit the bios so that it boots up from this drive.

Regards,
Stefan

mintvx · 09-30-2014, 04:51 PM

Quote:

Originally Posted by propofol

Seems ok to me. You could do a self check with "smartctl -t long /dev/sdX"

Seems fine as well. Did "dmesg" show any other file system errors?

If the drive is working properly the only other suggestion I have would be to try another SATA controller card. I have had issues with this in a cheap HP Slimline PC I bought on a special once. The OSes I had on it (both Windows & Debian) crashed after after a few weeks of use. After swapping drives & operating systems it finally dawned on me it was a hardware problem.

The fastest (if somewhat painful) way to check is to put the ssd in another computer & boot it up there. If you are using a Debian based system, delete the lines with "SUBSYSTEM=="net",..." lines from "/etc/udev/rules.d/70-persistent-net.rules" (or similar) to keep wlan0 & eth0 from being renamed. You would need to edit the bios so that it boots up from this drive.

Regards,
Stefan

Thank you for info.
"dmesg" not show errors, but I am not sure about lines 838-844 here.

The SSD disk is an external USB drive, connected to Windows laptop. I will check it on another PC when possible.

About use smartctl command: should I run it from Live CD on the unmounted disk?

propofol · 10-01-2014, 01:27 AM

Quote:

Originally Posted by mintvx

Thank you for info.
"dmesg" not show errors, but I am not sure about lines 838-844 here.

Code:

...[    3.320718] EXT4-fs (sdb2): INFO: recovery required on readonly filesystem
[    3.320721] EXT4-fs (sdb2): write access will be enabled during recovery
[    5.366367] EXT4-fs (sdb2): orphan cleanup on readonly fs
[    5.366375] EXT4-fs (sdb2): ext4_orphan_cleanup: deleting unreferenced inode 6072
[    5.366426] EXT4-fs (sdb2): ext4_orphan_cleanup: deleting unreferenced inode 6071
[    5.366442] EXT4-fs (sdb2): 2 orphan inodes deleted
[    5.366444] EXT4-fs (sdb2): recovery complete
...

It does look like there was some file system corruption. Is it possible that the drive was not properly unmounted prior to shutdown / restart?

Quote:

About use smartctl command: should I run it from Live CD on the unmounted disk?

Yes. As far as I am aware the smartctl self test should be done on a unmounted drive. Getting information with '-a' should not be a problem on a mounted drive.

mintvx · 10-01-2014, 05:07 AM

Quote:

Originally Posted by propofol

Code:

...[    3.320718] EXT4-fs (sdb2): INFO: recovery required on readonly filesystem
[    3.320721] EXT4-fs (sdb2): write access will be enabled during recovery
[    5.366367] EXT4-fs (sdb2): orphan cleanup on readonly fs
[    5.366375] EXT4-fs (sdb2): ext4_orphan_cleanup: deleting unreferenced inode 6072
[    5.366426] EXT4-fs (sdb2): ext4_orphan_cleanup: deleting unreferenced inode 6071
[    5.366442] EXT4-fs (sdb2): 2 orphan inodes deleted
[    5.366444] EXT4-fs (sdb2): recovery complete
...

It does look like there was some file system corruption. Is it possible that the drive was not properly unmounted prior to shutdown / restart?

It could be, its USB drive, maybe I improperly disconnected external SSD drive, but I'm not sure. Does linux completely repair and recover file system?

propofol · 10-02-2014, 01:09 AM

Quote:

Originally Posted by mintvx

It could be, its USB drive, maybe I improperly disconnected external SSD drive, but I'm not sure. Does linux completely repair and recover file system?

It looks like it was fixed:

Code:

[    5.366444] EXT4-fs (sdb2): recovery complete

mintvx · 10-04-2014, 02:22 PM

I'm still getting this error periodically.

Xfce Desktop crashes after some time of inactivity, and it becomes inaccessible any more. The part of folders in File Manager are missing, and the directories are completely empty. Also, when the terminal was opened and come this error, there was text "Message from syslog@debian at Oct 03 11:47:21 2014 ...Kernel: journal commit I/O error"

When try to log out, I got error "Failed to execute command Xfce-4-session-logout.(no such file or directory)"
I can only Ctrl+Alt+F1 which get me to a terminal with messages
[...] ETX4-fs error (device sdb2): ext4_find_entry:932: inode # xxxxxx: comm lightdm: reading iblock 0" or
[...] ETX4-fs error (device sdb2): ext4_find_entry:932: inode # xxxxx: com console-kit-dae: reading directory lblock 0".

The only way is to press power off button to shut down.

I'm thinking this can be somehow related to PC hardware, or insufficient current over USB ports (the port where was connected SSD).