Posts by NothingNowhere

    NOTE: THIS IS ONLY USEFUL if you are using an image later than 2022-01-28-raspios-bullseye-arm64-lite (as pointed out by ryecoaaron below)


    The wiki page at https://wiki.omv-extras.org/do…omv6:raspberry_pi_install is correct but as it says you must use an old image 2022-01-28-raspios-bullseye-arm64-lite. Not a problem really as apt update and upgrade doesn't take long. I just missed the bit about using that specific image.


    The following might be useful if using a latest image for Raspberry Pi OS. It removes the need for the section called 'Enabling Raspberry PI OS's SSH Server for Remote Access' (i.e. creating a file called 'ssh' before boot).


    Since 2022-04-04, Raspberry Pi OS (formerly Raspbian) Bullseye no longer comes with the default credentials of user:pi and password:raspberry (as explained in this blog post). New installations must be set up with a username and password of your choice.


    Probably the easiest way to do this is with Raspberry Pi Imager (though other options are outlined in the above linked blog post).


    1. Download and install the imager from https://www.raspberrypi.com/software/


    2. Launch the app and click 'CHOOSE OS', then scroll to the bottom for 'Use custom (Select a custom .img from your computer)', Then choose your downloaded and verified image file.


    3. Click on 'CHOOSE STORAGE' and select your target SD card.


    4. Click on the cog icon to access 'advanced options'. Tick the 'Enable SSH' box and leave the radio button 'Use password authentication' enabled.


    5. Tick the 'Set username and password' box and set a name and password for your SSH user. Be careful with the password entry as there is no confirmation of whatever you type.



    6. There are other options (e.g. for hostname, WiFi and locale) in this 'advanced options' section you may wish to configure. Once happy with your options, click 'Save', then 'Write'. Raspberry Pi Imager will automatically verify after writing.

    Hello! I've recently upgraded to OMV6 and I wonder if it's possible to disable the login screen's background animation as it gives me vertigo.


    Thank you for your help.

    I tried OMV6 for the first time last night (have used many older versions) and found the animation unpleasantly disorientating - vertigo, as you say.


    I'd possibly consider it an accessibility issue, but either way it would be good to have a webui option to disable the animation.

    sudo mv /var/lib/dpkg/info/openmediavault.triggers /var/lib/dpkg/info/openmediavault.triggers_backup

    Great, this worked for me with OMV 5 on my Odroid HC2. Thank you.


    I didn't need to reboot, I did sudo service openmediavault-engined restart then a force reload in my browser (ctrl-shift-R in chrome)

    Just sharing this for future reference, hopefully to save hair pulling for somebody along the line!


    I built an OMV box using a large case and a known good motherboard, CPU and memory. I was combining 10 HDDs from 2 old boxes but all drives were known good.


    I got a used Dell H310 SAS card from a reputable eBayer to host eight of the HDD's, connected the other 2 to the motherboard SATA and put the OMV operating system on a small SSD.


    I soon was getting lots of problems which I couldn't make sense of - sometimes the system booted fine, often it got to the GRUB menu but then had lots of mdadm no arrays found errors and dropped out to BusyBox. I tried various fixes relating to GRUB in case that was corrupted, but no change.


    Sometimes the system didn't find the OS drive at all. I tried changing power and data cables, but no change.


    I thought there might be an intermittent fault with the SAS card, causing some weird conflict with motherboard BIOS, and this led me on a fruitless internet goose chase.


    Finally it occurred to me that the SSD might be faulty. So I bought Crucial's smallest SSD, cloned the OS to that with Clonezilla and hey presto, everything working as it should.


    What I don't quite understand is why the system, once booted, would run for many hours without fault - suggests that SSD only had an intermittent problem at power-up I guess.

    Having had weird mobo issues for months and recently resolved them, first try:


    1. Remove all cables, cards, memory, CPU. Remove motherboard from case.

    2. Look over mobo very closely for any blown/bulging components or damage to copper traces.

    3. If OK, clean board with cotton buds and isopropyl alcohol. (mine was not just a bit dusty, it turned out!)

    4. Check closely for anything in the PCI / memory slots that might cause shorts/bad contacts. Hold board upside down, shake it about.

    5. Check case for the same before rebuilding.


    In my case, I think something very small was causing an intermittent short that threw all sorts of odd errors for months - POST problems, and once booted lots of "xz-compressed data is corrupted system halted" errors.


    I got new RAM, that didn't help. Reflashed BIOS, no help. Eventually it didn't POST at all, so I was about to order a new board but then did the above and so far, no problems at all.


    Hope this helps. If not, partpicker.com is very useful for sifting through mobos and components by specs.

    I am merging 2 Snapraid arrays into 1. From 4 data and 1 parity to 8 data and 2 parity.


    I added 3 of the disks from the old second array without error (using the Snapraid plugin in the OMV webui) but one disk threw this error and could not be added:


    Code
    The configuration object 'conf.service.snapraid.drive' is not unique. An object with the property 'mntentref' and value '5ec4c9fa-ab9a-4cfc-bc39-32c87808027f' already exists.

    Can anyone point me to how to correct this?

    Thanks gderf,


    So far so good, I enabled that mountpoint column (very useful, never realised it was there) and those drives are using disk-by-label.


    Once I was sure this was working as intended I rebooted and recreated my union/fuse mountpoints with the OMV ui for disks 5-8


    I will be creating shares using the union mountpoint rather than the disks so I think I'm OK.

    OK, answering my own question... I'd be grateful if someone with more linux wisdom could check this over though!


    I went into /srv and did

    sudo mkdir /dev-disk-by-label-disk6

    sudo mkdir /dev-disk-by-label-disk7


    Then

    sudo mount /dev/sdc1 /srv/dev-disk-by-label-disk6

    sudo mount /dev/sdd1 /srv/dev-disk-by-label-disk7


    Then

    sudo nano /etc/fstab to edit the fstab and replace

    dev-disk-by-id-ata-WDC_WD30EFRX-68AX9N0_WD-WCC1T1134175-part1

    dev-disk-by-id-ata-WDC_WD30EFRX-68AX9N0_WD-WCC1T1152903-part1

    with

    dev-disk-by-label-disk6

    dev-disk-by-label-disk7


    Rebooted, all seemed fine.


    Finally, I went into /srv again and checked the old mountpoints were empty:

    dev-disk-by-id-ata-WDC_WD30EFRX-68AX9N0_WD-WCC1T1134175-part1

    dev-disk-by-id-ata-WDC_WD30EFRX-68AX9N0_WD-WCC1T1152903-part1


    They were so I deleted them.

    Hello all,


    I am combining two old OMV systems into a new box. For simplicity I've labelled the main drives (using e2label) as disk[1-8]


    Under /srv/ I have 2 drives that haven't mounted with labels. This is output of lsblk:

    How can I change sdc1 and sdd1 to mount at dev-disk-by-label-disk[6-7] like the rest?


    Thanks for reading.

    Hello all,


    I have a problem with a Samsung D3 external HDD, which is USB 3.0


    With my Windows laptop it works fine on USB 3.


    With my OMV box (a PC case with this mobo http://www.asrock.com/mb/intel/H97%20Pro4/ ) it works fine on USB 2 but I connect it to USB 3 it is not recognised and I get the following errors in syslog:



    However, if I connect a different USB 3 drive (a slightly newer Seagate Expansion) BUT using the same PSU, USB cable and port, it works fine.


    Any thoughts welcome!

    Yes, I see it's possibly doable on Armbian, I might experiment one day.

    https://docs.armbian.com/User-…all-to-emmc-nand-sata-usb


    Cards are Kingston or SanDisk from Amazon as the seller, i.e. not fakes.


    I'll run them through badblocks maybe, it's not the cost of new cards it's just frustrating when I think I've got everything ticking over nicely, something odd like this comes along.


    Anyway, thanks as ever for your help.

    Hello, I have OMV 5 on my Odroid C2, which was working fine, now can't login to the webui. It seems omv-engine service isn't running.


    This is a recent installation using the instructions for Armbian installs. Not an upgrade from OMV 4.


    SSH, FTP, Samba etc. all working fine still.


    This seems to be a common problem but with various causes. I've tried a few suggestions from older threads, to no avail.


    Here are some more outputs from common suggestions.


    Webgui login error:


    Failed to connect to socket: No such file or directory



    journalctl -xe



    sudo omv-engined -d -f gives:

    Illegal instruction



    sudo dpkg --verify



    Just flashmemory and extras plugins installed:

    sudo dpkg -l |grep openme




    Lots of disk space left

    df -h



    Everything is up to date using apt.



    Any thoughts anyone?