Hi all, I am running Leap 15.1 on an HP laptop, I have been using Leap with no problems at all and have been very pleased, however, this happened:
As you can see, a folder named “C” just vanished…
Running dmsg gives me a lot of errors…*.
Thank you all for your time!*
I assume that you are using a graphical file manager.
Try browsing to that location in a console, eg with the following three commands
This test will try to determine if the file system itself has a problem or if it’s only the File Manager application
cd ~/Documents/
ls ~/Documents/
ls ~/
Post your results, and the File Manager you’re using.
TSU
Please also show
cat /etc/fstab
mount
Here it goes:
miguelarestahp@linux-3iq4:~/Documents> cd ~/Documents/
miguelarestahp@linux-3iq4:~/Documents> ls ~/Documents/
ls: cannot access '/home/miguelarestahp/Documents/C': Input/output error
ls: cannot access '/home/miguelarestahp/Documents/mal_chevskiy_v_v_matrichno_topologicheskiy_metod_sinteza_i_k': Input/output error
ls: cannot access '/home/miguelarestahp/Documents/firefox recovery': Input/output error
ACES books firefox recovery Misc
airdwg21 C HathiDownloadHelper_binaries
arrsub_files Codes mal_chevskiy_v_v_matrichno_topologicheskiy_metod_sinteza_i_k
miguelarestahp@linux-3iq4:~/Documents> ls ~/
Calibre Library Documents Music prevBackup rpmbuild Videos
Desktop Downloads Pictures Public Templates
miguelarestahp@linux-3iq4:~/Documents>
The File Manager is Dolphin.
It seems another folder is also missing…
Thank you!
miguelarestahp@linux-3iq4:~/Documents> cat /etc/fstab
/dev/system/root / btrfs defaults 0 0
/dev/system/root /var btrfs subvol=/@/var 0 0
/dev/system/root /usr/local btrfs subvol=/@/usr/local 0 0
/dev/system/root /tmp btrfs subvol=/@/tmp 0 0
/dev/system/root /srv btrfs subvol=/@/srv 0 0
/dev/system/root /root btrfs subvol=/@/root 0 0
/dev/system/root /opt btrfs subvol=/@/opt 0 0
/dev/system/root /home btrfs subvol=/@/home 0 0
/dev/system/root /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
/dev/system/root /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
/dev/system/swap swap swap defaults 0 0
/dev/system/root /.snapshots btrfs subvol=/@/.snapshots 0 0
miguelarestahp@linux-3iq4:~/Documents> mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=3784944k,nr_inodes=946236,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
/dev/mapper/system-root on / type btrfs (rw,relatime,ssd,space_cache,subvolid=453,subvol=/@/.snapshots/146/snapshot)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15885)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
/dev/mapper/system-root on /.snapshots type btrfs (rw,relatime,ssd,space_cache,subvolid=267,subvol=/@/.snapshots)
/dev/mapper/system-root on /tmp type btrfs (rw,relatime,ssd,space_cache,subvolid=260,subvol=/@/tmp)
/dev/mapper/system-root on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=266,subvol=/@/boot/grub2/i386-pc)
/dev/mapper/system-root on /srv type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/srv)
/dev/mapper/system-root on /home type btrfs (rw,relatime,ssd,space_cache,subvolid=264,subvol=/@/home)
/dev/mapper/system-root on /opt type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/opt)
/dev/mapper/system-root on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=265,subvol=/@/boot/grub2/x86_64-efi)
/dev/mapper/system-root on /usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/usr/local)
/dev/mapper/system-root on /root type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/root)
/dev/mapper/system-root on /var type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/var)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=759416k,mode=700,uid=1000,gid=100)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
/dev/fuse on /run/user/1000/doc type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
Thank you for your time.
I/O errors. Doesn’t seem good. I.e. a damaged hdd or ssd.
Agreed.
But first, try removing your drive and clean your electrical contacts with a pencil eraser.
You can also try installing smartcl and running tests, but ASAP you should make sure your data is backed up or otherwise preserved.
TSU
I see…thanks Knurpht!
Any advice?
Will do, I’ll let you know of the outcome.
Also, any straightforward way of backing up my home folder within Leap?
Thank you TSU.
Running smartctl on my /dev/sda4 where all of Leap’s stuff (including my Home) is located:
miguelarestahp@linux-3iq4:~> sudo smartctl -a /dev/sda4
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp151.28.13-default] (SUSE RPM)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: SanDisk SD8SNAT-256G-1006
Serial Number: 164321420718
LU WWN Device Id: 5 001b44 4a69f8d87
Firmware Version: Z2311006
User Capacity: 256,060,514,304 bytes [256 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: M.2
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Aug 22 12:05:13 2019 WEST
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No 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: ( 10) minutes.
SMART Attributes Data Structure revision number: 1
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 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 697
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2216
171 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
173 Unknown_Attribute 0x0033 100 100 005 Pre-fail Always - 731
174 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 229
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 4
194 Temperature_Celsius 0x0022 070 042 000 Old_age Always - 30 (Min/Max 0/58)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 2
230 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 6929
244 Unknown_Attribute 0x0032 000 100 000 Old_age Always - 0
SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 2
ATA Error Count: 0
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00 at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 78 d8 89 3f 00 00 00:00:00.000 WRITE FPDMA QUEUED
61 08 b8 20 89 3f 00 00 00:00:00.000 WRITE FPDMA QUEUED
61 08 b8 20 89 3f 00 00 00:00:00.000 WRITE FPDMA QUEUED
61 08 b8 20 89 3f 00 00 00:00:00.000 WRITE FPDMA QUEUED
61 08 b8 20 89 3f 00 00 00:00:00.000 WRITE FPDMA QUEUED
Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 697 -
# 2 Short offline Completed without error 00% 697 -
# 3 Short offline Completed without error 00% 697 -
# 4 Short offline Aborted by host 60% 695 -
# 5 Short offline Completed without error 00% 694 -
# 6 Short offline Completed without error 00% 694 -
# 7 Short offline Completed without error 00% 692 -
# 8 Short offline Completed without error 00% 691 -
# 9 Short offline Aborted by host 20% 691 -
#10 Short offline Completed without error 00% 690 -
#11 Short offline Completed without error 00% 689 -
#12 Short offline Completed without error 00% 688 -
#13 Short offline Completed without error 00% 687 -
#14 Short offline Completed without error 00% 686 -
#15 Short offline Completed without error 00% 686 -
#16 Short offline Completed without error 00% 685 -
#17 Short offline Completed without error 00% 684 -
#18 Extended offline Completed without error 00% 684 -
#19 Short offline Completed without error 00% 683 -
#20 Short offline Completed without error 00% 683 -
#21 Short offline Completed without error 00% 683 -
Selective Self-tests/Logging not supported
Regards,
Miguel
Since your SSD passed the test (I assume the short test),
There is a reasonable chance that the disk might be usable and the problem is elsewhere.
But, don’t rely on the smartctl tests entirely, they’re not perfect when identifying problems.
Have you done all recommended things to configure your system for an SSD?
As I described, clean and reseat electrical connections.
Review the following page, and note that firmware updates may be recommended for some SANDISK
https://wiki.archlinux.org/index.php/Solid_state_drive
TSU
What shall I do to locate the issue?
I’m not sure…I didn’t do anything special after installing Leap onto this SSD…
I will do so.
Here is the result of the extended test:
https://ibb.co/BnMh2hW](https://ibb.co/BnMh2hW)
I will read the page and follow the instructions
Thank you TSU.
Regards,
Miguel
That type of data loss often happens on external USB flash drives.
The first topic is, does the problem lie in the SSD or elsewhere.
Pull out the SSD. Connect to another computer or USB enclosure. The computer shall run Linux or Live Linux. Make backup if the data is needed, perhaps image the disk if possible.
Then run badblocks in data-destructive mode:
badblocks -wvs -t 3074 /dev/sdx
(replace the sdx with proper name)
Then connect another drive to the HP laptop. The drive must be known to be good. Run non-destructive or destructive badblocks on that drive from Live Linux.
If all badblocks succeed, I would suspect that btrfs or a RAM error caused the failure. Solution on the laptop: don’t use btrfs, check the RAM with memtest.
It is also possible that the motherboard is defective. Update the BIOS. Otherwise, it is difficult to find the hardware error of the motherboard if it doesn’t show itself often. To check, load the computer maximally, including with read-write operations, and run for a few days.
Errors of SSDs are rare. In my experience, they are 20 times less likely than errors of mechanical hard drives, but provided that the SSD was successfully installed during the installation of the OS. However, I think there is 20% chance that the SSD is defective.
Maybe the computer had lost power while the SSD was writing. This may lead to a similar pattern of data loss. The disk needs reformatting and is not defective in this case. I think there is 30% chance of this.