search

bryanbocao / awesome-cmd-cheatsheets

Quick search the commands you need.
3 stars 1 forks source link

mount: /mnt0: wrong fs type, bad option, bad superblock #14

Closed bryanbocao closed 1 year ago

bryanbocao commented 1 year ago 
(base) brcao@night:~$ ls /dev/sd*
/dev/sda   /dev/sda2  /dev/sdb1  /dev/sdb3  /dev/sdb5  /dev/sdd   /dev/sdd2
/dev/sda1  /dev/sdb   /dev/sdb2  /dev/sdb4  /dev/sdc   /dev/sdd1
(base) brcao@night:~$ sudo mkdir eData0
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc5 during installation
UUID=01e59cb8-6129-401a-8a37-425fd6d75e93 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc2 during installation
UUID=5268-F655  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/sdb2 /eData0  ext4  defaults  0 0
"/etc/fstab" 13L, 704B                                                                        13,1          All
# /etc/fstab: static file system information.
(base) brcao@night:~$ sudo vim /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc5 during installation
UUID=01e59cb8-6129-401a-8a37-425fd6d75e93 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc2 during installation
UUID=5268-F655  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/sdb /eData0  ext4  defaults  0 0
"/etc/fstab" 13L, 703B                                                                        13,8          All
# /etc/fstab: static file system information.
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo mount eData0
mount: eData0: can't find in /etc/fstab.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc5 during installation
UUID=01e59cb8-6129-401a-8a37-425fd6d75e93 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc2 during installation
UUID=5268-F655  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/sdd /eData0  ext4  defaults  0 0
"/etc/fstab" 13L, 703B                                                                        13,8          All
# /etc/fstab: static file system information.
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo mount eData0
mount: eData0: can't find in /etc/fstab.
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo mount eData0
mount: eData0: can't find in /etc/fstab.
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo mount eData0
mount: eData0: can't find in /etc/fstab.
(base) brcao@night:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo mount eData0
mount: eData0: can't find in /etc/fstab.
(base) brcao@night:~$ sudo mount /eData0
mount: /eData0: mount point does not exist.
(base) brcao@night:~$ mkdir /eData0
mkdir: cannot create directory ‘/eData0’: Permission denied
(base) brcao@night:~$ mkdir /eData0^C
(base) brcao@night:~$ ^C
(base) brcao@night:~$ sudo mkdir /eData0
(base) brcao@night:~$ sudo mount /eData0
mount: /eData0: /dev/sdb2 already mounted on /boot/efi.
(base) brcao@night:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
(base) brcao@night:~$ cd /eData0/
(base) brcao@night:/eData0$ ls
(base) brcao@night:/eData0$ ls
(base) brcao@night:/eData0$ cd ..
(base) brcao@night:/$ sudo vim /etc/fstab
(base) brcao@night:/$ sudo vim /etc/fstab
(base) brcao@night:/$ sudo mount /eData0
mount: /eData0: wrong fs type, bad option, bad superblock on /dev/sdd, missing codepage or helper program, or other error.
(base) brcao@night:/$ sudo vim /etc/fstab
(base) brcao@night:/$ sudo mount /eData0
mount: /eData0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:/$ fdisk -l
fdisk: cannot open /dev/loop0: Permission denied
fdisk: cannot open /dev/loop1: Permission denied
fdisk: cannot open /dev/loop2: Permission denied
fdisk: cannot open /dev/loop3: Permission denied
fdisk: cannot open /dev/loop4: Permission denied
fdisk: cannot open /dev/loop5: Permission denied
fdisk: cannot open /dev/loop6: Permission denied
fdisk: cannot open /dev/loop7: Permission denied
fdisk: cannot open /dev/sda: Permission denied
fdisk: cannot open /dev/sdb: Permission denied
fdisk: cannot open /dev/sdc: Permission denied
fdisk: cannot open /dev/sdd: Permission denied
fdisk: cannot open /dev/loop8: Permission denied
fdisk: cannot open /dev/loop9: Permission denied
fdisk: cannot open /dev/loop10: Permission denied
fdisk: cannot open /dev/loop11: Permission denied
fdisk: cannot open /dev/loop12: Permission denied
fdisk: cannot open /dev/loop13: Permission denied
fdisk: cannot open /dev/loop14: Permission denied
fdisk: cannot open /dev/loop15: Permission denied
fdisk: cannot open /dev/loop16: Permission denied
fdisk: cannot open /dev/loop17: Permission denied
fdisk: cannot open /dev/loop18: Permission denied
fdisk: cannot open /dev/loop19: Permission denied
(base) brcao@night:/$ sudo fdisk -l
Disk /dev/loop0: 4 KiB, 4096 bytes, 8 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

