File System not initialising

    • OMV 4.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • File System not initialising

      Hi.

      I seem to have come across this problem, where I go to create a file system for one of my 3TB drives, however it goes through the whole process, I can see the window showing me the process it's going through and in the background, I can see that the disk is 'Initialising'. However once the process of formatting and creating the file system stops, the disk just simply disappears from the list as if it was never there to start with.

      Is there anything you can think of that I'm doing wrong at all? I have made sure to wipe the drive first each time.
    • I think i can remember such situation where it helps to secure wipe the disk. There are still some fragments on the device when using the quick option. Maybe this helps.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • 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:

      digitalocean.com/community/tut…-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?

      The post was edited 1 time, last by KingEdward37 ().

    • KingEdward37 wrote:

      Still getting
      Failed to read file '/tmp/bgstatustVWtdc' (size=0).
      This should disappear once the system is updated.
      The fasted way to do the update on a fresh install is omv-update from CLI. Or use the update in the GUI, but in some cases this will cause some errors and the update has to be started several times.

      As your system might be a bit messed up I would start with a fresh install and then update.

      Then I would secure wipe ONE drive and let it complete. Then make a filesystem on that one drive and check if it disappears. May be also try a different file system type like btrfs instead of ext4. Not sure if it makes a difference, but it does not harm. And if it works you can quik wipe the drive and create ext4.

      Forget about the second drive until you have the first one up and running.

      I would also not use RAID, but this is another point and can be discussed once you have one drive working.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • If one wants a "spinning" hard drive that's virus free, free from persistent partition flags, with a fully wiped boot sector, etc., DBAN does the job. Since the boot sector is the first place DBAN wipes, it only takes a few minutes to clean things out. For this purpose, starting a build with a clean drive, a full pass is not really necessary.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • 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 btrfs.wiki.kernel.org for more information.
    • 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?
    • 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 btrfs.wiki.kernel.org for more information.

      Thoughts?
    • 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.

      The post was edited 1 time, last by KingEdward37 ().

    • Really, a few minutes per drive is enough (the boot sector is wiped almost immediately) but a full pass (any pattern) won't hurt anything.
      ________________________________________________________

      I'll assume you looked at the drives SMART stat's and all was OK?

      Are you attempting to setup a ZFS mirror (zmirror)?

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • 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...
    • KingEdward37 wrote:

      Was this suppoused to do something without specifying a drive?
      Nope. I didn't know your device path so I figured you would fill that in.

      KingEdward37 wrote:

      got what looks like some action
      That is a good sign if it removed something. Did it mention anything about zfs?
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • 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.
    • KingEdward37 wrote:

      macom suggested that I not use a RAID mirror for my data storage, why is that?
      Because it can be problematic when not used with server grade hardware. Why do you want raid? If you want it for redundancy because the system can't be down, then maybe it is ok. But it isn't backup and a scheduled rsync job is better than a mirror in my opinion.

      KingEdward37 wrote:

      I'm still curious about the need to jump through so many hoops to trick OMV into using the drives.
      Some filesystem signatures (especially from other OSes) are difficult to get removed. For those rare situations, dropping to command line is the best option.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • KingEdward37 wrote:

      I'm still curious about the need to jump through so many hoops to trick OMV into using the drives.
      Would be interesting to know what these drives were used for.

      KingEdward37 wrote:

      macom suggested that I not use a RAID mirror for my data storage, why is that?

      Regarding RAID: search the forum for "RAID is not backup". RAID is for availablility. If you want to have the server to record CCTV archiving you do not care about availability, I assume.

      Better use the first drive as your main drive, and then use the rsnapshot plugin to make backups of the first drive on your second drive.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!: