Filesystem creation (EXT4) error on shucked WD Mybook 6TB (OMV 5.0.10-1) (Atari partition table?)

  • Hello everyone, I'm having troubles creating the file system for a WD 6TB MyBook drive I recently shucked.
    My storage setup is a Netapp DS4243 -> PMC8003 Rev.5, the computer is running OMV 5.0.10-1. I'm been using standard disks as well as shucked Seagate's 6TB for a while without any issues.


    Here are the details:


    Error #0:OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mkfs -V -t ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init=0 -O 64bit -L 'WDC6TB1' '/dev/sdz1' 2>&1' with exit code '1': mke2fs 1.45.3 (14-Jul-2019)Found a atari partition table in /dev/sdz1Proceed anyway? (y,N) in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:673Stack trace:#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): Engined\Rpc\OMVRpcServiceFileSystemMgmt->Engined\Rpc\{closure}('/tmp/bgstatusNo...', '/tmp/bgoutputzI...')#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(689): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure), NULL, Object(Closure))#2 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->create(Array, Array)#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'create', Array, Array, 1)#6 {main}


    That's the first time I'm coming across this error and I've been unable to find useful information even when searching for this "atari partition table" bit.
    I've tried deleting every partition with fdisk but the error stays the same.



    The other strange thing is that the create file system window outputs this:


    Number Start (sector) End (sector) Size Code Name
    1 2048 11721045134 5.5 TiB 8300
    The operation has completed successfully.



    Any ideas where I should look for to fix this issue? Thanks a lot!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!