Posts by Perf!

    Story closed: Finally, I made a backup of all data I could grab and set-up a new OMV.


    My ratio: Updates, upgrades from within OMV-Extras and a new FW driver for the raid system (Micron) finally created three times different /dev/sda1 entries in /etc/fstab.

    Editing fstab resulted in files showing-up again, but access rights could not be administrated anymore.


    So long story short: Get all data you could grab, set-up a new server and there you go again.


    This time I was in luck: No data loss, just one weekend. 8:[

    What would happen, if I simply add the somewhat changed info in fstab?


    Here some additional data 'areascout', the maker of the great CloudShell2 image from the Odroid forum, did ask me to process:


    Let me know, if you need additional data.

    I have a problem with a raid1 system running on JMICRON USB controller with 2 SATA disks.


    Reading through the forum, I already found the issue about the UDEV database. Maybe this is also related to this one?


    Introduce a UDEV database to fix USB PATA/SATA bridge contoller issues #746


    Error Message:



    Maybe helpful trace output:



    Circumstances:


    The system was running fine and SMB shares could be shared across my network. Docker files populated and all alive and kickin'.

    In the next step I did an update via the OMV Extras menu and after reboot, I could use the nginx web pages from the docker, but SBM shares did fail.

    Looking at the OMV (great thing!) File Systems entry, /dev/sda1 wasn't mounted anymore. File references in the SMB menu were still showing the disc correctly.


    Note:


    I found a note about the JMICRON HW at the bottom of the troubleshooting guidelines and already added the "fix" as instructed. Bit w/o any improvement after reboot.



    Any support appreciated. - Please instruct me what additional info I could provide.

    User Adoby provided the solution in another Post LINK:


    Quote: "I used to have a lot of strange problems with my HC2s. I figured out that if I used or activated ANY of the physical disk properties, then everything went haywire."


    I remember that I compared settings of my 2 OMVs yesterday, and added physical disk properties in the morning.
    So the power outage was not the root cause, but indeed the physical disk properties!


    After deactivation and reboot, the system came back to normal operation!


    Again what learned! <LoL>

    Hallo Leo,


    Schickes Cabrio! : )


    Ich kann die /dev/sda1 auch mounten, es funktioniert dennoch nicht.
    Eigenartig ist auch, daß der Automount der Platte nicht mehr funktioniert.
    OMV scheint hier nach dem Disk-Label virtuell vorzugehen, doch hier ist durch den Stromausfall irgendetwas vermurkst.


    Das syslog rund um den Stromausfall hätte ich, wenn's jemand lesen möchte.
    Hier der erste kritische Ausschnitt von gestern:


    Nov 3 17:37:07 DatenKaschterl systemd[1]: Mounted /boot.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: dev-sda1.device: Job dev-sda1.device/start timed out.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: Timed out waiting for device dev-sda1.device.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: Dependency failed for File System Check on /dev/sda1.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: Dependency failed for /srv/dev-sda1.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: srv-dev\x2dsda1.mount: Job srv-dev\x2dsda1.mount/start failed with result 'dependency'.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: systemd-fsck@dev-sda1.service: Job systemd-fsck@dev-sda1.service/start failed with result 'dependency'.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: dev-sda1.device: Job dev-sda1.device/start failed with result 'timeout'.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: dev-disk-by\x2dlabel-DatenKaschterl.device: Job dev-disk-by\x2dlabel-DatenKaschterl.device/start timed out.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-DatenKaschterl.device.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: Dependency failed for /srv/dev-disk-by-label-DatenKaschterl.
    Nov 3 17:37:07 DatenKaschterl systemd[1]: Dependency failed for /export/Pit.



    und ein paar Sekunden später:



    Nov 3 17:37:44 DatenKaschterl monit[1513]: 'rrdcached' process is running with pid 1841
    Nov 3 17:37:44 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-disk-by-label-DatenKaschterl' status failed (1) -- /srv/dev-disk-by-label-DatenKaschterl is not a mountpoint
    Nov 3 17:37:44 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-sda1' status failed (1) -- /srv/dev-sda1 is not a mountpoint
    Nov 3 17:38:14 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-disk-by-label-DatenKaschterl' status failed (1) -- /srv/dev-disk-by-label-DatenKaschterl is not a mountpoint
    Nov 3 17:38:14 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-sda1' status failed (1) -- /srv/dev-sda1 is not a mountpoint
    Nov 3 17:38:34 DatenKaschterl systemd[1]: dev-disk-by\x2dlabel-DatenKaschterl.device: Job dev-disk-by\x2dlabel-DatenKaschterl.device/start timed out.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-DatenKaschterl.device.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: Dependency failed for /srv/dev-disk-by-label-DatenKaschterl.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dDatenKaschterl.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2dDatenKaschterl.mount/start failed with result 'dependency'.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/DatenKaschterl.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-DatenKaschterl.service: Job systemd-fsck@dev-disk-by\x2dlabel-DatenKaschterl.service/start failed with result 'dependency'.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: dev-disk-by\x2dlabel-DatenKaschterl.device: Job dev-disk-by\x2dlabel-DatenKaschterl.device/start failed with result 'timeout'.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: dev-sda1.device: Job dev-sda1.device/start timed out.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: Timed out waiting for device dev-sda1.device.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: Dependency failed for File System Check on /dev/sda1.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: Dependency failed for /srv/dev-sda1.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: srv-dev\x2dsda1.mount: Job srv-dev\x2dsda1.mount/start failed with result 'dependency'.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: systemd-fsck@dev-sda1.service: Job systemd-fsck@dev-sda1.service/start failed with result 'dependency'.
    Nov 3 17:38:34 DatenKaschterl systemd[1]: dev-sda1.device: Job dev-sda1.device/start failed with result 'timeout'.
    Nov 3 17:38:44 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-disk-by-label-DatenKaschterl' status failed (1) -- /srv/dev-disk-by-label-DatenKaschterl is not a mountpoint
    Nov 3 17:38:44 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-sda1' status failed (1) -- /srv/dev-sda1 is not a mountpoint
    Nov 3 17:39:00 DatenKaschterl systemd[1]: Starting Clean php session files...
    Nov 3 17:39:00 DatenKaschterl systemd[1]: Started Clean php session files.



    Wenn ich die Disk manuell mounte (Bild anbei), kann ich auf der Konsole die Dateien sehen und nutzen. Jedoch funktionier die Freigabe immer noch nicht über das OMV Interface.



    Hier der file system table:


    UUID=2db917ed-05ca-4752-961e-fd93b71d4fd4 / btrfs defaults,noatime,nodiratime,commit=600,compress=lzo 0 1
    UUID=449b9d35-2d43-4613-840c-19929c49201e /boot ext4 defaults,commit=600,errors=remount-ro 0 2
    tmpfs /tmp tmpfs defaults 0 0
    # >>> [openmediavault]
    /dev/disk/by-label/DatenKaschterl /srv/dev-disk-by-label-DatenKaschterl ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /srv/dev-disk-by-label-DatenKaschterl/Pit /export/Pit none bind,nofail 0 0
    /srv/dev-disk-by-label-DatenKaschterl/Claudia /export/Claudia none bind,nofail 0 0
    /srv/dev-disk-by-label-DatenKaschterl/Yvonne /export/Yvonne none bind,nofail 0 0
    # <<< [openmediavault]



    Der virtuelle Eintrag für


    /dev/disk/by-label/DatenKaschterl /srv/dev-disk-by-label-DatenKaschterl ext4


    ist vorhanden, aber /dev/disk/sda1 erst nachdem ich es manuell im OMV-Interface mounte:


    UUID=2db917ed-05ca-4752-961e-fd93b71d4fd4 / btrfs defaults,noatime,nodiratime,commit=600,compress=lzo 0 1
    UUID=449b9d35-2d43-4613-840c-19929c49201e /boot ext4 defaults,commit=600,errors=remount-ro 0 2
    tmpfs /tmp tmpfs defaults 0 0
    # >>> [openmediavault]
    /dev/disk/by-label/DatenKaschterl /srv/dev-disk-by-label-DatenKaschterl ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/sda1 /srv/dev-sda1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /srv/dev-disk-by-label-DatenKaschterl/Pit /export/Pit none bind,nofail 0 0
    /srv/dev-disk-by-label-DatenKaschterl/Claudia /export/Claudia none bind,nofail 0 0
    /srv/dev-disk-by-label-DatenKaschterl/Yvonne /export/Yvonne none bind,nofail 0 0
    # <<< [openmediavault]



    Dennoch funktioniert die Verlinkung nicht.
    Wie kann ich ein Device /dev/disk/by-label/DatenKaschterl manuell anlegen?


    Hat noch jemand einen Tipp?


    Beste Grüße,
    -Pit

    Files

    • gemounted.png

      (98.86 kB, downloaded 107 times, last: )

    Hi there,



    I lost my disk after a power outage, yesterday.


    The disk is still visible in the OMV web interface, I can mount the disk, but can't access directories anymore.
    My syslog report shows the following suspicious entry:


    Nov 4 00:09:15 DatenKaschterl monit[1513]: 'mountpoint_srv_dev-disk-by-label-DatenKaschterl' status failed (1) -- /srv/dev-disk-by-label-DatenKaschterl is not a mountpoint


    Any idea how I could get this fixed?
    Output of blkid attached.



    Thanks,
    Perf!

    Files

    • Error.txt

      (2.89 kB, downloaded 78 times, last: )