I have problems with my ssd disk. This disk is used less than 6m. I install on it Windows 10 and after this Debian linux and use linux. Windows is used very rare. I have updates on my linux and restart system. And problems start. It give me a lot of input/output errors (i don`t have pic of them). Now i have connected disk on other computer again with Win10 and linux. This is situation on ssd disk: Disk /dev/sdb: 223,57 GiB, 240057409536 bytes, 468862128 sectors Disk model: Patriot Burst El Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x393a909f

Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 1126399 1124352 549M 7 HPFS/NTFS/exFAT /dev/sdb2 1126400 183175167 182048768 86,8G 7 HPFS/NTFS/exFAT /dev/sdb3 183175168 184262655 1087488 531M 27 Hidden NTFS WinRE /dev/sdb4 184262656 468862127 284599472 135,7G 5 Extended /dev/sdb5 184264704 188166143 3901440 1,9G 82 Linux swap / Solaris /dev/sdb6 188168192 468860927 280692736 133,8G 83 Linux

Sometimes it show me /home folder and my name but folders inside are empty. Yesterday it show me that there is no partitions on disk. From yesterday work testdis with deepscan, but no luck. Today after restart with fdisk -l i see partition above. Now i try to scan for badblocks but i receive this

sudo e2fsck -cfpv /dev/sdb1 e2fsck: Bad magic number in super-block while trying to open /dev/sdb1 /dev/sdb1: 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 or e2fsck -b 32768

/dev/sdb1 contains a ntfs file system labelled 'System Reserved' So i skip to sda6 where is my /home folder and important data:

star@stars:~$ sudo e2fsck -cfpv /dev/sdb6 /dev/sdb6: recovering journal Error reading block 27262992 (Input/output error) while reading inode and block bitmaps.

/dev/sdb6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Error reading block 2097152 (Input/output error) while reading inode and block bitmaps.

/dev/sdb6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Error reading block 10485761 (Input/output error) while reading inode and block bitmaps.

/dev/sdb6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x60 e2fsck(+0x31ece)[0x558e5ee78ece] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f4854642520] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_super_and_bgd_loc2+0x43)[0x7f4854a12cf3] Error reading block 18874368 (Input/output error) while reading inode and block bitmaps. /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_flush2+0x226)[0x7f4854a159d6]

/dev/sdb6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_close2+0x11b)[0x7f4854a1db0b] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_close_free+0x1a)[0x7f4854a1db9a] Signal (11) SIGSEGV e2fsck(preenhalt+0x8d)[0x558e5ee6f84d] si_code=SEGV_MAPERR fault addr=0x3a e2fsck(+0x36fa9)[0x558e5ee7dfa9] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x40d0f)[0x7f4854a42d0f] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x3ca17)[0x7f4854a3ea17] e2fsck(+0x31ece)[0x558e5ee78ece] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f4854642520] e2fsck(preenhalt+0x7f)[0x558e5ee6f83f] e2fsck(+0x36fa9)[0x558e5ee7dfa9] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x40d0f)[0x7f4854a42d0f] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x3ca17)[0x7f4854a3ea17] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x3cce1)[0x7f4854a3ece1] /lib/x86_64-linux-gnu/libc.so.6(+0x94b43)[0x7f4854694b43] /lib/x86_64-linux-gnu/libc.so.6(+0x126a00)[0x7f4854726a00] star@stars:~$

What other to try?

yeah something screwed the pooch . prob debain on install, I'd say start over. get a live usb, wipe the drive, if UUID, create GPT table, if not MBR

I think, correct me if I am wrong but windows can make partitions and you can size them during that install, so I'd do that for the system and let windows size for the recovery, and that other directory it has to have, reboot make sure windows it working like it should and you have that blank space left over for linux.

use the EFI partition that windows created for linux as well.

then do the same with linux, create your partitions in linux live system with gparted, or during the install, make sure it formats all of the linux partitions before installing anything. then is should work.

I had issues with Debian a few days ago for a just one more linux distro on my laptop install so I shit canned it, and don't have it. they have not even updated their installer app. : puke : sad so sad. anyways good luck.

oh, no. i don`t want just to use this ssd. i even will put it in trash. I need my info from linux partition /dev/sda6
This is the whole problem

Sounds suspiciously like the device itself is less than healthy. This why backups were invented.

Prospects for recovery are diminished if there is no ability of reading the device consistently.

wow get that out of the trash, bad magic number is just a oops not necessarily a bad ssd, I had that on my nmv stick the other day, and I am still using it. to get back what you lost, might be lost forever like the other said back up stuff. but try doing what I suggested repair disk/partition reestablish partition table. for a mechanical drive maybe toss it but for a ssd, I don't think its trash yet. unless you have like ~100000000 hours on it.

1. Unplug all other drives from computer except an optical drive (CD|DVD|BD) if you cannot boot from USB.
2. Boot a live linux into console. Your questionable SSD will become /dev/sda.
3. smartctl -s on /dev/sda
4. smartctl -a /dev/sda
5. Post output of smartctl -a.

A check for bad blocks e.g. with badblocks -wsv is completely useless on SSDs.

This is normal, e2fsck only checks ext2/3/4 filesystems.
Did you try running fsck manually? i.e.
sudo fsck -v /dev/sdb6

It would help to know the status from the output of smartctl. If partitions are not always detected then the drive could be failing.

No! Lack of backup - or at least a snapshot - before fiddling with the system is the one and only problem.

Why not spend two or three minutes for a backup first? Then you can do whatever... in worst case scenario you can do a full bare metal restore in less than ten minutes... ready for another go.

Sorry, a vein just popped!

Carry on!

I ran into something like this in FreeBSD where on my mnv stick I'd moved a few partitions around getting rid of windows and putting everything in order then when I booted fbsd I got that magic number run fsck manually single user mode and I had no idea what happened, then I had to mount rw open fstab and looked at it then seen I needed to change the efi mount point because I moved it from p2 to p1 and it was trying to mount ext4 as msdos.

so what's in your fstab? is it trying to read the partition properly? its just another thing to check off to try and figure this out..

this sounds good. But what to do to access my files?
This is ssd is used less than 1000 hours.

kubuntu@kubuntu:~$
kubuntu@kubuntu:~$ sudo smartctl -s on /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-27-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

kubuntu@kubuntu:~$
kubuntu@kubuntu:~$
kubuntu@kubuntu:~$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-27-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: Patriot Burst Elite 240GB
Serial Number: PBEEDBB210120067272
LU WWN Device Id: 5 000000 000000006
Firmware Version: SN07985
User Capacity: 240,057,409,536 bytes [240 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Wed Jun 7 14:16:20 2023 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: (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: ( 33) 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: ( 2) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x0031) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 20
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 8
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 3465
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 173
167 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 0
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 2
169 Unknown_Attribute 0x0013 100 100 010 Pre-fail Always - 34361180207
171 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0
173 Unknown_Attribute 0x0012 200 200 000 Old_age Always - 21486108770
175 Program_Fail_Count_Chip 0x0022 100 100 010 Old_age Always - 0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033 099 099 000 Pre-fail Always - 802
187 Reported_Uncorrect 0x0032 099 000 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 105
194 Temperature_Celsius 0x0022 028 028 000 Old_age Always - 28 (Min/Max 22/47)
196 Reallocated_Event_Count 0x0012 100 100 000 Old_age Always - 0
206 Unknown_SSD_Attribute 0x0032 200 200 000 Old_age Always - 5
207 Unknown_SSD_Attribute 0x0032 200 200 000 Old_age Always - 172
208 Unknown_SSD_Attribute 0x0032 200 200 000 Old_age Always - 98
209 Unknown_SSD_Attribute 0x0032 200 200 000 Old_age Always - 1
210 Unknown_Attribute 0x0032 200 200 000 Old_age Always - 2203
211 Unknown_Attribute 0x0032 200 200 000 Old_age Always - 1673
231 Temperature_Celsius 0x0023 094 094 005 Pre-fail Always - 6
233 Media_Wearout_Indicator 0x0032 100 100 000 Old_age Always - 33488804096
234 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 52013749644
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 3210174450
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 1148784003
243 Unknown_Attribute 0x0032 050 050 000 Old_age Always - 24707449
245 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 29

SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 41 50 f8 af 95 40

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ec 00 01 00 00 00 00 80 00:02:42.000 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 80 00:02:37.700 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 80 00:02:37.700 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 80 00:02:37.700 SET FEATURES [Set transfer mode]
ef c3 01 00 00 00 a0 80 00:02:37.700 SET FEATURES [Sense Data Reporting]

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

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.

kubuntu@kubuntu:~$

Sorry to replay 1 by one, but i click on "multiquote" but nothing change...

star@stars:~$ sudo fsck -v /dev/sda6
[sudo] password for star:
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext2: Input/output error while trying to open /dev/sda6

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>

star@stars:~$

this is from installed linux on harddisk, but here ssd is sda6 and harddisk is sdb...

Attached Thumbnails

   

I try backup with dd but it give me a lot if i/o errors.


I don`t think that this is fstab problem. When i open ssd from livecd or from other installation of linux i can see /home folder. It is empty, after some minutes it show
my username and when i open it show folder inside (desktop, downloads, music and other) but all of them are empty. I leave it in this position for some hours but it is still empty.

This looks bad. This value should be 0.

This SSD has run over 3465 hours and not only "used less than 1000 hours".

for that magic number thing, it may have lost its partition info, I tired doing that recover thing, now I got a look it up... how to recover partition table. but that did not work for me. I ended up wiping that partition, but everything I had on it was something that I can replace. sometimes you just lose stuff and have to carry on.