A month ago, during an update of Tumbleweed, the system crashed and I was never able to recover the data. (Dell laptop with a USB C SSD drive). Thus, I decided that I will be running leap going forward.
I am unable to install leap on this SSD drive. (windows can format and read/write on the drive with no problem.
The error occurs when the partitions are created. i use the default partition suggested by the installer.
Exemples of the errors I have:
Thanks for your help.
During the installation, did you simply accept the suggested partition scheme or, did you enter the custom/expert section and,
Have you considered the possibility that the TW crash resulted from SSD hardware failure? Is your SSD under warranty? Windows may not be trying to use some bad spot on the device that the YaST2 installer/partitioner is.
That is what I thought.
Here is a picture of the 4 partitions that openSUSE created during the failed installation. I use the recommended partitioning.
Do you know a software to check the hardware more thoroughly?
More thoroughly than what? I normally check with smartctl -t long devname, later smartctl -x devname.
Yes I do!
Healthy drives will work flawlessly through months of testing:
erlangen:~ # btrbk -c /etc/btrbk/btrbk-home.conf stats
SOURCE_SUBVOLUME SNAPSHOT_SUBVOLUME TARGET_SUBVOLUME SNAPSHOTS BACKUPS
/home /Btrbk/btrbk_snapshots/home.* /Backup/btrbk_snapshots/home.* 82 311
/ /Btrbk/btrbk_snapshots/ROOT.* /Backup/btrbk_snapshots/ROOT.* 82 311
Total:
164 snapshots
622 backups (164 correlated)
erlangen:~ #
(Dell laptop with a USB C SSD drive)
Drive 1 seems to be the removable USB drive where you’re trying to install an openSUSE system.
You could try to reformat that drive with Windows – write zeros to the entire drive – <https://www.howtogeek.com/751529/how-to-wipe-a-drive-on-windows-10-or-windows-11/>.
OK – you’ll end up with a windows partition on the drive but, when you install an openSUSE system on that drive, you can then choose to delete everything that’s on the thing and then, be left with only the UEFI and Btrfs partitions on the thing which the openSUSE system needs to boot.
I have plugged the external SSD to a different machine and here is the output:
sudo smartctl --scan
[sudo] password for root:
/dev/sda -d scsi # /dev/sda, SCSI device
/dev/sdb -d sntrealtek # /dev/sdb [USB NVMe Realtek], NVMe device
sudo smartctl --health /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.4.11-1-default] (SUSE RPM)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
sudo smartctl -t long /dev/sdb
[sudo] password for root:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.4.11-1-default] (SUSE RPM)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
Warning: NVMe Get Log truncated to 0x200 bytes, 0x034 bytes zero filled
NVMe Self-test cmd with type=0x2, nsid=0xffffffff failed: NVMe admin command 0x14 not supported
sudo smartctl -x /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.4.11-1-default] (SUSE RPM)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 980 500GB
Serial Number: S64ENS0W108324V
Firmware Version: 3B4QFXO7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 500,107,862,016 [500 GB]
Unallocated NVM Capacity: 0
Controller ID: 5
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 500,107,862,016 [500 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 d1314072b7
Local Time is: Sun Oct 1 10:00:21 2023 +07
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055): Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f): S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 82 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Namespace 1 Features (0x10): NP_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 5.24W - - 0 0 0 0 0 0
1 + 4.49W - - 1 1 1 1 0 0
2 + 2.19W - - 2 2 2 2 0 500
3 - 0.0500W - - 3 3 3 3 210 1200
4 - 0.0050W - - 4 4 4 4 1000 9000
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: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 31 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 58,942 [30.1 GB]
Data Units Written: 3,121,704 [1.59 TB]
Host Read Commands: 1,967,019
Host Write Commands: 98,372,624
Controller Busy Time: 27
Power Cycles: 148
Power On Hours: 15
Unsafe Shutdowns: 33
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 31 Celsius
Temperature Sensor 2: 33 Celsius
Warning: NVMe Get Log truncated to 0x200 bytes, 0x200 bytes zero filled
Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged
Warning: NVMe Get Log truncated to 0x200 bytes, 0x034 bytes zero filled
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged
Is this a SSD failure?
Thanks.
I am following your advice now.
sudo fdisk --list
[sudo] password for root:
Disk /dev/sda: 64 GiB, 68719476736 bytes, 134217728 sectors
Disk model: OpenSUSE Linux-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BFA8925C-CB70-4528-8721-9B57B887C4BC
Device Start End Sectors Size Type
/dev/sda1 2048 18431 16384 8M BIOS boot
/dev/sda2 18432 130021375 130002944 62G Linux filesystem
/dev/sda3 130021376 134217694 4196319 2G Linux swap
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model:
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 2048 bytes
I/O size (minimum/optimal): 2048 bytes / 2048 bytes
Disklabel type: dos
Disk identifier: 0xae918fba
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 976769023 976766976 465.8G 7 HPFS/NTFS/exFAT
donald@localhost:~> sudo shred -n 1 -z -v /dev/sdb
shred: /dev/sdb: pass 1/2 (random)...
shred: /dev/sdb: pass 1/2 (random)...308MiB/466GiB 0%
If its a SanDisk then, possibly …
I see that, you have another Linux system available –
# dd if=/dev/urandom of=/dev/sd? iflag=fullblock bs=1G count=2 status=progress
The Super-Block of the SDD is erased – you can increase the value of the “count” parameter if you want to be absolutely certain.
The external SSD will then be almost “factory fresh” and any subsequent installations should work around any bad blocks on the device.
Thanks for your help. It is a HW failure.