Beiträge von PepeOMV

Well Tricky for noobs I...

I went through exactly that documentation for OMV5 VM FlashMem/Extras installation.

Without checking those...

"(Optional, but recommended)

Under System, OMV-Extras:

In the Settings Tab, highlight OMV-Extras.org Testing and click Edit. Enable and Save."

...my Flasplugin in the VM wasn't visible.

For OMV4 I'd need an OMV4 Extras .deb file to upload (Which I had tried, too), but anyway 4.1.7 Extas are installed, I just can't see/find the flashmemplugin anywhere.

Hence the question if there is some documentation for the OMV4 extras flashmem installation... Must be similar I guess, but still GUI looks different and features too from 4->5.

OK.. while the activation of the Flashmemory Plugin on the OMV5 VM worked.... although a bit tricky to activate.

So I though I might get on the real machine with OMV4 and simply activate the flashmemory plugin.... until OMV6 is out.

I have OMV Extras Version 4.1.7 installed, OMV-Extras /-Testing is activated - but again Flashmemory plugin is not visible...

Why is this? What Am I doing wrong?

Zitat von crashtest

You can check the flashmemory plugin with:

folder2ram -status (and)
folder2ram -syncall

Look for "successful" in the various /var folders.

If it's not running (in OMV5) it can be installed with the following one line script command:

wget -O - <a href="https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install">https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install</a> | sudo bash

Hey. I used

sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | sudo bash

to get OMVExtras 5.6.0 installed (which now appear in my list of Extensions/"Erweiterungen", also active).

In the SSH Shell it appeared to install successfully, too.

Unfortunately the Flashmemory plugin is still not visible in extensions or under "storage".

It then appeared to me that only SATA Hard-Drives are mounted in the OMV-VM-

Does OMV recognize Flash drives and is my VMPlayer 14 probably not able to deliver this message to OMV?
Anyway I would think the FlashMemory Plugin would appear anyway....

Any other plugins I need to activate/ Install?

EDIT: Obviously I had the tresting repo and extras repo deactivated... Flashmemory now appears

Agree so far... If 6 is coming soon I'd maybe wait.

Nevertheless I build a virtual Machine to test the migration to 5 and play around with it.

I came across the "issue" that Flashmemory plugin was not visible in the List of plugins. I recall that this was the case in 4 earlier...(Hence I knew it exists).

Does this become accessible after an installation of some updates?

So far I created a RAID 5 in the VM and ripped out one of the drives (virtually of course). OMV recognized and left an degraded RAID as expected. Because the drive needs to be mounted manually first to rebuild the RAID, I need access to a CLI.

This left me on the WebGui not able to get on the CLI in the first place.

Is there a Plugin or so that allows CLI access from the webpage?

Or do I need to SSH remotely?

In general it would be a nice feature in OMV to handle a broken raid completely remotly via WebGui (being a Linux Rookie this might be just a nice User-Wish). This makes the Likely case more easy for unexperienced users to rebuild their NAS RAID...

Thanks

Hey. Thanks for the hint. Basically, I don't care using all the space for OMV.

I have a backup of the OMV4 Disk both physically and digitally.

Any hints for the preferences/setting moving from 4 to 5?

Thanks

Hello. I successfully moved the old system to a new System SSD with Clonezilla.

Basically I am still running on old 4.x OMV but the migration to the new disk worked.

I split the 120GB SysDrive into 3 partitions, one hosting the old 4.x system of the old PATA drive.

Another one should be used for the OMV 5 Upgrade.And the third is there just in case I need to backup a system to another partition.

The USB Stick with the OMV5 ISO etched to it is prepared.

Tomorrow I will backup the raid again to my offline Backup Disk.

(I do this with FreeFileSync via a PC that has the FFS configs)

Before installing OMV5 and mounting the Raid, is there a way to export/import the current OMV4 system settings to the new OMV5.x?

Or will it have to be set up newly due to too many differences in the systems?

Thanks for the prompt reply.

Will then be shoping for a new Sysdisk. Probably I just by an external SSD Drive with USB IF, which should as before and report.

