You are not logged in.
- Topics: Active | Unanswered
#1 2024-09-13 14:34:46
- Neroman
- Member
- Registered: 2024-09-13
- Posts: 21
[SOLVED] Can't detect/repair SSD after playing with fstab
Hello, got problem with second NVME SSD.
Problem Background:
I wanted to make it automount in home directory via fstab.
1. Formatted it via gparted to ext4
2. Added it to fstab via UUID
3. Saved and Rebooted
4. At first it was mounting but I couldn't use it
5. Decided to use disk path (/dev/nvme1n1)
6. After reboot got some boot processes related to LVM2
7. Skipped it with Ctrl+Alt+Delete, restored fstab
8. Noticed that NVME disappeared
Can't see disk with fdisk -l
Can't see disk with parted/gparted
Can't see disk with lsblk
But i can see it in lshw. I tried to make researches and I think i corrupted it. Is there any chances to repair it?
The most similar case was in this thread.
dmesg related to nvme:
[ 3.280033] nvme 0000:06:00.0: platform quirk: setting simple suspend
[ 3.280036] nvme 0000:07:00.0: platform quirk: setting simple suspend
[ 3.280112] nvme nvme0: pci function 0000:06:00.0
[ 3.280112] nvme nvme1: pci function 0000:07:00.0
[ 3.282633] nvme nvme1: bad crto:0 cap:8200030ff0103ff
[ 3.282905] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[ 3.285010] nvme nvme0: missing or invalid SUBNQN field.
[ 3.291982] nvme nvme1: allocated 40 MiB host memory buffer.
[ 3.295645] nvme nvme0: allocated 64 MiB host memory buffer.
[ 3.299374] nvme nvme1: 8/0/0 default/read/poll queues
[ 3.310430] nvme nvme0: 8/0/0 default/read/poll queues
[ 3.314826] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 3.330218] nvme1n1: p1 p2 p3
[ 3.461139] nvme0n1: Read(0x2) @ LBA 0, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 3.461209] critical medium error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.461248] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.521274] usb 1-6: new full-speed USB device number 2 using xhci_hcd
[ 3.604976] nvme0n1: Read(0x2) @ LBA 0, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 3.605044] critical medium error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.605093] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.605180] ldm_validate_partition_table(): Disk read failed.
[ 3.663432] usb 1-6: New USB device found, idVendor=1532, idProduct=006e, bcdDevice= 2.00
[ 3.663446] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.663451] usb 1-6: Product: Razer DeathAdder Essential
[ 3.663455] usb 1-6: Manufacturer: Razer
[ 3.670600] usbcore: registered new interface driver usbhid
[ 3.670602] usbhid: USB HID core driver
[ 3.748410] nvme0n1: Read(0x2) @ LBA 0, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 3.748457] critical medium error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.748481] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.784725] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 3.805990] usb 2-1: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[ 3.806003] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3.806009] usb 2-1: Product: DataTraveler 3.0
[ 3.806013] usb 2-1: Manufacturer: Kingston
[ 3.806017] usb 2-1: SerialNumber: C2C5F260C4D11760E14D0C1D
[ 3.812458] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3.812847] scsi host5: usb-storage 2-1:1.0
[ 3.812941] usbcore: registered new interface driver usb-storage
[ 3.893486] nvme0n1: Read(0x2) @ LBA 0, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 3.893541] critical medium error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.893569] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.924622] usb 1-8: new high-speed USB device number 3 using xhci_hcd
[ 4.037269] nvme0n1: Read(0x2) @ LBA 0, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 4.037346] critical medium error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 4.037389] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 4.037478] nvme0n1: unable to read partition table
[ 4.043578] nvme0n1: Read(0x2) @ LBA 2000409088, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 4.043595] critical medium error, dev nvme0n1, sector 2000409088 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 4.045334] input: Razer Razer DeathAdder Essential as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/0003:1532:006E.0001/input/input9
[ 4.045385] hid-generic 0003:1532:006E.0001: input,hidraw0: USB HID v1.11 Mouse [Razer Razer DeathAdder Essential] on usb-0000:00:14.0-6/input0
[ 4.045559] input: Razer Razer DeathAdder Essential Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.1/0003:1532:006E.0002/input/input10
[ 4.045776] nvme0n1: Read(0x2) @ LBA 2000409088, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE
[ 4.045789] critical medium error, dev nvme0n1, sector 2000409088 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 4.045799] Buffer I/O error on dev nvme0n1, logical block 250051136, async page read
[ 4.047295] usbcore: registered new interface driver uas
[ 4.058261] raid6: skipped pq benchmark and selected avx2x4
[ 4.058264] raid6: using avx2x2 recovery algorithm
[ 4.060678] xor: automatically using best checksumming function avx
[ 4.084616] usb 1-8: New USB device found, idVendor=04f2, idProduct=b685, bcdDevice=54.04
[ 4.084620] usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 4.084621] usb 1-8: Product: Chicony USB2.0 Camera
[ 4.084622] usb 1-8: Manufacturer: Sonix Technology Co., Ltd.
[ 4.101295] input: Razer Razer DeathAdder Essential as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.1/0003:1532:006E.0002/input/input11lshw:
*-pci:1
description: PCI bridge
product: Comet Lake PCI Express Root Port #21
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:121 memory:c5400000-c54fffff
*-nvme
description: NVMe device
product: SSDPR-PX500-01T-80
vendor: Silicon Motion, Inc.
physical id: 0
bus info: pci@0000:06:00.0
logical name: /dev/nvme0
version: S0614B0
serial: GW2048931
width: 64 bits
clock: 33MHz
capabilities: nvme pm msi pciexpress msix nvm_express bus_master cap_list
configuration: driver=nvme latency=0 nqn=nqn.2014.08.org.nvmexpress:126f126fGW2048931 state=live
resources: irq:16 memory:c5400000-c5403fff
*-namespace:0
description: NVMe disk
physical id: 0
logical name: hwmon4
*-namespace:1
description: NVMe disk
physical id: 2
logical name: /dev/ng0n1
*-namespace:2
description: NVMe disk
physical id: 1
bus info: nvme@0:1
logical name: /dev/nvme0n1
size: 953GiB (1024GB)
configuration: logicalsectorsize=512 sectorsize=512 wwid=nvme.126f-475732303438393331-53534450522d50583530302d3031542d3830-00000001
*-pci:2
description: PCI bridge
product: Comet Lake PCI Express Root Port #9
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:122 memory:c5300000-c53fffff
*-nvme
description: NVMe device
product: HP SSD FX900 Plus 512GB
vendor: Biwin Storage Technology Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: /dev/nvme1
version: SN13683
serial: HBSE34030100842
width: 64 bits
clock: 33MHz
capabilities: nvme pm msi pciexpress msix nvm_express bus_master cap_list
configuration: driver=nvme latency=0 nqn=nqn.2014-08.com.maxio:nvme:1602:M.2:HBSE34030100842 state=live
resources: irq:16 memory:c5300000-c5303fff
*-namespace:0
description: NVMe disk
physical id: 0
logical name: hwmon3
*-namespace:1
description: NVMe disk
physical id: 2
logical name: /dev/ng1n1
*-namespace:2
description: NVMe disk
physical id: 1
bus info: nvme@1:1
logical name: /dev/nvme1n1
size: 476GiB (512GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: guid=c7d9fb55-d031-4e0d-9ff8-ec07c150f243 logicalsectorsize=512 sectorsize=512 wwid=eui.00000000000000000000004030100842
*-volume:0
description: Windows FAT volume
vendor: mkfs.fat
physical id: 1
bus info: nvme@1:1,1
logical name: /dev/nvme1n1p1
logical name: /boot
version: FAT32
serial: 2892-683c
size: 1022MiB
capacity: 1023MiB
capabilities: boot fat initialized
configuration: FATs=2 filesystem=fat mount.fstype=vfat mount.options=rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro state=mounted
*-volume:1
description: Linux swap volume
vendor: Linux
physical id: 2
bus info: nvme@1:1,2
logical name: /dev/nvme1n1p2
version: 1
serial: a6f5cd8f-b08f-4b23-954e-67fd3cda8090
size: 23GiB
capacity: 23GiB
capabilities: nofs swap initialized
configuration: filesystem=swap label=swap pagesize=4095
*-volume:2
description: EFI partition
physical id: 3
bus info: nvme@1:1,3
logical name: /dev/nvme1n1p3
logical name: /
serial: 6bfd8006-7fa0-45b3-9cc9-4d62fe1ead77
capacity: 4 51GiB
configuration: mount.fstype=btrfs mount.options=rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/ state=mountedUpdate#1
If i couldn't reach it in any linux mediums, I tried to format SSD in windows installer (got an error) and it appeared in 'lsblk'. Still can't see it via fdisk/parted.
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 28.9G 0 disk
├─sda1 8:1 1 28.8G 0 part
└─sda2 8:2 1 32M 0 part
[ins]nvme0n1 259:0 0 953.9G 0 disk [/ins]
nvme1n1 259:1 0 476.9G 0 disk
├─nvme1n1p1 259:2 0 1G 0 part /boot
├─nvme1n1p2 259:3 0 24G 0 part [SWAP]
└─nvme1n1p3 259:4 0 451.9G 0 part /
[root@laptop roman]# sudo fdisk -lfdisk -l
[root@laptop roman]# sudo fdisk -l
Disk /dev/nvme1n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: HP SSD FX900 Plus 512GB
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: gpt
Disk identifier: C7D9FB55-D031-4E0D-9FF8-EC07C150F243
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 2099199 2097152 1G EFI System
/dev/nvme1n1p2 2099200 52430847 50331648 24G Linux swap
/dev/nvme1n1p3 52430848 1000214527 947783680 451.9G Linux filesystem
Disk /dev/sda: 28.87 GiB, 30995907072 bytes, 60538881 sectors
Disk model: DataTraveler 3.0
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: 0xee6b1bd0
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 60473343 60471296 28.8G 7 HPFS/NTFS/exFAT
/dev/sda2 60473344 60538879 65536 32M ef EFI (FAT-12/16/32)Last edited by Neroman (2024-09-17 12:29:47)
Offline
#2 2024-09-13 16:04:19
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 23,606
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
Please use code instead of quote for command outputs and edit your post in this regard.
That doesn't look good, but I doubt that the preface you did had anything to do with it. (in case it had, you did remember that you need to chown the drive to your user after mounting to write to it without root?) Can you run
smartctl -a /dev/nvme0n1and post the output?
Last edited by V1del (2024-09-13 16:22:34)
Offline
#3 2024-09-13 16:11:05
- Neroman
- Member
- Registered: 2024-09-13
- Posts: 21
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
V1del wrote:
Please use code instead of quote for command outputs and edit your post in this regard.
That doesn't look good, but I doubt that the preface you did had anything to do with it. (in case it had, you did remember that you need to chown the drive to your user after mounting to write to it without root?) Can you run
smartctl -a /dev/nvme0/n1and post the output?
My bad, edited outputs.
smartctl -a /dev/nvme0/n1returns failed
[root@laptop roman]# smartctl -a /dev/nvme0/n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.9-arch1-2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
Smartctl open device: /dev/nvme0/n1 failed: No such deviceBut it returns some output for whole disk: smartctl -a /dev/nvme0. I think it's gone 
[root@laptop roman]# smartctl -a /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.9-arch1-2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: SSDPR-PX500-01T-80
Serial Number: GW2048931
Firmware Version: S0614B0
PCI Vendor/Subsystem ID: 0x126f
IEEE OUI Identifier: 0x000000
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1,024,209,543,168 [1.02 TB]
Namespace 1 Formatted LBA Size: 512
Local Time is: Fri Sep 13 19:07:18 2024 EEST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0007): Security Format Frmw_DL
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x03): S/H_per_NS Cmd_Eff_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 90 Celsius
Namespace 1 Features (0x04): Dea/Unw_Error
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
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: 46 Celsius
Available Spare: 96%
Available Spare Threshold: 10%
Percentage Used: 1%
Data Units Read: 96,194,610 [49.2 TB]
Data Units Written: 63,128,492 [32.3 TB]
Host Read Commands: 1,353,869,383
Host Write Commands: 641,530,847
Controller Busy Time: 46,583
Power Cycles: 2,995
Power On Hours: 10,008
Unsafe Shutdowns: 238
Media and Data Integrity Errors: 720
Error Information Log Entries: 721
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 721 6 0x53c1 0x4502 - 2000409088 1 - Unrecovered Read Error
1 720 6 0x43c1 0x4502 - 2000409088 1 - Unrecovered Read Error
2 719 6 0x33c1 0x4502 - 2000409088 1 - Unrecovered Read Error
3 718 6 0x23c1 0x4502 - 2000409088 1 - Unrecovered Read Error
4 717 6 0x13c1 0x4502 - 2000409088 1 - Unrecovered Read Error
5 716 6 0x03c1 0x4502 - 2000409088 1 - Unrecovered Read Error
6 715 6 0x03c0 0x4502 - 2000409088 1 - Unrecovered Read Error
7 714 7 0x5380 0x4502 - 2000409088 1 - Unrecovered Read Error
8 713 7 0x4380 0x4502 - 2000409088 1 - Unrecovered Read Error
9 712 7 0x3380 0x4502 - 2000409088 1 - Unrecovered Read Error
10 711 7 0x2380 0x4502 - 2000409088 1 - Unrecovered Read Error
11 710 7 0x1380 0x4502 - 2000409088 1 - Unrecovered Read Error
12 709 7 0x0380 0x4502 - 2000409088 1 - Unrecovered Read Error
13 708 2 0x0340 0x4502 - 2000409088 1 - Unrecovered Read Error
14 707 4 0x5342 0x4502 - 0 1 - Unrecovered Read Error
15 706 4 0x4342 0x4502 - 0 1 - Unrecovered Read Error
... (48 entries not read)
Self-tests not supportedOffline
#4 2024-09-13 16:15:09
- Neroman
- Member
- Registered: 2024-09-13
- Posts: 21
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
V1del wrote:
Please use code instead of quote for command outputs and edit your post in this regard.
That doesn't look good, but I doubt that the preface you did had anything to do with it. (in case it had, you did remember that you need to chown the drive to your user after mounting to write to it without root?) Can you run
smartctl -a /dev/nvme0/n1and post the output?
I didn't chown the drive
Offline
#5 2024-09-13 16:25:08
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 23,606
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
Whoops that slash isn't supposed to be there -- /dev/nvme0n1 of course. But yeah this doesn't look good. That was likely already on it's way out
Offline
#6 2024-09-13 18:02:08
- Neroman
- Member
- Registered: 2024-09-13
- Posts: 21
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
V1del wrote:
Whoops that slash isn't supposed to be there -- /dev/nvme0n1 of course. But yeah this doesn't look good. That was likely already on it's way out
So that happened because of not gived chown disk to my user to write? (option field in fstab?)
Thanks for trying to help
Last edited by Neroman (2024-09-13 18:02:28)
Offline
#7 2024-09-13 18:47:34
- xerxes_
- Member
- Registered: 2018-04-29
- Posts: 823
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
You may try to diagnose your drive by this commands:
sudo smartctl -x /dev/nvme0
sudo nvme list
sudo nvme list-ctrl /dev/nvme0
sudo nvme list-subsys
sudo nvme smart-log /dev/nvme0
sudo nvme error-log /dev/nvme0
sudo nvme self-test-log /dev/nvme0
sudo nvme endurance-log /dev/nvme0
sudo nvme get-feature /dev/nvme0 -f 3
sudo nvme show-regs /dev/nvme0 -HOffline
#8 2024-09-17 11:42:46
- Neroman
- Member
- Registered: 2024-09-13
- Posts: 21
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
xerxes_ wrote:
You may try to diagnose your drive by this commands:
sudo smartctl -x /dev/nvme0 sudo nvme list sudo nvme list-ctrl /dev/nvme0 sudo nvme list-subsys sudo nvme smart-log /dev/nvme0 sudo nvme error-log /dev/nvme0 sudo nvme self-test-log /dev/nvme0 sudo nvme endurance-log /dev/nvme0 sudo nvme get-feature /dev/nvme0 -f 3 sudo nvme show-regs /dev/nvme0 -H
Nah, it's dead. Thx for trying to help
Offline
#9 2024-09-18 20:26:53
- xerxes_
- Member
- Registered: 2018-04-29
- Posts: 823
Re: [SOLVED] Can't detect/repair SSD after playing with fstab
Do you see drive in bios/uefi?
If you don't have precious data on it you can hardware format it by command: 'nvme format -s1 /dev/nvme0n1' (it is format/secure erase).
Change from 4096-byte sector size to 512-byte (or vice versa) like here: https://halestrom.net/darksleep/blog/054_nvme/ ?
Last edited by xerxes_ (2024-09-18 20:28:01)
Offline