Filesystem Mountpoint Missing

claredad · Dec 14th 2020

Hey graves.

Rebuild is complete. When I try to apply changes, I get the following error:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian: Data failed to compile: ---------- ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted.
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; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusGM...', '/tmp/bgoutput8R...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Display More

geaves · Dec 14th 2020

Quote from claredad

Rebuild is complete. When I try to apply changes, I get the following error:

I think this is from the reboot you did in post 9 and this -> "If I do a reboot, it goes back to the old storage filesystem" didn't make sense, the only option I can assume is that the newly created Raid from the fresh install was using the metadata on the drives, but you had created a new name during the install. This is just supposition.

OK, if the following works then will need some more information, if it doesn't then I would suggest a restore from your backup.

update-initramfs -u and reboot

claredad · Dec 14th 2020

Quote from geaves

I think this is from the reboot you did in post 9 and this -> "If I do a reboot, it goes back to the old storage filesystem" didn't make sense, the only option I can assume is that the newly created Raid from the fresh install was using the metadata on the drives, but you had created a new name during the install. This is just supposition.

OK, if the following works then will need some more information, if it doesn't then I would suggest a restore from your backup.

update-initramfs -u and reboot

No change.

I see someone here has the same issue.

Is it wrong to assume that from the below message the issue is in the process.inc file, on row 182? Ive attached that file.

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian: Data failed to compile: ---------- ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted.
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; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus0e...', '/tmp/bgoutput9V...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Display More

geaves · Dec 14th 2020

Quote from claredad

I see someone here has the same issue.

No, I believe the user there had simply failed to remove the raid correctly.

What's the output of blkid trying to work out if it's detecting a file system

claredad · Dec 14th 2020

Quote from geaves

No, I believe the user there had simply failed to remove the raid correctly.

What's the output of blkid trying to work out if it's detecting a file system

Code

root@omv-server:~# blkid
/dev/sdd: UUID="7686503f-2d11-c7ae-48f9-f41b39240c72" UUID_SUB="ecd11196-6f83-09da-f6c0-fc6df6311909" LABEL="pool-ipv6-pd-omv:Storage" TYPE="linux_raid_member"
/dev/sda1: UUID="b470e674-d414-4ae1-b471-7c40a7b544a1" TYPE="ext4" PARTUUID="9685734b-01"
/dev/sda3: UUID="3a9d6220-5d48-4efd-9b36-a0996bb194dd" TYPE="ext4" PARTUUID="9685734b-03"
/dev/sda5: UUID="b78cf05b-c6c7-4a13-b2e3-1ceb42b3689d" TYPE="swap" PARTUUID="9685734b-05"
/dev/sdb: UUID="7686503f-2d11-c7ae-48f9-f41b39240c72" UUID_SUB="177c655c-90be-6e57-305d-a6e1477e4c24" LABEL="pool-ipv6-pd-omv:Storage" TYPE="linux_raid_member"
/dev/md127: LABEL="Storage" UUID="a9cf4321-ae30-4bcb-bf17-9c5a333761f3" TYPE="ext4"
/dev/sdc: UUID="7686503f-2d11-c7ae-48f9-f41b39240c72" UUID_SUB="648cee8c-3f1e-fe3e-ff96-36149a8eae9d" LABEL="pool-ipv6-pd-omv:Storage" TYPE="linux_raid_member"

geaves · Dec 14th 2020

Ok the raid has a file system, does it display under file systems in the GUI

claredad · Dec 14th 2020

Yes, it does.

geaves · Dec 14th 2020

If you select and click mount, will it mount

claredad · Dec 14th 2020

Quote from geaves

Ok the raid has a file system, does it display under file systems in the GUI

No, I get an error.

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-label/Storage' 2>&1' with exit code '32': mount: /srv/dev-disk-by-label-Storage: cannot mount; probably corrupted filesystem on /dev/md127.
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; mount -v --source '/dev/disk/by-label/Storage' 2>&1' with exit code '32': mount: /srv/dev-disk-by-label-Storage: cannot mount; probably corrupted filesystem on /dev/md127. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(738): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(931): OMV\System\Filesystem\Filesystem->mount()
#2 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(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('mount', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
#6 {main}

Display More

geaves · Dec 14th 2020

TBH I don't know how to proceed and I think that initial reboot has thrown a spanner in the works and I'm going to ask if votdev can shed some light on what's going on.

claredad · Dec 16th 2020

Geaves has been a massive help getting me this far, and is a credit to the OMV community.

But we're stuck. Anything else got any ideas?

geaves · Dec 16th 2020

Quote from claredad

Anything else got any ideas

I had one idea based upon this -> probably corrupted filesystem on /dev/md127 What you could try is fsck /dev/md127 that will check the file system on the raid

claredad · Dec 16th 2020

Quote from geaves

I had one idea based upon this -> probably corrupted filesystem on /dev/md127 What you could try is fsck /dev/md127 that will check the file system on the raid

Hey Geaves. I assume I press y?

Code

root@omv-server:~# fsck /dev/md127
fsck from util-linux 2.33.1
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Superblock checksum does not match superblock
fsck.ext4: Superblock invalid, trying backup blocks...
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
Storage: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Inode 106170680 passes checks, but checksum does not match inode.  Fix<y>?

geaves · Dec 16th 2020

You'll need to answer y for it proceed, this was one reason I asked if you had a backup, I was hoping that it may not need fsck but this might be the only to resolve it.

claredad · Dec 16th 2020

Quote from geaves

