Posts by themagicm

    anyone have an actual fix for this? The one right above, lol, just delete that reply.


    I did the nfsver=3 on the nfs server and disabled NFSv4 @ OMV but that didnt help. On reboot the remote mount fails and Plex doesnt work along with other served out shares.

    I have OMV installed and configured with the remote mount plugin. I disabled NFSv4 and at the remote server I have nfs v3 enabled.


    When OMV reboots it cannot mount my NFS share. At the command line as root I can do a mount -a and it mounts fine.


    Error in syslog:

    Code
    Jan 28 14:23:30 omv-proxmox smbd[1374]: [2020/01/28 14:23:30.375812, 0] ../source3/smbd/service.c:755(make_connection_snum)
    Jan 28 14:23:30 omv-proxmox smbd[1374]: canonicalize_connect_path failed for service ProxMoxData, path /srv/5c237b85-8e5d-4120-979d-c51219ee3205/ProxMoxData/backups


    Stumped.

    ananas:


    I wish I saw this earlier. After OMV 3.x to 4.x upgrade my RAID6 didnt show up in filesystem. I reinstalled 4.x from scratch and couldnt mount my RAID6.


    My previous 3.x install worked fine but stopped wanting to upgrade. So I manually did an apt-get upgrade which got me to 4.x but it still was acting weird. Raid6 not there.


    Fresh install same issue.
    What fixed it was doing :


    wipefs -n /dev/md127


    then every time it came back with a zfs signature, delete:
    wipefs -b -o <signature> -t noext4 /dev/md127


    Did that about 10 times until it came back clean. Then it was immediately seen in "Filesystems" and I was able to mount.


    THANK YOU THOMAS!!! A+++++++

    I have an R410 and created a RAID 6 with 4 disks. I cloned an R310 server's boot USB device and fired up the R410. I changed its hostname and IP, configured Plex, setup an rsync process to sync the r410 with the r310. All seemed well. I powered down the r410 and a decided it was time to rsync because I have additional media to sync.


    After powering up, my filesystem says status "missing".


    blkid on the r410 says:

    Code
    root@openmediavault-r410:~# blkid
    /dev/sdb1: UUID="88ab6787-760b-40b0-bdf3-893769eb1276" TYPE="ext4" PARTUUID="31e62b09-01"
    /dev/sdb5: UUID="cbffa3e8-45f8-4c4a-8522-4f73ac7954d2" TYPE="swap" PARTUUID="31e62b09-05"
    root@openmediavault-r410:~# fdisk -l|grep -i "Disk"
    Disk /dev/sda: 3.7 TiB, 3999688294400 bytes, 7811891200 sectors
    Disk /dev/sdb: 14.6 GiB, 15664676864 bytes, 30595072 sectors
    Disklabel type: dos
    Disk identifier: 0x31e62b09





    fdisk -l shows:


    Now, the r410 used to reference drives in the nomenclature the r310 did. The RAID setup is different between the two. R310 uses a RAID config created in OMV. The r410 uses DELL's PERC hardware.


    OMV shows:
    https://ibb.co/ggqrXf


    fstab shows:


    syslog shows:

    Code
    Oct 29 20:13:11 openmediavault-r410 systemd[1]: Dependency failed for /srv/dev-disk-by-label-data.
    Oct 29 20:14:28 openmediavault-r410 systemd[1]: Expecting device dev-disk-by\x2dlabel-data.device...
    Oct 29 20:15:58 openmediavault-r410 systemd[1]: Job dev-disk-by\x2dlabel-data.device/start timed out.
    Oct 29 20:15:58 openmediavault-r410 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-data.device

    lsblk shows:


    Code
    root@openmediavault-r410:/var/log# lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sdb 8:16 1 14.6G 0 disk
    ├─sdb2 8:18 1 1K 0 part
    ├─sdb5 8:21 1 656M 0 part [SWAP]
    └─sdb1 8:17 1 14G 0 part /srv/8bb88c6117a2b68f182d4073dc81efff
    sr0 11:0 1 1024M 0 rom
    sda 8:0 0 3.7T 0 disk


    Its as if multipath is screwing up my stuff.


    Any clue as to how to get my data disks back?

    Trying to move from FreeNAS to OMV so I decided to test on a spare server.I have a 60gb boot drive with OMV installed. Boots up fine with only 1 HD. If plug in a 2TB drive to set it up as a "share" it fails on boot.
    If I hotswap the 2TB, I can quick wipe it but then when I try to setup a share I cannot select the hard drive in the browser. Its like the interface isnt working correctly. On reboot with a hard drive in as a data drive, I see the below pictured error.



    pic of error:
    https://imgur.com/a/aNQMt