Can't create file system (/dev/sdg1 does not exist and no size was specified)

Denne · 22. Juni 2016

Hi guys,

I'm trying to set up OMV on my new NAS with 3 5TB drives (new) and 4 2TB drives (old).
When I'm trying to create a new file system it fails on one drive. On every other drive there weren't any problems.

error message:

Code

Error #0:
exception 'OMV\ExecException' with message 'Failed to execute command 'export LANG=C; mkfs -V -t ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init=0 -O 64bit -L 'Daten5' /dev/sdg1 2>&1': mke2fs 1.42.12 (29-Aug-2014)
The file /dev/sdg1 does not exist and no size was specified.' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:601
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->create(Array, Array)
#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc/rpc.inc(81): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)
#3 /usr/sbin/omv-engined(524): OMV\Rpc\Rpc::call('FileSystemMgmt', 'create', Array, Array, 1)
#4 {main}

fdsik output:

Code

Command (m for help): p
Disk /dev/sdg: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3EF85236-045F-4020-BA99-B9DFCE3EA7B9


Device     Start        End    Sectors  Size Type
/dev/sdg1   2048 3907029134 3907027087  1,8T Linux filesystem

Alles anzeigen

I did find a bug report in Mantis but with no result or any tips how to resolve the problem (http://bugtracker.openmediavault.org/view.php?id=1539)

I'm not that good with linux. I tried google without any success. I know OMV 3 ist still beta and this could be a bug. I'm happy to help out identifying the bug and resolve the issue if you can tell me how

ryecoaaron · 22. Juni 2016

Did you wipe the drive? Look in Physical Devices tab if you didn't.

Denne · 22. Juni 2016

Yes I did wipe all the old drives (Quick mode).

I just tested the command from the error message via ssh:

Code

root@NAS:~# mkfs -V -t ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init                                                                                                                                                             =0 -O 64bit -L 'Daten5' /dev/sdg1 2>&1
mkfs from util-linux 2.25.2
mkfs.ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init=0 -O 64bit -L Dat                                                                                                                                                             en5 /dev/sdg1
mke2fs 1.42.12 (29-Aug-2014)
Ein Dateisystems mit 488378385 (4k) Blöcken und 122101760 Inodes wird erzeugt.
UUID des Dateisystems: 2844218f-73f0-4c6c-b541-39628d95424b
Superblock-Sicherungskopien gespeichert in den Blöcken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848


beim Anfordern von Speicher für die Gruppentabellen: erledigt                                                                                                                                                                                
Inode-Tabellen werden geschrieben: erledigt
Das Journal (32768 Blöcke) wird angelegt: erledgt
Die Superblöcke und die Informationen über die Dateisystemnutzung werden
geschrieben: erledigt

Alles anzeigen

I'm sorry the output is in german.
If you do it manually there doesn't seem to be a problem. After refreshing the WebGUI the drive gets listed correctly in the File System tab.
I don't know why the OMV script running the command doesn't work but at least there seems to be a workaround. If you want me testing something for debugging purposes I'm happy to help out.

ryecoaaron · 22. Juni 2016

Try:

dd if=/dev/zero of=/dev/sdg bs=512 count=10000

Then see if you can create a filesystem in the webgui.

Denne · 22. Juni 2016

I deleted the file system I created manually and did what you asked but I got the same error message.

ryecoaaron · 22. Juni 2016

You shouldn't have to delete anything if you zero'd the drive with the command I posted.

I would post a new bug on bugtracker. Maybe there is something Volker would have you try.

Denne · 22. Juni 2016

I did create a file system before manually. I thought I had to remove it first in order to create a new one through the WebGUI. Nevertheless it shouldn't make any difference because I did use your command after deleting the file system.

I did leave a note in Mantis in the existing bug report (bug report isn't that old, didn't want to post a new bug report for the samebug).

edit: I did install OMV2 yesterday night because OMV 3 seemed too unstable for me and there weren't any problems. Just wanted to let you know.

Jetzt mitmachen!