"Unauthorized" Error on creating of a filesystem

Feuerhamster · 14. Dezember 2019

Hello everyone.

I am currently installing an OMV NAS on a Raspberry PI 4.
Therefore I followed these instructions: https://github.com/OpenMediaVa…ing_OMV5_on_an%20R-PI.pdf
OMV is running smoothly so far. Only with my hard disks there are problems.
I have 2 HDD hard disks in this dock: https://www.amazon.de/Inateck-Dockingstation-Dual-Schacht-Offline-Klonen-unterstützt/dp/B07DZWBN5Y/ref=sr_1_6?__mk_de_DE=ÅMÅŽÕÑ&keywords=hdd+dock&qid=1576337575&sr=8-6
I formatted both disks previously on Windows 10 in NTFS. They are recognized and work correctly in Windows.
In the OMV Web-Panel both are displayed under "Drives".
They don't appear under "File systems", so I clicked on "Create", selected one of the two disks and started it with ext4.
(This surprised me, because one of my other external hard disks with NTFS can be used and integrated successfully )

After a short time this window opened:

On details this text show up:

Code

{
   "response":null,
   "error":{
      "code":0,
      "message":"Session not authenticated.",
      "trace":"OMV\\HttpErrorException: Session not authenticated. in \/usr\/share\/php\/openmediavault\/session.inc:146\nStack trace:\n#0 \/usr\/share\/php\/openmediavault\/rpc\/proxy\/json.inc(81): OMV\\Session->validateAuthentication()\n#1 \/var\/www\/openmediavault\/rpc.php(45): OMV\\Rpc\\Proxy\\Json->handle()\n#2 {main}"
   }
}

Now every time I clicked on a button or a menu entry, this window comes up again.

How do I use my Hard Drives now in OMV correctly and how do I fix this error?

Greetins,
Feuerhamster

Feuerhamster · 14. Dezember 2019

Ok Update!

I've restarted the PI and tried again.
Now this error appears when i want to create a new filesystem on my hard drive.

Code

Fehler #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; sgdisk --new=1:0:0 --typecode=1:8300 --print '/dev/sda' 2>&1' with exit code '4': Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Creating new GPT entries.
Disk /dev/sda: 2930277168 sectors, 1.4 TiB
Model: ASM1156-PM
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 061E61EA-FAC0-4BBD-81BE-DB8296C655ED
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 2930277134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)


Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048      2930277134   1.4 TiB     8300
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable. in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:636
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): Engined\Rpc\OMVRpcServiceFileSystemMgmt->Engined\Rpc\{closure}('/tmp/bgstatus7d...', '/tmp/bgoutput1u...')
#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(688): 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}

Alles anzeigen

ryecoaaron · 14. Dezember 2019

ntfs drives really shouldn't be used on Linux. Your old drive is probably an older version of ntfs than the newly created drives. Wipe the drive in the Physical Disks tab before formatting as a native Linux filesystem.

Feuerhamster · 15. Dezember 2019

hm i get a lot of input/output errors when wiping. Is it possible that the Sata-Dock I am using doesn't work because the Dock has 2 hard drive bays and it seems to run through one controller? I am using this: https://www.amazon.de/Inateck-Dockingstation-Dual-Schacht-Offline-Klonen-unterstützt/dp/B07DZWBN5Y/ref=sr_1_6?__mk_de_DE=ÅMÅŽÕÑ&keywords=hdd+dock&qid=1576337575&sr=8-6

Jetzt mitmachen!