Beiträge von mrfaggio

    Hi folk,

    If you have similar problems, I recommend the following video by Techno Dad (very well done and which unfortunately I only discovered a short while ago) that explains the main settings of OMV 6.

    Externer Inhalt www.youtube.com
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.

    Have fun and good work.

    Hi everybody,


    After ruining the contents of the previous microsd with OMV6 installed of my 4GB RPI4, I proceeded to a new installation on a new microsd.


    The installation finished successfully and I redefined all options, download plugins, etc.


    Now I am in the situation that OMV6 sees all the connected disks: the microsd, a 128 GB SSD, and two 2.5 1 and 2 TB HDDs (the 2 TB one partitioned into two 1 TB ones).


    SSD is connected via the usb3, while the two HDDs are connected also to the second usb3, but they are powered separately.


    Now I am in the situation that OMV6 sees the disks,

    but not the fs

    And if I try to do a mount it only sees the two partitions of the SSD.

    Also I have the same problem with S.M.A.R.T which sees the 3 disks as a device

    But if I try to schedule a check and try to select the device it doesn't find anything.

    I have forced the mount of the disks from fstab

    proc /proc proc defaults 0 0

    PARTUUID=1f09f3c2-01 /boot vfat defaults 0 2

    PARTUUID=1f09f3c2-02 / ext4 noatime,nodiratime,defaults 0 1

    # a swapfile is not a swap partition, no line here

    # use dphys-swapfile swap[on|off] for that

    # added manually

    PARTUUID=769ce51b-01 /media/Backup_A ext4 defaults 0 0

    PARTUUID=9a9cbdb3-01 /media/Backup_B ext4 defaults 0 0

    PARTUUID=9a9cbdb3-02 /media/Altro ntfs-3g defaults 0 0

    And the s.o. sees them

    Filesystem Size Used Avail Use% Mounted on

    /dev/root 59G 2.7G 54G 5% /

    devtmpfs 1.7G 0 1.7G 0% /dev

    tmpfs 1.9G 0 1.9G 0% /dev/shm

    tmpfs 759M 948K 758M 1% /run

    tmpfs 5.0M 4.0K 5.0M 1% /run/lock

    tmpfs 1.9G 0 1.9G 0% /tmp

    /dev/mmcblk0p1 255M 31M 225M 12% /boot

    /dev/sdb1 916G 5.2G 865G 1% /media/Backup_A

    /dev/sdc1 916G 66G 805G 8% /media/Backup_B

    /dev/sdc2 932G 717G 216G 77% /media/Altro

    folder2ram 1.9G 93M 1.8G 5% /var/log


    And ls shows me their contents

    total 56

    drwxrwxrwx 2 root root 16384 Mar 29 2021 lost+found

    drwxrwxrwx 3 root root 4096 Mar 29 2021 Mame

    drwxrwsrwx 2 root users 4096 Jun 11 2021 Document

    drwxrwsrwx+ 5 root users 4096 Aug 25 22:39 Photo

    -rw------- 1 root users 7168 Aug 25 23:24 aquota.user

    -rw------- 1 root users 7168 Aug 25 23:24 aquota.group

    drwxrws--- 4 root users 4096 Aug 26 16:18 Backup_B

    drwxr-xr-x 5 root root 4096 Oct 11 19:43 ..


    I also tried a write test with success.


    Also, with the previous version of OMV6 (I don't remember which one) I had no problem, it saw both disks and fs and allowed me to create shared folders by selecting fs, so, personally, I rule out it being a disk power problem also because at the s.o. level there are no reported anomalies.


    So what could it be?


    The current version I am using is 6.0.43-1 on the latest 64 version of raspios lite from September, kernel 5.15.61-v8+



    Thank you very much!

    Never used berryboot. Why do you want to do that? I don't see any need and with the problems you are having with it, that confirms my comment.

    It is pointless to look for bad blocks on an SD card. If you suspect something is wrong with the card, it is not to be trusted.

    I use berryboot because I want to use the RPI also as a desktop pc with a second partition with RPI os with desktop, and I want to use it also like a game pc with a third partition and batocera. I also used pinn but with the same result. I used badblocks command to check the usb disk.

    I think it has been a problem with the debian repositories.

    the problem seems to depend on the card.

    But now I have a problem with the OMV script and berryboot as I writed to ryecoaaron.

    Thank you.

    cards can start to hit their write limit on certain sectors. And I have seen them fail in odd ways where only one or two files are corrupt.

    You have right. I changed the card and after the OMV script and reboot everything works.

    So I tried the next step: to use berryboot to create a partition on a usb/ssd disk with the same Bullseye os and to use the same script.

    The result is that after the first reboot the RPI continues to reboot.

    I checked the /dev/sda1 fs of the usb disk to find bad blocks with the command

    sudo badblocks -v /dev/sda1 > badsectors.txt

    but it did not find any error.

    So why the RPI continues to reboot after the end of the OMV script?

    Thanks!

    Hi guys,

    I tried to install with success several OMV6 to RPI4 on o.s. Bullseye, but now after i execute the script

    wget -O - https://raw.githubusercontent.…tallScript/master/install | sudo bash

    the RPI reboot automatically and then hangs after creating with success the system users.

    Seems it found something on a fs, but the message vanishes after 1 second and I cannot read it.

    The screen tells me that no longer receive a signal from the raspberry, which has both the green and the red light permanently on, and the router does not see the raspberry connected either.

    The installation seems to finish correctly, the problems occur after reboot.

    Is this a problem with the script?

    Thank you.