By backing up the install, you mean not just cloning the old sysdisk, right? I was about to get the old disk out of the system and store it away until the new Sysdisk runs.... Do you recommend to backup (=clone drive) additionally?

Flashmemory Plugin is a good hint thanks! Will install that...

Thanks again...

Hey guys.

My OMV is running as intended for some years now with rare use oaccasionaly.

Of course I missed to update regularly, so update requests for the underlying linux System now fail.

OMV tells me that the system is basically to old to be updated.

Back then when I build the NAS, I used a left-over 40GB 1.8" IDE Drive as the system drive. This Drive is pretty Old and it was on schedule to be replaced after a couple of years anyway.

To not block the SATA ports of my System, the boot drive is hooked up with a USB-to-IDE Adapter, which works fine and the system boots from it.

Some things now (forgive the rookie questions):

As I plan to replace the bootdrive:

- does it make sense to put a new, clean up-to-date OMV image to it and re-mount my RAID? Is there anything to do before replacing the Boot drive like unmounting the RAID?

- plan to run SSD Sata drive connected to a USB Interface again for booting. I am worried a bit about TRIM and BSM. Would assume OMV covers that for SSD boot drives, but is this true for USB attached SSDs as well?

- Can the update Process somehow be automated so I don't run into not-being-able-to-update issues in the future?

Thanks for some recommendations and tricks

EDIT: Sorry guys, I realized to late I wrote i ngerman Will continue in English later....

Hallo Leute,

ich habe ganz vergessen zu berichten.

Nach oben benanntem Neueinrichten läuft das NAS nun recht einwandfrei.

Ich habe es nur selten and und fahre es nur hoch wenn ich Daten brauche. reicht mir hin.
Gebackuped wird per Hand mit einer externen Platte und Freefilesync aufträgen.

Bisher funktioniert das ganz gut.

leider funktionieren die email-Benachrichtigungen nicht (mehr). Ich bin der Meinung das ich die während der Testphase erfolgreich erhalten habe (über gmx oder web.de), nun klappts aber leider nicht mehr.

Nach einigem Lesen habe ich rausgefunden das GMX und Web.de scheinbar das problem sind.

Ich habe zwar ein googlemail konto möchte aber nicht zu viele Konten warten und aufmachen.

Woran liegt es das Web.de und gmx nicht funktionieren?

Nochwas: Wie zuverlässig funktioniert die RAM auslastung und Erkennung in der Übersicht?
Ich hatte schon mehrfach den Fall das nur 2 statt 4 GB angezeigt werden. 2x 2 GB Riegel sind drin. Die waren gebraucht und ggf ist einer ja defekt, aber ich bin der Meinung das sich das Bios dann beschweren sollte bzw der Rechner nicht startet.

Hallo Leute,

ich habe ganz vergessen zu berichten.

Nach oben benanntem Neueinrichten läuft das NAS nun recht einwandfrei.

Ich habe es nur selten and und fahre es nur hoch wenn ich Daten brauche. reicht mir hin.
Gebackuped wird per Hand mit einer externen Platte und Freefilesync aufträgen.

Bisher funktioniert das ganz gut.

leider funktionieren die email-Benachrichtigungen nicht (mehr). Ich bin der Meinung das ich die während der Testphase erfolgreich erhalten habe (über gmx oder web.de), nun klappts aber leider nicht mehr.

Nach einigem Lesen habe ich rausgefunden das GMX und Web.de scheinbar das problem sind.

Ich habe zwar ein googlemail konto möchte aber nicht zu viele Konten warten und aufmachen.

Woran liegt es das Web.de und gmx nicht funktionieren?

Nochwas: Wie zuverlässig funktioniert die RAM auslastung und Erkennung in der Übersicht?
Ich hatte schon mehrfach den Fall das nur 2 statt 4 GB angezeigt werden. 2x 2 GB Riegel sind drin. Die waren gebraucht und ggf ist einer ja defekt, aber ich bin der Meinung das sich das Bios dann beschweren sollte bzw der Rechner nicht startet.

Soo...

finally i was again a bit frustrated about my non-knowledge of Linux and decided from a time perspective it would be best to clean the system and rebuild.

I am now back on OMV 3 and had extended the Raid, which needed to be done again on CLI as this doesn't work in OMV webgui for whatever reason.

