Mounted file system but no mount 'tick' and not selectable

  • Hello,


    I have a new USB drive plugged in to my Raspberry PI. Have wiped and created the EXT4 file system for the device and though I can see the filesystem listed, it doesn't have a 'tick' under the 'Mounted' column and has no mount point. Under 'Available' there is just a dash and status says 'Online'. I'm not able to create a shared folder for this device because it's not shown in the drop down. Any advice appreciated.


    Thanks.

    • Official Post

    I have a new USB drive plugged in to my Raspberry PI. Have wiped and created the EXT4 file system for the device and though I can see the filesystem listed, it doesn't have a 'tick' under the 'Mounted' column and has no mount point. Under 'Available' there is just a dash and status says 'Online'. I'm not able to create a shared folder for this device because it's not shown in the drop down. Any advice appreciated.

    How many units and how are they connected to the Raspberry? If they are connected directly via USB you may have power supply problems.

  • Hello, It would just be 2 units. But I am doing this with just the one drive (the new one) plugged in. And have used fine with 2 drives previously (am replacing the old one as 5+ years old and starting to show bad sectors). Thanks.

    • Official Post

    A Raspberry does not provide enough power for two USB mechanical drives simultaneously. You must use an external power supply, search the forum, there is information about this.

    • Official Post

    I have a new USB drive plugged in to my Raspberry PI. Have wiped and created the EXT4 file system for the device and though I can see the filesystem listed, it doesn't have a 'tick' under the 'Mounted' column and has no mount point

    If it is not a power issue, did you mount the filesystem?

  • A Raspberry does not provide enough power for two USB mechanical drives simultaneously. You must use an external power supply, search the forum, there is information about this.

    Well that does scupper plans to use the two drives (I was using two previously, but there you go). But even so, just having the one drive connected (the new one) is still producing this problem.


    What's the optimum set up for use with RPIs then? Am I best to look into a SATA set up?


    If it is not a power issue, did you mount the filesystem?

    I did indeed. As I say, went through the steps I've followed previously but the mount 'tick' just isn't showing. Drive says 'online'.


    Thanks both for responses.

    • Official Post

    that does scupper plans to use the two drives

    Because? Buy a power supply for the hard drives, or a case.

    But even so, just having the one drive connected (the new one) is still producing this problem.

    There is something you are not doing right. Maybe you haven't mounted the filesystem after creating it, like macom said.

    What's the optimum set up for use with RPIs then?

    An external hard drive enclosure.

    Am I best to look into a SATA set up?

    Yeah. But it is not possible with Raspberry PI4. It will be with Raspberry PI5. Sata is always better than any USB connection. I would never trust a USB connection for a NAS.

  • Because? Buy a power supply for the hard drives, or a case

    Well because I've already bought the drive but I guess I'll just return it and use a powered enclosure isntead. Thanks for the tip.


    There is something you are not doing right. Maybe you haven't mounted the filesystem after creating it, like macom said

    I have mounted it. I have tried unmoutning and remounting. I've tried reformatting the drive and restarting the process but it just won't give it a mountpoint/mount check mark. Here's how it looks:


    image.png


    Thanks for the other advice re. R PIs. You live and learn.

  • Hi all,


    Since my last post, i've purchased a different hard drive to use with my powered USB HDD enclosure and I'm having the same problem. I have wiped the drive (EXT4), created/mounted the file system (that's all fine), but then it's not selectable to use as a shared folder. As with the previous screenshot, there's no mount point. I should say that this is just with the one drive (powered via the external enclosure). This set up worked fine for me in the past and essentially mimics my original setup (in my signature) but just swapping out the HDD in the enclosure, so I think something's going on with my OMV rather than hardware issues. Appreciate any further troubleshooting advice on this.


    Thanks.


    EDIT: just ssh'd into the machine and ran sudo fdisk -l and see the drive listed at the bottom:


    Code
    Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: ASM1153E
    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: AA3D8E97-2D35-427B-B060-8C9F3BF1EA39
  • votdev

    Added the Label OMV 6.x
  • Hello, thanks for the reply. Just the GUI (as before). I've seen a few posts that say to stick to the GUI but I just used the CLI to confirm the drive being registered by the system (I haven't actually mounted any drive with the CLI). Thanks.

  • lsblk:

    Code
    NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    sda           8:0    0  1.8T  0 disk
    └─sda1        8:1    0  1.8T  0 part
    mmcblk0     179:0    0 29.7G  0 disk
    ├─mmcblk0p1 179:1    0  256M  0 part /boot
    └─mmcblk0p2 179:2    0 29.5G  0 part /

    blkid:

    Code
    /dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="0B22-2966" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="39b8aa0c-01"
    /dev/mmcblk0p2: LABEL="rootfs" UUID="3ad7386b-e1ae-4032-ae33-0c40f5ecc4ac" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="39b8aa0c-02"
    /dev/sda1: UUID="805bdd45-eb02-4b7c-ab0b-af0e7df30b3f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cfd553a5-235d-4502-b859-5cf7b32e5bda"

    Thanks.

  • Code
    proc            /proc           proc    defaults          0       0
    PARTUUID=39b8aa0c-01  /boot           vfat    defaults          0       2
    PARTUUID=39b8aa0c-02        /    ext4    noatime,nodiratime,defaults    0 1
    # a swapfile is not a swap partition, no line here
    #   use  dphys-swapfile swap[on|off]  for that
    # >>> [openmediavault]
    /dev/disk/by-uuid/fef97aeb-b887-4334-bdcb-ca42c0c70724        /srv/dev-disk-by-uuid-fef97aeb-b887-4334-bdcb-ca42c0c70724    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
    # <<< [openmediavault]

    Thanks.

  • EDIT: just ssh'd into the machine and ran sudo fdisk -l and see the drive listed at the bottom:

    /dev/sda1: UUID="805bdd45-eb02-4b7c-ab0b-af0e7df30b3f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cfd553a5-235d-4502-b859-5cf7b32e5bda"

    This doesn't add up:

    Your output from fdisk shows NO PARTITION on the drive except that it has a GPT header.

    This is how it should look if it was partitioned:


    UNLESS, you didn't post the complete output of sudo fdisk -l /dev/sda

  • but just swapping out the HDD in the enclosure, so I think something's going on with my OMV rather than hardware issues.

    Disk model: ASM1153E

    Let me throw darts here:

    You swapped the drive inside the enclosure and reuse it to attach to OMV?

    If you did, the issue isn't OMV, it's the enclosure. The Disk model that is passing to OMV is still the same but the UUID of the drive, surely is different.


    OMV/Debian will want to see the UUID that you have mentioned on fstab:

    Code
    # >>> [openmediavault]
    /dev/disk/by-uuid/fef97aeb-b887-4334-bdcb-ca42c0c70724        /srv/dev-disk-by-uuid-fef97aeb-b887-4334-bdcb-ca42c0c70724    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
    # <<< [openmediavault]


    But instead, your drive is passing (according to blkid)

    Code
    /dev/sda1: UUID="805bdd45-eb02-4b7c-ab0b-af0e7df30b3f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cfd553a5-235d-4502-b859-5cf7b32e5bda"


    SO, please post the output of:

    sudo omv-showkey fstab


    sudo omv-showkey mntent


    sudo fdisk -l /dev/sd

  • Thanks for the help. I've tried the USB enclosure with the new drive in other machines and it works on those. It worked with the previous set up, as I say it was just the drive that needed swapping. This is now the 2nd brand new HDD I'm having the issue with. Both this one and the previous one I'd purchased worked fine on other machines.


    I've even tried wiping the new HDD and creating the ext4 partition in Ubuntu. Have dragged some files there, seems to be working fine. I then try it with my OMV machine and I can mount it in there but it's the same issue. I'm not able to select it for a file system.


    If there seems to be some discrepancy between the outputs i've pasted across posts, I wonder if it's because I've accidentally left the other main working drive in while doing the command line. I don't think I did but could be that, sorry if that's the case!


    Anyway, here's the outputs of the commands you've asked for. Error with the last one i'm afraid.


    sudo omv-showkey fstab:



    sudo omv-showkey mntent:



    sudo fdisk -l /dev/sd:

    Code
    fdisk: cannot open /dev/sd: No such file or directory


    Thank you so much again!

  • For what it's worth here's full the output of sudo fdisk -l /dev/sda. Perhaps, as you suggested, I have mis-pasted in my previous posts! Sorry about that.


    Code
    Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: ASM1153E        
    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: A5B921C0-050B-42E9-BF76-528917DCF499
    
    Device     Start        End    Sectors  Size Type
    /dev/sda1   2048 3907028991 3907026944  1.8T Linux filesystem
  • Anyway, here's the outputs of the commands you've asked for. Error with the last one i'm afraid.

    Let's be practical:

    According to the outputs and the OMV dB (those commands), you should have 2x drives mounted and visible on the GUI.

    Both UUIDs match from either omv-showkey mntent and fstab



    This will have to be seen on the GUI filesystems unless you are removing drives.

    OMV, expects both drives to be seen all the time (unless you use the USB backup plugin on one of them, which I don't think is the case)


    So, powerdown the Pi, plug both drives and boot up.


    Show again, the outputs of:


    blkid

    lsblk

    cat /etc/fstab

    sudo omv-showkey fstab

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!