Unable to mount USB drive after rebuilding the storage node

murthydevarakonda · January 8, 2020, 5:21am

Hello,

My raspberry pi got crashed due to some kernel issues and I could not fix those issues. I need to rebuild the node again. After rebuilding, when I connected the USB drive to the pi, I could not mount it. I get the following error. I do not want to format the drive. Is there a way to resolve this issue?

mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

[ 2501.970145] sd 1:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[ 2501.978004] sda: unknown partition table
[ 9387.289324] JBD2: Unrecognised features on journal
[ 9387.289340] EXT4-fs (sda): error loading journal
[ 9826.466769] sd 1:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[ 9826.475169] sda: unknown partition table
[10460.040501] sd 1:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[10460.048125] sda: unknown partition table
[10752.531883] JBD2: Unrecognised features on journal
[10752.531901] EXT4-fs (sda): error loading journal

Alexey · January 8, 2020, 5:35am

Hello,

Please, show result of these commands:

sudo lsblk
sudo blkid

murthydevarakonda · January 8, 2020, 4:00pm

Here you go.

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 7.3T 0 disk
zram0 253:0 0 122.7M 0 disk [SWAP]
zram1 253:1 0 122.7M 0 disk [SWAP]
zram2 253:2 0 122.7M 0 disk [SWAP]
zram3 253:3 0 122.7M 0 disk [SWAP]
mmcblk0 179:0 0 14.9G 0 disk
|-mmcblk0p1 179:1 0 100M 0 part /boot
`-mmcblk0p2 179:2 0 14.8G 0 part /

/dev/mmcblk0: PTUUID=“76e92800” PTTYPE=“dos”
/dev/mmcblk0p1: SEC_TYPE=“msdos” LABEL=“BOOT” UUID=“D53B-9C84” TYPE=“vfat” PARTUUID=“76e92800-01”
/dev/mmcblk0p2: LABEL=“rootfs” UUID=“0cd17b3d-39ae-4b12-a1c7-9b0a96daefe2” TYPE=“ext4” PARTUUID=“76e92800-02”
/dev/zram0: UUID=“eeb8b401-34b2-4705-a21e-aaf2b5f3d0b8” TYPE=“swap”
/dev/sda: UUID=“05d57eef-f115-47e4-945d-0cb5f31f972d” TYPE=“ext4”
/dev/zram1: UUID=“bdbd9d6c-0706-4ca7-983b-8c47918f91c6” TYPE=“swap”
/dev/zram2: UUID=“2ce05c5a-ed4d-4af7-8dc2-0e5d8207663c” TYPE=“swap”
/dev/zram3: UUID=“663db47e-2b1f-48cc-89fc-058c65f21822” TYPE=“swap”

Alexey · January 8, 2020, 6:56pm

Have you added your /dev/sda to the /etc/fstab?
Or try at least

sudo mount -t ext4 /dev/sda /mnt

murthydevarakonda · January 8, 2020, 7:16pm

Thanks @Alexey

I tried that and get the same error.

pine64@StorJ-Node:~$ sudo mount -t ext4 /dev/sda /mnt/storagenode/
[sudo] password for pine64:
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

Alexey · January 8, 2020, 7:24pm

Try to fix issues:

sudo fsck /dev/sda

murthydevarakonda · January 8, 2020, 7:27pm

I tried that too but no luck.

fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sda has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!

murthydevarakonda · January 8, 2020, 7:44pm

I tried e2fsck also. I got bunch of errors.

Alexey · January 8, 2020, 7:51pm

You need to have a new version of e2fsck

dpkg --print-architecture
lsb_release -a

murthydevarakonda · January 8, 2020, 10:35pm

Thank you @Alexey . I have latest e2fsck and e2fsprogs. Still get the error. What would I lose if I format my drive?

kajar9 · January 9, 2020, 12:38am

You need to start from 0 as formatting would lose all data, you’ll fail audits.

You need New identity, everything.

Fortunately there isn’t a wait for new invites, but you’ll still have to wait out the audit period. ~1 month. Where your in/out is quite crappy.

murthydevarakonda · January 9, 2020, 1:22am

@kajar9 I backed up my identity. So, I do not need a new invite. I know that I will lose the data, but what will be impact of losing that data.

deathlessdd · January 9, 2020, 1:27am

You need a new identity You will get DQed because you lost all the data.

murthydevarakonda · January 9, 2020, 2:01am

@Alexey, I ran newer version of fsck on the disk, but still cannot mount.

pine64@StorJ-Node:~$ sudo e2fsck.static /dev/sda
e2fsck 1.43.4 (31-Jan-2017)
/dev/sda: clean, 673761/244191232 files, 187584451/1953506645 blocks

Alexey · January 9, 2020, 3:50am

sudo mount -t ext4 /dev/sda /mnt/storagenode/

What does it say?

murthydevarakonda · January 9, 2020, 4:38am

Thanks for the reply. I get the same error.

mount: wrong fs type, bad option, bad superblock on /dev/sda,

Alexey · January 9, 2020, 4:46am

Try to fix the filesystem

sudo e2fsck.static -p /dev/sda

hlbcal · October 17, 2020, 1:52pm

Hello,

I encountered the same problem as you had. Unfortunately, I also did not find any solution. Below steps are what I did.

Format ext4 on Pi3.
Rsync all my existing data.
Umount my USB disk from Pi3.
Move the USB disk to another ARM device which is running Armbian.
Trying to mount this USB disk.

Now, I have the same error “mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or helper program, or other error”

I spent a lot of time on Google but none of the solutions work. The best alternative is to mount is a “read only”.

So far have you got a workable solution?

Thanks in advance.

Alexey · October 17, 2020, 5:26pm

Could you show result of this command:

fdisk -l

hlbcal · October 17, 2020, 5:50pm

pi@raspberrypi:~ $ sudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 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: 0x5e3da3da

Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1        8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      532480 31116287 30583808 14.6G 83 Linux


Disk /dev/sda: 3.7 TiB, 4000752599040 bytes, 7813969920 sectors
Disk model: Elements 25A3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: AD7ADA9D-8D55-4A44-BB9C-BE846791DD6C

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7813969886 7813967839  3.7T Linux filesystem


Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: AS2115
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 34E1081B-C8E0-4AAF-8737-D93B33469A35

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 7814037134 7814035087  3.7T Linux filesystem

/dev/sda1 is my working disk.
/dev/sdb1 is my new disk. I’m moving data to this disk now and it will be used on my Armbian device.

In the very beginning, I use mount command to mount this disk as /mnt/storagenode-new, it is able to rsync. But when I bring it back to Armbian, it cannot be mounted anymore.

Now I notice after inserting a USB disk into Pi3, it will be auto-mounted as something like /media/pi/019879b6-7adb-4a23-8fa7-3c0805132f1d

So I just use this path for syncing. One more thing, I formated this disk on Armbian without journal. Seems “without journal" and using “auto-mount path” is a workaround for me. I will report back after full sync, it will be probably a few days later due to USB2.0 on Pi3.

Cheers