Posts by Alexeon

    Hello, I am having a problem and I'm not sure how to fix it.

    So, I've been running OMV2 for a while and today I decided to upgrade to OMV4. I installed the OS on a 40GB HDD. Then, once I was on the webUI, I created a user and started mounting my 7 data drives via Samba. Once that was done, I went and gave my user read/write access to each drive via the Shared Folders ACL options. I was using the recursive option to apply the setting. Drives 1 and 3-7 went fine. Drive 2 gave me an error saying it wasn't able to apply the setting. I tried rebooting the server thinking that might help. When it was shutting down, it seemed to be stuck on something for a bit. I didn't manage to write down what the issue was. It rebooted and when I went to try the permissions on Drive 2 again, it had been replaced with what you can see in the attachment.

    Drive 2 should be the same as the other drives. I removed the shared folder from SMB so that's why it says No for referenced, but it still said yes when it first happened. The scary part is that the drive, which had been full of data, now showed up as empty on my share. When I check via SSH at /dev/disk/by-label/Drive2, it shows blank. I don't know what could have happened. I didn't write any data to the drive so I'm hoping my data might still be able to be brought back. Any clues on what I can do? I did some Googling but I didn't find this exact issue anywhere.

    EDIT: After a lot of hesitating, I opened up my server and found what might possibly have been the culprit. The power cable was slightly out of place on the drive in question. I'm not 100% sure that didn't happen when I opened the case since the machine had not been touched before this. I was able to see the drive again, but the original error I ran into when trying to apply the ACL setting is still happening. It says that the disk is read-only but it shouldn't be. I'll attach a second screenshot of it. I am robocopying the data from that drive to another in case its starting to die, but I'd like to know for sure.

    Here is what I get:

    root@Luna:~# dpkg -l | grep grub
    ii grub-common 1.99-27+deb7u3 amd64 GRand Unified Bootloader (common files)
    ii grub-legacy 0.97-67 amd64 GRand Unified Bootloader (Legacy version)
    rc grub-pc 1.99-27+deb7u3 amd64 GRand Unified Bootloader, version 2 (PC/BIOS version)
    ii grub-pc-bin 1.99-27+deb7u3 amd64 GRand Unified Bootloader, version 2 (PC/BIOS binaries)

    I managed to do apt-get grub, but the install failed.

    Here you go:

    Sure, here it is:

    Disk /dev/sda: 4000.8 GB, 4000787030016 bytes
    255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00000000
    Disk /dev/sda doesn't contain a valid partition table

    That's one of the HDDs in my RAID. I have 4 4TB disks and one 40GB disk that's holding the OMV installation.

    Here is the sdb, just in case:

    Hello, I previously posted a different topic regarding my recent reinstall of OMV. I was able to resolve my WebGUI issue but there was something I wanted to fix, though its not broken exactly. When I installed this new OMV installation, I got an error when trying to install Grub so I went for LILO, but I've noticed that LILO takes a lot longer to boot up than Grub. I'd like to install Grub instead. I looked up some guides and I downloaded Grub onto my system, but when I try to run

    grub-install /dev/sdb

    I get the following output:

    I don't know how to resolve this. Please help.


    Hi, so I just had to reinstall OMV and I was setting everything up. I installed a couple of plugins and everything was working fine, but then I restarted and I can't get the WebGUI to open. I can access my shares and everything, though. Based on what I read earlier on other threads, it seems like the problem might be with my firewall, but I tried the suggestions in the other threads and that wasn't working for me. I'm not too good with Linux... just tell me what information you need to possibly help me and I'll provide it.


    EDIT: For whatever reason, it now works. I don't know what, out of the things I tried, did the trick. I tested the page after every possible change and it didn't work and then I refreshed the page again on a whim and there it was... sorry to any future people with the same issue.