Posts by pug_ster

I mostly use Microcenter's free 32gb or 16gb microsd cards . I also used adata ones too but they failed too. I copied some files to the hard drive and then put it back to the raspberry pi and omv crashed again. Guess booting off from hard drive is a bridge too far. I think I will try booting off from usb stick and my 5tb as a storage drive and see how it goes.

Before I used the flashplugin in the microsd card and I still have problems.

Thanks but I did a similar thing. But I ended up raspberry pi imager to install the OS in the hard drive, then used the mbr2gpt to only convert to gpt drive. Then I took out the drive used gparted to extend the root drive. Kind of weird but got it to work.

Can't count how many times my microsd card flubbed out and I have to re-install because of the microsd card issue. I would like to get OMV to boot off from the hard drive so and sae Technodad's youtube video about OMVsharedrootfs plugin which allows you to do that.

However, My hard drive is 5tb and the Raspberry Pi imager would only make hard drive to use MBR that means that I can only use 2gb of that partition. However, I saw on a forum in raspberry's website where you can download a usb-boot utility into the microsd card which copies the contents of the microsd card into the hard drive and boot off from the gpt drive.

https://forums.raspberrypi.com/viewtopic.php?f=29&t=196778

So here's the steps that I did.

1) Updated the bios to boot from microsd card and if not present, boot from hard drive.

2) Used Raspberry Pi imager to get install rasp os lite 64 bit into a micro sd card (if I install this in usb hard drive it will be an mbr partition.)

3) Boot the microsd card into raspberry pi 4.

4) copy the usb-boot utility into microsd card using winscp. chmod 755 the files and put them in the /bin directory.

5) With the 5tb hard drive plugged in formatted into a gpt format, I ran the usb-boot utility which allows me to copy the contents of the microsd card to the hard drive while making it a gpt partition.

6) After rebooting, the partition sdb2 took up the whole space.

7) Ran sudo apt upgrade and installed OMV6.

the installation went fine and after omv reboot, stuck here and then reboot.

Not sure what's going on, couldn't figure out how to fix the problem?

Quote from ryecoaaron

Why did you skip networking? The install script works well on the RPi. Some routers don't handle the dhcp change though.

I put an dhcp reservation in my router and it works for me. I'm using an Asus rt-68u flashed with a merlin firmware.

I've upgraded to a synology running dockers recently (sorry guys). My Raspberry pi was running the OMV5 with the buster version and installed new 64bit bullseye version and omv6. Reconfigured the dockers running the 64 bit version and pointing to the same /config files in the location of the hard drive and it little config is needed. Here's my checklist of how I did it.

1. Download 64 bit raspbian lite OS from the website.
2. Use Raspberry Pi Image and install Os by going to “Use Custom” and use image from step #1.
3. After image is done, pull out sd card, and put in sd card, put in a blank “ssh” file in the boot partition.
4. Put sd card into raspberrypi and bootup. Wait for 5 minutes until you can log in as pi, password raspberry. Change password by putting in command “passwd”
5. Change Localization features by running “sudo raspi-config”
6. Run the commands “sudo apt update”, “sudo apt upgrade”, “sudo rpi-update” and reboot by running “sudo shutdown” Unplug power. plug in Usb hard drive and plug in power.
7. Install OMV by putting the 3 commands

wget https://github.com/OpenMediaVa…Script/raw/master/install

chmod +x install

sudo ./install -n

1. Log into OMV by going to http://<ip of raspberry pi> log in as admin and password openmediavault
2. Change admin’s password by click on the “cog” on the upper hand corner and go to “change password”
3. Change the local time zone by going to System -> Date and Time.
4. Change auto logout time by going to System -> Workbench Change from 5 minutes to about an hour to prevent yourself from auto logoff.
5. Go to Network -> Interfaces. Add Network for eth0 for raspberry pi.
6. Add the external hard drive. Go to Storage File Systems, Mount the hard drive as /dev/sda1 Format the hard drive to ext4 partition if needed.
7. Install docker and portainer by going to System => OMV Extras - Docker and Portainer and install them.
8. Install symlinks is recommended. Go to System -> Plugins under openmediavault-symlinks 6.0. After installed, it should appear in Services -> Symlinks. Your hard drive location is under /srv/dev-desk-by-uuid-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx something like that. Create a simlink from the one above to something simple like /mnt/sda1
9. Add the Dockers back using cli and point back to the old locations of the /config files
10. Create Shares/ folder shares and user accounts if needed.

Quote from ryecoaaron

Did you look in the Diagnostics -> Performance Statistics section?

Otherwise, sudo apt-get install cockpit will install cockpit

Thanks, I ran the sudo command and it installed cockpit. But it doesn't display the cpu and memory utilization of dockers.

