Wrong FS type from mount / Losing mount setup

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Wrong FS type from mount / Losing mount setup

      Hello everyone. The past couple of months I have the issue that my /dev/sdb2 is not mounting during boot (while /dev/sdc2 does).

      I am running Erasmus (3.0.99 - kernel 4.9.0.0) with 3 HDDs: one for OMV (sda1) and 2 2TB HDDs setup as plain ext4 (no RAID, just rsync copying sdb2 to sdc2 every night).

      I managed to umount sdb2, do e2fsck (no errors), add the mount option in /etc/fstab and then when mounting back it worked fine (I could see my SMB shares on the drive from windows and from OM web front-end)

      When rebooting I get that sdc2 cannot because of wrong fs type, etc. giving the message:
      mount: wrong fs type, bad option, bad superblock on /dev/sdc2,
      missing codepage or helper program, or other error

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

      Trying dmesg | tail gives:

      [ 35.547235] ip_tables: (C) 2000-2006 Netfilter Core Team
      [ 36.555828] Initializing XFRM netlink socket
      [ 37.380756] Netfilter messages via NETLINK v0.30.
      [ 37.388209] ctnetlink v0.93: registering with nfnetlink.
      [ 115.207536] EXT4-fs (sdc2): Unrecognized mount option "noe$" or missing value
      [ 406.466475] EXT4-fs (sdc2): Unrecognized mount option "noe$" or missing value
      [ 435.598777] EXT4-fs (sdc2): Unrecognized mount option "noe$" or missing value
      [ 435.599032] EXT4-fs (sda2): unable to read superblock
      [ 1073.461794] EXT4-fs (sdc2): Unrecognized mount option "noe$" or missing value
      [ 2088.678864] EXT4-fs (sdc2): Unrecognized mount option "noe$" or missing value

      root@server:~# e2fsck /dev/sdc2
      e2fsck 1.43.3 (04-Sep-2016)
      /dev/sdc2: clean, 112734/61054976 files, 237805693/244190390 blocks

      root@server:~# fdisk -l

      Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: 0x6f668dc7

      Device Boot Start End Sectors Size Id Type
      /dev/sda1 * 2048 943736831 943734784 450G 83 Linux
      /dev/sda2 943738878 976771071 33032194 15.8G 5 Extended
      /dev/sda5 943738880 976771071 33032192 15.8G 82 Linux swap / Solaris

      Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 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
      Disklabel type: dos
      Disk identifier: 0x22d354ff

      Device Boot Start End Sectors Size Id Type
      /dev/sdb2 2048 1953523711 1953521664 931.5G 83 Linux

      Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 0x08ca6e72

      Device Boot Start End Sectors Size Id Type
      /dev/sdc2 2048 1953525167 1953523120 931.5G 83 Linux

      root@server:~# lsof /dev/sdc2

      gives nothing

      root@server:~# blkid
      /dev/sda1: UUID="ddaf4f07-c50f-41c8-b1da-d1599c5cbfda" TYPE="ext4" PARTUUID="6f668dc7-01"
      /dev/sda5: UUID="d3ba9191-b42c-4b0a-9b79-6172f1cf35f0" TYPE="swap" PARTUUID="6f668dc7-05"
      /dev/sdb2: UUID="c7bf35bc-0276-454a-b2cb-d5750ce3c91e" TYPE="ext4" PARTUUID="22d354ff-02"
      /dev/sdc2: UUID="9bdcb397-6854-4e3d-867a-8a9160c2e2d4" TYPE="ext4" PARTUUID="08ca6e72-02"

      root@server:~# more /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/sda1 during installation
      UUID=ddaf4f07-c50f-41c8-b1da-d1599c5cbfda / ext4 errors=remount-ro 0 1
      # swap was on /dev/sda5 during installation
      UUID=d3ba9191-b42c-4b0a-9b79-6172f1cf35f0 none swap sw 0 0
      tmpfs /tmp tmpfs defaults 0 0
      # >>> [openmediavault]

      /dev/disk/by-id/ata-Hitachi_HDS721010DLE630_MSE5235V0KU94E-part2 /srv/dev-disk-by-id-ata-Hitachi_HDS721010DLE630_MSE5235V0KU94E-part2 ext4 defaults,nofail,user_xattr,no
      exec,acl 0 2
      /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW30604150-part2 /srv/dev-disk-by-id-ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW30604150-part2 ext4 defaults,nofail,user_xattr,noe$
      /dev/disk/by-id/ata-ST3500830AS_9QG5274W-part2 /srv/dev-disk-by-id-ata-ST3500830AS_9QG5274W-part2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota
      =aquota.group,jqfmt=vfsv0,acl 0 2



      What am I missing ? How come every reboot (well not every but every 3-4 reboots) one of the sdb/c will not mount properly ?

      Thanks,
      -Nikos