error mounting disk

  • In that case, you can create a partition via CLI, format it and (hopefully) OMV will/should pick it.


    For that, and since you have a 6Tb disk, you can use "gdisk" instead of "fdisk" (gdisk deals better with >2Tb disks, IMO).


    apt install gdisk


    Then follow these instructions to create a GPT partition table and a partition with Linux signature for the whole partition:

    See only the Topics:

    Creating a new GPT partition table

    Creating a new partition

    How to manipulate gpt partition tables with gdisk and sgdisk on Linux - Linux Tutorials - Learn Linux Configuration


    After a reboot, goto OMV webGUI and you should be able to format the partition with ext4 FS and have it available.

  • I've been following this thread with interest, I think the issue here is related to #7 with the output from wipefs -n /dev/sdc this shows a PMBR (Protected Master Boot Record) this correlates to the original error in #1.


    #1 references a missing NTFS signature, this and the PMBR suggests that the drive was preformatted with NTFS.


    The way forward would be to run dd on the drive and write zeros to the whole drive, this is out of my remit as I use dban

    Raid is not a backup! Would you go skydiving without a parachute?


    OMV 5x amd64 running on an HP N54L Microserver

  • Hi Soma, well method worked perfectly. I guess your right, OMV is a bit of a bitch with the larger drives. Drive is now formated and mounted with NO error. Can't thank you enough for the help. Now the next thing is for me to figure out the best way to do a complete back of ALL my data ( Movies, Music, TV, Configs )

  • Having the same issue with a 3 Tb drive.

    I tried mounting the drive and then openmediavault crashes with the following error: 'Removing the directory '/' has been aborted, the resource is busy.' and the system reboots.

    Then I re-partioned and formatted the drive added it to fstab and rebooted so now the drive is visible in 'filesystem' but when I try to add a shared folder the drive is not showing up?

  • Man! I followed these instructions to a T, hoping they would work, but I'm still getting an error.


    I am running OMV 5 and have OMV installed on a 250GB Samsung SSD. I started with two drives, a WD Red and WD White (both 8TB) and used mergerfs to 'create' a single, 16TB drive. That drive has since been filled, so I recently added a 16TB Seagate Exos drive to my server.


    Unfortunately, when I installed it, formatted it through OMV (EXT4), etc., I can't get it to mount. It formats fine, it's detected by the OS, but when I try to mount, I get the same error 100% of the time:


    The people in r/selfhosted (reddit and Discord) have told me there's a salt issue, but I've tried all sorts of omv-salt commands to rectify that to no avail. I stumbled upon this post and it sounded SO similar to mine, so I used gdisk, created a partition table, etc., then deleted and re-added the drive through the OMV GUI. It formatted fine, so once it was done initializing, I tried mounting it and got this error AGAIN.


    I'm hoping to finally get it mounted so I can add its absolute path to mergerfs and open up another 16TB. Otherwise, my drives are full.


    If anyone can help, I would be indebted to you. Soma?

  • Ok, solved the problem.

    This is definitly a problem of/bug in the openmediavault interface.


    Solution:

    If the drive is visible within the 'drives' tab of the openmediavault interface do the following:

    Open a terminal within cockpit (or use the terminal display after startup) with the 'root' user.

    Discover the uuid of the drive by typing: blkid and remember the uuid of the drive you want to mount.

    See if the folder of this drive exists within the dev folder by typing: cd /dev/disk/by-uuid.

    Then type: ls -l and see if the uuid of the drive is listed (it should be since the drive is vissible).


    Now go to the folder srv with: cd /srv and see that a folder exists with the name dev-disk-by-uuid-<yourdrives UUID>.

    If it does not exist create it with: mkdir dev-disk-by-uuid-<yourdrives UUID> and give it the proper userrights (same userrights as the existing drives? -> list user rights of existing drives with: ls -l and change userrights with chmod u=rwx,g=rwx,o=rwx).


    Now edit fstab to ensure that the drive is mounted each time you start openmediavault with: pico /etc/fstab.

    Add a line at the end of fstab like this: /dev/disk/by-uuid/<yourdrives UUID> /srv/dev-disk-by-uuid-<yourdrives UUID> ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2

    Save the fstab file.


    Now create your own shared folders on this drive with: mkdir /srv/dev-disk-by-uuid-<yourdrives UUID>/<your shared folders name> and give it the proper userrights with chmod.


    To access this shared folder with Windows make it a samba share by editing the smb.conf file as follows: pico /etc/samba/smb.conf and copy the contents of an already samba share folder to the end of the file and edit it by replacing the path with: path = /srv/dev-disk-by-uuid-<yourdrives-UUID>/<your shared folders name>/ .


    Reboot the system and now your created folder is visible in Windows. However, the shared folder is NOT vissible within the openmediavault interface!

  • I have not read the whole post, but what you tell is working against OMV. No wonder that it causes problems.



    To access this shared folder with Windows make it a samba share by editing the smb.conf file as follows: pico /etc/samba/smb.conf and copy the contents of an already samba share folder to the end of the file and edit it by replacing the path with: path = /srv/dev-disk-by-uuid-<yourdrives-UUID>/<your shared folders name>/ .

    Really ????? Why do you use OMV if you do everything manually?


    To all of you reading the above post, ignore it please.

  • I really want to use the interface of openmediavault but I'm stuck at adding a new drive: the whole damn system reboots if I want to add a new drive!

    So to all: for now you can use this as a workaround until this bug is fixed.


    votdev: until you have a better answer/workaround for this bug I really want to ignore your kind of comments!

  • I really want to use the interface of openmediavault but I'm stuck at adding a new drive: the whole damn system reboots if I want to add a new drive!

    So to all: for now you can use this as a workaround until this bug is fixed.


    votdev: until you have a better answer/workaround for this bug I really want to ignore your kind of comments!

    Maybe explain what has happend AND how it can be reproduced. According to your posts i have the feeling you are doing things that work against how OMV internally works. Adding a 3 TiB disk via the UI is not rocket science, this is done thousands of times by OMV users already.


    I tried mounting the drive and then openmediavault crashes with the following error: 'Removing the directory '/' has been aborted, the resource is busy.' and the system reboots.

    You didn't tell us that you are trying to delete the mount point entry. This message only appears in that scenario; it is an indication that a system service or process, e.g. SMB, is accessing the file system. In that case you need to remove the SMB share, apply the settings, remove the share and only then the file system can be removed.


    But based on your posting i assume a process which is not managed by OMV is accessing the disk. So make sure this process is stopped before removing the file system.

  • chente

    Added the Label resolved

Participate now!

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