Beiträge von savellm

Zitat von chente

take a look here

https://wiki.omv-extras.org/do…nfiguring_a_windows_11_vm

I was missing the TPM button!

Thank you very much

Hi all,

I might be a bit dumb here, but I'm trying to install Win11 as a VM.

If I choose UEFI I get Windows cannot be installed on this PC

UEFI + Secure boot - I get Windows cannot be installed on this PC

No UEFI - I get Windows cannot be installed on this PC

I cant find a way to install Win11...

Can anyone help a n00b

Zitat von chente

I understood that you wanted to remove that drive from the pool because you have too much space. In that case you must follow that procedure.

Since there was data on that disk that you lost, you should have a backup to copy that data back to the pool.

If what you want is to recover that data from the parity disk, you will have to replace the disk, recover the data from the parity, and, later, if you want to remove that disk from the pool, follow the process to update the parity and copy the data again to the pool from the removed disk.

This is a bit confusing, I don't know if I explained myself clearly...

Yup I got it... Unless I have a backup of this failed drive, its better to replace and restore from Parity.

After this I can think about moving data off the drive and reducing my drive stack

Zitat von chente

Yes, but you must follow a special procedure to avoid losing parity.

I think this procedure is not on the wiki but you have it here. https://www.snapraid.it/faq#remdatadisk

umm not sure what it’s asking to do.

If that drive is dead and I can’t copy any files off of it. Is it better to just replace it and then copy files off after parity restores it?

Then I can remove it and keep it as a spare?

Zitat von gderf

Of course.

Is there a way I can just remove that drive if I dont need the space?

I still have 60tb left so debating about just removing the drive and spreading that data across the remaining drives?

Is this possible with SnapRAID and the parity I have running?

Zitat von gderf

Of course.

Sweet, I'll follow the guide from omv-extras seems pretty straight forward

Zitat von chente

On the omv-extras wiki https://wiki.omv-extras.org/do…are_for_drive_replacement

In the SnapRaid documentation. https://www.snapraid.it/faq#repdatadisk

Bit confused, but if that drive is dead and offline, can I replace it and restore files from my dual parity?

Zitat von chente

On the omv-extras wiki https://wiki.omv-extras.org/do…are_for_drive_replacement

In the SnapRaid documentation. https://www.snapraid.it/faq#repdatadisk

Thanks i'll take a look now

Hi all.

I have setup SnapRAID, this is up and running doing its daily scrub.

Recently I got an alert that my one drive has failed and is now offline. It is old so partially expected.

I have a new drive on its way, so just getting ready to replace the failed drive.

Is there any documentation on how to do a swap properly and cleanly?

Thanks in advance

Zitat von ryecoaaron

compose 6.7.5 is in the repo now and adds a hyperlink to each tcp port (should skip udp). The hyperlink works just like the kvm plugin - it gets the fqdn of the host from the OMV database. Seems to work better than portainer that on my system is just doing something like this - 0.0.0.0:28080 (which doesn't work).

Amazing, nice and quick!

Thank you so much

Forgot to report back, updating resolved it... thanks

ryecoaaron please can you create a little link button like KVM or something so you can click it like in Portainer and it'll open up your containers web UI?

Like SABnzbd or whatever, log into OMV, click the button and it opens in a new page, in case we forget the port or what not?

Zitat von ryecoaaron

good to hear.

Thank you very much tho, appreciate all you do for us

Zitat von ryecoaaron

What is the output of: lsmod | grep nvidia

root@omv:~# lsmod | grep nvidia

nvidia_modeset 1204224 0

video 65536 1 nvidia_modeset

nvidia_uvm 1216512 2

nvidia 35532800 362 nvidia_uvm,nvidia_modeset

drm 614400 7 drm_kms_helper,drm_vram_helper,ast,nvidia,drm_ttm_helper,ttm

But yeah got it resolved via re-running: sudo m-a prepare

Restarted Docker and all good again.

Ok so fixed it:

Went back to the guide and re-ran:

sudo m-a prepare

This worked and all good now. Thanks

Zitat von ryecoaaron

I can't think of anything that installing the kvm plugin would cause this. Kind of looks like your nvidia driver is not loaded. maybe rebooting would help.

Just rebooted to update to new OMV version, no joy, still same error message

Zitat von chente

Upgrade to openmediavault 6.4.0-2

Done will report back

Hi all,

I had my Jellyfin setup up and running well, utilising my P2000 to transcode when needed.

I installed KVM and then noticed that my docker container for Jellyfin will no longer start.

This is my compose:

---
version: "2.1"
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/London
      - JELLYFIN_PublishedServerUrl=10.0.0.10
      - NVIDIA_VISIBLE_DEVICES=all
    volumes:
      - /appdata/jellyfin:/config
      - /srv/mergerfs/data/media:/media
      - /transcoding:/transcoding
    ports:
      - 8096:8096
    restart: unless-stopped
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu]

This was working well, and I followed the guide to get my NVIDIA drivers installed fine.

But like I say since I installed KVM it no longer starts, this is the error from Portainer:

failed to deploy a stack: Network jellyfin_default Creating Network jellyfin_default Created Container jellyfin Creating Container jellyfin Created Container jellyfin Starting Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown

I'm not sure if the KVM is a red-herring or not as I didnt notice JF being down right away, it was a few days later.

Or an update that may have run.

Also not sure if just a good ol fashioned reboot of OMV would solve this or not?

I did restart docker and this did not help.

Hi all

Lately I've started getting this message every hour:

run-parts: /etc/cron.hourly/openmediavault-cleanup_sf_snapshots exited with return code 1

Do I need to do anything with this?

Like I say its only happening recently.

I have not tried restarting yet as my server is busy doing some heavy work so dont want to stop it yet.

Is this something I can fix?

Zitat von ryecoaaron

The openmediavault-unionfilesystem plugin pooled with mergerfs

The openmediavault-mergerfsfolders plugin pooled with mergerfs

So, with OMV 6.x, I combined them in the openmediavault-mergerfs plugin. This was mentioned in the 6.x plugin thread - omv-extras plugins - porting progress to OMV 6.x (done)

Thank you ryecoaaron

So I just created a folder and used most free space to get things to shift over each drive. Will test it out now. Appreciate it