RPI v1.4 image has currupted FS

Discuss KerberosSDR - 4x Coherent RTL-SDR
Post Reply
baz
Posts: 3
Joined: Tue Oct 01, 2019 2:41 pm

RPI v1.4 image has currupted FS

Post by baz » Tue Oct 01, 2019 2:47 pm

RPI v1.4 image has currupted ext4 filesystem and won't start on PI without manual intervention.

myke
Posts: 37
Joined: Wed Aug 28, 2019 7:03 pm

Re: RPI v1.4 image has currupted FS

Post by myke » Tue Oct 01, 2019 9:26 pm

I am running that image with much success. What errors are you seeing?

rtlsdrblog
Site Admin
Posts: 2428
Joined: Mon Nov 19, 2012 11:54 pm

Re: RPI v1.4 image has currupted FS

Post by rtlsdrblog » Wed Oct 02, 2019 1:26 am

You're the first one with this problem, so I don't think it's an image problem. How are you writing it to the SD card? Could your SD card be faulty?

baz
Posts: 3
Joined: Tue Oct 01, 2019 2:41 pm

Re: RPI v1.4 image has currupted FS

Post by baz » Wed Oct 02, 2019 9:50 am

I can show it without sdcard:

Code: Select all

tarantula!root# md5sum rpi3_kerberossdr_image_240719.zip
547b8e4ca44c7bddbdd9d3e040506d0b  rpi3_kerberossdr_image_240719.zip

tarantula!root# unzip rpi3_kerberossdr_image_240719.zip
Archive:  rpi3_kerberossdr_image_240719.zip
  inflating: rpi3_kerberossdr_image_240719.img

tarantula!root# md5sum rpi3_kerberossdr_image_240719.img
bc7284cf3cf9e5c8b38e18ab6e68e9da  rpi3_kerberossdr_image_240719.img

tarantula!root# fdisk -l rpi3_kerberossdr_image_240719.img
Disk rpi3_kerberossdr_image_240719.img: 7 GiB, 7516192768 bytes, 14680064 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
Disklabel type: dos
Disk identifier: 0x115336b8

Device                             Boot Start      End  Sectors  Size Id Type
rpi3_kerberossdr_image_240719.img1       8192    98045    89854 43,9M  c W95 FAT32 (LBA)
rpi3_kerberossdr_image_240719.img2      98304 15126527 15028224  7,2G 83 Linux

tarantula!root# losetup --show -f -o $((98304*512)) rpi3_kerberossdr_image_240719.img
/dev/loop9

tarantula!root# md5sum /dev/loop9
7d4af158eace1219d9f375d87b948c9f  /dev/loop9

tarantula!root# e2fsck -fn /dev/loop9
e2fsck 1.45.3 (14-Jul-2019)
Warning: skipping journal recovery because doing a read-only filesystem check.
The filesystem size (according to the superblock) is 1878528 blocks
The physical size of the device is 1822720 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no

Pass 1: Checking inodes, blocks, and sizes
Deleted inode 7731 has zero dtime.  Fix? no

Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 35272 was part of the orphaned inode list.  IGNORED.
Inode 35277 was part of the orphaned inode list.  IGNORED.
Inode 41722 was part of the orphaned inode list.  IGNORED.
Inode 41754 was part of the orphaned inode list.  IGNORED.
Inode 41987 was part of the orphaned inode list.  IGNORED.
Inode 42048 was part of the orphaned inode list.  IGNORED.
Inode 289505 was part of the orphaned inode list.  IGNORED.
Inode 398660 was part of the orphaned inode list.  IGNORED.
Inode 398819 was part of the orphaned inode list.  IGNORED.
Inode 399106 was part of the orphaned inode list.  IGNORED.
Inode 399110 was part of the orphaned inode list.  IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (910976, counted=910974).
Fix? no

Inode bitmap differences:  -7731
Fix? no

Free inodes count wrong (351104, counted=351101).
Fix? no


rootfs: ********** WARNING: Filesystem still has errors **********

rootfs: 124032/475136 files (0.2% non-contiguous), 967552/1878528 blocks

tarantula!root# losetup -d /dev/loop9
And after fsck image is fine, but is not on first boot.

myke
Posts: 37
Joined: Wed Aug 28, 2019 7:03 pm

Re: RPI v1.4 image has currupted FS

Post by myke » Wed Oct 02, 2019 6:53 pm

Interesting - however, I am getting some strange results on raspian image : 2019-09-26-raspbian-buster.img -- I might not be doing something exactly as you tested Kerberos. I do not have more time I can devote at the moment. However, i do know after installing the Kerberos image - I have booted fine and have not seen anything related to OS error....

could not seem to resolve mount point on raspian image - I'm sure someone else might have tried this?

Code: Select all

xt2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/loop7

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:

baz
Posts: 3
Joined: Tue Oct 01, 2019 2:41 pm

Re: RPI v1.4 image has currupted FS

Post by baz » Thu Oct 03, 2019 2:07 pm

myke wrote:
Wed Oct 02, 2019 6:53 pm
Interesting - however, I am getting some strange results on raspian image : 2019-09-26-raspbian-buster.img -- I might not be doing something exactly as you tested Kerberos.
Most probably you missed to take start of second partition from fdisk output and use it in loseup command (-o switch).

Post Reply