Posts by Coxeroni

    Had time to think about this over the weekend. I will probably switch to a proprietary solution (QNAP probably), since this USB case probably takes me nowhere.
    My family media is also precious enough to spend a euro or two more, if things run smooth and without hiccups.


    Thanks to everybody that helped to support me, I always appreciate the communities around these kind of projects.


    Cheers

    (Had to seprate the posts due to too many characters)


    This is what the smart-log said yesterday when I rebooted. The upper four entries where from former boots with different drive IDs:


    Additionally, I am not sure whether smart status can be checked correctly. "not capable of SMART Health Status check" does not sound like everything is ok. Dunno if it makes sense to investigate further or if I just ditch that case (I can still send it back) and look for a different solution.

    Sorry for being so unspecific, so here is a bit more info on the subject:


    What I am taking about is the ID as in /dev/disk/by-id/ :


    The part behind the RANDOM changes with every reboot. This is also, what is displayed in the drives section of OMV (s. screenshot attached).


    The UUIDs are different and probably do not change during reboot (haven't checked that). See the "ironwolf" entries.


    Code
    root@chromebox:~# blkid
    /dev/sda1: UUID="3a4bfe58-2d98-4b26-b97a-988100f310a2" TYPE="ext4" PARTUUID="0443930c-01"
    /dev/sda5: UUID="8e937b4d-72d8-4a67-bfc8-6812c4afc9da" TYPE="swap" PARTUUID="0443930c-05"
    /dev/sdb1: LABEL="ironwolf1" UUID="e8a0ab25-f031-4f04-8faa-f5a8a77950dd" TYPE="ext4" PARTUUID="0d621189-a97d-44ef-b945-0f1bb83ea4ff"
    /dev/sdc1: LABEL="ironwolf2" UUID="680ee841-1f68-4a0d-ab99-f287c6a18ac4" TYPE="ext4" PARTUUID="ea15b7be-7425-44b0-b2a3-92049a0aaca4"
    /dev/sdd1: LABEL="sd" UUID="da30eda9-c56d-4a67-b216-1933ebf21d74" TYPE="ext4" PARTUUID="328e759b-9aa5-4f88-ba8e-3fab2052b4f8"

    But as I said, the s.m.a.r.t monitoring is directed to the "by-id" devices and therefore fails after reboot, since the drive now has a different id:

    First annoyance probably related to the case:
    The drives have a different ID after every reboot, since their serial number is displayed as "RANDOM_some characters", and that characters change with every reboot. Therefore smart monitoring doesn't work after reboot and has to be activated again every time.


    Can I put the /dev/by-label in the /etc/smartd.conf instead of the ID? Or is there any other possibility for solving this?

    I happened to order a different external case (IB-RD3662U3S), but from the same brand. Should be here today, I didn't read any reports that these don't work with Linux, so my hopes are still high that I won't encounter any problems.
    In the mean time I already got used to OMV and so far like the capabilities of it.
    I also bought a small UPS, altouhght there are barely any power outages in my area ;)

    Wenn es nur für den Zugriff für dich selbst geht, würde ich bei VPN bleiben und Total Commander installieren. Damit kannst du auf smb/cifs Freigaben zugreifen ((S)FTP wäre auch möglich).


    Zum Teilen an Freunde würde ich dir eine Lösung über Nextcloud an's Herz legen. Erstens weil du freigebene Ordner über smb nicht über's Internet teilen kannst und zweitens weil du mit Nextcloud eine bessere Kontrolle darüber hast, wer auf was und wie zugreifen darf.


    Nextcloud gibt es z.B. auch über docker und läuft dann über Port 80 (unter OMV vermutlich nicht, da dort schon das WEB-UI drüber läuft) bzw. 443 sofern du SSL-Verschlüsselung aktiviert bekommst (benützt noch ein Zertifikat z.B. über Letsencrypt). Diese Ports würde ich dann im Router freigeben. Aber zuerst sollte die Nextcloud Instanz laufen und mit sicheren Passwörtern abgesichert sein.



    Nextcloud hat den Vorteil, dass du damit dann quasi eine eigene, private Cloud hast auf die du bequem von unterwegs zugreifen kannst.

    I have not fully understood the concept of folders, shares and mounts of OMV... Currently I am thinking how I should share an rclone mount I need to distribute to my nvidia Shield.


    So normally I would mount the rclone mount to something like /mnt/whatever and put that into the smb config. As I already learned, this is not how to do I properly in OMV.


    So first, where do I need to put the rclone mount? On the OS drive? On a data drive? With the latter I can probably add it to the shared folders and work my way from there. Is this the proper way to do it?

    You just have to get used to the syntax of the compose file, but often you find an example at docker hub for the respective container, just like for the run command. Containers created with compose also appear in the docker gui of OMV, so can see there status from there.

    Thanks Adoby for that long answer. The RAID setup was just for information. I will see if the case suits my purpose and if it doesn't work properly, I will send it back. It seems as I don't need the RAID function of the case anyway, but now it is ordered ;)


    How will the speed from one HDD to the other be in such a setup? I mean the files don't need to pass the USB bus twice, don't they? Since I don't copy to both HDDs simultaneously, speed won't be cut in half I hope.

    Thank you both, so be it :)
    I will have a look at rsnapshot. haven't heard of that yet. Sounds well suited for my case as it seems.


    One question about that Icy box encasing (IB-RD3621U3): if I understood correctly, this case also has a RAID controller on board, the settings RAID 0, 1, Single or JBOD/Big can be set with a jumper-linke setup (https://www.raidsonic.de/produ…x_de.php?we_objectID=3589). If I would want to use any of the RAID settings of the drive, how would that needed to be addressed in OMV? I wouldn't set a software RAID on top, would I?

    After operating two external drives on my Asus Chromebox for some years, I recently discovered that (at least) one of them is having bad sectors. Since I don't want to jeopardise my digital family memories, I want to switch to a more robust setup with OMV on the Chromebox and two 2 TB Ironwolfs in an external Icy Box case. Since I am new to the OMV family, I appreciate any hints or advice to my planned setup. OMV4 is already installed on the Chromebox and I have made the first steps with it (the HDDs were not yet delivered).


    My plan is to operate the two HDDs separately (i.e. no RAID), writing to disk A and rsync the files to disk B as a backup. I also plan on regularly making an off-site backup to an external volume. I would prefer to let rsync run without --delete flag to avoid any loss due to accidental deletion on drive A.


    In the beginning I was thinking about a RAID 1 setup, but apart from the photos I also automatically copy recordings from TV (from my cable receiver) to drive A , which are then directly uploaded to the cloud and deleted after upload from the drive. So these files do not need to be mirrored and mirroring them only increases writings without any purpose in my opinion. Future usage might change, but currently this is what is planned.


    As file system for the discs I thought about keeping things simple using ext4 on both drives, but I have no experience with the other formats (XFS, ZFS, BTRFS) and if they offer any advantages in my case.


    So if you have any comments/hints on my setup please let me know. If I posted in the wrong section, please move to a more appropriate area.