Posts by square_eyes

    I'm struggling to find a tutorial for optimising for 10GbE. I found this which has some steps but no real explanation as to where each setting is and what it's doing (such as - Parameters for NFS export: "async,no_subtree_check,insecure"). In another 10GbE thread there is a vague reference to OMV taking over all system config, and eventually overwriting things.


    Is there an approach to take with OMV in mind - e.g. omv-env variables and other system settings? I'd say with multi gig becoming more commonplace, it's worth a look if it doesn't exist somewhere already.

    Just upgraded my home lab to 10GbE, picked up a cheap 10GbE NIC... and I'm looking to reduce the hard drive speeds as a bottleneck.


    Currently I don't have raid, and my SAMBA shares act as a landing zone for Greyhole to run in the background and distribute files on other drives for redundancy.


    Since this home NAS is a bit of DIY fun, I'm looking at cheap and creative ways to take advantage of 10GbE,

    1. Could I add a RAID / SSD array as a cache to frequently accessed files?
    2. Or is my best bet to put the SAMBA shares on a more classic RAID, which doubles as the Greyhole landing zone. I'm not sure how this will affect read speeds, but I guess if I make the RAID LZ big enough, and also a destination drive, most reads will come off that drive?
    3. Or is it time for a rebuild? I love Greyhole and its ability to pool storage across random sized drives. But if it's not going to be performant I may look to change things.
    4. Finally, are there any resources on how I can optimise Linux with my build in mind for multi GB LANs?

    Soma... thanks for the suggestion. It didn't work and I was unable to work out why.


    I did actually break my original USB somehow (pretty sure not by being careless with dd!).


    So I thought I was in for a rebuild. Also using a boot-repair bootable USB I somehow fried the mobo of the old machine I was trying to migrate to. So my efforts switched to restoring a bootable USB from my backup, using the current OMV machine (hopes of building a budget gaming PC are long gone at this point).


    After much distress and head banging... I was able to get the restored backup booting on my current/non-fried NAS. First I had to flash the bios, then boot-repair progressed (which had been previously been giving me vram errors), finally allowing me to get to work on making the new USB bootable. Boot-repair asked me to make tiny unformatted grub boot partition. It worked its magic and I was able to boot into Debian. I had a kernel panic at first, so booted into advanced mode, and selected an older version (kernel 5.7), and then it fully booted.


    I'm permanently booting off 5.7 now, since 5.10 isn't stable. I saw another user on here having similar issues with 5.10... so am going to assume it's unrelated to my recovery process.


    Can't believe I'm back up and running.


    I have one last issue... When I browse to samba shares they are read only. I checked and it doesn't seem to be user/perms in the GUI - these haven't been changed. Could there be some file system restrictions linked to the restoration?

    gderf - Yeah but I think my motherboard requires MBR, as Soma suggested, and using Ease US to convert it hasn't worked.


    Now, I even purchased a 64GB USB 2.0 drive, and got the same result. So I'm in the unfortunate position of opportunity cost trying to get the 8GB work, giving up after days, and finding the bigger drive didn't work either.


    Which is hilarious because I could have rebuilt the whole NAS by now.


    I'm just really surprised that of all the tools and the users online having similar issues, there is none that clones a drive to a smaller drive, giving the user a chance to select the preferred partition table. I'm sure it's not simple, but it must be doable.

    I may be over simplifying but I can't fathom why an app/service couldn't clone partitions/boot info from a larger drive, if they have been prepared (shrunk and contiguous) to fit on the smaller drive. There seems to be a myriad of tools, none of which tackle this use case.


    Ease US Free can do this with Windows disks (e.g. cloning OS drive to smaller SSD - assuming data size fits), but it's not equiped aparently for Linux OS drives.

    gderf that was basically the command I tried, but with BS=8 && sync - have tried yours but I think Soma has a good point. Maybe I'll retry the dd clone then change the partition to MBR so my motherboard sees it.


    I'm a little unclear on what to do to make the USB 3 bootable, also that sounds like it's more risky at this point as it messes with my working original OS drive.

    gderf Using gparted I was able to shrink my USB 3.0 partitions (os/swap), and make all 3 (boot/os/swap) contiguous - total size is now smaller than available space on the other drive (it still functions too). Using DD, I was able to complete a clone to the 8GB USB 2.0 flash drive. But the new drive doesn't boot. On inspection, there are errors about it having partition sizes bigger than the volume.


    What DD command should I be using? I feel like I'm nearly there but the info online is varied and complex.


    Note: I investigated purchasing a bigger USB 2.0 drive to save time but they are not common and actually quite expensive. For the price I could get a used computer with USB 3.0! But I'm really trying to recycle here. I actually pulled this box out of a dumpster many years ago so I've become quite attached to keeping it alive :)

    I am migrating my OMV to a new case. Currently OS is on a USB 3 thumb drive but new case doesn't have USB 3 (only 2).


    Current thumb drive is 64GB and overkill. I have a 8GB USB thumb drive. Instructions here... https://openmediavault.readthe…ackup#cloning-flash-media


    I'm having two issues.

    1. Firstly it asks to select a source drive letter in Win32 Disk Imager. But OMV shows up as two drive letters in Windows (D: & F: in my case). It's not clear in Windows which one is the OMV OS since windows doesn't recognise the file system. I can't even do it by size as the sizes aren't shown anywhere. Selecting a random one starts the image process.
    2. Even though I selected "Read Only Allocated Partitions" the resulting image is the full 64GB

    In reality, my OMV used space is under 8GB, though this and other methods for cloning to smaller drives online (Ease US etc) refuse to make the clone from 64GB to 8GB drive.


    I'd rather not install from fresh and loose my config. I have Greyhole working in the background (independent of OMV), and it took me a long time to get it setup correctly.

    Hi. Sorry. Context is I broke my GUI and got it to a point where advice on another thread was to upgrade the kernel. An entire day of Googling and thread reading had me here. I followed the instructions in the prev post and got that error on running that line.


    I agree it was too little info. Most people Google a lot and get very stressed before posting. I ended up doing a clean install, and now I'm having grief with that but I'll post separately.

    Reinstalling OMV using

    Code
    sudo apt-get install --reinstall openmediavault

    Has brought back the GUI login screen but I still can't log in


    OMV\Rpc\Exception: Failed to connect to socket: Connection refused in /usr/share/php/openmediavault/rpc/rpc.inc:141


    Though, now I can run omv-firstaid.