> You might have to boot from a recovery CD image, such as a Debian live > install image, or GParted Live. You can't actually run fsck on a drive > while said drive is mounted.
Thank, Jeremy. But - is /dev/sda1 mounted at this point? Isn't it being indicated to us that it can't be successfully mounted? (Thinking of the Busybox appearance and (intramfs) reference.) > On Tue, 2 Feb 2021 at 19:24, Stefan Monnier <monn...@iro.umontreal.ca> > wrote: > >> >> My brother's Debian system suddenly says on attempt to boot, >> "/dev/sda1: >> >> UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were >> part >> of >> >> a corrupted orphan linked list found." >> >> >> >> He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck >> >> identifying it's version, and nothing else. Tha appears to take >> place >> >> from (initramfs) and Busybox. An attempt to reboot just starts the >> >> problem all over again. >> >> >> >> We'd be grateful for help with this. Thanks. >> >> >> > hello, >> > >> > fsck -fy /dev/sda1 is probably what you want >> >> Then again, after the "UNEXPECTED INCONSISTENCY", the `-f` flag to >> `fsck` shouldn't be needed. This is weird. >> >> >> Stefan >> >> >
