Posts by rfv-370

    Hello

    we are 7 month later and.... I have the very same problem.

    My LUKS encrypted disk just disapear few days after reboot , all the time...

    What is terrible is that on the OMV interface it appears as mounted !!! But it is not...

    Any idea for a workaround ????

    This is really a big issue...

    I got the same issue apparently...

    The ssh works and the VNC as well but nginx is non-updatable... and I cant find a way to get OMV web gui back to work any help would be helpful...


    I tried

    $ sudo apt install --reinstall --install-recommends nginx

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.

    1 not fully installed or removed.

    Need to get 88.5 kB of archives.

    After this operation, 0 B of additional disk space will be used.

    Get:1 http://ftp.igh.cnrs.fr/pub/os/linux/raspbian/raspbian buster/main armhf nginx all 1.14.2-2+deb10u4 [88.5 kB]

    Fetched 88.5 kB in 1s (153 kB/s)

    (Reading database ... 133910 files and directories currently installed.)

    Preparing to unpack .../nginx_1.14.2-2+deb10u4_all.deb ...

    Unpacking nginx (1.14.2-2+deb10u4) over (1.14.2-2+deb10u4) ...

    Setting up nginx-full (1.14.2-2+deb10u4) ...

    Job for nginx.service failed because the control process exited with error code.

    See "systemctl status nginx.service" and "journalctl -xe" for details.

    invoke-rc.d: initscript nginx, action "start" failed.

    ● nginx.service - A high performance web server and a reverse proxy server

    Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)

    Active: failed (Result: exit-code) since Sun 2021-06-27 12:33:39 CEST; 30ms ago

    Docs: man:nginx(8)

    Process: 18328 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

    Jun 27 12:33:39 Minerva systemd[1]: Starting A high performance web server and a reverse proxy server...

    Jun 27 12:33:39 Minerva nginx[18328]: nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (2: No such file or directory)

    Jun 27 12:33:39 Minerva nginx[18328]: 2021/06/27 12:33:39 [emerg] 18328#18328: open() "/var/log/nginx/access.log" failed (2: No such file or directory)

    Jun 27 12:33:39 Minerva nginx[18328]: nginx: configuration file /etc/nginx/nginx.conf test failed

    Jun 27 12:33:39 Minerva systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE

    Jun 27 12:33:39 Minerva systemd[1]: nginx.service: Failed with result 'exit-code'.

    Jun 27 12:33:39 Minerva systemd[1]: Failed to start A high performance web server and a reverse proxy server.

    dpkg: error processing package nginx-full (--configure):

    installed nginx-full package post-installation script subprocess returned error exit status 1

    dpkg: dependency problems prevent configuration of nginx:

    nginx depends on nginx-full (<< 1.14.2-2+deb10u4.1~) | nginx-light (<< 1.14.2-2+deb10u4.1~) | nginx-extras (<< 1.14.2-2+deb10u4.1~); however:

    Package nginx-full is not configured yet.

    Package nginx-light is not installed.

    Package nginx-extras is not installed.

    nginx depends on nginx-full (>= 1.14.2-2+deb10u4) | nginx-light (>= 1.14.2-2+deb10u4) | nginx-extras (>= 1.14.2-2+deb10u4); however:

    Package nginx-full is not configured yet.

    Package nginx-light is not installed.

    Package nginx-extras is not installed.

    dpkg: error processing package nginx (--configure):

    dependency problems - leaving unconfigured

    Errors were encountered while processing:

    nginx-full

    nginx

    E: Sub-process /usr/bin/dpkg returned an error code (1)


    No success. I thought it was because I had clone my original SD card but can't find a link between cloning and the upodating...

    Hi,

    I am looking at finding a way to catch the result of disk.decrypted.sucessfully , so I can trigger a daemon or a script after the decryption is sucessful?


    I get fine the email that my disk is decrypted fine:


    The system monitoring needs your attention.

    Host: \M**********

    Date: Sun, 20 Jun 2021 18:00:06

    Service: mountpoint_srv_HDA1

    Event: Status succeeded

    Description: status succeeded (0) -- /srv/HDA1 is a mountpoint

    This triggered the monitoring system to: alert


    this is cool but I cannot see any specific related services or targets in systemd/system/ that I could use as a trigger to start a service or a script after the decryption is sucessful.

    May be I look in the wrong place? Any ideas on the matter ?

    Hi,
    I have been banging my head on a similar problem for few days.
    I checked absolutely everything in and out....-user permission, ACL, privilige, shares, smb.conf... etc...


    And finally for some reason I discovered that OMV seems NOT to add user to the Samba database - or I do not know how to do it!!!


    But when I did

    smbpasswd -a MyUser

    So suddenly MyUser (being the name of your user) was able to access all shares... - use the same Unix password... just in case.
    I did this for all my users and then bang everything worked.

    it might help.

    ps: I thought that adding the user to the group 'sambashare' was enough but apparently not....

    @ ryecoaaron


    I was kidding about the poll. ;-)


    1 - People having the problem are probably using the same (or same family) usb-to-sata chipset
    -Good point. I will have a check around this.
    here are mine for my 2 2To disks:
    FYI:
    Bus 001 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
    Bus 001 Device 006: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge


    2 - Due to the low power consumption of an RPi, most people don't shut it down and avoid the issue.
    -yes, it is probably true.
    FYI:mine must reboot everyday via a root-cron programmed job.


    3 - Some are trying to power the drive directly from the usb port on the RPi with a power supply that is too small to power both.
    Agree. All drives must externally powered.
    FYI:All my drives are externally powered.


    4 - People using multi-drive usb enclosures are probably seeing the RPi boot before the enclosure is ready.
    Not quite sure about this point.
    In my case the drives (and the rpi) are always on power.
    Just the pi is asked to reboot. So the drives and the usb-sata chipset should be ready and the drives spinning when Rpi boots up and call for them.


    You are right usb-stick always mount...even in Wheezy.


    More thoughts into this issue, I must have.


    Thanks Ryecoaaron.


    Ps: in the back of my mind, I wonder is systemd has not improved the boot-up sequence on the fresh Debian8 images? Which would give the impression that it is smoother with Jessie...

    ryecoaaron
    I would not be so straightforward and sure about the fact it is not widely spread...
    - ie that USB external should connect on boot.
    And that only very few people have the issue. It would be interesting to have a poll ! :))
    -at least I do have the problem...


    FYI: I run about 5 to 6 Rpi (all Rpi3) at all time and I am still trying to understand why some Rpi do boot with USB external drive 100% of the time fine and some not...And I noticed that some would not boot fstab samba shares either while some other of my Rpi would boot fine on the very same network and same system and config... strange isn't it?.



    arxaios
    Only one of my Rpi (my NAS!) out of the 6 runs OMV stonerbuner. The others do run on Raspbian Jessie and some of them have the very same problem. So I think, I can say that the issue is not OMV related. But I noticed this issue is high certainly with Wheezie...(even CUPS is a problem on Wheezy, rats!) and the image of OMV stonerburner runs on Wheezie! I really doubt USB drive connection at boot is an OMV issue. It is a system issue. Most probably a boot-up sequence order issue...



    I have noticed that using a clean image of Raspbian 'tends' to improve the situation, yes, it is true. The last 6 SD I flashed (for me and friends) with a new Raspbian where stable with usb connect and samba share connect at boot time - yeah!!.
    So I have less issue "statistically" when I re-install from a clean image -at least on Jessie- than if I do some upgrade...
    Several of my SD are Jessie upgraded from Wheezie and yes I can say that most of them will have issue booting USB share.
    So from my little experience I would say: system issue / Wheezie issue translated into a Jessie issue when upgarded -rats again!.
    Or may be I do something wrong... but if so, why the "sudo mount -a" works 100% ...?
    weird!
    As "sudo mount- a" forces a re-read of fstab... why it shoudl work when I SSH and not at boot time?
    So I suspect it is an issue of how the boot order sequence is done really - the "mount -a" arrives too early in the boot sequence and something is missing for mounting all properly. It seems to be the most realistic issue for me.
    And this is issue "may" be inherited when upgrade a Wheezie to Jessie.



    keksznet
    Yes, even with the above tricks USB external drive gets disconected twice a month for me usually for no reason I can understand on my OMV stoneburner (Wheezie)...


    Using delay in rc.d and/or cdmline.txt certainly helps (it was every day before adding the delays!) but it is not foolproof...yet.
    I am investigating a further forced-delayed-mount using cron on user level as user is the last in boot sequence so all daemon should be up and running properly.
    I will report when/if I have some results or improvement.

    I have done the following:


    added "auto" in the FSTAB right after "defaults,"


    and put the delay to 8 in /boot/cmdLine.txt and delay to 35 in rc.local sleep 35 .


    I will test a week with this settings...



    and rc.local



    and the cdmline.txt



    Code
    dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
    rootdelay=8


    I will post back to let you know about stability.

    Hi Gents & Gals(maybe?),


    one step further in Pi with OMV and probably solving the issue that pbauer and I faced - with RAID and with not mounting drive on reboot:


    I realise (now) that the USB drives are not mounting each time automatically...after a reboot. Ah ah ah!


    Which probably was a real problem for the RAID manager to access the disks....potentially...


    I had this issue of losing the USB drives after having removed the RAID so clearly not a RAID issue but a USB mount issue with fstab. (and of course my Samba was donw because of not USB disk mounted, eh eh eh!)


    So each time I had to manually 'mount -a' ... a pain in the neck... really. Browsing for a boot script around gave me the answer:


    I had to use this post here http://www.htpcguides.com/prop…usb-storage-raspberry-pi/ - scroll down to the chapter : "
    Fix Raspberry Pi 2 Mounting Issues"
    This does 2 things - add a delay on bootup and activate "mount -a" via a boot script.


    So now I have USB drives mounting properly mounted at each boot!


    I have not dared to re-configure the RAID 1...(still planning of using rsync instead).


    But if some want to use RAID on Pi they should know about this - I think. (it was new to me!).


    Hope this helps.


    Best


    rfv


    ps: Started hacking with ZX81 (yeah I know I am the Yoda of the team, I guess!)- and Raspi is to young generation what ZX81 was to mine!
    I just love it! Triple bang for the Raspi Foundation!


    pps: just to cross reference as this issue of USB not mounting leads to RAID failure, it was also discussed here for RAID 1 issue on Raspi for OMV:
    Lost RAID1 after reboot


    ppps: just in case the post is not there any longer: here the solution for mounting each time you boot USB drive script on a raspberry pi (raspi):
    Fix Raspberry Pi 2 Mounting Issues
    Thanks to Jake for bringing this to my attention. Apparently there is a bug in the Pi 2 that messes up automounting. You can fix it by creating a delay.
    Open up the /boot/cmdline.txt file
    sudo nano /boot/cmdline.txtAdd this line to the bottom, you can increase this delay if necessary
    rootdelay=5Hit Ctrl+X, Y and Enter to save and exit, then reboot to see if it automounts now.
    If the Raspberry Pi hard drive still does not automount we can use rc.local (thanks Julian)
    sudo nano /etc/rc.localAdd this lines before the exit line
    sleep 30sudo mount -aexitCtrl+X, Y and Enter to save
    Reboot again to test
    sudo reboot


    Enjoy Raspi!

    Hi pbauer and Aaron,


    one step further in Pi with OMV and probably solving the issue that pbauer and I faced - with RAID and with not mounting drive on reboot:


    I realise (now) that the USB drives are not mounting each time automatically...after a reboot. Ah ah ah!


    Which probably was a real problem for the RAID manager to access the disks....potentially...


    I had this issue of losing the USB drives after having removed the RAID so clearly not a RAID issue but a USB mount issue with fstab.


    So each time I had to manually 'mount -a' ... a pain in the neck... really. Browsing for a boot script around gave me the answer:


    I had to use this post here http://www.htpcguides.com/prop…usb-storage-raspberry-pi/ - scroll down to the chapter : "
    Fix Raspberry Pi 2 Mounting Issues"
    This does 2 things - add a delay on bootup and activate "mount -a" via a boot script.


    So now I have USB drives mounting properly mounted at each boot!


    I have not dared to re-configure the RAID 1...(still planning of using rsync instead).


    But if some want to use RAID on Pi they should know about this - I think. (it was new to me!).


    Hope this helps.


    Best


    rfv


    just in case the post is not there any longer: here the solution for mounting each time you boot USB drive script on a raspberry pi (raspi):



    Fix Raspberry Pi 2 Mounting Issues


    Thanks to Jake for bringing this to my attention. Apparently there is a bug in the Pi 2 that messes up automounting. You can fix it by creating a delay.
    Open up the /boot/cmdline.txt file
    sudo nano /boot/cmdline.txtAdd this line to the bottom, you can increase this delay if necessary
    rootdelay=5Hit Ctrl+X, Y and Enter to save and exit, then reboot to see if it automounts now.
    If the Raspberry Pi hard drive still does not automount we can use rc.local (thanks Julian)
    sudo nano /etc/rc.localAdd this lines before the exit line
    sleep 30sudo mount -aexitCtrl+X, Y and Enter to save
    Reboot again to test


    sudo reboot

    Hi pbauer84,
    well yes, actually a samba share + rsync of the full drive will do the same as a raid 1 actually.
    Which I may have to do as I can see a solution right now - but I am uneasy of this situation for several issues:
    1) I have lost data apparently (still checking) - so the there would be a serious RAID issue somewhere
    2) GPT table can't be corrupted just by chance (have you checked yours?)
    3) OMV is not reacting well when I try to re-setup the RAID through the interface


    I am new to OMV and I may do something which frustrate the system philosophy/process...
    But still it is weird...
    I want /need to understand if not I cannot trust the system with my data!
    so I will try to trace the trail

    Hi pbauer84,
    both drives are in casing with their own power supply, so the usb card of each drive already powered - I guess.
    And I do not understand how a USB connection error could trigger the full raid to disappear...
    I will try to trace all logs to understand what happened - but I need some time - may be tonight.


    What I find strange is that we both experienced the same issue with the same config at the same time...
    This may be related more with OMV on this specific config...and/or an issue with an update....?


    Is there anybody who could help on how to find an explanation ?

    Hi,


    I got the very same problem!
    Same configuration - RPi3 with StoneBurner!
    cat /proc/mdstat is empty as well!
    Really weird. It means either something is wrong during our install or there is an inherent instability in stoneburner on RPI3???
    It was so hard to get OMV working to have a just a RAID 1 working....
    Frustrating...


    Well anybody has an idea on how we get back the Raid partition up?


    and / or what I (or we?) did wrong ?


    Really strange it says GPT is corrupted:

    it is quite weird when mounting the md1 I got this error message:



    apparently as FSTAB error but I can see how to correct this....


    Idea are welcome?

    here is what I have done, just in case someone needs to use it again:
    (my two disks where sda and sdb, I kept the boot and OS partition as in the orginal Tuto - just in case, it can be useful, but unlike in the original tuto I have not activated OMV on the USB drive, so it still runs on the SD car on the RPi):


    From Josip Lazic:
    http://lazic.info/josip/post/i…ediavault-on-raid-device/


    Used to create my RAID:
    1) créer les partitions: (avec un boot, un free pour un os si besoin, et les datas)
    parted -a optimal /dev/sda mklabel gpt
    parted -a optimal /dev/sda mkpart grub ext2 2048s 12M
    parted -a optimal /dev/sda mkpart root ext4 12M 4096M
    parted -a optimal /dev/sda mkpart data ext4 4096M 100%
    parted -a optimal /dev/sda set 1 bios_grub on
    parted -a optimal /dev/sda set 2 boot on


    2) Cloning partition a to b
    sgdisk -R=/dev/sdb /dev/sda
    sgdisk -G /dev/sdb


    3)Creating the RAID
    mdadm --create /dev/md0 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda2 /dev/sdb2
    mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3


    4)Creating File Systems
    mkfs.ext4 /dev/md0
    mdadm --detail --scan >> /etc/mdadm/mdadm.conf
    and then
    mkfs.ext4 -m 1 -L DATA /dev/md1


    I did all thsi work as root logged via ssh.
    best