하드 디스크 오류로 인해 더 이상 부팅되지 않은 Ubuntu를 fsck로 오마화
"Ubuntu에서 MINECRAFT"
htps : // m / 난부 wks / ms / df10 9f0 에 d473827d7
이 중 HDD로 구축한 환경이 있었습니다만 떨어뜨리거나 낙하시키거나 하고 있었기 때문에 기동하지 않게 되어 버렸습니다.

키즈용으로는 HDD는 피하는 편이 좋을까? 우선 SSD나 USB 메모리로 환장할 때까지의 연결로서, 적당하게 오마화해 움직이게 했습니다.
단일 사용자 모드?
이런 경우 싱글 유저 모드로 fsck를 합니다만, Ubuntu에서는 어땠습니까?

여기까지 왔지만 여기에서 fsck를 부를 수 없었기 때문에 다른 USB 메모리에서 Ubuntu를 움직여 fsck 할 수 있도록 했습니다.
USB 메모리로 fsck

Ubuntu20.04에서 시작하여 터미널을 엽니다.
$ sudo fdisk -l
에서 HDD 주소를 확인합니다.
$ sudo fdisk -l
Disk /dev/loop0: 1.10 GiB, 2123702272 bytes, 4147856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 29.9 MiB, 31334400 bytes, 61200 sectors
Units: sectors of 1 * 512 = 512 bytes
.
.
.
Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: HGST HTS725050A7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x966ff116
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1050623 1048576 512M b W95 FAT32
/dev/sda2 1052670 976771071 975718402 465.3G 5 Extended
/dev/sda5 1052672 976771071 975718400 465.3G 83 Linux
Partition 2 does not start on physical sector boundary.
Disk /dev/sdb: 28.66 GiB, 30752636928 bytes, 60063744 sectors
Disk model: Ultra Fit
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 32 60063743 60063712 28.7G c W95 FAT32 (LBA)

/dev/sda였습니다.
우선/dev/sda1.
$ sudo fsck /dev/sda1
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
Perform changes ? (y/n) y
/dev/sda1: 0 files, 1/130812 clusters

여기는 아마 문제가 없다.
다음으로/dev/sda5
$ sudo fsck /dev/sda5
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Superblock checksum does not match superblock
fsck.ext4: Superblock invalid, trying backup blocks...
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda5: recovering journal
Error reading block 60850860 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 68681781 in log
Error reading block 60851762 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 111149515 in log
Error reading block 60852186 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 7872947 in log
Error reading block 60852663 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 70778988 in log
Error reading block 60856641 (Input/output error). Ignore error<y>? yes
결코 없기 때문에 일단 취소.
/dev/sda5: e2fsck canceled.
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
다시 y 옵션을 사용하여 실행
$ sudo fsck /dev/sda5 -y
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda5 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 55581559 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 55581780 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 55582001 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
.
.
.
Error reading block 61873469 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 61873703 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 61873938 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Deleted inode 23593234 has zero dtime. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Error reading block 57671691 (Input/output error) while reading inode and block bitmaps. Ignore error? yes
Force rewrite? yes
Block bitmap differences: +(4096000--4097083) -(6060032--6060543) -(9281024--9281463) +(20480000--20481083) +(23887872--23888955) +(71663616--71664699) +(78675968--78677051) +(102400000--102401083) -(120523409--120523413)
Fix? yes
Free blocks count wrong for group #0 (23454, counted=2984).
Fix? yes
Free blocks count wrong for group #1 (31684, counted=963).
Fix? yes
Free blocks count wrong for group #2 (32768, counted=0).
Fix? yes
Free blocks count wrong for group #3 (31684, counted=964).
Fix? yes
.
.
.
Free blocks count wrong for group #3709 (32768, counted=20737).
Fix? yes
Free blocks count wrong for group #3710 (32768, counted=32738).
Fix? yes
Free blocks count wrong (119769515, counted=113199036).
Fix? yes
Inode bitmap differences: -1444172 -23593234
Fix? yes
Free inodes count wrong for group #0 (8181, counted=8174).
Fix? yes
Free inodes count wrong for group #48 (8192, counted=6150).
Fix? yes
Directories count wrong for group #48 (0, counted=679).
Fix? yes
.
.
.
Free inodes count wrong for group #3680 (8192, counted=5923).
Fix? yes
Directories count wrong for group #3680 (0, counted=670).
Fix? yes
Free inodes count wrong for group #3696 (8192, counted=3957).
Fix? yes
Directories count wrong for group #3696 (0, counted=499).
Fix? yes
Free inodes count wrong (30498805, counted=30126918).
Fix? yes
Padding at end of inode bitmap is not set. Fix? yes
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 371898/30498816 files (0.9% non-contiguous), 8765764/121964800 blocks
ubuntu@ubuntu:~$
어떻게든 끝났어.
복구
HDD만으로 부팅해보기

