Beiträge von edterbak

Zitat von ryecoaaron

Uh, the OP is using a helios64. My instructions only apply to that board (well, any rk3399 board).

No. The version of zfs in the debian repos does not support the 5.10 kernel. Install the proxmox kernel/remove debian kernel using omv-extras and you will be good to go.

Great! your right. I was to quick with my judgement thinking the problem is the same. It was only some time after I posted, I noticed the very first sentence of the OP. THen it hit me. My bad, sorry for that.

On the flipside. Your last reply solved the issue for me completely.
In OMV-Extras > Kernel > Install Proxmox kernel.

reboot

In OMV extras > Kernel > set as default (the pve kernel)

remove non-Proxmox kernels.

Update everything

reboot

Check the current set kernel.

All 100% working.

Thank you for the latest post. It helped me a lot. Despite me starting off on the wrong foot.

From withing Proxmox, I just did a restore of an earlier backup of OMV. (OMV is a vm inside my proxmox, passing through pci sata controller to OMV)

Everything is fine now again.

The rollback took me back to this kernel: Debian GNU/Linux, with Linux 5.6.0-0.bpo.2-amd64. But it is fine.

question remaining. Was this a random issue? or can I update again and expect it to work normally.

Plugin I use currently is the "openmediavault-zfs 5.0.5"

Zitat von ryecoaaron

The first three lines do the install. The fourth line checks to see if the zfs module is loaded. The last nine lines are output from the lsmod command.

Wait, I am running OMV inside Proxmox.

This is the kernel I am running:

Debian GNU/Linux, with Linux 5.10.0-0.bpo.3-amd64

I have been running this setup now for 1y+.

The error cause is probably not the same as Armbian (Helios 64 NAS) as the topic started describes. Obviously

The error message is the same, but the setup is different. probably the solution as well. Is this solvable?

This is the output from the third line

root@openmediavault:~# sudo modprobe zfs
modprobe: FATAL: Module zfs not found in directory /lib/modules/5.10.0-0.bpo.3-a                md64
root@openmediavault:~#

Just to be complete. this is the error message I receive when clicking on the ZFS plugin

aaarh.. nah, first line gives me this:

sudo apt-get install linux-headers-current-rockchip64
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
E: Kan pakket linux-headers-current-rockchip64 niet vinden

<niet vinden = cant find>

second line works:

sudo apt-get install dkms zfs-dkms
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
dkms is reeds de nieuwste versie (2.6.1-4).
dkms staat ingesteld op handmatig geïnstalleerd.
zfs-dkms is reeds de nieuwste versie (0.8.6-1~bpo10+1).
zfs-dkms staat ingesteld op handmatig geïnstalleerd.
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd       .

Ok, I will do it now . report back soon thanks for the quick reply

Hi ryecoaaron

I have the exact same issue after updating just now.

Your previous post.

Do you need me to type in each of the 13 lines in the spoiler?

Thanks for clearing it up for me.

Thanks for the reply again. I will probably go for that then.

Regardless. What do you think about the solution of the guy in the video? is it a good alternative?

How does virtmanager compare to virtualbox in your opinion?

user friendlyness, in regards of usb passthrough of deviced etc. Curious for your more experienced opinions.

Hi Macom,

Thank you for the reply. I already saw that guide.

I posted a question about that in another thread about that. Dont want to get it mixed up.

Question was,: I intend to do an install of OMV5 as ISO, just as I did with OMV4.

Is the guide still valid in that case?

(I rather stick with VirtialBox because I know it works as I expect it.)

Hi all,

I had VirtualBox running on OMV4. I was very happy with it. I need to do a fresh install due to crash.

There is no virtualbox plugin readily available in OMV5.

I googled a lot on this, and I ran into this video.

It looks like the result is very similar to Virtualbox.

It got my interest.

Question: Is this possible in OMV5 installed as ISO as well?

In short, he tells you to;

install KVM

install qemu

install libvirt

install virtmanager

I can try myself soon, but if you tell me this wont work because.... (im an idiot and dont understand it ) it saves me a lot of time

Any thought on this is welcome.

Regards

Hi,

I am reading the guide noiro posted.

I think it says, Install Debian 10, and then install OMV in it.

Will the result be the same when installing openmediavault 5 from ISO image?

(so to start the guide after the install OMV step.)

Kind regards

Little bump..

I am still having issues with the stability of the virtual OS. within a week it is unreachable. Even when I start the server from within OMV GUI.

@ geaves, I am doing good copys and backups now. thanks for that tip.

Anyone who can have a look at those SMART results I posted? I hope someone can give me some comfort things are OK in that area.

Regards,

Hi Geaves,