The ubuntu Community was really helpful here.

A problem is that the mdadm after wiping the UFS disks on after the other and the new systems and after rebooting showed /dev/md127 instead of /dev/md0 as before.... obviously a common issue in mdadm.
I wasn't ablt to rectify this yet and it still is md127 but I can access it and the raid 5 is now online after 9h of extension, checks and rebuild with 3.5TB (I was expecting something closer to 4).

A good thing is that all in all the data was so far never lost because of any user Errors, fails or oddities...

grub countains 4 Entries
OMV4.16
OMV4.16 recovery mode
OMV4.9
OMV4.9. recovery mode´

In the meantime fdisk -l /dev/sdc  yielded:

GPT PMBR size mismatch (size differs by one) will be corrected by w(rite).
The backup GPT is corrupt, but the primary appears OK, so that will be used.

Is this defect MBR the error?
it is otherwise correctly identified as a FreeBSD UFS.
the other disks a,b, d, e and f appear ok.

Basically I was ready to put sdc / sdd into md0 Array, I was able to mount them and back them up.
could I "wipe" sdc ?
I read about wipefs but do not understand it fully. When wiping the MBR how can it then be accessed... pretty rookie here too...
or format sdc?

...on the root cli I was able to mount the md0 array.

I used
mkdir /dev/md0 to create the mountpoint /mnt/md0 and then mounted the /dev/md0 to that which worked ok and on cli I can now see my Raid data.

So far so good.

but how would I convince OMV system to do so during booting?
Can't I repair from root cli so I don't need a systemrescue cd or USB stick?

HI. RAID Drives are all SATA 6G. Backupdrive is eSATA 6G. Boot drive is USB2IDE disk

I'll try to boot from USB and try to restore the mountpoint... Let's see If I manage that

Thanks so far...

So
/srv/dev-disk-by-label-StorageRaid5 couldn't be found on /dev/md0 Raid

is preventing the system to boot to webGUI and restrict SSH access too? Shouldn't OMV system be unaffected to be able to debug?

Anyway it has me now. I don't know how to progress other than starting from scratch....
I've made my backup so this should be ok, but I'd be interested in what this is before moving on..

I did search a bit through the forum and tried some commands. UNfortunately I cannot access SSH so I cant copy them to full extend here.

Tried
cat /proc/mdstat
blkid
fdisk -l | grep "Disk "

mdstat shows all 3 Raided Disks in md0 and active so looks ok.
blkid shows sda, sdb and sde (the md0 ext 4 RAID5) and the two sdc1 and sdd1 - those two are my UFS drives.
sdc1 and sdd1 have exactly the same entries and numbers for LABEL, UUID, TYPE and PARTUUID but apart from that nothing obviously wroong points to my eye....
fdisk though showed something:
on sdb and sdc it says Backup GPT table is corrupt, but the primary seems OK, so that will be used.

Does this point somebody to an obvious issue?
I am a bit lost...

Well OK. Possible I didn't understand correctly. And forgive me if I compare with a Windows system.
When backing up in windows say to a USB drive it is pluging in the device, setting up the backuptool with some clicks and let it copy then. When done the drive can be USB-ejected.

I would like this to work the same with an eSATA drive, hence I installed the USB/eSATA Backup plugin.
And this worked fine.
But as I want to hotplug this drive (I do not want to leave it connected all the time for good reason but store it away in another place), how can it be unplugged?
As soon as it is reference in any job or the like it is impossible to unplug it...This way it could as well be an internal drive.

Regarding the booting issue the problem the console flags is Starting Enable file System Qoutas fails and ends in emergency mode.
Trying what is written then

systemctl status quotaon.service

and  journalctl -xb 

tells me that a

/srv/dev-disk-by-label-StorageRaid5 couldn't be found on /dev/md0 RaidThe service exited with status=2/INVALIDARGUMENT

Also something pointing to my 4 TB backup-harddisk:
Message
Unit dev-disk-by/x2dlabel-Bespin_BACKUP_4TB.device has failed.

