You are not logged in.
- Topics: Active | Unanswered
#1 2020-08-02 05:38:52
- lakso
- Member
- Registered: 2020-08-02
- Posts: 32
Can I recover the system or is my SSD broken?
I've recently installed Arch linux and KDE plasma on my brand new 250GB Kingston NVMe SSD, it run perfectly for a day but today out of nowhere it suddenly froze. The audio of the video I was watching kept going but the image was completely frozen, not only of the video, but the entire OS. I tried doing Ctrl+Alt+F2 to see if I could do something from there and it must have registered it because the audio stopped, but the image stayed froze. After a while I tried shutting down the computer by pressing the off button but nothing seemed to happen, so I forced the shutdown. When it rebooted the computer took a long time thinking and then booted from my Ubuntu installation on the HDD on my PC.
I tried to pick the Arch partition to boot from BIOS but the option was gone.
When I try to read the files inside the SSD from Ubuntu I get an error message saying:
Error mounting /dev/nvme0n1p3 at /media/lakso/c4b78565-abac-4b0d-851f-62fc4d39735e: can't read superblock on /dev/nvme0n1p3I thought maybe I could get into the system from the Arch iso that I used to install the OS in the first place, but when I try to mount the drive it returns:
blk_update_request: critical medium error, dev nvme0n1, sector 5220392 op 0x1:(WRITE) flags 0x800 phys_seg 10 prio class 0
Buffer I/O error on dev nvme0n1p3, logical block 5, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 6, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 7, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 8, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 9, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 10, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 11, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 12, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 13, lost async page write
Buffer I/O error on dev nvme0n1p3, logical block 14, lost async page write
blk_update_request: critical medium error, dev nvme0n1, sector 5220352 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 5220504 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 5220552 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 5228792 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 5228848 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 5228864 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 5228896 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 9414680 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0
blk_update_request: critical medium error, dev nvme0n1, sector 9414712 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
EXT4-fs (nvme0n1p3): error loading journal
mount: /mnt can't read superblock on /dev/nvme0n1p3when i run
smartctl -a /dev/nvme0n1it prints
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-7634-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: KINGSTON SA2000M8250G
Serial Number: 50026B76838AAD8A
Firmware Version: S5Z42105
PCI Vendor/Subsystem ID: 0x2646
IEEE OUI Identifier: 0x0026b7
Controller ID: 1
Number of Namespaces: 1
Namespace 1 Size/Capacity: 250.059.350.016 [250 GB]
Namespace 1 Utilization: 30.429.884.416 [30,4 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 0026b7 6838aad8a5
Local Time is: Sun Aug 2 02:14:00 2020 -03
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 75 Celsius
Critical Comp. Temp. Threshold: 80 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 9.00W - - 0 0 0 0 0 0
1 + 4.60W - - 1 1 1 1 0 0
2 + 3.80W - - 2 2 2 2 0 0
3 - 0.0450W - - 3 3 3 3 2000 2000
4 - 0.0040W - - 4 4 4 4 15000 15000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- media has been placed in read only mode
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x08
Temperature: 28 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 22.889 [11,7 GB]
Data Units Written: 106.644 [54,6 GB]
Host Read Commands: 721.450
Host Write Commands: 1.622.958
Controller Busy Time: 27
Power Cycles: 23
Power On Hours: 9
Unsafe Shutdowns: 9
Media and Data Integrity Errors: 47.646
Error Information Log Entries: 9.264
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Error Information (NVMe Log 0x01, max 256 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 9264 4 0x0284 0x0280 - 412371040 1 -
1 9263 4 0x0284 0x0280 - 412367176 1 -
2 9262 4 0x0284 0x0280 - 412139672 1 -
3 9261 4 0x0284 0x0280 - 412138656 1 -
4 9260 4 0x0284 0x0280 - 412138624 1 -
5 9259 4 0x0284 0x0280 - 412138368 1 -
6 9258 4 0x0284 0x0280 - 412138384 1 -
7 9257 4 0x0284 0x0280 - 412138296 1 -
8 9256 4 0x0284 0x0280 - 412138280 1 -
9 9255 4 0x0284 0x0280 - 412137456 1 -
10 9254 4 0x0284 0x0280 - 412371040 1 -
11 9253 4 0x0284 0x0280 - 412367176 1 -
12 9252 4 0x0284 0x0280 - 412139672 1 -
13 9251 4 0x0284 0x0280 - 412138656 1 -
14 9250 4 0x0284 0x0280 - 412138624 1 -
15 9249 4 0x0284 0x0280 - 412138384 1 -
... (240 entries not shown)Is this an issue with my Arch installation? can I recover it? Or is it an issue with my drive? In that case, what caused it? It's new.
Offline
#2 2020-08-02 10:03:28
- ondoho
- Member
- Registered: 2013-04-30
- Posts: 692
- Website
Re: Can I recover the system or is my SSD broken?
How is the SSD connected to the computer?
Did you check the connections?
Last edited by ondoho (2020-08-02 10:03:56)
Offline
#3 2020-08-02 10:31:30
- frostschutz
- Member
- Registered: 2013-11-15
- Posts: 1,417
Re: Can I recover the system or is my SSD broken?
=== START OF SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! - media has been placed in read only mode SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x08 Media and Data Integrity Errors: 47.646 Error Information Log Entries: 9.264 Error Information (NVMe Log 0x01, max 256 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 9264 4 0x0284 0x0280 - 412371040 1 - 1 9263 4 0x0284 0x0280 - 412367176 1 - 2 9262 4 0x0284 0x0280 - 412139672 1 -
Well, that doesn't look good at all.
Critical Warning 0x08 just means what it says above, media placed in read only mode.
There is not much you can do here except perhaps see if it persists after cold reboot.
Sometimes too aggressive power saving can interfere with SSDs but somehow I doubt that is your problem...
Offline
#4 2020-08-02 17:00:03
- lakso
- Member
- Registered: 2020-08-02
- Posts: 32
Re: Can I recover the system or is my SSD broken?
lakso wrote:=== START OF SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! - media has been placed in read only mode SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x08 Media and Data Integrity Errors: 47.646 Error Information Log Entries: 9.264 Error Information (NVMe Log 0x01, max 256 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 9264 4 0x0284 0x0280 - 412371040 1 - 1 9263 4 0x0284 0x0280 - 412367176 1 - 2 9262 4 0x0284 0x0280 - 412139672 1 -Well, that doesn't look good at all.
Critical Warning 0x08 just means what it says above, media placed in read only mode.
There is not much you can do here except perhaps see if it persists after cold reboot.
Sometimes too aggressive power saving can interfere with SSDs but somehow I doubt that is your problem...
What could have caused this problem? I can still return the disk and get a new one, I don't mind reinstalling that much but I fear it would happen again. I reconnected it just in case, but everything seems fine.
Offline
#5 2020-08-02 19:04:08
- Stefan Husmann
- Member
- From: Germany
- Registered: 2007-08-07
- Posts: 1,391
Re: Can I recover the system or is my SSD broken?
Maybe coincidence, but read this.
Offline
#6 2020-08-03 07:55:58
- ondoho
- Member
- Registered: 2013-04-30
- Posts: 692
- Website
Re: Can I recover the system or is my SSD broken?
^ Not so sure, the symptoms seem different here (simply not recognized there, recognized but errors here).
I've recently installed Arch linux and KDE plasma on my brand new 250GB Kingston NVMe SSD
...
When it rebooted the computer took a long time thinking and then booted from my Ubuntu installation on the HDD on my PC.
Something's off about this description.
How exactly does this setup work?
And when I asked "how is it connected" I also meant: internally (properly) or USB enclosure?
More general info/troubleshooting please.
Offline
#7 2021-01-20 16:46:09
- JPenuchot
- Member
- Registered: 2020-02-10
- Posts: 7
Re: Can I recover the system or is my SSD broken?
Hi,
It seems to be a problem specific to the Kingston A2000. I have the same one except it's 1TB and I get the exact same errors, at mounting and when getting SMART reports.
Regards,
Jules
Offline