You are not logged in.

Pages: 1

#1 2020-12-22 22:08:50

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 19

[SOLVED] SSD failure on a fresh install

Hi,

I've just bought a used Thinkpad X260 with a new SSD (MC960 model reported by Speccy). I probably did some noob mistakes while preparing the disk for encryption (I suppose the 'securely erasing' part was... unnecessary), so I want to know if it still can be saved or I just need to get a new one. Here's the boot log (excuse the possible image to text mistakes):

x86/cpu: VMX (outside TXT) disabled by BIOS
ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6 frozen
ata2.00: failed command: READ FPDMA QUEUED
ata2.00: cmd 60/08:10:a8:1a:c8/00:00:6f:00:00/40 tag 2 ncq dma 4096 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRY }
ata2: COMRESET failed (errno=-16)
ata2: COMRESET failed (errno=-16)
ata2: COMRESET failed (errno=-16)
ata2: COMRESET failed (errno=-16)
ata2: reset failed, giving up
blk_update_request: I/O error, dev sda, sector 1875385000 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
Buffer I/O error on dev sda, logical block 1875385000, async page read
Buffer I/O error on dev sda, logical block 1875385001, async page read
Buffer I/O error on dev sda, logical block 1875385002, async page read
Buffer I/O error on dev sda, logical block 1875385003, async page read
Buffer I/O error on dev sda, logical block 1875385004, async page read
Buffer I/O error on dev sda, logical block 1875385005, async page read
Buffer I/O error on dev sda, logical block 1875385006, async page read
Buffer I/O error on dev sda, logical block 1875385007, async page read
running early hook [udev]
Starting version 246.6-1-arch
running hook [udev]
Triggering uevents...
sd 1:0:0:0: [sda] tag#5 access beyond end of device
blk update_request: I/O error, dev sda, sector 1050496 op 0x0:(READ) flags 0xB00700 phys_seg 1 prio class 0
sd 1:0:0:0: [sda] tag#6 beyond end of device
sd 1:0:0:0: [sda] tag#19 beyond end of device
sd 1:0:0:0: [sda] tag#8 beyond end of device
blk_update_request: I/O error, dev sda, sector 269483904 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
blk_update_request: I/O error, dev sda, sector 1050496 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
blk_update_request: I/O error, dev sda, sector 1875384192 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Buffer I/O error on dev sda1, logical block 1048448, async page read
sd 1:0:0:0: [sda] tag#20 access beyond end of device
sd 1:0:0:0: [sda] tag#7 access beyond end of device
blk_update_request: I/O error, dev sda, sector 269483904 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
blk_update request: I/O error, dev sda, sector 1050497 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Buffer I/O error on dev sda2, logical block 268433280, async page read
sd 1:0:0:0: [sda] tag#9 access beyond end of device
blk_update_request: I/O error, dev sda, sector 1050498 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
sd 1:0:0:0: [sdal tag#10 access beyond end of device
blk_update_request: I/O error, dev sda, sector 1875384192 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
sd 1:0:0:0: [sda] tag#11 access beyond end of device
blk_update_request: I/O error, dev sda, sector 1650499 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
sd 1:0:0:0: [sda] tag#12 access beyond end of device
sd 1:0:0:0: [sda] tag#13 access beyond end of device
sd 1:0:0:0: [sda] tag#14 access beyond end of device
sd 1:0:0:0: [sda] tag#1S access beyond end of device
sd 1:0:0:0: [sda] tag#21 access beyond end of device
sd 1:0:0:0: [sda] tag#22 access beyond end of device
sd 1:0:0:0: [sda] tag#23 access beyond end of device
sd 1:0:0:0: [sda] tag#31 access beyond end of device
sd 1:0:0:0: [sda] tag#1 access beyond end of device
sd 1:0:0:0: [sda] tag#2 access beyond end of device
sd 1:0:0:0: [sda] tag#3 access beyond end of device
sd 1:0:0:0: [sda] tag#4 access beyond end of device
sd 1:0:0:0: [sda] tag#5 access beyond end of device
Waiting 10 seconds for device sdev/disk/by-uuid/UUID
ERROR: device ’UUID=’ not found. Skipping fsck.
mounting ’UUID=’ on real root
mount: /mew_root: can’t find UUID=.
You are now being dropped into an emergency shell.
sh: can’t access tty: job control turned off
[rootfs ]# _

Sometimes the laptop eventually boots up, so I will get the smartctl output next time and update the post.

Edit: I post in the Arch forums section not only because I use Arch (obviously), but because I had HDD problems in the past on another laptop (check my post history) and it can possibly be my install-specific mistake I make every time I install Arch.

Last edited by dr3amyxen0 (2021-04-28 01:12:19)

Offline

#2 2020-12-22 22:22:44

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED] SSD failure on a fresh install

Nothing to do with your installation procedure, you can't break a drive by typing the wrong commands.

It was probably either broken when you got it or you have a loose connection. Try reseating it first and if that doesn't work then either get the seller to send you a new one or take the whole thing back for a refund.

If you want to know exactly what's wrong with it then perform a Smart test and post the results.

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2020-12-22 22:47:18

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 19

Re: [SOLVED] SSD failure on a fresh install

