Posts by Jopa

    Well, file system discussion is similar to OS discussion: There are systems coming from the high end and went down, and systems basing on small computers and grew up with their facilities. ZFS is one of the former - brought down especially by (Free)BSD - and md with ext4 one of the latter. Btrfs is a later development inbetween, trying to bring the best of ZFS down to smaller hardware.


    During the past 10 years I used all three FS and can tell, that FreeBSD implementation of ZFS was my favorite - until FreeNAS (today TrueNAS) moved from FreeBSD to debian linux (sic!) and the branch NAS4Free (today XigmaNAS) still does not really support Multi-Gb LAN. And btrfs users (Synology and Rockstor) still warn about using it with RAID5 or 6 configurations without an UPS...


    So when I got the hardware below, and saw, that latest proxmox rely on ZFS, too, I decided to go back to OMV, of which I used versions 2 and 3 already, and use the proxmox 8 kernel with it, that supports ZFS natively, rather than as the addon in former versions.


    It looks to be a good decision. Even if ZFS not seems to allow reducing the pool size yet like md or btrfs. But this is just a need to make sure about, what I really want. I.e. if I really want to accept possible break-down of my whole 6-HDD-RAID5/ZFS-1, if I need to replace one of the disks, or if I rather setup a RAID6/ZFS-2, which still allows a second disk to give up while resyncing the RAID...


    BTW: That was, what I meant, when I wrote, that I would not use RAID5/ZFS-1 with eight HDDs no more.

    Maybe it sounds a bit stupid. But did you always reboot or even shut omv down and restarted after installing updates - before you did something else?

    I learned this to be essential with debian linux. And so with omv, too.

    Latest news:


    Qnap BIOS actually can boot from a nvme in the pcie extension slot.


    So I flattened the slot bracket of a low-profile pcie-to-nvme adapter, drilled a threaded hole (M3) and now have omv on yet another drive, keeping all 6 hdd bays for data storage.


    And all without changing a single bit of original firmware, but BIOS boot setting only.


    BTW: This is possible with all TS-x53D (2, 4 or 6 bay types), as they all share the same motherboard and BIOS.

    There was a maintainance recently, and looks like montserrat wght font accidently got reestablished....


    From source code of this page:

    Code
    <!-- Stylesheets -->
    <link rel="stylesheet" type="text/css" href="https://forum.openmediavault.org/wsc/style/style-9.css?m=1753650872"><link rel="preload" href="https://forum.openmediavault.org/wsc/font/families/Montserrat/Montserrat%5Bwght%5D.woff2?v=1753647188" as="font" crossorigin><link rel="preload" href="https://forum.openmediavault.org/wsc/font/fontawesome-webfont.woff2?v=4.7.0" as="font" crossorigin type="font/woff2">

    Hey reycoaaron,

    well, as you probably read, unreadable issue is solved - and had nothing to do with software as such, and so with your omv expertise. Sorry, that I mixed it at first.

    Best regards

    Hi dcoulon,


    I have no idea no more, what happened to your OMV. Ok, give Boot repair a try - don‘t know it. I use testdisk and/or Hiren‘s Boot CD (HBCD) PE 1.08 running Win11 PE as a Live System.


    Re to add existing RAID5 drives I just know, that it is possible, but I did not do it yet.


    I‘m not at home until next monday, and cannot look after real omv procedures.

    Well, then let's try another way. First with the question, if you installed OMV on one of HDDs, or on a separate drive, before you added RAID drives?


    In first case it looks like the HDD, you replaced first, was the HDD, which OMV installed on and set as boot drive, and after you replaced it, BIOS did not find bootable HDD no more and changed its Boot Order settings or just cleared them. In second case, even if there was no need to, BIOS seems to have reacted same way.


    So next step, I'd do, is to check BIOS Boor Order or simply try Boot Override one by one. And if this does not do it, "Load optimized default settings" or even clear CMOS completely. At least the latter must BIOS let find a bootable drive if any.


    If OMV boots again now, then go Web GUI and there directly to Storage->S.M.A.R.T.->Devices and see, which of devices has status "bad" - should be the same as BIOS complained about -, highliight it and then click "Show details" and there "Attributes". Please make screenshot(s) of the bad attribute(s) and post it here. Further look, if OMV already set RAID5 "degraded" or still not, but anyway you should be able to access all your data to make backup(s). After data backup I'd suggest to clone the bad disk to your new one either from within OMV by omv-extras plugin "openmediavault diskclone" or by using a clonezilla boot stick.


    If BIOS is not able to boot from any of the disks, then things get more complicated. Because you either need extra tool (kit) booting from an USB stick to repair your original boot drive or install OMV completely new then. In case of new OMV installation I strongly recommend to use a seperate small (32GB is enough) but HiQ SSD for system. You can add existing RAID drive set then and run all procedures needed to exchange one drive via Web GUI.

    As BIOS S.M.A.R.T. check does not tell, what exactly is bad or assumed to be, try this:

    Put back the original HDD,

    enter BIOS,

    set "S.M.A.R.T. status check" to "Off",

    "Save changes and Reset".

    The PC should boot normally then and you can do a backup of data and system.

    The further depends on, how you created the RAID (by BIOS or by OVM). Maybe you can tell some more about it?

    I am currently running OMV on a QNAP 251D. It's a lot of fun. Apart from the LEDs, everything fits.


    But here I also boot from an NVME and have left the EMMC as it was, it's too small for OMV anyway. OMV, swap and docker applications are then on the NVME, , each on different partitions.


    I think I'll do the same with the ugreen. Unless someone explains to me that there are disadvantages to having everything on one physical SSD.

    I read about this, and about fan control not working. But with the 653D I had neither the LEDs nor the fan control issue.


    I'm looking forward to try an NVME attached at the expansion PCIe. Still need a suitable adapter card. If Qnap BIOS allows boot from there, then I can use all 6 bays for HDDs.


    Don't know, what disadvantages there could be with one physical SSD. Ok, any drive, regardless what type, allways may fail, and then you need to copy your backup to a new device, before you can go on. A RAID1 for system is more comfortable, of course, but for a private NAS I don't think it vital. In the past I used 32GB SLC-SSDs for all my DIY NAS setups (OMV, TrueNAS, XigmaNAS), and none of them ever failed. Not sure, what NVME I'll use for my Qnap, if possible, yet.

    Thank you Volker, for the screenshot.

    I see clearly now and can tell the "mechanism" of the unreadable issue. The font Montserrat[wght] aka Montserrat Thin actually is the lightest font I've ever seen, and its unreadability has nothing to do with OS, browser, plugins or other software, nothing with font source (local or web), but with the resolution of display.

    Think, all fellows, who have the issue, (still) use Full HD like me or even below. And rendering a font as light as Montserrat Thin for such "low" resolution just may result in lines only one pixel wide or even interrupted, making text hard to read or unreadable at all. With higher resolution (2K+ or better) there maybe some pixels rendered blanc, too, but this does not impact readability.

    For own trials I searched and installed some of the Montserrat fonts on my pc and used them with Custom CSS. For me Montserrat Light is nice with omv forum, ExtraLight is normally readable as well, but still a bit "shallow". See examples from Windows font viewer below.

    Best regards

    So, TO is obviously one of the <1 promille of users, for which it does not work, and me another one. And Volker was at least no so busy with other things, that he could not write the second post in this thread. Which, btw and sorry, was just like in the joke: "Everything fine at my site".

    And your reply reads to be the same: "Everything fine at my side". And then even: chatgpt will probably help you more.

    Great. You declare it as my own problem, or better: the problem of those, who have it. That includes the TO, elspeth and probably others, who were not aware of this thread.

    Away of that, I'm more than a bit disappointed about your last reply. In the past, you were a reliable "expert" for me, but now you don't even know about such simple basic things like system fonts...

    And again to Volker: I know, what he is doing, and as you mention his family, please tell him my best wishes. Hope, he never will have similar with his family as I have with mine actually.

    I followed Ugreens activities and the UDX2800 and especially the UDX4800 (Plus). They are really big steps in NAS market, and if I had not get a bad UDX4800 - that did not work not at all - I probably would be a fan of Ugreen NAS, too. As I'm a fan of other Ugreen devices, nevertheless.

    Only, after my trial with Ugreen NAS did not work, I looked around a bit more and found a Qnap NAS family, that Ugreen obviously tried to shift to the next level: the TS-x53D family. That are some years older already and still based on a J4125, but have already 2.5GbE and are fully open for 3rd party OSses, even without the need to overwrite the original eMMC. Maybe the smallest device TS-253D is too small for this, but the TS-453D and -653D are noteworthy. As one can let them boot from one of their bays without changing any bit of their eMMC.

    For details please search for "Qnap TS-x53D - nice 2.5GbE hardware to run OMV" in the forum. I admit, that I was quite sure, that Ugreen was the first with 2.5GbE for their NAS. Until I realized, that Qnap had it already some 5 years before.,,

    So well, let's run OMV this speed nativly. While others still run (1)GbE.

    I still spent some time looking after the Montserrat font. Just to find out, that this is already a family of 18 members now.

    Find details at github.com/JulietaUla/Montserrat/

    Shall I really download them all and rename one after the other to simply "Montserrat" to find out the one that fits for the omv forum? Or should I better spend my time with looking for system global substitutions for all "Montserrat" fonts? The existing as well as future.....


    Sorry, but I just cannot beleive, that even Volker does not seem to be engaged to make his omv forum comfortably readable for everyone.


    Best regards

    I overlooked to mention, that windows tells you anything about the fons installed. And my told me, that Montserrat was not installed, So I searched for that font and got one "Standard" and "Bold" couple, but this did not do it. So again: Which is the right Montserrat font, I can download to overcome the unreadable issue?

    You are right. And btw: I'm a developer for my own. More hardware but not only mcu software, too. And having some 280 fonts installed on my home pc and some 500 on my pc at work. But as both are windows machines, I'm still not knowing, what "standard" Linux fonts are. And where I can find the right Montserrat download, that would do the job and not urge me to use workarounds like plugins.

    And no. I won't install Debian or Ubuntu. I'm using latest Waterfox - a branch of Firefox, coming out to reduce it's absolutely to frequent updates - which is using same mozilla repos. And for me everthing is working fine. Except websites using Montserrat font.

    Hi all, who want to speed up your NAS to 2.5G,


    after I tried a bit with my Synology DS620slim and USB-to-2.5GbE-adapters - quite promissing - and had to give back a not working Ugreen DSX4800, I got an exceptional quote for a Qnap TS-653D including 5x14TB seagate EXOSs, which I accepted, and which turned out to be kind of a bingo.


    Because that Qnap, even if already some years old, has two native 2.5GbE ports, an intel J4125 SoC and a standard BIOS setting one able to boot from any EFI disk attached.


    As the first, I plugged in a monitor at the HDMI port, a keyboard at one of the USB2 ports and my Ventoy multi ISO stick at an USB3 port and pressed F7 after the first beep. Amazingly the boot menu allowed me to boot from Ventoy stick quite normally, and I could run memtest86 with or without "+", gparted, and even HBCD PE (Win11) and a live Linux (elementary OS 8) without any problems. Ok, with all QTS formatted drives plugged in there were not enough drive letters left for HBCD PE, and most of its tools were missing, but there was nothing keeping it from running basically. Funny enough. I actually had not thought, that a NAS hardware would run a full featured PC OS so completely at all.


    By that first trials I had noticed, that the BIOS could not only boot from "QNAP OS" and my stick as "UEFI OS", but still from a "P0". So I installed OMV on a separate SSD, and plugged this into one bay ofter the other, until it was offered as "P0" in bay5 and as "P1" in bay6. With OMV ssd in bay6 I went to BIOS and set boot order accordingly, rebootet and - had OMV booting. Without having anything of original Qnap installation touched, except for the BIOS settings.


    After this, I removed OMV ssd and booted QNAP OS again, saved the config, removed all disks and put an old but known good 500GB drive into bay1, to which I let install the actual Qnap software - just to set me able to check for later firmware updates, meaning espacially BIOS updates. For this, I just need to plug out all OMV drives, plug in the QTS drive, monitor and keyboard and let run QNAP OS again. If there is a new firmware update, I can do it, and then go back to OVM.


    Maybe there is yet another way to add a ssd/nvme with OMV by using a ssd adapter card in the pcie slot of the TS-x53D. But this is not clear at the moment. Some folks say, it is, other say no chance except with (expensive) original Qnap adapters only. I will just try out and keep you informed.


    Best regards