Openhabian-config "raw copy" : getting "FAILED (e2fsck)"

Edited - see below

Hello, I have a question about RAW copy (option 54 in openhabian-config):

To upgrade from v4.1.0 to v4.1.1 I wanted to create a copy of the SD card first.

When I create the raw copy via option 54, the message FAILED (e2fsck) appears.
See third last line in the first code block.

When I check the two partitions with e2fsck I get following results (see the second code block)

This happens also with unused/new SD cards.

xxxxx@yyyyy:~ $ sudo openhabian-config 
2024-01-13_14:24:55_CET [openHABian] Checking for root privileges... OK
2024-01-13_14:24:55_CET [openHABian] Loading configuration file '/etc/openhabian.conf'... OK
2024-01-13_14:24:55_CET [openHABian] openHABian configuration tool version: [openHAB]{2023-12-31T13:09:51+01:00}(9ac4ddd)
2024-01-13_14:24:55_CET [openHABian] Checking for changes in origin branch openHAB... OK
2024-01-13_14:24:56_CET [openHABian] Switching to branch openHAB... OK
2024-01-13_14:24:56_CET [openHABian] Checking openHAB Signing Key expiry.
2024-01-13_14:24:56_CET [openHABian] Checking expiry date of apt keys... OK
blockdev: cannot open /dev/sda1: Datei oder Verzeichnis nicht gefunden
raw device copy of /dev/mmcblk0p1 is larger than /dev/sda1... blockdev: cannot open /dev/sda2: Datei oder Verzeichnis nicht gefunden
raw device copy of /dev/mmcblk0p2 is larger than /dev/sda2... Checking that no-one is using this disk right now ... OK

Disk /dev/sda: 29,72 GiB, 31914983424 bytes, 62333952 sectors
Disk model: STORAGE DEVICE  
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: 0x90ac96be

Old situation:

>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Created a new DOS disklabel with disk identifier 0x05ba41dd.
/dev/sda1: Created a new partition 1 of type 'W95 FAT32 (LBA)' and of size 256 MiB.
Partition #1 contains a vfat signature.
/dev/sda2: Created a new partition 2 of type 'Linux' and of size 14,7 GiB.
Partition #2 contains a ext4 signature.
/dev/sda3: Done.

New situation:
Disklabel type: dos
Disk identifier: 0x05ba41dd

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sda1         8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/sda2       532480 31399935 30867456 14,7G 83 Linux

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
Taking a raw partition copy, be prepared this may take long such as 20-30 minutes for a 16 GB SD card
FAILED (e2fsck)
2024-01-13_14:31:58_CET [openHABian] Checking for default openHABian username:password combination... OK
2024-01-13_14:31:58_CET [openHABian] We hope you got what you came for! See you again soon ;)

xxxxx@yyyyy:~ $ sudo e2fsck /dev/sda1
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_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/sda1

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:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sda1 contains a vfat file system labelled 'boot'
xxxxx@yyyyy:~ $ sudo e2fsck /dev/sda2
e2fsck 1.46.2 (28-Feb-2021)
rootfs: clean, 114243/932672 files, 2716848/3858432 blocks

Can I ignore this, because the copy works perfectly?

EDIT:
After a little research I think I understand that I can ignore the message, because e2fsck only refers to ext2/3/4 file systems and the partition with the invalid superblock in question is FAT32.

Could someone confirm this for me ?

I have the same issue. No idea if this “FAILED” message can be neglected.

Anyone who is more experienced?

Hi, I’m now pretty sure that you can ignore the message.

thx

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.