Disk /dev/loop1: 63.32 MiB, 66392064 bytes, 129672 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

Disk /dev/loop2: 63.34 MiB, 66412544 bytes, 129712 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

Disk /dev/loop3: 72.99 MiB, 76537856 bytes, 149488 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

Disk /dev/loop4: 72.99 MiB, 76537856 bytes, 149488 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

Disk /dev/loop5: 241.9 MiB, 253648896 bytes, 495408 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

Disk /dev/loop6: 241.49 MiB, 253222912 bytes, 494576 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

Disk /dev/loop7: 349.69 MiB, 366673920 bytes, 716160 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

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-08W
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: 91B33B4E-737F-4BC3-8553-5C8DE35F8858

Device     Start        End    Sectors   Size Type
/dev/sda1     34      32767      32734    16M Microsoft reserved
/dev/sda2  32768 1953521663 1953488896 931.5G Microsoft basic data

Partition 1 does not start on physical sector boundary.
The backup GPT table is not on the end of the device.

Disk /dev/sdb: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: Lexar SSD
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: gpt
Disk identifier: 2ACD08E6-F349-4A12-A512-08B78EBDECC2

Device        Start       End   Sectors  Size Type
/dev/sdb1      2048   1087487   1085440  530M Windows recovery environment
/dev/sdb2   1087488   1292287    204800  100M EFI System
/dev/sdb3   1292288   1325055     32768   16M Microsoft reserved
/dev/sdb4   1325056  54841863  53516808 25.5G Microsoft basic data
/dev/sdb5  54843392 250068991 195225600 93.1G Linux filesystem

Disk /dev/sdc: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: SSD 870 EVO 1TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes

Disk /dev/sdd: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model:
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 19F84D14-FC72-4D91-A25B-24A22182000D

Device       Start       End   Sectors   Size Type
/dev/sdd1     2048   1050623   1048576   512M EFI System
/dev/sdd2  1050624 468860927 467810304 223.1G Microsoft basic data

Disk /dev/loop8: 349.69 MiB, 366678016 bytes, 716168 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

Disk /dev/loop9: 460.56 MiB, 482930688 bytes, 943224 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

Disk /dev/loop10: 460.56 MiB, 482930688 bytes, 943224 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

Disk /dev/loop11: 81.26 MiB, 85209088 bytes, 166424 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

Disk /dev/loop12: 91.69 MiB, 96141312 bytes, 187776 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

Disk /dev/loop13: 37.09 MiB, 38891520 bytes, 75960 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

Disk /dev/loop14: 45.93 MiB, 48160768 bytes, 94064 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

Disk /dev/loop15: 12.32 MiB, 12922880 bytes, 25240 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

Disk /dev/loop16: 53.24 MiB, 55824384 bytes, 109032 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

Disk /dev/loop17: 53.24 MiB, 55824384 bytes, 109032 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

Disk /dev/loop18: 428 KiB, 438272 bytes, 856 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

