You are not logged in.
Suddenly started getting input/output errors on running commands in terminal. Restarted, now the disk isnt recognized and wont mount leading to “timeout waiting for disk …” error on systemd. Hasn’t even been a year since I got the new SSD.
Attaching fsck and fdisk ouptut. On IRC told that it could be hardware failure and can reach out to WD and see if they can recover. I'd like to see if there's something I can do in the meantime and if it is easily fixable. I need the data on it and going to WD and recovering data if any is going to take weeks.
[meet@meet-laptop dev]$ sudo fdisk -l /dev/sda
Disk /dev/sda: 16 KiB, 16384 bytes, 32 sectors
Disk model: Sandisk Milpitas
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[meet@meet-laptop dev]$ sudo fsck /dev/sda
fsck from util-linux 2.36
e2fsck 1.45.6 (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Offline
You run fsck on a filesystem level, so passing the entire blockdevice is wrong, you'd pass a partition.
What you actually should pass the entire device to before the fsck is a smartctl command: https://wiki.archlinux.org/index.php/S. … Run_a_test
Run a long test, wait for the mentioned time to pass and post the output of
sudo smartctl -a /dev/sda
Last edited by V1del (2020-10-21 15:28:31)
Offline
I see, the partitions aren't visible.
[meet@meet-laptop flamy]$ ls /dev/sda*
/dev/sda
The long test command failed
[meet@meet-laptop flamy]$ sudo smartctl -t long /dev/sda
[sudo] password for meet:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.1-arch1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
SMART support is: Unavailable - device lacks SMART capability.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
The later command output even though the earlier one failed if helpful
[meet@meet-laptop flamy]$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.1-arch1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Sandisk Milpitas SSD
Serial Number: [No Information Found]
Firmware Version: 0.00
User Capacity: 16,384 bytes [16.3 KB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA/ATAPI-6 T13/1410D revision 1
Local Time is: Wed Oct 21 21:03:08 2020 IST
SMART support is: Unavailable - device lacks SMART capability.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Last edited by meetm (2020-10-21 15:34:00)
Offline
Check https://wiki.archlinux.org/index.php/S. … .#smartctl in that case and enable smart if possible, if that's not possible then I'd choose another brand as that's pretty basic diagnostic functionality that's lacking here...
Offline
This is from WD. I believe lack of smartctl not able to get the info maybe the same problem?
[meet@meet-laptop flamy]$ sudo smartctl --info /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.1-arch1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Sandisk Milpitas SSD
Serial Number: [No Information Found]
Firmware Version: 0.00
User Capacity: 16,384 bytes [16.3 KB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA/ATAPI-6 T13/1410D revision 1
Local Time is: Wed Oct 21 21:10:22 2020 IST
SMART support is: Unavailable - device lacks SMART capability.
Offline
Potentially, user capacity 16KB really reads like the HW controller is hosed.
If possible try another SATA cable/port or so, maybe it's just a cable issue
Last edited by V1del (2020-10-21 15:46:56)
Offline
Can that happen out of blue without any reason? And what can be done about it? Anyway to get the data back?
Offline
It isn't a cable issue because I tried connecting another HDD with the same cable and it and its partitions all were detected correctly.
Offline
I also suspect that only WD can really help you here. Unless it's a kernel bug? Any other operating systems to test?
Offline
Not really, got different version of kernel, but that's it. However, it was working fine until now, so unlikely it could be a kernel bug..?
Offline
google "Sandisk Milpitas SSD" … this device seems to have this problem more often :-(
Offline
SSDs are finitely durable storage and will fail hard and for most users irrecoverably when their time comes. I hope you have backups -- in that case I'd ddrescue everything that's left readable, discard this faulty device and move on. Getting the data off this thing is first priority if not already. If it's under warranty get it replaced.
Last edited by jsoy9pQbYVNu5nfU (2020-10-21 18:14:11)
Offline
google "Sandisk Milpitas SSD" … this device seems to have this problem more often :-(
Yes, seeing quite many grievances
Offline
SSDs are finitely durable storage and will fail hard and for most users irrecoverably when their time comes. I hope you have backups -- in that case I'd ddrescue everything that's left readable, discard this faulty device and move on. Getting the data off this thing is first priority if not already. If it's under warranty get it replaced.
Sadly no backups and I had some idea with the SSD failures however did not expect this soon. It hasn't been a year yet and failing while still under warranty.
If ddrescue can get me the data, it'd be great!
Offline
ddrescue also only rescues the 16kb that kernel is able to report is the size of the device
flamy@meet-laptop ~ [1]> sudo ddrescue -d /dev/sda test.img test.logfile
GNU ddrescue 1.25
Press Ctrl-C to interrupt
ipos: 0 B, non-trimmed: 0 B, current rate: 16384 B/s
opos: 0 B, non-scraped: 0 B, average rate: 16384 B/s
non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s
rescued: 16384 B, bad areas: 0, run time: 0s
pct rescued: 100.00%, read errors: 0, remaining time: n/a
time since last successful read: n/a
Finished
Offline