What would be the best way to release the Disk?
Storage -> Disks click wipe on the menu, this will erase signatures on the drive then format it.
What would be the best way to release the Disk?
Storage -> Disks click wipe on the menu, this will erase signatures on the drive then format it.
Would you please tell where are they?
Hmm, sorry but in this guide I only can see the instructions for the installation of OMV5...
It's the same!! follow the instructions for deploying Buster Lite but you use Stretch Lite and run the script and it will install OMV4, but as ryecoaaron has stated OMV5 has been deployed and used successfully
So, we only can install this beta version…
No, if you download Stretch Lite and follow the guide it will install OMV4
Install OMV5, there no images for OMV4 for the Pi they have been removed, to install OMV5 follow this guide if you want to install OMV4 you'll need to locate a copy of Raspbian Stretch Lite then follow the guide.
To answer your questions you have to ask yourself why do you need a raid setup, what do you understand about mdadm raid software.
A better way to do this is to use rsync which will copy/update the data from one drive to another, you have 4x2Tb and 1x4Tb that's a lot of drive space connected to an SBC via a hub.
There are UPS's available for a Pi these are powered by rechargeable Lithium batteries, but would they be enough to keep the drives up, probably not. The way to shutdown safely is to shutdown via the WebUI wait for the Pi to shutdown so that the drives are in effect disconnected then power them off.
It's unrecoverable;
1. raid 5 allows for one drive failure
2. mdstat shows the raid md0 as inactive (not a problem) but only one drive sdb
3. blkid references only one drive sdb as TYPE="linux_raid_member" sd[cde] do not have have that signature
4. mdadm conf has no reference to a raid array
I can only surmise that during the shut down there was some corruption.
If you want confirmation of what the above should be then I'm happy to post that information.
Post the output from here please use the </> option on the menu for each one
any ideas how to find out why omv is spaming my upstream dns?
A google search will give some information, but one option is not to use pi-hole on omv but to use a public dns server e.g. 1.1.1.1
I wanted to know if there is a way to bypass the control on the omv5 usb ,
not sure what you mean, OMV5 should see the two drives, if I understand what I think you mean the answer is no. Wipe both the drives in Storage -> Disks then create the raid on the command line and it will appear under Raid Management.
the Apache page replaced OMV's web GUI,
It will OMV uses NGINX
so I was wondering if there were a way to change the address of the web GUI from ipaddress to ipaddress/omv
No, search the forum, to install Apache use Docker
You're welcome, good night
Yep, I'm sorry should have realised that on the first page, this will mean a complete rebuild either with 4 or 5, check the drives before you start re using any of them.
No file system!! WTF if that's the case something fried this array before we started.
Try fsck /dev/md0 if you get any requests to fix answer y if get nothing then there's nothing left to do.
That output confirms your post 5 it can't find any partition/file system information.
I'm going to have to sign off getting late here but what's the output of these two
wipefs -n /dev/md0 wipefs -n /dev/sdb
Also the array isn't listed under device column in the file system tab
After all this it could be toast
blkid fdisk -l | grep "Disk " we need to see a file system on one if not both of those
If you select the array in file systems can you mount it from the menu.
My apologies. I should've clarified that I meant I still can't see the files.
So it shows as clean in raid management but under file system n/a
When you say no change does mdstat still show active (auto-read-only)