I just tried to reboot again.
The error message says:
„Invalid shim signatures“
Please install kernel first.
Any support will be highly appreciated …
I just tried to reboot again.
The error message says:
„Invalid shim signatures“
Please install kernel first.
Any support will be highly appreciated …
I guess so, just keep in mind that most modern kernels can sometimes have some instability. This is why the openmediavault-kernel plugin offers several options.
Sorry for following up :-D.
I installed the kernel via the OMV-GUI.
When trying to boot, it tells me that the initial ramdisk cannot be initialized, I needed to load the kernel first.
What am I missing here?
Thank you
Thank you! I will keep this in mind.
Thank you for your suggestion - I would assume that the latest kernel (6.2) would be the one to go?
Dear,
I am currently facing a (from my perspective) strange issue. After switching hardware, I am currently refilling my HDDs with the data that it should have.
Unfortunately, I am getting into issues here.
When I start to copy the data (either via SMB or via SFTP), everything is running smoothly. The network speed is about 100 - 115 MB/s and the files are being
1. written and
2. evenly distributed on my mergerfs-pool (consisting of two HDDs (sdb and sdc)
What I can see in the dashboard is that there are a lot of Soft-IRQs, like this
After "some" data being transferred (100 GB to 2,5 TB), at least one of the HDDs is falling into RO mode, which obviously stops any transfer.
As soon as this happens, I do a reboot via the GUI (which is still available). After the reboot the data transfer can start again.
My current setup:
NUC11ATKPE (Pentium Silver N6005)
16 GB RAM
1 M2-SSD (/dev/nvme0n1p2)
2 HDDs (/dev/sdb, /dev sdc)
1 SSD (/dev/sda)
connected via a 4 bay HDD enclosure and connected via USB.
My idea is that there are some drivers for the USB ports are missing, since the HDDs were working without any issue on a RaspPi v4.
I have enclosed roughly 15 minutes of syslog events - hopefully this helps, otherwise, any idea is highly appreciated :-D.
Thank you for pushing me in the right direction.
Best regards
Gilhin
As an update and to solve this thread:
I have bought a SSD/ HDD enclosure (thank you for naming one in your signature, Soma 😁).
Since using it, no further issued occured.
Thank you for your support,
best regards
Gilhin
If it has
nowno external power supply, yes.
Got it - thank you for your feedback.
I will double check the possibilities for HDD enclosures.
Regards
Gilhin
Alles anzeigenThere's a typo there, the command is: (you need sudo since you're not running as root)
sudo cat /proc/partitions
You need to read a bit on the power requirements and outputs of the USB bus of the Pis.
Even with the Official Power Supply from Raspberry, power delivery will be limited on the USB.
Search the web for raspberry pi under voltage to see a few.
And, just a side note: a NAS isn't meant to be run with portable drives.
Thank you for mentioning the typo .
Concerning your side note: Is a SSD a portable drive in this context?
Regards
Gilhin
What is the output of blkid and cat /pro/partitions?
pi@raspNAS:~ $ blkid
/dev/mmcblk0p1: LABEL_FATBOOT="boot" LABEL="boot" UUID="0F92-BECC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b569bd61-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="41c98998-6a08-4389-bf74-79c9efcf0739" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b569bd61-02"
pi@raspNAS:~ $ sudo cat /proc/partitions
major minor #blocks name
1 0 4096 ram0
1 1 4096 ram1
1 2 4096 ram2
1 3 4096 ram3
1 4 4096 ram4
1 5 4096 ram5
1 6 4096 ram6
1 7 4096 ram7
1 8 4096 ram8
1 9 4096 ram9
1 10 4096 ram10
1 11 4096 ram11
1 12 4096 ram12
1 13 4096 ram13
1 14 4096 ram14
1 15 4096 ram15
179 0 124868608 mmcblk0
179 1 262144 mmcblk0p1
179 2 124602368 mmcblk0p2
Alles anzeigen
The Raspi is very tight with its power supply. Do the SSDs have their own power supply?
Thank you for mentioning - no they haven‘t.
However, if it was the power supply, I would have expected that the SSDs would „fail“ in general, but not „just“ after a reboot.
Dear,
I have switched my setup to a Raspberry Pi 4 due to energy consumption issues.
My setup is now a Pi 4 (8GB) with two SSD connected via USB. The setup (on top of PiOS 64 Lite) was smooth and easy as expected
However, when I needed to reboot my machine, I am not getting the SSDs back online.
The filesystem tab shows
and the log says
20.1.2023, 07:50:42
monit[800]: 'mountpoint_srv_dev-disk-by-uuid-4ed185e7-1e82-471a-be43-babf14bb055f' status failed (1) -- /srv/dev-disk-by-uuid-4ed185e7-1e82-471a-be43-babf14bb055f is not a mountpoint
20.1.2023, 07:50:42
monit[800]: Lookup for '/srv/dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d' filesystem failed -- not found in /proc/self/mounts
20.1.2023, 07:50:42
monit[800]: Filesystem '/srv/dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d' not mounted
20.1.2023, 07:50:42
monit[800]: 'filesystem_srv_dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d' trying to restart
20.1.2023, 07:50:42
monit[800]: 'mountpoint_srv_dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d' status failed (1) -- /srv/dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d is not a mountpoint
20.1.2023, 07:50:42
monit[800]: 'mountpoint_srv_dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d' status failed (1) -- /srv/dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d is not a mountpoint
Alles anzeigen
Looking in the /etc/fstab it shows
pi@raspNAS:~ $ cat /etc/fstab
proc /proc proc defaults 0 0
PARTUUID=b569bd61-01 /boot vfat defaults 0 2
PARTUUID=b569bd61-02 / ext4 noatime,nodiratime,defaults 0 1
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
# >>> [openmediavault]
/dev/disk/by-uuid/b7e26625-4434-4163-83e8-c3c40d6f148d /srv/dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d btrfs defaults,nofail 0 2
/dev/disk/by-uuid/4ed185e7-1e82-471a-be43-babf14bb055f /srv/dev-disk-by-uuid-4ed185e7-1e82-471a-be43-babf14bb055f btrfs defaults,nofail 0 2
# <<< [openmediavault]
Looking into /srv shows the SSDs - and they are accessible on the CLI.
pi@raspNAS:~ $ cd /srv
pi@raspNAS:/srv $ ls -al
total 28
drwxr-xr-x 7 root root 4096 Jan 15 10:08 .
drwxr-xr-x 21 root root 4096 Jan 15 18:38 ..
drwxrwxrwx 5 root root 4096 Jan 19 19:52 dev-disk-by-uuid-4ed185e7-1e82-471a-be43-babf14bb055f
drwxrwxrwx 2 root root 4096 Jan 14 15:56 dev-disk-by-uuid-b7e26625-4434-4163-83e8-c3c40d6f148d
drwxr-xr-x 2 ftp nogroup 4096 Jan 14 15:42 ftp
drwxr-xr-x 3 root root 4096 Jan 19 18:54 pillar
drwxr-xr-x 7 root root 4096 Jan 19 18:54 salt
What can I do to get the two disks back up again - and to have them up reliably?
In the forum I found the two possibilities mount -a or mount -o remount / - unfortunately both commands did not change anything for me.
Thank you for supporting me here.
Best regards
Gilhin
So from my understanding you need one machine that does the network administration - like seemingly your router does, assumingly via DHCP.
Is your switch capable of doing so?
So I would change the setup and have the switch and the NAS connected to the router and the windows machines connected to the switch.
Gesendet von meinem SM-G925F mit Tapatalk
Dear all,
after having used Virtual Box for a longer time, it isn't starting anymore.
When trying to open the .vdi-file manually via the GUI, I receive the following error:
VirtualBox error: rc=0x80004005 Extra content at the end of the document. Location: '/media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi', line 1 (0), column 2. /home/vbox/vbox-4.3.34/src/VBox/Main/src-server/MachineImpl.cpp[472] (nsresult Machine::initFromSettings(VirtualBox*, const com::Utf8Str&, const com::Guid*)) (0x80004005)
When clicking on details, I receive a longer error:
SoapFault Object
(
[message:protected] => VirtualBox error: rc=0x80004005 Extra content at the end of the document.
Location: '/media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi', line 1 (0), column 2.
/home/vbox/vbox-4.3.34/src/VBox/Main/src-server/MachineImpl.cpp[472] (nsresult Machine::initFromSettings(VirtualBox*, const com::Utf8Str&, const com::Guid*)) (0x80004005)
[string:Exception:private] =>
[code:protected] => 0
[file:protected] => /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php
[line:protected] => 850
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php
[line] => 850
[function] => __soapCall
[class] => SoapClient
[type] => ->
[args] => Array
(
[0] => IVirtualBox_openMachine
[1] => Array
(
[0] => Array
(
[_this] => c329e814d2cc4e5a-0000000000000761
[settingsFile] => /media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi
)
)
)
)
[1] => Array
(
[file] => /usr/share/phpvirtualbox/lib/vboxconnector.php
[line] => 2307
[function] => openMachine
[class] => IVirtualBox
[type] => ->
[args] => Array
(
[0] => /media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi
)
)
[2] => Array
(
[file] => /usr/share/phpvirtualbox/lib/vboxconnector.php
[line] => 938
[function] => remote_machineAdd
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => Array
(
[file] => /media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi
[fn] => machineAdd
)
)
)
[3] => Array
(
[file] => /usr/share/phpvirtualbox/lib/ajax.php
[line] => 304
[function] => __call
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => machineAdd
[1] => Array
(
[0] => Array
(
[file] => /media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi
[fn] => machineAdd
)
[1] => Array
(
[0] => Array
(
[data] => Array
(
[responseData] => Array
(
)
)
[errors] => Array
(
)
[persist] => Array
(
)
[messages] => Array
(
)
)
)
)
)
)
[4] => Array
(
[file] => /usr/share/phpvirtualbox/lib/ajax.php
[line] => 304
[function] => machineAdd
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => Array
(
[file] => /media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi
[fn] => machineAdd
)
[1] => Array
(
[0] => Array
(
[data] => Array
(
[responseData] => Array
(
)
)
[errors] => Array
(
)
[persist] => Array
(
)
[messages] => Array
(
)
)
)
)
)
)
[previous:Exception:private] =>
[faultstring] => VirtualBox error: rc=0x80004005 Extra content at the end of the document.
Location: '/media/3c9d366f-10ed-4d58-a7ef-32dc9542500f/VMs/Debian Jessie/Debian Jessie.vdi', line 1 (0), column 2.
/home/vbox/vbox-4.3.34/src/VBox/Main/src-server/MachineImpl.cpp[472] (nsresult Machine::initFromSettings(VirtualBox*, const com::Utf8Str&, const com::Guid*)) (0x80004005)
[faultcode] => SOAP-ENV:Client
[detail] => stdClass Object
(
[RuntimeFault] => stdClass Object
(
[resultCode] => -2147467259
[returnval] => c329e814d2cc4e5a-0000000000000762
)
)
)
According to this, an error must be residing in Debian Jessie.vdi - but how can I handle it to at least export my data?
Thank you for any help,
best regards,
Gilhin
Just as a quick feedback: It is also wirking again at my mobile. Thank you for your swift support.
Same issue with me - any suggestion on how to resolve it?
According to this http://ubuntuforums.org/showthread.php?t=2206093 it might be a repo problem.
Did you add a source via the CLI?
Apart from the reasons that tekkb already pointed out:
OMV is based on Debian and at least from my use case I realised that this gave the the possibility to use and to try very different approaches to my tasks (using the CLI) - from my point even more than a Windows Server allowed me. I think I can compare these two microsystems, as I host an OMV-based NAS and a Windoes server at home.
Hi Roland,
there are quite a few possibilities that were already discussed in the forum.
Tty to search for DMS or related wordings.
Personally, I use ecoDMS as solution - and can recommend it, which is definetely affordable (I think EUR 49,00/ needed connection between server and client).
But you might also consider in simply using a defined folder structure, where you save your PDFs.
Best regards,
Gilhin
Greetings,
When you say that you enabled everything, did you enable SMB/CIFS?
And did you furthermore add a shared folder that should be broadcasts by samba?
If not, please do so. This should work.
Best regards,
Gilhin
As your problem looks like your OMV installation does not recognize the JDownloader repository, have you checked that you are on OMV 2.X and you have enabled the most recent OMV-extras plugins?