Are you able to reach the server via SSH?
I'm having a similar issue where I can't reach the server's services, shares, etc. But the server is reachable via SSH and the web GUI, although I can't log-in to the GUI.
Beiträge von sonofwatt
-
-
So the same thing has happened again. First noticed today that I couldn't access the network file share, and then couldn't log into the web GUI.
I tried to follow the instructions from the results in @votdevs post, but had to install strace first. When I tried to install it, I get the following error.
Zitatapt-get install strace
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
strace
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 533 kB of archives.
After this operation, 1,396 kB of additional disk space will be used.
Err:1 http://deb.debian.org/debian stretch/main amd64 strace amd64 4.15-2
Could not open file /var/cache/apt/archives/partial/strace_4.15-2_amd64.deb - open (30: Read-only file system)
W: Not using locking for read only lock file /var/lib/dpkg/lock
W: chown to _apt:root of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/cache/apt/archives/lock
W: Problem unlinking the file /var/cache/apt/archives/partial/.apt-acquire-privs-test.2PNfO8 - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/cache/apt/archives/partial/strace_4.15-2_amd64.deb - PrepareFiles (30: Read-only file system)
E: Failed to fetch http://deb.debian.org/debian/p…e/strace_4.15-2_amd64.deb Could not open file /var/cache/apt/archives/partial/strace_4.15-2_amd64.deb - open (30: Read-only file system)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?Tried running apt-get update, but again got a ton of errors ending in (30: Read-only file system).
-
Ah I see what you did there. You searched just for the relevant part of the error message. My eyes glazed over as soon as I hit the Path=/ part so ended up just searching for the whole string.
Last night I got impatient and re-started the server and that resolved it. For now. I'll check those search results if it happens again and try the mentioned strace -f -e trace=file command.
-
Oh. How do I check that?
It's a 150GB ssd.EDIT: ran the df command and this was the output.
ZitatFilesystem 1K-blocks Used Available Use% Mounted on
udev 12315196 0 12315196 0% /dev
tmpfs 2466992 274852 2192140 12% /run
/dev/sda1 90094440 3032944 82441876 4% /
tmpfs 12334944 0 12334944 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 12334944 0 12334944 0% /sys/fs/cgroup
tmpfs 12334944 4740 12330204 1% /tmp
JXNSRZ-part1:K5R14N-part1 19376767176 12746113800 6630620608 66% /sharedfolders/Colossus
/dev/sdd1 9764087780 6397883200 3366188196 66% /srv/dev-disk-by-label-Parity
/dev/sde1 491207900 10717244 480474272 3% /srv/dev-disk-by-id-ata-Samsung_SSD_850_PRO_512GB_S250NXAGB52683Y-part1
/dev/sdb1 9688383588 6393550548 3294816656 66% /srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEJXNSRZ-part1
/dev/sdc1 9688383588 6352563252 3335803952 66% /srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEK5R14N-part1So looks like my boot drive sda is 4% full.
-
Tried to log into the web gui today and was told my username or password was incorrect. Tried the usual stuff, no luck. I'm certain I didn't change my password since the weekend, but decided to just do a re-set with omv-firstaid and be done with it.
When I try to execute the control panel admin password change, I get the following error.
Updating control panel administrator password. Please wait ...
ERROR: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; usermod --password '$1$wITgGd9N$iASwhljseorIBYRc.f5hx/' admin 2>&1' with exit code '1': usermod: cannot lock /etc/passwd; try again later.I did find this thread with a similar issue, but the steps listed there don't work for me. https://forum.openmediavault.o…update-OMV-on-raspberry2/
Also, I'm not sure if this matters, but the system seems sluggish.
Any ideas?
-
Hey guys, How do I uninstall Shellinabox?
I "uninstalled" it from the plug-in list, even tried a restart of the server, but it's still showing in the left side menu under Services.When I click on Shellinabox now, I get this error.
ZitatError #0:
OMV\Rpc\Exception: RPC service 'Shellinabox' not found. in /usr/share/php/openmediavault/rpc/rpc.inc:99
Stack trace:
#0 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Shellinabox', 'getSettings', NULL, Array, 1)
#1 {main} -
Then something in the bios is throwing this, is there a bios setting to enable ahci
This server the HP DL360 G7 apparently doesn't support AHCI.
At a guess, it's BIOS related? And there may to 2 BIOS' involved, the host adapter and the motherboard.
ryecoaaron has way more experience with something like this. I've never seen anything like it.(The only thing that comes to mind is, with building a USB thumb-drive and the Debian installer said something like, "error partitioning drive - reboot recommended" or something like that. I rebooted, went through the install routine again and on the second time around all was fine.)
There definitely is a BIOS on the SAS card, but I ran into the same issue after I'd physically removed the card.
At this point I've installed OMV to various SD cards and USB thumb-drives easily a dozen times, and haven't seen that error. I guess this older server just isn't easily compatible with OMV or Debian.
Yes, run swapoff from the command line. And no, just idling along would not be a valid test. Only operations that use up all the memory would trigger a swap, and if there is no swap available the machine would crash.
I ran swapoff, and did as much as I could to test the system. Was able to run a Windows VM without any problems. I used DiskGenius to erase the Linux Swap folder, then expand the primary partition. The system would boot, but not without a screen of error messages.
The first screen was filled with this message again and again mdadm: No arrays found in the config file or automatically, then later at the bottom before loading OMV, A start job is running for dev-disk-by\(long list of characters).device.
I tried creating the OMV disk again from scratch, then using DiskGenius again. Same errors. So I guess the Linux Swap is needed. -
Last night I played around, and physically removed the PCI-E SAS controller from the system and completely removed the sas cable from the backplane/system. I still got the hd0 error!
There aren't any sata power connectors on the mobo, so it would be a chore to go that route.With the user in the other thread using a sata controller, wouldn't that be like my setup with this HBA controller card? (Assuming it is working properly and is in IT mode)
The card is an LSI 9207, and the server is an HP DL360 G7. -
@gderf Can you think of any problem with using the 32GB card as is? The boot partition is 5.7GB. If I remember, the minimum install volume size for OMV is 4GB? So 1.7GB left over. Will that cause issues for logs, or any temp files that might accumulate?
Also, wondering how you were able to install to an SSD the same size as your systems amount of RAM? When I try to use a smaller SD or Flash Drive, I get the error Failed to partition the selected disk. This probably happened because the selected disk or free space is too small to me automatically partitioned.
When I first ran into this error the other week, I did some research and found people talking about the Linux Swap volume needing to be the same size as your system RAM. -
No it's not, but the hd0 error has something to do with the backplane, I'll see if I can find the thread where this came up but HP's can be an issue but not impossible to resolve.
I'm really confused! I thought the physical backplane was a 'dumb' interface. Just a physical connection to some sort of controller.
Yes please do, this is so weird.
I wonder if the SD reader is managed by the same chipset that would be in use by the motherboard's onboard SAS controller.Yes, run swapoff from the command line. And no, just idling along would not be a valid test. Only operations that use up all the memory would trigger a swap, and if there is no swap available the machine would crash.
Can you think of something simple I could do to stress the system?
-
But before doing this I would disable swap with the swapoff command and run it a while to be sure you can go without swap.I'm guessing I have to run this from the Debian command line. I'll give it a try. Will just having the system idle be enough of a test. I haven't set anything up on OMV yet, other than the basics.
That's what is throwing the hd0 error, the last thread I dealt with with a similar problem was to remove the backplane but use the caddies, but the OP had purchased sata controller card and connected each drive to the sata controller.
If your new controller supports IT mode it may require flashing with firmware depends on the card.
I have had 2 HP servers and I have turned off the raid in the bios, but I have only used 32Gb flash drives. I don't know, but what might be worth a try is to disconnect the backplane from the card and try an install to the 256Gb sd card. If it works and boots then re connect the card and reboot, if it boots then the problem is solved other then trying to get the new PCI-E flashed to IT mode.
All this is guess work, but I always prefer to try options out at first.
Sorry I've mis-explained. The backplane is for some SATA 2.5 inch SSD drives. Those 2 caddies are currently removed from the system. The backplane is connected to the SAS card, which is in IT mode already. The server's onboard raid controller is disabled in the BIOS. Also the SD Card reader isn't connected to the backplane, it's a card-slot soldered directly to the motherboard. Does that make sense?
I will try physically removing the add-on SAS card to see if that helps. I'm not sure if there is a way to further disable the onboard RAID controller. It's currently not connected to anything, disabled in the BIOS, and the cache card is removed. -
You disable and delete the swap partition after the install and optionally grow the primary partition to fill the disk.
How do you do that?
Sorry I knew it was one or the other but @gderf is right you wouldn't need a swap.
Is there another command I can try? Both grub-update and update-grub gave the error. I'd still prefer to use the 256GB card I bought. Don't have much other use for it.
Best guess it's still attempting to boot from the hw raid hence the error, depending on the machine in the bios you can set the raid option to sata, ide legacy, ahci depends on the bios, but some require the raid to be flashed to IT mode this 'turns into' a sata controller.
When you say your not using it I take you're still using the 'caddies' if so it's running off a backplane, that all the drives plug into that backplane then has a single connection to the m'board. This is typical of HP and Dell machinesSorry I should have said I've disabled the on-board raid controller. AFAIK, there isn't an IT mode available for that controller, the P410i. I bought a PCI-E add-on card that supports IT mode. But it's giving issues acting as the boot device, so that's what lead me down the path of trying to use the motherboard's SD slot.
That's correct. It's an HP server. I run a SAS cable from the backplane port to the SAS add-on card. And I have an external SAS enclosure I'm going to use for a SnapRAID array that's going to be the main storage pool.The weird thing here is that the 32GB SD card works fine, and anything larger that I've tried (64GB or higher) gives the attempt to read or write error. So weird that it's size dependant.
-
Oh interesting. How do I choose to not have a swap partition? The OMV installer adds it on that swap partition automatically.
-
On my previous install I noticed OMV was storing certain things on the boot partition. I moved Docker images to another physical volume, but assumed there would be other things I couldn't move that would accumulate over time. The system has 24GB of RAM, so a 32GB card was the smallest I could get to work initially. Smaller cards didn't leave enough space for the Linux Swap partition. Apparently that is always the same size as the system RAM.
Tried typing grub-update at the grub rescue> prompt and got the error Unknown command 'grub-update'.
Elsewhere I saw that people use the syntax update-grub but that gave the same error.Oh that's interesting. This system does have onboard HW RAID, but I'm not using it. Also I thought it was only for the SAS connected drives. Maybe the SD Card is managed as part of the same system?
-
For some reason I can't install to 64, 128, or 256GB SD Cards, but when I tried to use a 32GB card it worked fine.
With the larger cards, the install goes fine, but on boot I get the error:ZitatAttempting Boot From USB DriveKey (C:)
error: attempt to read or write outside of disk 'hd0'Entering rescue mode...
grub rescue>I tried the guide https://askubuntu.com/a/1088738, but I get an error every time when I get to the "ls /boot" command.
I also tried with a USB to SD Card adapter and got the same error as above.Any ideas? Is there a known limitation with the size of SD card used in OMV or Debian?
-
Thanks for the reply @gderf.
Ahh ok interesting. I saw you ask a similar question in the other thread about docker base path. I'm not sure what it means. How do I check?
Ideally the base path would be on my array where I have the most free space.I wonder, do you also have unionFS installed? I think the error with 'quataon' started after I installed that plugin.
-
I changed my 'Docker Base Path' to a shared folder on a UnionFS mount. As soon as I hit save I got an error message and the docker service failed. After a restart the docker service is still down.
Here's the error:
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; systemctl start 'docker' 2>&1' with exit code '1': Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
#1 /usr/share/php/openmediavault/system/systemctl.inc(146): OMV\System\SystemCtl->exec('start', NULL, false)
#2 /usr/share/omvdocker/Utils.php(109): OMV\System\SystemCtl->start()
#3 /usr/share/omvdocker/Utils.php(541): OMVModuleDockerUtil::startDockerService()
#4 /usr/share/openmediavault/engined/rpc/docker.inc(1205): OMVModuleDockerUtil::changeDockerSettings(Array, Array)
#5 [internal function]: OMVRpcServiceDocker->setSettings(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setSettings', Array, Array)
#8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'setSettings', Array, Array, 1)
#9 {main}Any ideas how to fix this?
On a side note, is anyone else having a lot of stability/reliability issues with OMV? This is my 4th install of it in as many weeks trying to get it to work without error, and I still have a lingering quota service failure, and unfortunately now Docker is broken.
-
I reinstalled OMV, worked great without errors for a while. Then after a restart the quotaon service failed again.
This thread says its a conflict with the quota service. https://www.howtoforge.com/com…aon-service-failed.70322/
Does anyone know, which service quotaon or quota OMV relies on?
-
*bump*
Hoping to find a solution for this. If not I'll have to try a fresh install. But would really prefer not do that if I can avoid it.
-
Hi guys,
I keep getting these alerts, 4 so far. I can log-in to the OMV GUI no problem, so not sure what is going on.ZitatThe following users are locked/banned or are candidates for too many failed login attempts:
Login Failures Latest failure From
admin 1 06/04/19 02:14:48 unknownYou can reset their counters and unlock them via the omv-firstaid command.
I should note that I have no WAN ports open on my network firewall to this server.Any ideas?