I have a very old OMV 2.2.14 as media server running on a HP N54L with 6GB Ram. I think its time to bring it up to date 
There is a quite full SW Raid 5 (4x3TB hdd) and one single 3TB hdd attached, this data i would like to keep. The other settings (shares, plugins, ...) i dont care, i can reconfigure.
Whats the best way to do this?
Thanks!
P.S. i did google, but a jump over so many releases there is no much content
In case you wanna use OMV6, wait some months until it is released. If you wanna update right now, use OMV5 as it is the current stable release.
However, I would do the following steps:
1. Setup a virtual omv on your pc just to get familiar with it. Test things that you gonna need. Solve any problems prior to doing anything on your NAS.
2. BACKUP ALL DATA
3. Disconnect data drives
4. Swipe system drive and install new omv
5. Reconnect data drives
6. Configure ..
The big question is just if a new OMV install will recognize my raid properly or if i have to save some configuration to reimport.
Didnt do much with Linux sw raids since ages
Ah sorry I did not even think of that since I use btrfs raid. Whats yours? mdadm?
THATs the question I assume its mdadm cause /dev/md0, but i dont know what OMV2 was using. And im not a debian guy, just linux (centos) .. but i played around with the linux software raid many years ago
do you think a newly setup omv would automatically detect the raid?
It should detect a software RAID5 set, but nothing is guaranteed.
This is a question for geaves .
So i have mdadm.conf with the settings ... import wise how is this handled by V 5
You cannot import any settings or files into a new deployment, the norm is to take screen shots of shares, users etc, there is a thread on the forum upgrading from 2 -> 3 -> 4 -> 5. However, this was created by a user and is not officially supported.
do you think a newly setup omv would automatically detect the raid
Technically yes, but there have been instances where this has not worked for users moving from 3 -> 4, I upgraded from 3 -> 4 without issue, but I was also changing hardware, and the errors seen elsewhere were attributed to the kernel.
tom_tav I have exactly the same hardware albeit I run ZFS with 4GB of Ram and not 16 
I also run mine on a 32Gb USB flash drive, bit of an overkill as it only uses around 6GB + makes it easier for cloning backups.
Simplest way to test OMV5 is to run it on a USB flash drive, disconnect all your drives, install, boot and configure OMV5 on a flash drive, once it's all up to date then connect the raid drives. BUT, whilst I suggest this, I would not proceed without a backup, which reading between the lines you don't have
there is a thread on the forum upgrading from 2 -> 3 -> 4 -> 5. However, this was created by a user
the user Dleidert is a debian development contributor and gave advise on certain topics even to OMV developer.
I'd use his excelent scripts for upgrading
I'd use his excelent scripts for upgrading
Well thank you for your flag waving and usual helpful comment.
Thanks guys, seems i have a plan now
The road to desaster is ahead of me
I have exactly the same hardware albeit I run ZFS with 4GB of Ram and not 16
Oh yes, i forgot the 16GB ram is on my 40TB raid machine. With the smaller raid it should be ok with my 6GB Ram, youre right.
So how is ZFS on OMV now? Back then it was so fuzzy (aka not implemented fully) that i changed my bigger raid to another distribution. Is ZFS support fully integrated in the frontend now?
BUT, whilst I suggest this, I would not proceed without a backup, which reading between the lines you don't have
I will do a rsync backup to a external 8TB drive, im mad but not crazy
So how is ZFS on OMV now
I'll tag crashtest on this as he's helped me understand it, although I had previously used Freenas which is now Xigmanas, but to me like most of OMV it just works, the great thing about it is the GUI, beats the hell out of using the cli. Mine is used for Movies, TV Shows, Photos and some file storage, particularly for the wife as she's a teacher. The backup drive is also used for UrBackup of the Windows machines, which, thanks to another mod macom runs directly on OMV rather than a docker (works better).
My N54L has 6 drives, 4 in the ZFS pool, a big drive for back up, and a small laptop drive for docker and docker containers, the containers are all deployed using stacks, so for that I just keep a copy of the stack should I need to redeploy. All I then have to do is to change any bind mounts within the stack before deploying.
OMV runs on a flash drive from the internal usb port, basically all this is doing is booting OMV, because I do a monthly clone I rotate the flash drives, which also leaves me something to fall back on should something go wrong. That's why I suggested using a flash drive for OMV5 then connect your raid, if it doesn't pick up the raid signatures and start the raid you've lost nothing, reboot with your current drive and reevaluate.
Did you flash your N54's with the modded bios or is it HP's stock
I will do a rsync backup to a external 8TB drive, im mad but not crazy
that's a good plan
Oh FYI when I moved from V4 to V5 I did a clean install, took me less than a day to set it up and get all the data on.
On OMV4 and 5 ZFS works well. The plugin allows OMV shares to be mounted on ZFS filesystems and subfolders. It also allows for the creation of additional VDEV's, which allows for the expansion of an array. More than one array is supported as well. Most pool and filesystem options are editable in the GUI and there's a provision for manual SNAPSHOTs. (Personally, I prefer automated SNAPSHOTs as setup according to this -> document. Automated SNAPSHOTs are viewable in the GUI.)
Finally, there's an automated scrub, VIA a cron job setup by the plugin, that runs every two weeks by default.
In summary, I don't know how other distro's support ZFS but, for the average user and admin, ZFS support on OMV isn't lacking anything substantial.
EDIT: On one machine, I've been running a 4TB pool on weak hardware (an ATOM CPU) and 4GB ram with no issues whatsoever.
Ok, did a look into dleiderts scripts. I think it doesnt make any sense for me to start the journey 2-3-4-5, more easy to just start from scratch and reimport my raid. I did modify my OMV back in the days (newer netatalk and other hacks) so update desaster would be around the corner
For others, this is the post from dleidert:
Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5)
I will do the backup, setup a new OMV and see if and how it works. Then i can decide if i keep OMV on this machine or if i use xigma as well. In the beginning i liked OMV cause of the use of plex/sickbeard and co which i dont use anymore.
Main reason which drove me away back then (at least on my big nas) was the lacking support of ZFS and some outdated packages (especially netatalk and samba). On the other hand, xigma became more and more commercial after the name change, i prefer clean open source. And finally, im firm with Linux but not with FreeBSD, another point for OMV.
I think i will try a USB boot for OMV, and use the little SSD as Cache for ZFS. Lets see...
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
