Mailinglist Archive: opensuse (626 mails)

< Previous Next >
Re: [opensuse] Login weirdness
On 04/11/2018 17.37, Michael Fischer wrote:
On Sat, Nov 03, Carlos E. R. wrote:

...


I repeated the method you describe above (amusingly, also ended up being
/dev/sda3)
...which unfortunately turned out to be /home... also made a notes-to-self
of the above routine (h/t).

Yes, /home is unfortunate.


In the meantime, I decided (perhaps wisely, given what I just found ^^^ here),
to purchase a replacement (EVO 860 500G) and just install that as a new /home.

Yes, that is sensible


Interestingly, I've not hit any READ|WRITE errors on any files in /home in
daily usage, so ... who knows which files may be affected.

Maybe none.

Perhaps I can keep the old disk in there as some `data` partition(s), and it
might make the restore of /home easier (though I run double backup external
drives... *shrug*)

see later.


In the interest of completeness: `smartctl --test=long` results below.

(Thanks again for all the tips)


smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.14.6-1.g45f120a-default] (SUSE
RPM)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST1000DM003-1SB102
Serial Number: Z9ACC0MX
LU WWN Device Id: 5 000c50 0a28684ad
Firmware Version: CC43
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Nov 4 11:20:46 2018 EST
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
...

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
...
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 16
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline
- 16
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
- 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline
- 7780h+54m+58.740s
...

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Extended captive Interrupted (host reset) 90% 7815 -
# 2 Extended offline Completed: read failure 50% 7808
1001593016
# 3 Extended offline Completed: read failure 50% 7807
1001593016
# 4 Extended offline Completed: read failure 50% 7804
1001593016
# 5 Extended offline Aborted by host 90% 7803 -
# 6 Short captive Interrupted (host reset) 60% 7752 -
# 7 Short offline Completed without error 00% 7752 -
# 8 Extended offline Completed: read failure 50% 7136
1001593016
# 9 Extended offline Completed: read failure 50% 6296
1001593016
#10 Extended offline Completed: read failure 50% 5624
1001593016
#11 Extended offline Completed: read failure 50% 4784
1001593016
#12 Extended offline Completed: read failure 50% 4112
1001593016
#13 Extended offline Completed: read failure 50% 3440
1001593016
#14 Extended offline Completed: read failure 50% 2600
1001593016
#15 Extended offline Completed: read failure 50% 1929
1001593016
#16 Extended offline Completed: read failure 50% 1257
1021004240
#17 Extended offline Completed: read failure 50% 585
1001593008
#18 Short offline Completed without error 00% 0 -


Well, you see there is always an error at the same LBA and that the
testing stops, never completes.

I would backup the files in that partition, then write over that LBA
sector as the howto I linked I think explains. Then retest.

If another sector then appears, you can repeat the procedure, or
overwrite the entire partition.

--
Cheers / Saludos,

Carlos E. R.

(from openSUSE 15.0 (Legolas))

< Previous Next >