and:
systemd[1]: Dependancy failed for /srv/dev-disk-by-label-Bespin_BACKUP_4TB <-- this i understand somehow, as the 4TB disk is not present, but why is system not booting because of that???
Is something wrong with the raid as the previous message points to md0?

Some time has past and I made some progress but also encounters various time consuming issues with OMV.

- I was able to mount my UFS disks readonly and copied all data to an external eSATA disk. I compared the result with diff -rq.
first both UFS disk vs each other (was Raid1) then with the USB backup (via a windows PC.
Both diffs did not flag anything . To be safe I compared rsults too via windows tools and that showed some differences, so to be safe I made a freefilesync copy of the contetns of NAS to the eSATA in a separate folder.

- I hope the old data is safe now.
Nevertheless I haven't got a good feeling about this.

- In my interest to run ZFS I prepared the sytem with the plugins and updates (which I also found a bit complicated). Finally I decided to stay away from zfs as I do not understand it deep enough (especially as I do not understand so much about linux).
I simply will Raid5 an ext4 Which I hope in emergency I can rebuilt easyily with a USB Linux.

- System now is completed, painted (:)), all wired up finally and running from a Dell 19V 130W Notebook PSU with a Pico PSU board 120W.

Issues:
- after I freefilesynced yesterday and hit the power button for the omv to shutdown (which it did ) it doesn't start anymore: It says failed to start Enable File System Qoutes.
This is likely because I removed any services and all that that had to do with my eSATA disk that was - once monúnted . not possible to be unmounted again. So OMV complained every boot the drieve is not present.
Strange for an eSATA driver to not check this. But how should it know... stupid.

- I guess there may have been some network issues too. The NAS has WiFi. So has the Sink laptop, but its also wired via dock.
it happend when freefilesyncing that the throughput dropped down to 1-2 MBy/s, whereas is was up to 70 MBy/s before. Stopping the filesync action, decativating WiFi first on the Laptop, and when this all happend again also on the FritzBox Router, that rectified the issue and the systems went up to 50-60 MBy/s again...
No idea what this is, maybe router ?!

as mentioned :
It doesn't boot anymore.

I now need to find out why (one more last time, as I have encountered too many things like this)...
Especially the eSATA backup (the removeable driver mounts and cannot easily be unmounted, as the systems doesn't tell me, WHY it is possible to not unmount it!) really pisses me off.
To the Backup could be a bit more sophitcated. Maybe a bit like freefilesync, which is relatively intuitive for a backup tool and works fairly ok.

I recall there wasn't that much trouble involved in the FreeNAS I build 10 years ago, but that also was far lex complex.

PS: Almost forgot: Can't access neither SSH nor webGUI , only console...

thanks FLMAXEY.

sounds encouraging... I had a bit of a downpoint on the whole project due to this.

Write hole understood. Can fsck fix issues caused by this (meaning saving the rest of the files even if the one written is corrupt?

I am looking into it a bit more again now. Your word build up some confidence again...
Some more background: My disk array was build and could be accessed without issues. It was a trial "what happens when".

ZFS sounds promising but this is not the topic here.
Only that much isn't btrfs the better choice as its developed for linux instead of Solaris Unix?

mdadm and ext4 being separate and "unaware" of each other is known. I honestly didn't know zfs and btrfs fixes this...

Not sure though if my weak hardware can cope with zfs or btrfs (E450 AMD APU and currently dual channel 4 GB RAM).

EDITH: You mentions btrfs is not like zfs?

... thanks anyway

Sorry,

but I think there is a misunderstanding.

I am in the trial phase still and thought I'd try what happens if I ever need to swap a disk if it fails.
Hence I thought I force an error on an (empty) Raid5 of loosing a disk through Power outage on one disk.

So some questions:
1. If this happens, do I HAVE to wipe that disk that is not recognized and reconstruct the array? Is there no other way other than wiping the disk?
2. in ANY power outage condition where usually ALL disks will fail at once, will ALL Data on a RAID5 will be lost?
Isn't there something like a consistency check for bad data or checkdisk?
in real life only the data currenly written to disk will be damaged...everything else should be ok.
And the Raid5 Array in OMV should be able to cope with that.

If there is nothing that can handle this I definitly will not/cannot use OMW