First; thank you for reading and taking the time to reply. Much appreciated.

I hear what you are saying. I could start the VM from within the GUI of OMV itself. You are right. Next time I will do that.

I do not believe that will prevent any of my issues. This is an assumption on my side though, which could be wrong ofc.
I (should) only start the VM once, where after I connect to the software itself through the briged IP.

@ryecoaaron did I miss something? ghehehe.. a post deleted and the boy or girl is banned.. curious

Hi all,

First off: I am a happy camper with OMV and its options and capabilities.

I think there are a number of areas where I could use some pointers, guidance or confirmation I did or didnt do things correctly. 1, SSD SMART data, 2 Virtualbox correct setup with rights, and 3 maybe even on best settings for virtual OS (HASSIO) itself.
Here is my issue in I guess is called story-mode. Please bear with me.

I am probably my own worst enemy at times. Now, after using a Pi3 for a couple of months for HomeAssistant (HASSIO), I decided to migrate the setup to a virtual environment. Faster, more stable, no write errors on SDcards or anything, snapshots possible.
I have the OS working quite well now, the HA setup, but the virtual OS is not set up propperly I think.
I run the virtual OS in bridged mode

Symptom: after an VirtualOS uptime of >2 days the server becomes unresponsive / lagging. When I open Virtualbox again as admin I see this.

The text under Details is shown in the spoiler below.

When I see the above screen, I press OK. and the Virtualbox loading circle keeps spinning until the ends of time... probably.
When press F5, the VirtualBox screen does show.

To get the virtual OS up n running again, I need to stop it manually and start it again. It is snappy again then.
Attached is screenshot of the virtualbox main screen. IF you require more detaild info, please ask for it. I will provide.

I did some more reading, and I saw somewhere this could be due to bad disks n error on it etc.
At that time, I did noticed my old Vertex SSD (60GB) was showing signs of failure in SMART. This SSD is the operatirng disk for OMV, so I replaced it with a new Samsung 860 250GB Version. It was from the stone ages anyway, one of the first vertex ssd's and held out pretty well. I used clonezilla to do a SSD > SSD copy action, where after I increased the SSD size on the Samsung to make use of the 250GB agian. Anyways...
Funny thing though, is when I run SMART and look at the results, It looks to me (as a total noob as I dont understand this part very well) that the SSD is still wonky.
Attached is the SMART report.

Now, after replacing the SSD (=OS disk for OMV) I still get the same errors. I am beginning to suspect when I copied the image with clonezilla, I did this incorrectly including the erors or something. I dont know if this is possible with SMART data.

I did some more reading, and my issues could also be related to users and rights. But to be honest, I am at a loss how to tackle this.
I am hoping so much someone here can point me to the right direction.

My Setup.
I have attached my full report as well.
content1561066771.zip

So again; I think there are a number of areas where I could use some pointers, guidance or confirmation I did or didnt do things correctly. 1, SSD SMART data, 2 Virtualbox correct setup with rights, and 3 maybe even on best settings for virtual OS (HASSIO) itself.

Kind regards,
Ed

Zitat von ryecoaaron

If people can test my update. WARNING!!!! This may destroy your setup. Use at your own risk and have a backup.http://omv-extras.org/testing/…-docker-gui_4.0.4_all.deb

worked for me flawelessly. !! Thanks.

Download the above file;
in Extensions press upload this file > OK;
in Update Management select the 4.0.4 and update

errors gone straight away.

Zitat von geaves

You didn't have to do that OMV-Extras Kernel tab scroll to the bottom, install from there and then use the reboot button....but that's OK you now have a rescue usb for next time

No, I didnt. Missed that.
However, I called the wipefs command. It is there and it reacts as it should. Although, when it tells me the ZFS signature is deleted, it is not. Just as mentioned in other threads.
I would gues (as a noob) that if a command responds, it can be used and it is functional. But I might be wrong

Anyway. You are right. I got it working thanks to your help. THANKS!!!

just to confirm.

wipefs -b -o 0xe8e0d3f000 -t noext4 /dev/sdb

does NOT work in OMV,

instead I used:
- systemrescuecd-x86-5.3.1.iso as OS.
- Used Rufus to burn iso to USB.

Yes, succes!!

Did exactly as you all suggested.

to see the zfs signatures to delete:
wipefs -n /dev/sdb

Then to delete them
wipefs -b -o 0xe8e0d3f000 -t noext4 /dev/sdb

In my case, there were only zfs signatures on the sdb drive, not on any sdb1...
after that rebooted into OMV 4.x and the drive is there again. And most important, all data is there and still in one piece. !!!

Thank you @geaves, thank you @ananas and thank you @tkaiser