You'll need to answer y for it proceed, this was one reason I asked if you had a backup, I was hoping that it may not need fsck but this might be the only to resolve it.

Ill keep going in the morning, but after doing a few fixes of different nodes, I started getting an error about *Free blocks count wrong for group ...*

Ive had my finger on Y for the last 15 minutes from group 1 up to 49378. Will finish in the morning, but this cant be good...

Code

Free blocks count wrong for group #49351 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49352 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49353 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49354 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49355 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49356 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49357 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49358 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49359 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49360 (28640, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49361 (32768, counted=14336).
Fix<y>? yes
Free blocks count wrong for group #49362 (32768, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49363 (32768, counted=22528).
Fix<y>? yes
Free blocks count wrong for group #49364 (32768, counted=12288).
Fix<y>? yes
Free blocks count wrong for group #49365 (32768, counted=16384).
Fix<y>? yes
Free blocks count wrong for group #49366 (32768, counted=16384).
Fix<y>? yes
Free blocks count wrong for group #49367 (32768, counted=22528).
Fix<y>? yes
Free blocks count wrong for group #49368 (32768, counted=14336).
Fix<y>? yes
Free blocks count wrong for group #49369 (32768, counted=8192).
Fix<y>? yes
Free blocks count wrong for group #49370 (32768, counted=22528).
Fix<y>? yes
Free blocks count wrong for group #49371 (32768, counted=20480).
Fix<y>? yes
Free blocks count wrong for group #49372 (32768, counted=10240).
Fix<y>? yes
Free blocks count wrong for group #49373 (32768, counted=14336).
Fix<y>? yes
Free blocks count wrong for group #49374 (32768, counted=18432).
Fix<y>? yes
Free blocks count wrong for group #49375 (32768, counted=22528).
Fix<y>? yes
Free blocks count wrong for group #49376 (28640, counted=0).
Fix<y>? yes
Free blocks count wrong for group #49377 (32768, counted=10240).
Fix<y>? yes
Free blocks count wrong for group #49378 (32768, counted=18432).

Display More

geaves · Dec 17th 2020

Quote from claredad

Will finish in the morning, but this cant be good...

This was one reason why I didn't want to do it and why I asked if you had a backup as all this takes me back to your comment in post 9 ->

I ran this, and in Filesystems, in the web interface i saw the new filesystem, /dev/127/. It was showing as normal.

If I do a reboot, it goes back to the old storage filesystem.

I know you had to rebuild due to the failure of your boot device, but, as I have no idea how you did this it would suggest there was a name change somewhere. The one thing about raid is that omv will detect it after a rebuild, when I used a raid set up and moved server hardware omv just picked it up all I had to do was recreate the shares in the GUI from the directory tree still on the raid.

The other error that stood out was mdadm conf missing any reference to your raid, not a problem as a simple command would correct that. Most users raid issues are fairly straightforward to resolve but I have no knowledge of omv's inner functions, so I couldn't answer the errors you were seeing.

Another problem is a backup you would be surprised users who 'believe' that raid is a form of backup, hence my sig and the fact I asked if you had a backup, sometimes it's just easier to start again and restore than to try and fix the errors.

I'm sincerely hoping that running fsck resolves the problem, I'm assuming the free block count is in relation to the free space, I don't know.

claredad · Dec 17th 2020

Quote from geaves

I'm sincerely hoping that running fsck resolves the problem, I'm assuming the free block count is in relation to the free space, I don't know.

Well it looks like your sincere hoping worked... Looks like everything is recovered and working now!

Thanks so much for your help. As I said previously, you're a credit to the OMV community!

Edit, I posted too early. I can see all the information when I brows the drives to a my phones explorer, but after doing the RAID rebuild, I still need to apply those changes in OMV web interface.. Whe I try, I get this erros:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian: Data failed to compile: ---------- ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted.
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; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusBF...', '/tmp/bgoutputvV...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Display More

geaves · Dec 17th 2020

Quote from claredad

Whe I try, I get this erros:

TBH I have no idea how to resolve that, so 'applying' the changes to the raid rebuild causes that error.

ryecoaaron or votdev can you help with this please I have no idea how to proceed with the above error

claredad · Dec 17th 2020

Quote from geaves

TBH I have no idea how to resolve that, so 'applying' the changes to the raid rebuild causes that error.

ryecoaaron or votdev can you help with this please I have no idea how to proceed with the above error

Just to reiterate, I can access the RAID and all files through my phones...so I assume the rebuild went fine. Its just getting OMV to accept the changes thats the issue.

votdev · Dec 17th 2020

Quote from claredad

Edit, I posted too early. I can see all the information when I brows the drives to a my phones explorer, but after doing the RAID rebuild, I still need to apply those changes in OMV web interface.. Whe I try, I get this erros:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian: Data failed to compile: ---------- ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted.
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; omv-salt deploy run --no-color initramfs 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    ID 'update_initramfs' in SLS 'omv.deploy.initramfs.default' contains a short declaration (cmd.run) with a trailing colon. When not passing any arguments to a state, the colon must be omitted. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusBF...', '/tmp/bgoutputvV...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Display More

The issue has been fixed in openmediavault 5.5.18, see https://github.com/openmediava…7fa5fc10149fefa686fc9a036.

Filesystem Mountpoint Missing

Participate now!

Similar Threads

corrupt file system - Please help

File system missing after reboot

FTP: Error when trying to turn FTP OFF!

Filesystem status after disconnecting drive

All my data is missing! ZPOOL says there is data but nothing shows up! HELP!

Filesystem devices are missing after upgrade to OMV 4