Since this is the second time it happens in 1 month I'd like to understand what might be causing it and how do I make sure it doesn't happen again? UNEXPECTED INCONSISTENCY RUN fsck MANUALLY. Today, after booting up, I noticed that my / mount was read-only, I rebooted and got this message: Inodes that were part of a corrupted orphan linked list found. Inode 36850013, i_blocks is 4024, should be 4016.I bought a Centurion Nano from the now defunct Alpha Computers, it ships with Alpha OS (that is essentially a tampered Ubuntu): $ cat /etc/os-release Inode 35922361 was part of the orphaned inode list. Inode 35921468 was part of the orphaned inode list. Inode 35921467 was part of the orphaned inode list. Inode 35921463 was part of the orphaned inode list. Inode 35921462 was part of the orphaned inode list. Inode 35921456 was part of the orphaned inode list. Inode 35921453 was part of the orphaned inode list. Inode 35921434 was part of the orphaned inode list. Inode 35921418 was part of the orphaned inode list. Inode 35921415 was part of the orphaned inode list. Inode 35921405 was part of the orphaned inode list. Inode 35921393 was part of the orphaned inode list. Inode 35921387 was part of the orphaned inode list. ![]() Inode 35921383 was part of the orphaned inode list. Inode 35921351 was part of the orphaned inode list. Inode 35921343 was part of the orphaned inode list. Inode 35921340 was part of the orphaned inode list. Inode 35916554 was part of the orphaned inode list. Inode 35915647 was part of the orphaned inode list. Inode 35915189 was part of the orphaned inode list. Inode 35915013 was part of the orphaned inode list. Inode 35915012 was part of the orphaned inode list. Inode 35915011 was part of the orphaned inode list. Inode 35915010 was part of the orphaned inode list. Inode 35914970 was part of the orphaned inode list. Inode 35914969 was part of the orphaned inode list. Inode 35914968 was part of the orphaned inode list. Inode 35914967 was part of the orphaned inode list. Inode 35914966 was part of the orphaned inode list. Inode 35914965 was part of the orphaned inode list. Inode 35914964 was part of the orphaned inode list. Inodes that were part of a corrupted orphan linked list found. ![]() Pass 1: Checking inodes, blocks, and sizesÄeleted inode 35914963 has zero dtime. dev/md2 contains a file system with errors, check forced. EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: fsck.ext3 /dev/md2 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 37949889 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923105 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35915175 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35915170 ![]() EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923111 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923112 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923110 EXT3-fs error (device md2): ext3_lookup: deleted inode referenced: 35923106 Nov 29 20:17:58 ubuntu kernel: md0: unknown partition tableįilesystem not responding/reading properly with du or rsync (this needed an fsck). Nov 29 20:17:58 ubuntu kernel: md: md1 stopped.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |