Posts by BT6600

    Regarding access via hostname, I can only say a few things. The first thing I would do is modify the hostname to one without capital letters. Capital letters can cause problems in some cases. The second thing is that Windows can give you problems if you had previously configured that host with the same IP.


    Regarding docker, etc., you can read this thread, it's old, but it seems like you haven't been to the forum in a while or haven't updated your server. You should update your server more often.


    Thanks yes I am up to date now on the latest version at 7.x
    I did have my previous machine named openmediavault on the same IP when I was using the previous version. I flushed the DNS on that machine but that did not seem to help any other ideas you have on that?

    I have recently installed a fresh system and trying to get everything configured as before. I have a few issues. My network is simple just local LAN Main Pcs connect to my router that is about it.

    New OMV name is OMVNAS.Local

    My Router has the machines IP hard set to the name OMVNAS


    1. I can see the OMVNAS machine under my Windows 10 Network area from my main machine. Clicking it I am challenged for Creds which none of them work. If I \\192.x the same credentials work and I can get in and do what I want. Why am I unable to access via \\Name? I have another OMV Server named OMVGateway on my network and I can see and get to it via name easily.
    I have tried flushing DNS on my main machine I am trying to connect from.

    2. I installed OMVExtras I expected to see a drop down below that showing me Portainer and Yacht but I don't see a drop down at all. Why are those not showing? Thanks


    Here is the error I get when I try to connect with known password:

    [Window Title]

    Open Folder


    [Content]

    \\OMVNAS is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.


    Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.



    [OK]

    yes, use NTFS disk on debian is only recomended to facilitate copy of data to other data disk first/one time.


    NTFS is not POSIX filesystem and you only have problems sharing data or using this data on dockers. so please consider to use EXt4 or other well supported Filesystem on debian.

    Yep will plan a switch after upgrade I just use NTFS when I installed because that was all I knew at the time.

    I am on version 4.1. I tried an in place upgrade but it failed. I have decided to just do a complete reinstall since I am this far behind but I have questions.

    1. the install media will wipe the current OS disk completely during installation?

    2. Should I unmount my drives on 4.1 before I start the installation process? I have several NTFS Raid 1 Disk pairs. I assume I should unmount those first. During the reinstall process I intend to only have the OS drive plugged in, do the install, then start plugging in the other drives and adding them to the 7.x system.


    Thanks

    I don't know what exactly "pairs" of units means. but once OMV is reinstalled you should be able to connect any disk, boot the system and mount existing file systems. Do not create filesystems or you will delete all data, just mount existing filesystems in the OMV GUI.

    If those file systems are going to be permanently mounted on OMV, I would recommend not using NTFS and replacing it with native Linux file systems.

    Thanks by pairs I mean they are mirrored pairs 2 disks in mirrored configuration. How do I add those back? If the disks are in NTFS how do I convert to the Linux file system? Or do I have to clean the files off of the disk first?

    My machine will not fully boot it will post but then cannot find the boot drive. I dont think the BIOS sees it either because I have tried all the ones it can see. Machine will POST then go to a blinking cursor after a while it will say reboot and select proper boot device. I have a new SSD.
    My question is this before it died I had 3 drive pairs and some random disks all in NTFS.

    If I install the new SSD to be the OS and leave everything else unplugged. Then go plug some drives in is it going to be easy to reintroduce those drive pairs to the newly installed system or how do I go about making things right again without losing data?

    I recently upgraded from OMV 5.6 to the latest version this was an in-place upgrade. Portainer was upgraded along with that. In Portainer I run an Emby server container. This was all working in OMV 5.6.

    My server is simple and internal only I have the internal OS drive in EXT4 and an external disk NTFS that houses movies etc. Currently, nothing plays if it is housed on the external disk. If I move the file to the EXT4 disk it plays fine. This leads me to think some permissions errors are occurring. When I try to run a movie file that previously worked I get the error message in Emby of
    No compatible streams are currently available. Please try again later or contact your system administrator for details.


    I looked at permissions for the file shares and compared to previous version screen shots nothing has changed. I have tried reapplying permissions to the shares that are on the external drive. All of my shares are SMB with Guest allowed (Public), The shares also have Inherit ACLs and Inherit permissions(tried this with and without originally it was not in place).


    My Docker compose is pretty simple just pointing to the folder directories path for movie files.
    This could be an Emby issue but sure seems like permissions. Thanks in advance for taking a look as I am stumped.

    Thanks all I will check out these possible resolutions. I wonder if Docker is being restarted before OMV? because When I start the maintenance mode type startup I can see Docker restarting there. Also i would assume that it restarted with the machine because the containers are running they just cant get to their config files it would seem.

    This is a laptop with one disk 2 partitions one for OMV one for data. OMV still shows all drives and shares in good working order even when Docker containers cannot get to them. The logs for the containers will say Access denied.

    "I added a docker systemctl override to wait for local storage a few weeks ago" Not sure what this means or if it still applies.

    I am using OMV 5 on a test server/laptop. I have portainer and Docker running on this server. Whenever I go to OMV and reboot or restart OMV the laptop reboots however the docker containers are unable to find their data volumes which are set to persistent. This causes the docker images to think that they are brand new and are ready for their first configuration.I can sometimes see permissions errors in the emby containers log. The other way that I know it is a permissions error is that I have created Shares in OMV for each of my Emby areas like movies or TV Shows these shares are open to anyone and can be loaded from my Windows 10 pc. When it is working correctly I can see the files on these shares and interact with them. When it is not working correctly it seems like the shares are empty.

    I resolve this issue by doing a series of reboots and hard shutdowns and finally the containers come back the way that I left them. I have not found the right combination to bring the connections back as it certainly seems to be a permissions error. Right now the only way that I think it reliably comes back is if I do a hard power down and then power on with the lid open watching Linux warm up, I think when it asks to go into some sort of maintenance mode during the warm up that is the only time the permissions get fixed. I dont think that it asks to do this every time.


    Is this a bug? is there something that I can do to make sure this doesn't happen again? I want to run containers on my other OMV server but this issues keeps me from thinking this is reliable enough to do so. Thanks.



    Emby docker compose


    ---
    version: "2.1"
    services:
    emby:
    image: linuxserver/emby
    container_name: emby
    environment:
    - PUID=0
    - PGID=0
    - TZ=America/Chicago
    - UMASK_SET=022 #optional
    volumes:
    -
    /srv/dev-disk-by-id-ata-WDC_WD5000LPVT-22G33T0_WD-WX71C6271958-part6/appdata/Emby:/config
    -
    /srv/dev-disk-by-id-ata-WDC_WD5000LPVT-22G33T0_WD-WX71C6271958-part6/TV_Shows:/data/tvshows
    -
    /srv/dev-disk-by-id-ata-WDC_WD5000LPVT-22G33T0_WD-WX71C6271958-part6/Movies:/data/movies
    ports:
    - 8096:8096

    restart: unless-stopped

    The server cannot find the boot drive. I went into the bios and selected the SSD Drive and it still wont boot. I even tried removing all of the drives from the system And the server still does not boot. It runs through the Bios and then goes to the prompt after a while of sitting it says it cannot find the boot drive. Tomorrow I am going to remove all of the other hardware and probably only plug the ssd drive in. Something seems to be majorly hosed though. At this point can I get the data off of my Previously raided drives since they were in mirror? Can I just connect them to another computer and see the data? This is my worst case if I have to reinstall everything. If that is the case then OMV has not left me with a good impression of itself.

    Yeah I posted twice for whatever reason every post I was making I was getting server errors. I was getting what looked like apache type server errors for some reason. So I created another post in another subforum. that one also errored. Looked later and they both went through so I am not sure what was going on there. Thanks for the answers.

    My box had hot swap drives so I removed both of the new drives but not the sata card. Still wont boot. In other research I dont think my mobo even has RAID but OMV let me RAID two drives anyway and I have been using those for 6 months. I will check the bios thanks.

    Noob question here so this may be in the wrong place.
    I have OMV setup on SSD on an Asus E35M1-M https://www.asus.com/Motherboards/E35M1M/ A mobo I had from an HTPC
    I had been running just fine.
    I then needed to add additional mirrored storage (Dont hate on my Raid choicd) :)
    I Purchased this card
    https://www.amazon.com/gp/prod…tle_o02_s00?ie=UTF8&psc=1


    It booted up and I could see the two new WD 4TB Red drives I added. I mounted one of the new drives. The second one threw an error which I did not capture. I tried to reboot hoping that would clear the issue. The system doesnt come back now. It boots and then only shows a cursor never joins the network etc.
    I am going to remove all of the new gear
    Questions I have
    1. Looking at this board now it doesnt say anything about RAID However I was able to successfully get two drives into RAID 1 on OMV. Do I need a MOBO that Specifically has Raid capabilities?


    2. Does the SATA port card I added need to have RAID capabilities?
    3. If I get a new MOBO does that need to have RAID and if I do go this route would the non raid SATA card work or do I also need to get a SATA card with RAID?


    Thank you for helping me out.

    I have been running OMV for a while, Nothing fancy followed technodad install guides. I needed to add additional drives to expand storage to do that I had to add a SATA card. (I was adding two new WD REDs 4TB)


    https://www.amazon.com/gp/prod…tle_o02_s00?ie=UTF8&psc=1


    I installed the sata card and plugged in the drives one of the drives worked and I was able to mount it in OMV. The other gave an error when I tried to mount it which I did not capture. So decided to reboot to see if that cleared the issue. Now The computer reboots and goes through the bios but then goes to a blinking cursor. It never joins the network and I cannot see it on my router as connected. I guess I will remove all of the hardware I put into it to see if it then boots back to normal. Anyone else got any advice at this point?

    So I have installed the disks as described above

    • fully update system (wipe function has been improved some versions ago)
    • wipe drives (quick)
    • create RAID1 (if you are sure you want RAID1)
    • create filesystem
    • enable SMART


    Which is a different way from what Technodad shows in his video
    So I have drives, I have RAID1, I have mounted Raid1 and my extra disk. They do both show as referenced NO though not sure what that means.


    My issue is still setting SMART on all of my drives when I go to that section I can flip the general toggle but then it will error when I try to save it forcing me to hard reboot it. Likewise if I select the devices under SMART it goes into a looking state and will eventually fail with a Communication failure error. I will then have to hard boot the machine again to get to a good state. It takes me to a login and locks the session. Any help would be appreciated.

    Still unable to get the drives set here. I created RAID and I mounted that and my one stand alone 500GB drive so all drives are mounted. I still cannot enable SMART I tried from the first smart tab under general. That failed. I also tried from the devices area under SMART section but it just spins for a bit and then tells me communication failure. I think I am close just not quite there yet.

    First time installing OMV I have setup the file system on all of my drives and I have mounted the drives(not sure if I am supposed to do that or not as 2 of them will be in RAID). I have done a quick wipe on all the drives. I am trying to enable SMART however when I go into that section and select devices at the top it spins for a while and says software failure and sends me to the login screen which doesn't let me in. Additionally this happens when I just stay on the SMART general screen and try to enable the switch there to turn on SMART a Hard reboot lets me get back in. Additionally if I just try to go in and setup RAID straight away in Mirroring using my two new WD Reds there are no drives listed under available drives to create RAID with. Thanks for the help.