Disk /dev/loop19: 452 KiB, 462848 bytes, 904 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
(base) brcao@night:/$ wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.^C
(base) brcao@night:/$ ^C
(base) brcao@night:/$ sudo fsck /dev/sdd2
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:/$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
(base) brcao@night:/$ sudo mount /eData0
mount: /eData0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:/$ sudo fsck -N /dev/sdd2
fsck from util-linux 2.37.2
[/usr/sbin/fsck.ext4 (1) -- /eData0] fsck.ext4 /dev/sdd2
(base) brcao@night:/$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
(base) brcao@night:/$ sudo mount /eData0
mount: /eData0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:/$ sudo fsck -N /dev/sdd
fsck from util-linux 2.37.2
[/usr/sbin/fsck.ext2 (1) -- /dev/sdd] fsck.ext2 /dev/sdd
(base) brcao@night:/$ sudo mount /eData0
mount: /eData0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:/$ sudo fsck /dev/sdd2
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:/$ e2fsck -b 8193 /dev/ssd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: No such file or directory while trying to open /dev/ssd2
Possibly non-existent device?
(base) brcao@night:/$ e2fsck -b 8193 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Permission denied while trying to open /dev/sdd2
You must have r/w access to the filesystem or be root
(base) brcao@night:/$ sudo e2fsck -b 8193 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:/$ sudo e2fsck -b 32768 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:/$ sudo mount /eData0
mount: /eData0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:/$ sudo mount /dev/ssd2 /eData0
mount: /eData0: special device /dev/ssd2 does not exist.
(base) brcao@night:/$ sudo mount /dev/sdd2 /eData0
(base) brcao@night:/$ ls
bin   cdrom  eData0  home  lib32  libx32      media  opt   root  sbin  srv       sys  usr
boot  dev    etc     lib   lib64  lost+found  mnt    proc  run   snap  swapfile  tmp  var
(base) brcao@night:/$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
/dev/sdd2       224G   91G  133G  41% /eData0
(base) brcao@night:/$ cd /eData0/
(base) brcao@night:/eData0$ ls
'$RECYCLE.BIN'   CIFAR-10-images_n_cls_8_v0   Data  'System Volume Information'
(base) brcao@night:/eData0$ cd Data/
(base) brcao@night:/eData0/Data$ ls
checkpoints  datasets
(base) brcao@night:/eData0/Data$ cd checkpoints/
(base) brcao@night:/eData0/Data/checkpoints$ ls
XT  XT_Y2022M06D13Mon
(base) brcao@night:/eData0/Data/checkpoints$ cd ..
(base) brcao@night:/eData0/Data$ cd ..
(base) brcao@night:/eData0$ cd ..
(base) brcao@night:/$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
/dev/sdd2       224G   91G  133G  41% /eData0
(base) brcao@night:/$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0     4K  1 loop /snap/bare/5
loop1    7:1    0  63.3M  1 loop /snap/core20/1852
loop2    7:2    0  63.3M  1 loop /snap/core20/1879
loop3    7:3    0    73M  1 loop /snap/core22/607
loop4    7:4    0    73M  1 loop /snap/core22/617
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc5 during installation
UUID=01e59cb8-6129-401a-8a37-425fd6d75e93 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc2 during installation
UUID=5268-F655  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/sdd2 /eData0  ext4  defaults  0 0
"/etc/fstab" 13L, 704B                                                                        13,9          All
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# /etc/fstab: static file system information.
loop5    7:5    0 241.9M  1 loop /snap/firefox/2579
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc5 during installation
UUID=01e59cb8-6129-401a-8a37-425fd6d75e93 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc2 during installation
UUID=5268-F655  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/sdd2 /mnt0  ext4  defaults  0 0
/dev/s
"/etc/fstab" 14L, 709B                                                                        14,6          All
# /etc/fstab: static file system information.
loop6    7:6    0 241.5M  1 loop /snap/firefox/2605
loop7    7:7    0 349.7M  1 loop /snap/gnome-3-38-2004/137
loop8    7:8    0 349.7M  1 loop /snap/gnome-3-38-2004/140
loop9    7:9    0 460.6M  1 loop /snap/gnome-42-2204/102
loop10   7:10   0 460.6M  1 loop /snap/gnome-42-2204/99
loop11   7:11   0  81.3M  1 loop /snap/gtk-common-themes/1534
loop12   7:12   0  91.7M  1 loop /snap/gtk-common-themes/1535
loop13   7:13   0  37.1M  1 loop /snap/hunspell-dictionaries-1-7-2004/2
loop14   7:14   0  45.9M  1 loop /snap/snap-store/638
loop15   7:15   0  12.3M  1 loop /snap/snap-store/959
loop16   7:16   0  53.2M  1 loop /snap/snapd/18933
loop17   7:17   0  53.2M  1 loop /snap/snapd/19122
loop18   7:18   0   428K  1 loop /snap/snapd-desktop-integration/57
loop19   7:19   0   452K  1 loop /snap/snapd-desktop-integration/83
sda      8:0    0 931.5G  0 disk
├─sda1   8:1    0    16M  0 part
└─sda2   8:2    0 931.5G  0 part
sdb      8:16   0 119.2G  0 disk
├─sdb1   8:17   0   530M  0 part
├─sdb2   8:18   0   100M  0 part /boot/efi
├─sdb3   8:19   0    16M  0 part
├─sdb4   8:20   0  25.5G  0 part
└─sdb5   8:21   0  93.1G  0 part /var/snap/firefox/common/host-hunspell
                                 /
