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...



    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.

    • Offizieller Beitrag

    Did you wipe the drive in the physical disks tab?

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Not sure. Post the output of (as root):


    fdisk -l
    blkid

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • These are the bits relevant to the specific drive (at least I think so, let me know if i've missed anything)...



    fdisk...

    Code
    Disk /dev/sdb: 1.8 TiB, 2000365289472 bytes, 3906963456 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: gpt
    Disk identifier: 66C1382B-E30A-4E32-A1AD-4AF9AE32E53B
    Device     Start        End    Sectors  Size Type
    /dev/sdb1   2048 3906963422 3906961375  1.8T Linux filesystem

    blkid...

    Code
    /dev/sdb1: LABEL="DazDrive2" UUID="278221ea-4b22-489f-881d-e6aacea4d2b3" TYPE="ext4" PARTUUID="9f313324-733c-40ff-b85a-a4cd3c3800d8"
    /dev/mmcblk0: PTUUID="000b5098" PTTYPE="dos"
    • Offizieller Beitrag

    Assuming there is no data on the drive, do the following


    mkfs.ext4 /dev/sdb1
    mkdir /media/test
    mount /dev/sdb1 /media/test

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    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 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    ...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 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    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?

    • Offizieller Beitrag

    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 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    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...



    • Offizieller Beitrag

    Try mount -v /media/f3540206-a3c6-48d1-838f-2aca3ecca139 from the command line.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • 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.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!