Updating bad block inode

Posted by / 26-May-2020 08:33

Once programs are running that have files open for writing you can no longer remount the root file system as read only to run a file system check.

In the a former case, with a bit of luck, a data recovery specialist with an appropriately equipped lab can salvage its content. This is generally the best option, but usually only available on (non-ancient) hard disk and solid state drives. Further resources and instructions: This operation can take a lot of time, especially if the storage drive actually is damaged.

I can’t think of a way off hand to do it via SSH - the shutdown command on some Linux distributions has a -F option to force a file system scan on next boot but ours doesn’t appear to have that…

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Recently my Intel 1TB boot SSD started exhibiting some odd behavior. Thankfully almost everything was backed up, so this was mostly just an interesting experiment.

Frequently Ubuntu would crash unexpectedly whenever I would navigate into a folder which had large image files in it and Nautilus would attempt to display the thumbnails. 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 5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age Always - 1024 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 436 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 90 170 Unknown_Attribute 0x0033 098 098 010 Pre-fail Always - 0 171 Unknown_Attribute 0x0032 100 100 010 Old_age Always - 0 172 Unknown_Attribute 0x0032 100 100 010 Old_age Always - 0 174 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 59 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 090 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 299 190 Airflow_Temperature_Cel 0x0032 043 066 000 Old_age Always - 43 (Min/Max 28/66) 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 59 199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 3 225 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 206243 226 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 0 227 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 0 228 Power-off_Retract_Count 0x0032 100 100 000 Old_age Always - 0 232 Available_Reservd_Space 0x0033 023 023 010 Pre-fail Always - 0 233 Media_Wearout_Indicator 0x0032 098 098 000 Old_age Always - 0 241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 206243 242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 179722 249 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 3180 252 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 5SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining Life Time(hours) LBA_of_first_error1 Extended offline Completed without error 00% 436 -SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 70403103932424 70403103932424 Not_testing 2 70403103932424 70403103932424 Not_testing 3 70403103932424 70403103932424 Not_testing 4 70403103932424 70403103932424 Not_testing 5 70403103932424 70403103932424 Not_testing Selective self-test flags (0x4008): After scanning selected spans, do NOT read-scan remainder of disk. I still don’t quite know what corrupted the drive, but since I see these errors in the kernel log, it feels like a hardware issue.

updating bad block inode-65updating bad block inode-13updating bad block inode-26

Karnage’s suggestion would re-run the update but if you have file system corruption you need to solve that first, then try an update afterwards to see if it will finish re-installing what it couldn’t before. I only have the Apple Wireless Keyboard as external keyboard and a USB mouse. No other way to run the file system check than with a USB keyboard? When linux first starts booting the root file system is mounted read only, and a file system check (fsck) can be run at that time.

One thought on “updating bad block inode”