Posts by sorinmarkauv

    980 ti is not high end any more. Plus I had it laying around and the 2700x does not have any built in graphics. I do plan on setting up an alternate boot to utilize steam on mint and play games there. It's just kinda what I had

    Usually use terminal to edit files but I like to use the OMV interface for directory creation and management. Individual files i modify. I am familiar but haven't done much this round.


    x470 prime pro

    2700x amd

    EVGA GeForce GTX 980 Ti 06G-P4-1996-KR 6GB HYBRID GAMING, "All in One" No Hassle Water Cooling, Just Plug and Play Graphics Card

    pcie 1x sata card 10 ports, 6 gbps sata 3.0 controler expansion card.

    ASUS Hyper M.2 X16 PCIe 3.0 X4 Expansion Card V2 Supports 4 NVMe M.2 (2242/2260/2280/22110) Upto 128 Gbps

    750w platinum 80+ seasonic psu

    Every time I try to update OMV I get SOOOOOO Many issues. last time I had to reinstall the entirety of OMV. I was able to bypass my issues but then everything was breaking. Few errors on Boot, DNS stopped working. It was a nightmare. I thought it was network or isp issues and it ended up being the failed section in my OMV update.


    I just updated cause I had quite a few lingering things to do and BAM again getting errors on boot.


    WHAT am I doing wrong. Is there a way that you guys pick which updates you want or are not good for your system? Do you turn off or unmount your RAID through the MD plugin? What constitutes a good reason to update?

    looks like this might be solved over here


    i ended up running lsblk to get my drives listed. and sure enough my drive showed a partition

    i used the umount commands to make sure nothing was mounted to my linux system after going back to omv and deleting the MD

    i then used sudo fdisk /dev/(the drive that was giving me issues)

    deleted the drive with d then w

    loaded back up then made sure to do another wipe of them through linux instead of omv just to be sure

    sudo wipefs -a /dev/(drives)

    sure enough some file data was on one of the drives

    the other two were clean.

    was able to trigger the MD to start again, we will see the success later!

    go to the cli and show what the command produces

    Code
    mdadm --detail /dev/md1

    Hey sir. it responds with:


    mdadm --detail /dev/md1

    /dev/md1:

    Version : 1.2

    Creation Time : Sat Dec 28 21:49:13 2024

    Raid Level : raid1

    Array Size : 1953382464 (1862.89 GiB 2000.26 GB)

    Used Dev Size : 1953382464 (1862.89 GiB 2000.26 GB)

    Raid Devices : 2

    Total Devices : 2

    Persistence : Superblock is persistent


    Intent Bitmap : Internal


    Update Time : Sun Dec 29 06:42:37 2024

    State : clean

    Active Devices : 2

    Working Devices : 2

    Failed Devices : 0

    Spare Devices : 0


    Consistency Policy : bitmap


    Name : servername:1 (local to host servername)

    UUID : 1b1419be2:9f252c1d:e9b860df:b7a76f7

    Events : 6471


    Number Major Minor RaidDevice State

    0 8 32 0 active sync /dev/sdc

    1 8 0 1 active sync /dev/sda

    linux - How to access a CD/DVD drive over the network? - Super User
    Looks like i found a way to do it with linux. would this cause any errors with the SMB that OMV uses or already has set up?




    Jeff Ward -

    I feel like a Samba / NFS setup is kind of a big hammer for this little nail. I found a blog post on this topic which shows the use of a tool called nbd -- network block device. To use it, setup the server and client.

    (The tutorial is written for Ubuntu with a CD device at /dev/cdrom, so you may need to adjust for your setup.)

    On the server side (with the CDROM):

    Code
    sudo apt-get install nbd-server
    sudo adduser nbd cdrom

    (You may get a warning about no configured exports - ignore it, we'll set one up below.)

    Edit the /etc/nbd-server/config file:

    Code
    [generic]  group     = cdrom  allowlist = true
    [cdrom]  exportname = /dev/cdrom  readonly   = true

    Then: sudo /etc/init.d/nbd-server restart

    On the client side (access the server's CDROM):

    Code
    sudo apt-get install nbd-client

    Now map the block device (where 192.168.1.100 is the ip address of the server):

    Code
    sudo nbd-client 192.168.1.100 -name cdrom /dev/nbd0

    Now you can mount /dev/nbd0 as if it was a CDROM on the client:

    Code
    sudo mkdir /mnt/cdrom   # if it doesn't already exist
    sudo mount -t iso9660 /dev/nbd0 /mnt/cdrom

    Or grab an ISO:

    Code
    sudo dd if=/dev/nbd0 of=~/disc.iso

    thank you sir! From the looks of it OMV is not the way to get a DiskDrive to be shared. I do wonder if there is just a base linux way to make that drive fully shared out in the greater network so i can just access that DiskDrive

    I just finished setting up my first shares. I can't seem to connect a CD Disk drive to a share though. is there some protocol I don't know about that would prevent me from doing this? If not what script could I set up to map it and remove it from shares too. looks like there are some difficulties with it not recognizing the drive if I switch disks, probably messes with the UUID?



    Failed to create the directory '/srv/dev-disk-by-uuid-4273aeed00000000/DVD/': Unknown error


    OMV\Exception: Failed to create the directory '/srv/dev-disk-by-uuid-4273aeed00000000/DVD/': Unknown error in /usr/share/openmediavault/engined/rpc/sharemgmt.inc:393

    Stack trace:

    #0 [internal function]: Engined\Rpc\ShareMgmt->set()

    #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()

    #2 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()

    #3 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()

    #4 {main}