XK0-005 · Question #861
An administrator is reviewing the boot logs on a system that is having intermittent issues when trying to access certain directories and files. The following errors appear in dmesg: mathematica…
The correct answer is D. Boot a recovery disk, run fsck on unmounted drive. I/O errors on a disk partition typically indicate filesystem corruption or underlying physical disk issues, which require running a filesystem check on an unmounted partition from a recovery environment.
Question
An administrator is reviewing the boot logs on a system that is having intermittent issues when trying to access certain directories and files. The following errors appear in dmesg:
mathematica CopyEdit I/O error, dev sda1, sector 456788 Buffer I/O error on device sda1, logical block 378994 Which of the following actions should the administrator take to resolve the issue?
Options
- AUse dd to copy and reformat the disk
- BUse gddrescue to copy the disk, edit /etc/fstab, replace the disk
- CUse fsck /dev/sda1 in GRUB recovery
- DBoot a recovery disk, run fsck on unmounted drive
How the community answered
(29 responses)- A3% (1)
- B10% (3)
- C7% (2)
- D79% (23)
Why each option
I/O errors on a disk partition typically indicate filesystem corruption or underlying physical disk issues, which require running a filesystem check on an unmounted partition from a recovery environment.
`dd` is for raw data copying and reformatting would lead to data loss without attempting recovery or repair first, making it a destructive and premature step.
While `gddrescue` is useful for data recovery from failing disks, `fsck` is the primary diagnostic and repair tool for filesystem errors. Replacing the disk without attempting `fsck` first might be an overreaction if the issue is purely filesystem related.
Running `fsck /dev/sda1` directly in GRUB recovery might not guarantee the partition is unmounted, especially if it's the root filesystem, which can lead to further corruption or incomplete repairs.
I/O errors and buffer I/O errors point to potential filesystem corruption or hardware problems with the disk. Running `fsck` (filesystem consistency check) is necessary to diagnose and repair these issues. It is critical to perform `fsck` on an *unmounted* filesystem to prevent further damage and ensure accurate repairs, which is best achieved by booting from a recovery disk or live environment.
Concept tested: Linux filesystem corruption diagnosis and repair
Source: https://man7.org/linux/man-pages/man8/fsck.8.html
Topics
Community Discussion
No community discussion yet for this question.