You are not logged in.
Hello!
So, this is kinda strange for me:
Half an hour ago, I tinkered a bit with a bash config and while inside vim it suddenly told me, that the filesystem was read only.
I didn't think too much and thought that maybe a previous update may have caused this, so I rebooted.
Much to my disdain I was dropped to a systemd rescue shell...
btrfs rescue super-recover -v /dev/sdd1 says the blocks are okay
btrfs check on the other hand says that the checksums don't match.
Running btrfs rescue chunk-recover right now.
What else can I do?
Did the hdd really die on me? How can I be sure?
edit: I aborted btrfs rescued chunk-recover and instead looked at the logs again. It turns out, the error message is a bit different than it used to be, but I got "recover log failed" (more or less), so I ran
btrfs rescue zero-log /dev/sdd1
and then mounted successfully with
mount -t btrfs -o recovery,ro /dev/sdd1 /home
next I'll try without ro, but first I'll make a backup of the few changes I did since the last one
Last edited by Humar (2019-08-07 07:01:42)
Offline
I was too eager, it's not solved... falls back to read only after boot
So how can I check that the HDD is really dead/has a hardware failure?
Offline
Run a long SMART check on the drive and post the results of
smartctl -a /dev/sdd
after the mentioned self check time has elapsed.
Online
Thanks, the long one will take 386 minutes to complete, so I'll do a short one first
result of the short and conveyance one:
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-5.2.5-arch1-1-ARCH] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68EUZN0
Serial Number: WD-WMC4N2945918
LU WWN Device Id: 5 0014ee 05928be18
Firmware Version: 82.00A82
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Aug 4 14:03:56 2019 CEST
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: (0x00) Offline data collection activity
was never started.
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: (38460) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 386) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 2
3 Spin_Up_Time 0x0027 178 171 021 Pre-fail Always - 6091
4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3275
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5674
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2933
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 112
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4227
194 Temperature_Celsius 0x0022 121 110 000 Old_age Always - 29
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Conveyance offline Completed without error 00% 5674 -
# 2 Short offline Completed without error 00% 5674 -
# 3 Extended offline Aborted by host 90% 5674 -
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
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.
I must say though, I am not sure how to read the results - I mean there is a column saying "value" and one labeled "worst" and then there is one with "raw_value".
Value is often worst and raw_value is way over the top. But then if I run
smartctl -H /dev/sdd
output is:
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-5.2.5-arch1-1-ARCH] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, [url=http://www.smartmontools.org]www.smartmontools.org[/url]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Last edited by Humar (2019-08-04 12:16:34)
Offline
By any chance, did you convert your btrfs from another filesystem type? If yes, you will need to delete the backup that was made of your original filesystem (you should save it somewhere else, first), then rebalance the btrfs.
Offline
The RAW_VALUE is what's important, aside from 2 read_errors the drive looks fine, though you might want to post an updated log after the long test has run.
Online
Hey, no I did not convert it, it was btrfs since 2015. I formatted it and to my disdain fucked up my backup due to a very dumb error on my side (remember kids, mount backups as read only, especially if you do rsync --delete and have it mounted inside your home)
So, yes, I screwed this up big time and now my usb stick with the second backup is dying too... doesn't work on any of my laptops anymore, so yeah.
Luckily I could save some data, but I lost quite some projects.
On the bright side: I'll now quadruple my efforts to have sustainable backups, so I hope I learned my lesson.
Thanks everyone, it's "SOLVED"
Offline
Ok, please mark the thread as Solved.
Offline