Beiträge von liquid7

    Definitely need to defer to you on these things, as its way above my expertise. In any case, I now think my issue is slightly different from the others here. I'm failing to boot due to the mdadm message others are getting, followed by busybox prompt, But in my case, I was starting with a fresh install and no disks connected. I wanted to pull some baseline power numbers with no disks attached, and couldn't get it to boot due to that message. I never got to the point where I connected the disks, so different situation than failure to re-assemble an array.

    Check the last reply on my thread Unable to boot after installation (Dropping to a shell!) I think you may have the same problem which I did.

    Thanks, I'll try this.


    Lähetetty minun ONEPLUS A3003 laitteesta Tapatalkilla


    I found an easier way to do that. No need for live linux.


    During boot at Grub screen, press ESC to stop the countdown and then press e. There you can edit the mount point. In my case it was sda1. Press F10 to boot.


    After that, boot was successful. I was going to modify grub to point to sda1, but it was already pointing UUID. I rebooted and it worked.


    There was problems with my usb keyboard during some reboots. I think it somehow interferes with usb key during boot. After removing it boot was fine. I don't know if this is because of the motherboard or something else.


    Lähetetty minun ONEPLUS A3003 laitteesta Tapatalkilla

    I did a clean install with openmediavault_4.1.3-amd64.iso. I created the installation usb with Rufus and cleaned the target usb drive with DiskPart. The installation went fine without errors. During first boot I got stuck (see attachment). No data disks were connected during installation or the first boot. Please advice.


    I had previously OMV3 installed succesfully.


    Thanks!


    It didn't work because of the way it does architecture detection (uses uname). It uses the architecture specified in the kernel name. When you compile your own kernel and don't put amd64 in the name, it doesn't find an architecture. Since most people don't compile their own kernel and if they do, they can put amd64 in the name, I don't think anything needs to be changed with omv-extras. I can't think of a more reliable way that works across all architectures either.


    I tried to update to backport kernel before I installed kernel manually. It didn't work then. Only after that I installed the current kernel.


    I just installed 3.0.26 today and I'm having the same problem.

    Hi,
    I have problems installing OMV2.x on my new MSI B150M Eco with Intel I219V NIC. Maybe someone can help me with installing/compiling a suited driver? Unfortunately Google wasn't my friend so far <img src="http://forums.openmediavault.org/wcf/images/smilies/sad.png" alt=":(" />
    Thx,
    Chris


    Don't have time to update the script right now but look at <a href="http://omv-extras.org/intel.sh" class="externalURL" rel="nofollow" target="_blank">this</a> and update it for the code <a href="https://sourceforge.net/projects/e1000/files/e1000e stable/3.3.1/" class="externalURL" rel="nofollow" target="_blank">here</a>


    I ordered the same motherboard and I'm wondering how would you use the script? It needs a working network connection to download the drivers files to compile. I have already compiled a drivers in VM installation with instructions in this thread ASUS H170I-PLUS D3 . And I'm hoping it will work for me also.