Hi,

When I had OMV5 installed I recalled that you can install cockpit so I can look at the the cpu and memory utilization for dockers. After the upgrade to OMV6, I could not find it. Anybody know how to install or any kind of way to see how to find out cpu and memory utilization in a gui interface?

Okay, thanks. Just not crazy about booting off sd card which is not reliable. When I had the last build of my raspberry pi, I have a weekly backup of my sd card and occasionally I had to use it to restore.

Quote from chente

I don't understand what you've done. You have installed OMV on a 5TB USB disk.

Did you make a 100GB partition?...

/dev/sda1 is the boot partition /dev/sda2 is the partition for the RPI OS, it used to be 1.5gb and I've extended to 100gb.

I've started to see the limitations of support for 32 bit arm dockers for a raspberry pi, plus it is mostly a PITA of sd cards of corrupting all the time. So I recently moved all my data to my synology and now I can play around if I can run 64 bit arm containers in this thing.

So I installed the 64 bit lite version of bullseye booting off from a 5tb usb hard drive. I configured /dev/sda2 from 1.5gb to around 100gb. Installed OMV 6 and everything looks okay except for the file systems. Under the Strorage -> Disks , it list /dev/sda 5tb hard drive but when I go to Storage -> File Systems, it is blank. Is there a reason why this is happening?

Oh nevermind, the build number is:

linuxserver/radarr:arm32v7-version-v0.2.0.1504

This works, but it borked my radarr configuration and I have to re-configure everything.

Quote from nick2k3

Hi everyone, I am writing because I encountered some errors while updating the docker container for Radarr, maintained by linuxserver.

They issued an update last night :

following the link ( https://docs.linuxserver.io/fa…ges-based-on-ubuntu-focal ) their advice is:

So far, I have managed to run the previous-last image using the following tag: linuxserver/radarr:version-v0.2.0.1504

But my question is: is this safe to execute these command on a raspbian lite image on which OMV5 run?

Display More

I have the same problem with radarr too on my raspberry pi. I tried running that radarr version 1504 but I couldn't find it. Itried to backtrack to the libseccomp2 core and it doesn't work either. I tried putting an older version of radarr up to about 15 days ago and it doesn't work either. Anybody konw how to fix this?

I get slow transfer speed if I have too many torrents running or any software that you are using the hard drive, IE I use emby. I never used deluge, but I use haugene/transmission-openvpn:latest-armhf docker which is good for openvpn and transmission.

FYI, I am using the raspberry pi 4 4gb, with a 5tb seagate hard drive.

This happened to my Raspberry pi running OMV where my sd card got corrupted or something. At first I can't go to the OMV console and I have to constantly reboot my raspberry pi 4 to get it up and running. Fortunately, when I set up my raspberry pi, I used dd to backup my sd card and then used pi shrink. I was lucky enough to get a shrunk img file from a backup and copied it to my computer.

I originally installed an 16gb sd card from Microcenter shrink to about 3.7gb img file. Then I figured that I used a "reliable" 8gb samsung sd card to dump the image and then used the raspi-config tool to expand it. It is a good thing when I moved all the dockers into the hard drive instead of the sd card otherwise it will be more of a pain

You can secure the website using a login, password to access the webpage.

You should also install LetsEncrypt docker (which includes nginx web server) and use a reverse proxy subfolder to do access to your website. That way, you can access your website via https://<yoursite>duckdns.org/transmission/web/

Hi,

I am running raspberry pi 4 using Openmediavault to backup my sd card and shrink the file via pishrink. So every Tuesday at 4am, I run the scheduled tasks command under root:

sudo dd if=/dev/mmcblk0 of=/sharedfolders/Appdata/sdbackup/backup.img bs=1M

This job runs without issues.

At Tuesday 5am, I ran a job to shrink this file

sudo pishrink.sh /sharedfolders/Appdata/sdbackup/backup.img

and it would not run.

When I ran the pishrink command manually in the scheduled tasks panel, it would run fine. Is there a reason why this is happening? Thanks.

You might as well install Letsencrypt docker because this includes nginx.

It should be located in /srv/dev-disk-by-label-data/appdata/letsencrypt/etc/letsencrypt/live/mysite.duckdns.org/ (assuming that mysite.duckdns.org is your registered site by letsencrypt.)

Agreed. For mariadb, you can map ports: 3306:3306. Letsencrypt is the web server ported outside and should own 443 and 80. For me, I would map something like 2443:443 and 2080:80. Have your router route ports 443:2443 and 80:2080 respectively. That way, you can still use your OMV port server at port 80.

For nextcloud, you can map something like 3443:443 and 3080:443.