상당히 오류가 발생하지만 잠시 기다리면

시작했습니다.
Reference
이 문제에 관하여(하드 디스크 오류로 인해 더 이상 부팅되지 않은 Ubuntu를 fsck로 오마화), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다
https://qiita.com/nanbuwks/items/96e92023205d8f4bb694
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)

Ubuntu20.04에서 시작하여 터미널을 엽니다.
$ sudo fdisk -l
에서 HDD 주소를 확인합니다.
$ sudo fdisk -l
Disk /dev/loop0: 1.10 GiB, 2123702272 bytes, 4147856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 29.9 MiB, 31334400 bytes, 61200 sectors
Units: sectors of 1 * 512 = 512 bytes
.
.
.
Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: HGST HTS725050A7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x966ff116
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1050623 1048576 512M b W95 FAT32
/dev/sda2 1052670 976771071 975718402 465.3G 5 Extended
/dev/sda5 1052672 976771071 975718400 465.3G 83 Linux
Partition 2 does not start on physical sector boundary.
Disk /dev/sdb: 28.66 GiB, 30752636928 bytes, 60063744 sectors
Disk model: Ultra Fit
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 32 60063743 60063712 28.7G c W95 FAT32 (LBA)

/dev/sda였습니다.
우선/dev/sda1.
$ sudo fsck /dev/sda1
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
Perform changes ? (y/n) y
/dev/sda1: 0 files, 1/130812 clusters

여기는 아마 문제가 없다.
다음으로/dev/sda5
$ sudo fsck /dev/sda5
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Superblock checksum does not match superblock
fsck.ext4: Superblock invalid, trying backup blocks...
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda5: recovering journal
Error reading block 60850860 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 68681781 in log
Error reading block 60851762 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 111149515 in log
Error reading block 60852186 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 7872947 in log
Error reading block 60852663 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
JBD2: Invalid checksum recovering block 70778988 in log
Error reading block 60856641 (Input/output error). Ignore error<y>? yes
결코 없기 때문에 일단 취소.
/dev/sda5: e2fsck canceled.
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
다시 y 옵션을 사용하여 실행
$ sudo fsck /dev/sda5 -y
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda5 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 55581559 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 55581780 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 55582001 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
.
.
.
Error reading block 61873469 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 61873703 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Error reading block 61873938 (Input/output error) while getting next inode from scan. Ignore error? yes
Force rewrite? yes
Deleted inode 23593234 has zero dtime. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Error reading block 57671691 (Input/output error) while reading inode and block bitmaps. Ignore error? yes
Force rewrite? yes
Block bitmap differences: +(4096000--4097083) -(6060032--6060543) -(9281024--9281463) +(20480000--20481083) +(23887872--23888955) +(71663616--71664699) +(78675968--78677051) +(102400000--102401083) -(120523409--120523413)
Fix? yes
Free blocks count wrong for group #0 (23454, counted=2984).
Fix? yes
Free blocks count wrong for group #1 (31684, counted=963).
Fix? yes
Free blocks count wrong for group #2 (32768, counted=0).
Fix? yes
Free blocks count wrong for group #3 (31684, counted=964).
Fix? yes
.
.
.
Free blocks count wrong for group #3709 (32768, counted=20737).
Fix? yes
Free blocks count wrong for group #3710 (32768, counted=32738).
Fix? yes
Free blocks count wrong (119769515, counted=113199036).
Fix? yes
Inode bitmap differences: -1444172 -23593234
Fix? yes
Free inodes count wrong for group #0 (8181, counted=8174).
Fix? yes
Free inodes count wrong for group #48 (8192, counted=6150).
Fix? yes
Directories count wrong for group #48 (0, counted=679).
Fix? yes
.
.
.
Free inodes count wrong for group #3680 (8192, counted=5923).
Fix? yes
Directories count wrong for group #3680 (0, counted=670).
Fix? yes
Free inodes count wrong for group #3696 (8192, counted=3957).
Fix? yes
Directories count wrong for group #3696 (0, counted=499).
Fix? yes
Free inodes count wrong (30498805, counted=30126918).
Fix? yes
Padding at end of inode bitmap is not set. Fix? yes
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 371898/30498816 files (0.9% non-contiguous), 8765764/121964800 blocks
ubuntu@ubuntu:~$
어떻게든 끝났어.
복구
HDD만으로 부팅해보기

상당히 오류가 발생하지만 잠시 기다리면

시작했습니다.
Reference
이 문제에 관하여(하드 디스크 오류로 인해 더 이상 부팅되지 않은 Ubuntu를 fsck로 오마화), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다
https://qiita.com/nanbuwks/items/96e92023205d8f4bb694
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)
Reference
이 문제에 관하여(하드 디스크 오류로 인해 더 이상 부팅되지 않은 Ubuntu를 fsck로 오마화), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다 https://qiita.com/nanbuwks/items/96e92023205d8f4bb694텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)