Smart test:

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.9-arch1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     MC960
Serial Number:    
Firmware Version: Q0324A
User Capacity:    960197124096 bytes [960 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
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.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Dec 23 01:36:46 2020 MSK
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:  (0x02)	Offline data collection activity
					was completed without error.
					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: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x71) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (   2) minutes.
Conveyance self-test routine
recommended polling time: 	 (   1) minutes.
SCT capabilities: 	       (0x0035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0000   100   100   000    Old_age   Offline      -       0
  5 Reallocated_Sector_Ct   0x0000   100   100   000    Old_age   Offline      -       0
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       34
 12 Power_Cycle_Count       0x0000   100   100   000    Old_age   Offline      -       42
160 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
161 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       691
163 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       77
164 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       8251
165 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       3
166 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
167 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       1
168 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       1000
169 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       100
175 Program_Fail_Count_Chip 0x0000   100   100   000    Old_age   Offline      -       0
176 Erase_Fail_Count_Chip   0x0000   100   100   000    Old_age   Offline      -       0
177 Wear_Leveling_Count     0x0000   100   100   050    Old_age   Offline      -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0000   100   100   000    Old_age   Offline      -       0
181 Program_Fail_Cnt_Total  0x0000   100   100   000    Old_age   Offline      -       0
182 Erase_Fail_Count_Total  0x0000   100   100   000    Old_age   Offline      -       0
192 Power-Off_Retract_Count 0x0000   100   100   000    Old_age   Offline      -       14
194 Temperature_Celsius     0x0000   100   100   000    Old_age   Offline      -       30
195 Hardware_ECC_Recovered  0x0000   100   100   000    Old_age   Offline      -       0
196 Reallocated_Event_Count 0x0000   100   100   016    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0000   100   100   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x0000   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0000   100   100   050    Old_age   Offline      -       0
232 Available_Reservd_Space 0x0000   100   100   000    Old_age   Offline      -       100
241 Total_LBAs_Written      0x0000   100   100   000    Old_age   Offline      -       33830
242 Total_LBAs_Read         0x0000   100   100   000    Old_age   Offline      -       2262
245 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       33004

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 1

ATA Error Count: 0
	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 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
  -- -- -- -- -- -- --
  00 ec 00 00 00 00 00  Device Fault

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 00 00 00 00 00      00:00:00.000  READ DMA

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        34         -

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
    7        0    65535  Read_scanning was completed without error
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.

Offline

#4 2020-12-22 22:56:45

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 19

Re: [SOLVED] SSD failure on a fresh install

Slithery wrote:

Nothing to do with your installation procedure, you can't break a drive by typing the wrong commands.

It was probably either broken when you got it or you have a loose connection. Try reseating it first and if that doesn't work then either get the seller to send you a new one or take the whole thing back for a refund.

If you want to know exactly what's wrong with it then perform a Smart test and post the results.

That's good to hear, I was sure I could partition it incorrectly or do something wrong with the EFI partition or whatever else. I usually just stick to the wiki for these questions, though I've done it a dozen times already.

I think the Smart test shows the SSD is ok? Which is strange. I will try to reseat it.

Offline

#5 2020-12-23 02:59:12

Alexithymia2010
Member
Registered: 2012-02-25
Posts: 5

Re: [SOLVED] SSD failure on a fresh install

dr3amyxen0 wrote:
Slithery wrote:

Nothing to do with your installation procedure, you can't break a drive by typing the wrong commands.

It was probably either broken when you got it or you have a loose connection. Try reseating it first and if that doesn't work then either get the seller to send you a new one or take the whole thing back for a refund.

If you want to know exactly what's wrong with it then perform a Smart test and post the results.

That's good to hear, I was sure I could partition it incorrectly or do something wrong with the EFI partition or whatever else. I usually just stick to the wiki for these questions, though I've done it a dozen times already.

I think the Smart test shows the SSD is ok? Which is strange. I will try to reseat it.

I think the secure erase part probably froze the SSD. Look here for more info https://www.thomas-krenn.com/en/wiki/Pe … cure_Erase

Offline

#6 2020-12-23 20:10:18

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 19

Re: [SOLVED] SSD failure on a fresh install

Alexithymia2010 wrote:

I think the secure erase part probably froze the SSD. Look here for more info https://www.thomas-krenn.com/en/wiki/Pe … cure_Erase

I remember it being frozen even before I started doing this whole secure erase part (and I felt I needed to do it because cryptsetup complained about filesystem existing) and I couldn't figure out how to un-freeze it from a liveUSB so I just kinda skipped a step. As I've said in the topic some noob mistakes had been made. Thanks, I will look into the link you've posted and into the related wiki articles.

Offline

#7 2020-12-28 13:44:04

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 19

Re: [SOLVED] SSD failure on a fresh install

So I reseated the drive and it kinda seemed to solve the issue, but then I started getting the same error messages again and the laptop won't boot.
I guess I'll have to change the SSD to another one, because the seller probably won't even listen to me once I mention Linux so refunding is not an option unfortunately.
If you have any other suggestions, please leave a comment and I will mark the thread solved when I get a new SSD after the holidays.

Offline

Pages: 1

Board footer

Powered by FluxBB