New IT forum
12 August 2022, 02:37:25 pm *
Welcome, %1$s. Please login or register.

: CubieBoard 2 and Cubietruck both now in stock.
Pages: [1]

Author Topic: Corrupt Filesystem - What to do?  (Read 8150 times)


  • Newbie
  • *
  • Posts: 12
Corrupt Filesystem - What to do?
« on: 03 May 2011, 07:13:13 am »

looks like my filesystem got corrupted.
fsck -n /dev/sda2
fsck 1.41.4 (27-Jan-2009)
WARNING: Your /etc/fstab does not contain the fsck passno
   field.  I will kludge around things for you, but you
   should fix your /etc/fstab file as soon as you can.

e2fsck 1.41.4 (27-Jan-2009)
Warning!  /dev/sda2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
The filesystem size (according to the superblock) is 456676 blocks
The physical size of the device is 454254 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no

dreamv7_fs contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 454672 (Invalid argument) while reading indirect blocks of inode 109806.  Ignore error? no

Error while iterating over blocks in inode 109806: Invalid argument
e2fsck: aborted

How to fix this? Maybe the initrd could fix it? I have no idea if it can or how i can set boot parameters without jtag/uart. Is there a way?



  • Hero Member
  • *****
  • Posts: 960
Re: Corrupt Filesystem - What to do?
« Reply #1 on: 03 May 2011, 07:36:49 am »

Pages: [1]

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!