Posts by KingEdward37

    Macom,
    I originally purchased these drives for use in a 32bit FreeNAS deployed on an ancient Dell for our church office staff. They didn't really understand how to use network storage and the FreeNAS was turned off and stored. It sat in a closet for almost 2 years, off. That PC was recently discarded, & I pulled the drives for this new project.
    Thanks for your explanation of the RAID mirror vs rsnapshot plugin and I will consider it. If this archiving works out, I will be moving to larger drives anyway because the school has to maintain three months of CCTV at a reasonable resolution.
    Thank you again for taking the time to assist me.
    I really appreciate it.


    ryecoaaron,
    Thank you again as well. I appreciate you patience.
    I didn't expect instant responses to my questions, but I thought 24 hours should achieve some response. When I noticed that I had notices on the top of the window, I followed them to responses.
    Sorry about the length of my post. I'll do better.

    OK, I'm having trouble seeing your responses in the forum. Sorry about that. I'm having to check my Notifications often, then I see responses that I'm not seeing.
    Now that the drives are successful in File System, I can mount them.

    After using DBAN, the quick wipe, & format still failed in exactly the same way.


    After using wipefs -a /dev/sdb and wipefs -a /dev/sdc, I performed quick wipes on both drives, then moved to File System and created on /sdb an ext4 format, or partition, not really sure which.
    Drive appeared in the background as before, and...
    Holy Smoke, the drive remains!
    Let me try /sdc now...
    It worked as well...so THANK YOU THANK YOU THANK YOU for your help.
    macom suggested that I not use a RAID mirror for my data storage, why is that?
    If all goes well this machine will be used for CCTV archiving for a small private school and it seems to me that RAID would be a good choice, so I look forward to hearing a response.
    Thank you again for responding and for providing a solution.
    I'm still curious about the need to jump through so many hoops to trick OMV into using the drives.

    Rebooted to OMV.
    Attempted to quick wipe with the resulting error:
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; sgdisk --zap-all '/dev/sdb' 2>&1' with exit code '2': Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Caution! After loading partitions, the CRC doesn't check out! Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Invalid partition data! GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.


    In response to ryecoaaron,
    wipefs -a
    replied with:


    Usage:
    wipefs [options] <device>
    Wipe signatures from a device
    ...then lists all the possible options.


    Was this suppoused to do something without specifying a drive?


    OK, I entered this instead:
    wipefs -a /dev/sdb
    and got what looks like some action
    ditto for wipefs -a /dev/sdc
    so, now I'll try again...film at eleven...

    OK, my bad,
    DBAN is an ISO image.
    I'm booting to the CD now on the OMV box, let you know...
    First boot crashed, just one of those things...Ctl-Alt-Del...worked 2nd time...
    Selected interactive mode...
    Selected both of my 2TB disks...
    used default setting of DoD Short...
    F10 and now we wait...looks like about 17 mins...
    Wait, that's incorrect, that says 16 hours...
    Whattttt?
    It was difficult to get the programs attention because I don't know the break command because I didn't read the directions fully.
    Anyway, started over using Quick Erase.
    If it truly performs the header stuff first, then I should be good to go after a few minutes.
    The time estimate is 6 hours...
    Aborted the process after 15mins.

    Used diskpart to examine drives. One of them has a partition, no volumes, or anything else.
    The other one didn't have any partitions.
    Removed the partition found, re-installed drives into OMV.
    ...quick wipe...File System, used btrfs, looked good at first, then:
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mkfs -V -t btrfs -O skinny-metadata,^mixed-bg -L 'Bee' '/dev/sdb1' 2>&1' with exit code '1': /dev/sdb1 appears to contain an existing filesystem (zfs_member). ERROR: use the -f option to force overwrite of /dev/sdb1 btrfs-progs v4.7.3 See http://btrfs.wiki.kernel.org for more information.


    Thoughts?

    DBAN appears to be a windows program.
    I would need to pull the drives from the OMV box and use a USB external device to connect and wipe from a Windows PC.
    I don't think I need DBAN for this.
    I'll go with diskpart first, and see if it'll do the trick.
    I just don't follow the need for using another OS to fix a hard drive for Debian OMV, why can't OMV do it?

    I quick wiped the drives and then tried file create using btrfs I got the following error:



    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mkfs -V -t btrfs -O skinny-metadata,^mixed-bg -L 'Bee' '/dev/sdb1' 2>&1' with exit code '1': /dev/sdb1 appears to contain an existing filesystem (zfs_member). ERROR: use the -f option to force overwrite of /dev/sdb1 btrfs-progs v4.7.3 See http://btrfs.wiki.kernel.org for more information.

    good day all,
    I've done everything here and more
    The drives disappear after format.
    Tried:
    full secure wipe, more than once
    quick wipe, too many times to count
    Still getting
    Failed to read file '/tmp/bgstatustVWtdc' (size=0).
    Failed to read file '/tmp/bgstatusVlY9Es' (size=0).
    Failed to read file '/tmp/bgstatusenQluz' (size=0).
    Failed to read file '/tmp/bgstatus2iIpP7' (size=0).
    Failed to read file '/tmp/bgstatus8sNMLb' (size=0).
    Failed to read file '/tmp/bgstatusNwTjxS' (size=0).


    Even after updating via System UpdateManagement and since the forum post doesn't explain WHAT to update, I just updated all and waited until
    the errors finished...


    As I have been posting elsewhere on this forum and not getting any help, I am posting here hoping for any response.


    I found some instructions here:


    https://www.digitalocean.com/c…-storage-devices-in-linux


    And used these commands to partition the drives and format it successfully


    parted /dev/sdb mklabel gpt
    parted /dev/sdc mklabel gpt
    then
    mkfs.ext4 -L (nameofpartition) /dev/sdb
    mkfs.ext4 -L (nameofpartition) /dev/sdc


    This simply resulted in an error with something called fstab not being updated, and OMV wouldn't recognize the drives, despite confirming via CLI they were correct and ready to go.


    I'm not going to take the time to post anything else right now.
    lets see if I get some response help.


    thanks in advance and i apologize in advance for my frustration level.
    I am a newbie and will always be a newbie unless I get some help.


    I can't seem to reply to your comment, so I'll do it here...
    Thank you Thank you Thank you
    I really appreciate you taking the time to reply and offer me some assistance.


    I was already thinking along the same lines as you advised.


    Here's some basic info:
    Dell Optiplex 755 currently with 4GB of ram, CD/DVD drive, stock Dell Optiplex.


    sda is an 80Gb disk for the OMV OS.
    sdb is a 2TB drive intended for raid mirroring
    sdc is a 2TB drive intended for raid mirroring
    both drives were used previously with an old FreeNAS raid system and are in good shape as the system was not used much, spending most of its time off.

    Before starting a new installation, I used the CLI to perform hard drive preparation.
    These are my steps:



    sgdisk --zap-all /dev/sdbsgdisk --zap-all /dev/sdcthen:dd if=/dev/zero of=/dev/sdb bs=4M count=1dd if=/dev/zero of=/dev/sdc bs=4M count=1I used an ISO image of OMV from the website burned to a DVD yesterday afternoon.Performed full installation to sdaOpened the web GUIperformed quick wipes on both drivesmoved to File System and attempted to create file systemShortly after the formatting process begins, the drive shows up in the list seen in the background as initializing.Just after the popup window announces that it completed with success, the drive disappears from the list.Tried it again, same drive, sdbSame result.Tried with sdcSame result.Pulled together information, replied to your post.What am I doing wrong?

    I have the same problem, however, secure wipe didn't solve it.
    I'm trying hard to really like OMV.
    My first experience was excellent.
    My second experience taught me there is a bug in the program that causes the following type of error messages to appear when using the web GUI and it interferes with being able to properly save configurations, which I have experienced.


    Failed to read file '/tmp/bgstatustVWtdc' (size=0).
    Failed to read file '/tmp/bgstatusVlY9Es' (size=0).
    Failed to read file '/tmp/bgstatusenQluz' (size=0).
    Failed to read file '/tmp/bgstatus2iIpP7' (size=0).
    Failed to read file '/tmp/bgstatus8sNMLb' (size=0).
    Failed to read file '/tmp/bgstatusNwTjxS' (size=0).


    Although I read a very complex method of 'correcting' this issue, I am unwilling to modify the OMV source code.
    I can't help but wonder why, if this is actually a problem, it hasn't been fixed in the latest release.


    Currently, I am trying to assist my church academy by providing a server that can archive CCTV footage.
    OMV seems the perfect solution.
    A couple of 2TB drives and a scavanged pile of PC parts later, & I think I've got a pretty good starting system.
    If it works, I can expand drives etc. later.


    The install of OMV was straightforward.
    There is an 80GB hard drive dedicated to OMV.
    There are two, 2TB drives which I hope to use mirrored for archiving, heretofore called A & B.


    I began by wiping A and then B
    Next, I created file system on A.
    The file system appears on the list while its formatting, but then disappears as soon as its announces complete.
    I created file system on B.
    Same result.
    Moved to RAID management to find no drives available.
    Returned to DISKS, wiped using secure mode until about 10GBs was completed on both A and B.
    Next, I created file system on A.
    The file system appears on the list while its formatting, but then disappears as soon as its announces complete.
    Ditto for B.


    All through the process I get the above listed Failed to read... error messages.


    I read in the forums that having the file system disappear is also a common problem and has to do with drives not being properly formatted/cleaned/etc.
    So, OMV cannot properly clean/prepare a drive for its own use and other methods must be employed?


    I'm now looking into something called the dd command to run from the command line...


    Is there not a better way?


    Can any of the gurus in OMV give me some help?


    Thanks in advance.


    ...so I didn't use the dd command yet...instead i went back to the forums and read that I should do updates.
    I followed the directions to the letter, but there are many updates to choose from and no indication of which are needed for basics and which are just options...so I did them all.
    It was successful on some of the updates, others failed due to a variety of errors, mostly what appeared to be incompatibility, but it finished.
    Next, I returned to...
    ...wiping A and then B
    Next, I created file system on A.
    The file system appears on the list while its formatting, but then disappears as soon as its announces complete.
    I created file system on B.
    Same result.
    Moved to RAID management to find no drives available.
    One improvement, the Failed to read... error messages have disappeared!


    Still no usable system.


    Now, I'm going back to trying to fix 'OMV isn't properly updated' by downloading the newest version from OMV website, making a DVD, and starting from scratch...again...
    Did I mention that I've started over to insure no steps were missed 2-3 times?


    Thanks again, I'll come back and update when I can...


    Im back. The latest ISO image resulted in much the same experience. The Failed to read... errors have returned.
    AND the drive disappears right after the format completes.
    Yep, I did a quick and a secure wipe, although I stop the secure wipe after it reports that its covered the first 10gbs, I figure that should take out all the front end stuff and allow what I was taught to call a low level format. Regardless, it didn't work.
    I guess I'm back into a holding pattern waiting for some assist from the forum while I read up on the dd command.


    I could not login to the CLI because it didn't respond to the login and password setup in the installation process. I already understood that there were two logins, one for web GUI and one for CLI, but I gave them the same login so I wouldn't have to remember so much...until I got the system up and running anyway. I eventually figured out that the login for the CLI is NOT admin ever, but root. That plus the password I created got me to the CLI.
    I read on this web site:
    https://www.digitalocean.com/c…-storage-devices-in-linux
    how to manually find, partition, & format my two hard drives.
    They still do not show up under the web GUI under File Systems, but they do under RAID management and I successfully created a mirror RAID set...but the drives still don't show up as 'mounted'.
    This will probably bite me later, but for now I'm pretty happy with some success.


    So, under file systems I now have a RAID drive set which it wants to format, so although I'm a little nervous about this, because it has failed every single time as an earlier step, I let it format.
    All the little Failed to read... errors are back, & I have no faith it will be successful...
    I just formatted the drives successfully, so why format again? I used GPT by the way.


    It failed. Worked through to the end, then disappeared.
    I'm going to see if thats actually true by moving data to/from using the CLI.
    Frustrating.
    OK, it looks like the work is done, OMV just doesn't know it. Does this mystery file called fstab somehow tell OMV where/what the drives are? I see that is can control mounting.
    When I try the following command:
    mount /dev/md0
    I get:
    Can't find /dev/md0 in /etc/fstab


    I can see the drive(s) as a Raid1.
    It is partitioned as GPT
    I realized that I have tried to format it unsuccessfully in OMV, but not using the CLI.
    I used:
    mkfs.ext4 -L CCTV /dev/md0
    and it kicked back with/dev/md0 contains a zfs_member file system, (which it may or may not, regardless I WANT TO REPURPOSE IT), so I said yes to proceed.
    It appeared to do something.


    I just found something interesting.
    Under RAID management, it indicates:


    clean, resyncing (42.2% 823147/1953383488)
    finish=109.7min speed=170584K/sec


    So some syncing process is taking place that should end in about 2 hours and MAYBE the drive will show up and can be mounted????????
    Dang. Why won't the install go like the directions say it should.
    I'm done for now, maybe in the morning I'll do some more.
    I've got hours in this 'simple' OMV install simply because it will not wipe, partition, & format its own drives.
    Unbelievable.
    The two hour wait resulted in no progress whatsoever.
    Same problems.
    I've just used the dd command to destroy the first 100gbs of data, hoping to blow away whatever it is that stops the formatting.
    Since I can't edit the fstab file from the command line in OMV, and I've googled it, gedit isn't installed for example, the forums have no results to 'edit fstab' other than to explain what to do once you're already editing, assuming that everyone must know how to open a file and edit it...
    Its probably best that I didn't get it open for editing, I wouldn't know how to modify it properly without some assistance anyway...
    So
    The first format didn't work.
    Failed to read... errors are back.
    Drive disappears after format finishes.


    and, not a single response to my details and requests for help.


    Sadly, I'm looking for another solution.