File System Does Not Exists error on newly formatted drive

    • OMV 3.x
    • File System Does Not Exists error on newly formatted drive

      Hi,

      I bought a 2TB WD Passport drive at the weekend with the intention of using it as my main archive drive on my OMV Rpi 3.

      I've wiped the drive in 'physical disks' and created a file system in 'file systems' but when I try to mount it I get the following 'File system does not exists' error...


      Source Code

      1. Error #0:
      2. exception 'OMV\Exception' with message 'Failed to get the filesystem implementation for 'cce7017b-f2be-4c2f-8b4b-e3c17e139bac' or the filesystem does not exist.' in /usr/share/php/openmediavault/system/filesystem/filesystem.inc:855
      3. Stack trace:
      4. #0 /usr/share/openmediavault/engined/module/fstab.inc(84): OMV\System\Filesystem\Filesystem::assertGetImpl('cce7017b-f2be-4...')
      5. #1 [internal function]: OMVModuleFsTab->deleteEntry(Array)
      6. #2 /usr/share/php/openmediavault/engine/module/moduleabstract.inc(145): call_user_func_array(Array, Array)
      7. #3 /usr/share/openmediavault/engined/module/fstab.inc(44): OMV\Engine\Module\ModuleAbstract->execTasks('delete')
      8. #4 /usr/share/openmediavault/engined/rpc/config.inc(147): OMVModuleFsTab->stopService()
      9. #5 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      12. #8 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(879): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)
      13. #9 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
      14. #10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      15. #11 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
      16. #12 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
      17. #13 {main}
      Display All
      Also, the drive shows as 1.82TB instead of 2TB...is that correct?

      thanks,
      Darren
    • I still can't figure this one out - if anyone has any suggestions, that would be great.

      I've re-formatted the drive several times now. Each time I create a file system and try to mount the drive, I get the 'File system does not exist' error.

      I'm sure it's something simple, but I can't find any similar posts on here with a solution.
    • These are the bits relevant to the specific drive (at least I think so, let me know if i've missed anything)...


      fdisk...

      Source Code

      1. Disk /dev/sdb: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors
      2. Units: sectors of 1 * 512 = 512 bytes
      3. Sector size (logical/physical): 512 bytes / 512 bytes
      4. I/O size (minimum/optimal): 512 bytes / 512 bytes
      5. Disklabel type: gpt
      6. Disk identifier: 66C1382B-E30A-4E32-A1AD-4AF9AE32E53B
      7. Device Start End Sectors Size Type
      8. /dev/sdb1 2048 3906963422 3906961375 1.8T Linux filesystem
      blkid...

      Source Code

      1. /dev/sdb1: LABEL="DazDrive2" UUID="278221ea-4b22-489f-881d-e6aacea4d2b3" TYPE="ext4" PARTUUID="9f313324-733c-40ff-b85a-a4cd3c3800d8"
      2. /dev/mmcblk0: PTUUID="000b5098" PTTYPE="dos"
    • Assuming there is no data on the drive, do the following

      mkfs.ext4 /dev/sdb1
      mkdir /media/test
      mount /dev/sdb1 /media/test
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Dazzathedrummer wrote:

      I refreshed the GUI and it's there and its mounted!

      I wonder why it wouldn't work through the GUI?
      You need to unmount it from the command line and remount from the web interface if you want to use the drive in the web interface.
      umount /media/test/

      Must not be formatting correctly. Not sure why. Will have to test on my rpi.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Dazzathedrummer wrote:

      ...I'm still getting the 'file system does not exists' error if I unmount in command line and try to mount in the GUI.
      I'm working on a new RPi so I can test.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Looks like I might need to do a clean install. Another drive that was working fine suddenly disappeared and now refuses to mount.

      Also, if I try to look for updates, it sits on the 'checking' screen for about two minutes and then errors.

      I've only been using it as a plex server so far so it shouldn't take much to get back up - is there anyway that I can re-install remotely via ssh - or is it best to wipe the card?
    • Dazzathedrummer wrote:

      is there anyway that I can re-install remotely via ssh
      You could purge the openmediavault packages but I don't know if that would fix the issue.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Ok, the mystery continues!

      Clean install, 3.0.59.

      The new drive mounts perfectly, no errors - the old drive that was working perfectly gets this...


      Source Code

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v '/media/f3540206-a3c6-48d1-838f-2aca3ecca139' 2>&1' with exit code '32': mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.
      2. Error #0:
      3. exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v '/media/f3540206-a3c6-48d1-838f-2aca3ecca139' 2>&1' with exit code '32': mount: wrong fs type, bad option, bad superblock on /dev/sda1,
      4. missing codepage or helper program, or other error
      5. In some cases useful info is found in syslog - try
      6. dmesg | tail or so.' in /usr/share/php/openmediavault/system/process.inc:175
      7. Stack trace:
      8. #0 /usr/share/php/openmediavault/system/mountpoint.inc(135): OMV\System\Process->execute()
      9. #1 /usr/share/openmediavault/engined/module/fstab.inc(71): OMV\System\MountPoint->mount()
      10. #2 /usr/share/openmediavault/engined/rpc/config.inc(189): OMVModuleFsTab->startService()
      11. #3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      12. #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      13. #5 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      14. #6 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(880): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)
      15. #7 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
      16. #8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      17. #9 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
      18. #10 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
      19. #11 {main}
      Display All
    • This may be a un-related problem.

      I've noticed a couple of times that the power cable for my powered USB hub can be dodgy. Just before I re-installed OMV I noticed that the drive that I'm now having problems with was beeping, so I fiddled with the power cable and it stopped.

      I'm wondering if it dropped out while being written to and this has broken the file system. At the moment the drive only contains around 20 cd's that I've ripped, so I'm tempted to wipe it and start again (after fixing the power cable!).

      Is there a way to fix the file system while keeping the contents that would be simpler than starting from scratch?


      Edit: I just tried to mount from ssh and I'm getting a similar 'wrong FS type..' error, so I think it's genuinely broken.

      Edit2: I did some googling and ran fsck - problem fixed!

      So just to summarise all of the issues...

      After installing OMV 3.0.59 and adding, plexmediaserver, remote mount and VDR on a new RPi3 and applying all updates to Feb 14th, a new drive failed to mount plus other errors occurring throughout.
      Clean install fixed the problem although an un-related problem caused some confusion.

      Thanks for your help! - I'll report back if I get any more problems.

      The post was edited 2 times, last by Dazzathedrummer: Additional information ().