Seems to be a bug in mke2fs on latest rootfs

So, 2x 1TB HDDs, both formatted by my Goflex Net. Both had errors trying to mount on my Ubuntu laptop. Tried the first 12 or so backup superblocks in the filesystem with e2fsck, but those all had identical issues. The problem seems to be that the filesystem size was 1 block bigger than the partition size.

Fortunately, I only had about 300 GB of data on the one drive, and nothing on the other. In addition, the mount and fsck commands are tolerant of the above issue on the Goflex Net, so it can mount drives formatted on both my Laptop and the GoFlex. The solution, then, was to reformat the already blank drive in Ubuntu, and then put it back into the GoFlex Net.

I will copy 'n' paste the the exact error in a moment, after I finish copying over my 300 GB. Might take a little while for that.

Were the HDDs formated as Ext4?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

No, Ext3.

The specific command I used after partitioning, is

mkfs.ext3 /dev/sdX

aaronouthier Wrote:
-------------------------------------------------------
> The specific command I used after partitioning, is
>
>

> mkfs.ext3 /dev/sdX
>

In case you did mean X is a letter only, it should be with partition number. For example,

mkfs.ext3 -L someLabel /dev/sda1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Yes, you're correct. I'm a bit distracted right now, and I was typing from memory. I did indeed specify the partition, not the entire drive

/dev/sdX1

Strange. I never seen this problem using SATA or USB drives formatted in the Kirkwood boxes and used in Linux Mint 19 (Intel x86), or vice versa.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

As promised, the Logs:

$ sudo mount -t ext3 /dev/sdc1 /mnt
[sudo] password for theadmin: 
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.

sudo fsck.ext3 -f /dev/sdc1 
e2fsck 1.46.2 (28-Feb-2021)
The filesystem size (according to the superblock) is 244190390 blocks
The physical size of the device is 244190389 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes

$ sudo mkfs.ext3 -n /dev/sdc1 
mke2fs 1.46.2 (28-Feb-2021)
/dev/sdc1 contains a ext3 file system
        last mounted on /mnt/2 on Wed Dec 31 16:01:04 1969
Proceed anyway? (y,N) y
Creating filesystem with 244190389 4k blocks and 61054976 inodes
Filesystem UUID: f72fc65f-c820-4cb4-820c-be29a9c2639c
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
        102400000, 214990848

$ sudo fsck.ext3 -fb 32768 /dev/sdc1
e2fsck 1.46.2 (28-Feb-2021)
The filesystem size (according to the superblock) is 244190390 blocks
The physical size of the device is 244190389 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
Pass 1: Checking inodes, blocks, and sizes
^C/dev/sdc1: e2fsck canceled.

/dev/sdc1: ***** FILE SYSTEM WAS MODIFIED *****

> $ sudo mount -t ext3 /dev/sdc1 /mnt

Where was this command executed? in the pogoplug or in the host system?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Host system. “Pogoplug” doesn’t seem to notice either format source. Neither FSCK nor mount complain about either one.