This can be reversed. The line Remove "Blacklist R8169" in
/etc/modprobe.d/blacklist-r8169.conf
sudo apt purge r8168-dkms
sudo reboot
The last thing I would try would be to install the pve kernel. Install OMV > plugin >Openmediavault kernel and then Proxmox kernel 6.2.x install, restart and run omv-firstaid in the terminal, edit the Network.
Maybe it helps to install the RTL8168 driver and blacklist the RTL8169 driver, see:
sudo apt-get install r8168-dkms
echo "blacklist r8169" > /etc/modprobe.d/blacklist-r8169.conf
sudo reboot
A lot has been written about the Dell Wyse 3040 in these forums. Just try the search! Debian 11 works if you tinker a little, just like Debian 12. You can use a script to install OMV after installing Debian 11 (see OMV's Internet Manual). I had Debian 11 running with pihole on the Wyse 3040. Now pihole runs with Debian 12 on this thin client.
Blackview there are quite a few mini PCs. What kind of Blackview is it? What kind of CPU is installed?
I would first activate the backports via OMV's web interface. OMV->System->omv-extras->enable Backports
or via ssh
sudo nano /etc/apt/sources.list
Insert the line
deb http://deb.debian.org/debian bullseye-backports main contrib non-free
then save with ctrl+o and exit with ctrl+x nano. The firmware package is from 2023. Then I would install the firmware-realtek (20230210-5~bpo11+1) [non-free] from the backports via ssh.
sudo apt-get update
sudo apt-get install firmware-realtek
sudo reboot
Per Download:
Debian -- Paket-Download-Auswahl -- firmware-realtek_20230210-5~bpo11+1_all.deb
There is nothing wrong with using an RPi3/4/5 as a NAS. I use two of them as backups of my primary.
I just said that I wouldn't use a Rpi as a NAS. At least not as a primary NAS with Docker and containers. As a backup NAS, which you turn on from time to time, that's something else. I didn't say that it's wrong to use an Rpi. Everyone can do what they want. For me (and by that I mean only me) the disadvantages outweigh the disadvantages. With an x86 machine, I think you have more options. The power consumption is lower with a Raspi than with a computer with an Intel N or J processor. Thanks to Autoshutdown, wakeonlan and PicoPSU on the x86 computer, the whole thing is put into perspective again. My J5040 computer is passively cooled and works absolutely silently. With the PCIex interface and RTC, the Rpi 5 offers more possibilities than the Pi's before. In order to use the PCIex interface for data carriers, additional investments are again required. You need an m.2 (NVME) or a Sata hat. In this case, the data carriers must be supplied with external power. So you also need at least one case with SATA and power connection. Are there such cases for sale or does it ultimately come down to tinkering? At some point, there will be a relatively expensive case for the Rpi 5 with a sata hat, power supply, and space for third-party disks. Then the whole thing looks tidy. In the end, it will be easier and cheaper to attach a USB hard drive to the Rpi 5 in an external case than to deal with SATA.
I have my 4 old 3Tb drives using BTRFS with raid0 (which is what OMV set up).
Raid 0? This means a capacity of 12 TB for 4x3TB drives. If a drive breaks, all data is gone. Wouldn't it be more sensible to use mergefs instead of Raid 0? Then only the data of the defective hard drive is gone. I don't use RAID and back up to a second NAS on a thin client and a time-delayed to an external USB hard drive, which is only turned on when backing up. Raid from Raid 1 is only for reliability, is not a backup and contributes only to data security to a limited extent. In addition, raid means increased power consumption and higher hardware costs. In contrast to Germany, electricity costs do not yet seem to play a major role in many countries.
Based on my experience with a Raspi 4, I would not use a Raspi 5 for a NAS. In addition to the Raspi, you still have to buy the case, power supply and SATA-Hat. An m.2 Sata SSD will probably be mounted on top of the Sata-Hat. I don't know if there is a hat with "real" SATA connections. You still have to "tinker" with it. Then you quickly get to 150 euros. If you don't want it to look tinkered, you have to pay more money for the case. In my opinion, there are better alternatives. As a backup NAS, I now use a Wyse 5070 with a 4TB Sata m.2 SSD.
The board is for Intel CPU of the 8th/9th generation and should have no problems with OMV/Debian 11. You have probably already reset or deleted BIOS settings (via jumper or temporarily remove battery). I would test if the computer boots with a Linux Live system (Live USB stick). You don't have to install anything. I would test this with various Linux Live systems (Ubuntu, Manjaro, Debian) on a USB stick. If there are also problems, I think the board has a hardware problem (e.g. SATA controller) or the CPU is defective. You could also try installing OMV on a USB drive. I have here a Fujitsu Esprimo Q558 running a D3603 board with Proxmox. This works perfectly. Of course, it's different from your board.
Have you tried installing Debian with a nonfree firmware image (https://cdimage.debian.org/ima…-11.8.0-amd64-netinst.iso) of Debian 11.8.0? OMV is then installed via script (https://docs.openmediavault.or…stallation/on_debian.html)
Maybe there is another way to have this Asrock J5040 accepting legacy boot option...
No.
The installation is possible by first installing Debian, then restarting with the Debian installation stick and copying or creating or linking the file bootx64.efi to the EFI/boot directory. After that, you can start Debian 11 and install OMV via the installation script. You don't do any damage. I use a Wyse 3040 for pihole. Whether it makes sense to use a Wyse 3040 as a NAS is another matter. But that's also the case with the Raspi. As with the Raspi, the data drive can only be connected via USB 3. The 2 GB RAM and the 8 GB eMMC should be enough for the system. I wouldn't run Docker, containers on the ATOM machine. The Wyse 3040 should have about the same performance and almost the same power consumption as a Raspi 4 and is better suited for OMV than a Raspi in my opinion. The part has RTC, UEFI and you can use autoshutdown. I bought two wyse 3040 during the Raspi crisis for 35 euros each.
Have you tried to clear the browser cache to fix that issue?
Yes
The display or view in the autoshutdown plugin of the web interface is shifted in Firefox and Vivaldi (see picture).
He writes "Only Windows boots normally after installation. All Linux-based distributions behave the same way, as I wrote above.". So this is not just an OMV problem. Maybe the board's EFI can't find the Debian/OMV startup file. I would be interested to know which Linux distributions he has tested. There is also such a problem with the Dell Wyse 3040. Since the operating system does not start after installing Debian. Enter "Dell Wyse 3040 Debian install" via Google. Maybe this will help them
I don't use Virtualbox sorry mate.
Patrice78 has a problem and I asked him the question, not you!
I've never used OMV on Virtualbox before. Just always different operating systems. Have you created a USB filter in the VM's settings for the USB hard drive?
In my opinion, installing a second web server on the same IP address next to the one used by OMV often leads to problems. It would be better to set up a VLAN with its own IP address (see https://wiki.omv-extras.org/do…v6_plugins:docker_compose ).
The section Network for e.g. the pihole Compose looks like this for me:
ports:
“80:80/tcp”
networks:
vlan-name:
ipv4_address: xxx.xxx.xxx.xx
networks:
vlan-name:
external: true
What I had forgotten about the first method. The data HD for OMV created in Proxmox via hardware must not be included in the installation of OMV. So first create a VM with an HD for the OMV system in Proxmox, install OMV and only then create one (or more) data drives via the hardware settings of the OMV VM in Proxmox.
I know of two ways to set up a disk for data in the Proxmox OMV VM. The first... Create drives via the hardware settings on a hard disk mounted in Proxmox (see picture). The second and better way to pass a physical HD to the OMV VM. However, this must not be integrated or mounted in Proxmox. It is best to install them only after installing Proxmox. There are plenty of instructions on the Internet. A visit to the Proxmox forum would also be helpful. This is not an OMV problem. I have instructions on how to do this. Firstly, it's in german and secondly, I only put it together by searching the net. But it works.
Virtualizers like Virtualbox or VMWare are the better solution for me. Another advantage is that it is easy to back up a VM. If you are a gamer, I would install Windows and use Linux under Virtualbox as a VM. I do it the other way around. But I also only need a few applications under Windows, which unfortunately do not exist for Linux or which are insufficient for my purposes. Even under an old i5-6500, a VM with Windows 10 runs satisfactorily fast.
Running an os on a sd card is gambling, it will sooner or later break. I have home assistant running on rpi4, and it took one month before sd card broke. After i switched to ssd drive, it's been stable over a year. Guess that is what happened, corrupt sd.
A good SD card lasts longer if you always install and use folder2ram, and not just for OMV. This minimizes the write operations considerably.