sdc      8:32   0 931.5G  0 disk
sdd      8:48   0 223.6G  0 disk
├─sdd1   8:49   0   512M  0 part
└─sdd2   8:50   0 223.1G  0 part /eData0
(base) brcao@night:/$ cd ~
(base) brcao@night:~$ ls
Apps  Data  Desktop  Documents  Downloads  eData0  Music  Pictures  Public  Repos  snap  Templates  Videos
(base) brcao@night:~$ cd eData0/
(base) brcao@night:~/eData0$ ls
(base) brcao@night:~/eData0$ cd ..
(base) brcao@night:~$ du -h eData0
4.0K    eData0
(base) brcao@night:~$ rm -r eData0
rm: remove write-protected directory 'eData0'? ^[[A^C
(base) brcao@night:~$ ^C
(base) brcao@night:~$ sudo rm -r eData0
(base) brcao@night:~$ mkdir /ssd0
mkdir: cannot create directory ‘/ssd0’: Permission denied
(base) brcao@night:~$ sudo mkdir /mnt0
(base) brcao@night:~$ sudo mkdir /mnt1
(base) brcao@night:~$ sudo vim /etc/
Display all 239 possibilities? (y or n)
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ sudo mount /mnt0
mount: /mnt0: /dev/sdd2 already mounted on /eData0.
(base) brcao@night:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
/dev/sdd2       224G   91G  133G  41% /eData0
(base) brcao@night:~$ sudo unmount /eData0
sudo: unmount: command not found
(base) brcao@night:~$ sudo umount /eData0
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc5 during installation
UUID=01e59cb8-6129-401a-8a37-425fd6d75e93 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc2 during installation
UUID=5268-F655  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/sdd2 /mnt0  ext4  defaults  0 0
/dev/sdc /mnt1  ext4    defaults        0 0
"/etc/fstab" 14L, 735B                                                                        14,32-43      All
(base) brcao@night:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
(base) brcao@night:~$ sudo mount /mnt0
mount: /mnt0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:~$ sudo fsck /dev/sdd2
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:~$ e2fsck -b 32768 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Permission denied while trying to open /dev/sdd2
You must have r/w access to the filesystem or be root
(base) brcao@night:~$ sudo e2fsck -b 32768 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:~$ sudo mount /mnt0
mount: /mnt0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:~$ sudo vim /etc/fstab
(base) brcao@night:~$ ls
ls           lsb_release  lsinitramfs  lslogins     lsmod        lspci        lsusb
lsattr       lscpu        lsipc        lsm2bin      lsns         lspcmcia
lsblk        lshw         lslocks      lsmem        lsof         lspgpot
(base) brcao@night:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0     4K  1 loop /snap/bare/5
loop1    7:1    0  63.3M  1 loop /snap/core20/1852
loop2    7:2    0  63.3M  1 loop /snap/core20/1879
loop3    7:3    0    73M  1 loop /snap/core22/607
loop4    7:4    0    73M  1 loop /snap/core22/617
loop5    7:5    0 241.9M  1 loop /snap/firefox/2579
loop6    7:6    0 241.5M  1 loop /snap/firefox/2605
loop7    7:7    0 349.7M  1 loop /snap/gnome-3-38-2004/137
loop8    7:8    0 349.7M  1 loop /snap/gnome-3-38-2004/140
loop9    7:9    0 460.6M  1 loop /snap/gnome-42-2204/102
loop10   7:10   0 460.6M  1 loop /snap/gnome-42-2204/99
loop11   7:11   0  81.3M  1 loop /snap/gtk-common-themes/1534
loop12   7:12   0  91.7M  1 loop /snap/gtk-common-themes/1535
loop13   7:13   0  37.1M  1 loop /snap/hunspell-dictionaries-1-7-2004/2
loop14   7:14   0  45.9M  1 loop /snap/snap-store/638
loop15   7:15   0  12.3M  1 loop /snap/snap-store/959
loop16   7:16   0  53.2M  1 loop /snap/snapd/18933
loop17   7:17   0  53.2M  1 loop /snap/snapd/19122
loop18   7:18   0   428K  1 loop /snap/snapd-desktop-integration/57
loop19   7:19   0   452K  1 loop /snap/snapd-desktop-integration/83
sda      8:0    0 931.5G  0 disk
├─sda1   8:1    0    16M  0 part
└─sda2   8:2    0 931.5G  0 part
sdb      8:16   0 119.2G  0 disk
├─sdb1   8:17   0   530M  0 part
├─sdb2   8:18   0   100M  0 part /boot/efi
├─sdb3   8:19   0    16M  0 part
├─sdb4   8:20   0  25.5G  0 part
└─sdb5   8:21   0  93.1G  0 part /var/snap/firefox/common/host-hunspell
                                 /
sdc      8:32   0 931.5G  0 disk
sdd      8:48   0 223.6G  0 disk
├─sdd1   8:49   0   512M  0 part
└─sdd2   8:50   0 223.1G  0 part
(base) brcao@night:~$ sudo mount /mnt0
mount: /mnt0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:~$ sudo fsck -N /dev/sdd2
fsck from util-linux 2.37.2
[/usr/sbin/fsck.ext4 (1) -- /mnt0] fsck.ext4 /dev/sdd2
(base) brcao@night:~$ sudo mount /mnt0
mount: /mnt0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:~$ e2fsck -b 163840 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Permission denied while trying to open /dev/sdd2
You must have r/w access to the filesystem or be root
(base) brcao@night:~$ sudo e2fsck -b 163840 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:~$ e2fsck -b 8193 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Permission denied while trying to open /dev/sdd2
You must have r/w access to the filesystem or be root
(base) brcao@night:~$ sudo e2fsck -b 8193 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:~$ sudo e2fsck -b 32768 /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:~$ fsck.ext4 -v /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext4: Permission denied while trying to open /dev/sdd2
You must have r/w access to the filesystem or be root
(base) brcao@night:~$ sudo fsck.ext4 -v /dev/sdd2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdd2

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/sdd2 contains a vfat file system labelled 'eData'
(base) brcao@night:~$ sudo mount /mnt0
mount: /mnt0: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error.
(base) brcao@night:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
bryanbocao commented 1 year ago 
(base) brcao@night:~$ sudo mount /dev/sdd2 /mnt0
(base) brcao@night:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           4.7G  1.8M  4.7G   1% /run
/dev/sdb5        92G   88G     0 100% /
tmpfs            24G     0   24G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb2        96M   31M   66M  32% /boot/efi
tmpfs           4.7G   72K  4.7G   1% /run/user/1000
/dev/sdd2       224G   91G  133G  41% /mnt0

Reference: https://unix.stackexchange.com/questions/315063/mount-wrong-fs-type-bad-option-bad-superblock