Rockstor5.0.9.0 unable to install dependencies for startup

nyctopheliac · December 2, 2024, 12:15pm

Hello everyone,

I am a Linux beginner who is trying to make a NAS for my final project in this course.
I had gone with TrueNAS but the systems that I have cannot handle it thus I have moved to Rockstor.

I have two main problems:

1. I’ve downloaded Rockstor through a flash drive, first using the normal option and then using the failsafe option, and, when I insert it, it asks for a hard drive (I had 2, removed one but the issue persists), it does the installation in either the hard drive or the flash drive (I believe it’s the latter) but, when I boot it up without the flash drive, it says i don’t have an operating system installed.
2. As Rockstor installs, it encounters a few issues:
First, it fails to start Activation of DM Raid sets (which I am not that worried about at the moment, this might be since I removed the other hard drive I had in here).
Secondly, this shows up:

[FAILED] Failed to start Network Manager Wait Online.
[DEPEND] Dependency failed for Build Rockstor
[DEPEND] Tasks required prior to starting Rockstor
[DEPEND] Rockstor startup script
[DEPEND] Rockstor bootstrapping tasks

When typing journalctl -xe -u rockstor, journalctl -xe -u rockstor-pre and journalctl -xe -u rockstor
It shows me these reports:

Dec 02 11:26:36 localhost.localdomain systemd[1]: Depend failed for Rockstor startup script.
Subject: A start job for unit rockstor.service has failed
Defined-By: systemd
Support: https:/:lists.freedesktop.org/mailman/listinfo/systemd-dlevel

A start job for unit rockstor.service has finished with a failure.

The job identifier is 393 and the job result is dependency
Dec 02 11:26:36 localhost.localdomain systemd[1]: rockstor.service: Job rockstor.service/start failed with result 'dependency'```

Dec 02 11:26:36 localhost.localdomain systemd[1]: Depend failed for Tasks required prior to starting Rockstor.
Subject: A start job for unit rockstor-pre.service has failed
Defined-By: systemd
Support: https:/:lists.freedesktop.org/mailman/listinfo/systemd-dlevel

A start job for unit rockstor-pre.service has finished with a failure.

The job identifier is 394 and the job result is dependency
Dec 02 11:26:36 localhost.localdomain systemd[1]: rockstor-pre.service: Job rockstor-pre.service/start failed with result ‘dependency’```

Dec 02 11:26:36 localhost.localdomain systemd[1]: Depend failed for Rockstor bootstrapping tasks.
Subject: A start job for unit rockstor-bootstrap.service has failed
Defined-By: systemd
Support: https:/:lists.freedesktop.org/mailman/listinfo/systemd-dlevel

A start job for unit rockstor-pre.service has finished with a failure.

The job identifier is 392 and the job result is dependency
Dec 02 11:26:36 localhost.localdomain systemd[1]: rockstor-bootstrap.service: Job rockstor-bootstrap.service/start failed with result 'dependency'```


I have already considered downgrading Rockstor and trying to install it on the drive itself but I'm not sure if that's possible.
I can also give away the machine specifications although I don't think that's an issue.

Hooverdan · December 2, 2024, 4:26pm

@nyctopheliac welcome to the Rockstor community.

On your first issue, it should not try to install it to the flash drive, but offer you the hard drive for installation. It’s curious, that after a reboot/removing of the flashdrive it will not boot. May be you can post a screenshot of what driver the installer “offers” for installation, and we can take a look at that.

correct, you don’t have to worry about it. It’s more of an informational message than a real error.

Rockstor fails to start because Network Manager has an issue starting. In recent test channel releases the Network Manager has become a hard dependency, so if that runs into timeout issues (or no network card present) Rockstor will not start unfortunately. I assume you’re not doing anything like bonded network ports, etc. but that your network might take way longer to report back a connection/up status. If you have to network ports, and only one of them connected, you could try to disable the non-connected one in the BIOS to see whether that makes any difference.

If, after the boot Rockstor has not started up. You could try to restart Network Manager using systemctl restart network and then start Rockstor again using:
systemctl start rockstor-build
systemctl start rockstor-pre
systemctl start rockstor

See if that works.

nyctopheliac · December 4, 2024, 11:27am

Sorry for the late reply and thanks for the advice, I’ll be trying that out soon enough. I only have a single network port in this machine, that being Ethernet. It probably times out because we have a switch running into a router that then goes into another switch in the rack and that cycle repeats itself about 2 or 3 times.
We’ve thought of making a small network inside of this room to check that issue but that still takes a bit thus we are taking our time with that.
Once again, your advice is heavily appreciated. Thank you for your time.

nyctopheliac · December 5, 2024, 3:12pm

Follow up to this,
I’ve loaded up the machine today. Made a new installation ot Rockstor5.0.9.0 through Rufus this time. Since my BIOS is somewhat old, 2002-2011 it says, I went ahead and made some changes to the properties: I added 2 options, those being “Add fixes for old BIOSes” and “Enable runtime UEFI media validation” and followed through with the installation as explained in Rockstor USB install disk using Rufus

It seems the changes I’ve made to the flash drive did not work and I do not know how to check the drivers for the installation. If there’s any guide I’ve missed about that, please warn me of so.

Other than that, I also did those steps you told me and I don’t think the processes started up correctly. It did load something, or, at least, tried to.
I have some photos of it. Since I’m a new user I can only have one per post therefore I will also reply to this with some screenshots.

The Web GUI still didn’t load, I think it’s best that I downgrade the version I’m using.

nyctopheliac · December 5, 2024, 3:14pm

I took this screenshot when I was typing out the commands and letting them process what they had to process.

I’m not sure they’re meant to not return any response but they simply went to a new line and tried to load.

nyctopheliac · December 5, 2024, 3:17pm

This one was taken after I started all of the processes and took a quick trip to nmtui hence the discrepancies between the screenshots.

nyctopheliac · December 5, 2024, 3:41pm

Oh, and, yes I did ping the IP on my laptop before trying to check the GUI.

Hooverdan · December 5, 2024, 4:04pm

I think the installation worked, since it at least does not give you any errors of missing commands or files, but I could be wrong, of course.

They usually don’t return a response (I only have observed it sometimes in case of certain errors). By using systemctl status rockstor after the last command returns, you should get some feedback on whether Rockstor has successfully started or not. A successful start would likely show you something like:

● rockstor.service - Rockstor startup script
     Loaded: loaded (/usr/lib/systemd/system/rockstor.service; disabled; preset: disabled)
     Active: active (running) since Fri 2024-11-22 12:41:16 PST; 1 week 5 days ago
   Main PID: 16797 (supervisord)
      Tasks: 11 (limit: 4915)
        CPU: 3h 37min 14.021s
     CGroup: /system.slice/rockstor.service
             ├─16797 /opt/rockstor/.venv/bin/python /opt/rockstor/.venv/bin/supervisord -c /opt/rockstor/etc/supervisord.conf
             ├─16890 /opt/rockstor/.venv/bin/python /opt/rockstor/.venv/bin/gunicorn --config ./conf/gunicorn.conf.py wsgi:application
             ├─16891 /opt/rockstor/.venv/bin/python /opt/rockstor/.venv/bin/data-collector
             ├─16892 /opt/rockstor/.venv/bin/python /opt/rockstor/.venv/bin/django-admin run_huey --workers 2 --worker-type thread --logfile /opt/rockstor/var/log/huey.log
             └─16893 /opt/rockstor/.venv/bin/python /opt/rockstor/.venv/bin/gunicorn --config ./conf/gunicorn.conf.py wsgi:application

Nov 22 12:41:16 rockwurst systemd[1]: Started Rockstor startup script.
Nov 22 12:41:16 rockwurst poetry[16797]: 2024-11-22 12:41:16,936 INFO Set uid to user 0 succeeded
Nov 22 12:41:16 rockwurst poetry[16797]: 2024-11-22 12:41:16,966 INFO RPC interface 'supervisor' initialized
Nov 22 12:41:16 rockwurst poetry[16797]: 2024-11-22 12:41:16,966 INFO supervisord started with pid 16797
Nov 22 12:41:17 rockwurst poetry[16797]: 2024-11-22 12:41:17,971 INFO spawned: 'gunicorn' with pid 16890
Nov 22 12:41:17 rockwurst poetry[16797]: 2024-11-22 12:41:17,974 INFO spawned: 'data-collector' with pid 16891
Nov 22 12:41:17 rockwurst poetry[16797]: 2024-11-22 12:41:17,977 INFO spawned: 'ztask-daemon' with pid 16892
Nov 22 12:41:19 rockwurst poetry[16797]: 2024-11-22 12:41:19,979 INFO success: data-collector entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
Nov 22 12:41:22 rockwurst poetry[16797]: 2024-11-22 12:41:22,984 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
Nov 22 12:41:27 rockwurst poetry[16797]: 2024-11-22 12:41:27,990 INFO success: ztask-daemon entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

FYI, you leave that status screen by pressing q
Usually, even with a successful start at boot, it takes a couple of minutes (depending on speed of machine and OS drive) for the gateway and WebUI to be up and running, after Rockstor has started. So getting to the WebUI using the IP address should eventually be successful.

You can also check the logs by checking out:

journalctl -xe
as well as
tail -n200 /opt/rockstor/var/log/rockstor.log (also use q to return to the command prompt

What I found in the past is that you will likely have an easier time navigating these things if you connect remotely into the box using e.g. PuTTY, as you can easily scroll back up on the screen:

To see beforehand, whether the system is in such a state that you can “ssh” into it, you can use systemctl status sshd, which should give you something like this:

● sshd.service - OpenSSH Daemon
     Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-11-22 12:39:23 PST; 1 week 5 days ago
   Main PID: 903 (sshd)
      Tasks: 1
        CPU: 204ms
     CGroup: /system.slice/sshd.service
             └─903 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Nov 22 12:39:23 rockstorw sshd-gen-keys-start[876]: Checking for missing server keys in /etc/ssh
Nov 22 12:39:23 rockstorw sshd[903]: Server listening on 0.0.0.0 port 22.
Nov 22 12:39:23 rockstorw sshd[903]: Server listening on :: port 22.
Nov 22 12:39:23 rockstorw systemd[1]: Started OpenSSH Daemon.
Nov 22 12:41:37 rockstorw sshd[17236]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.16.0.126  user=root
Nov 22 12:41:39 rockstorw sshd[17234]: error: PAM: Authentication failure for root from 172.16.0.126
Nov 22 12:41:43 rockstorw sshd[17234]: Accepted keyboard-interactive/pam for root from 172.16.0.126 port 64726 ssh2
Nov 22 12:41:44 rockstorw sshd[17234]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 05 07:54:48 rockstorw sshd[18013]: Accepted keyboard-interactive/pam for root from 172.16.0.126 port 52090 ssh2
Dec 05 07:54:48 rockstorw sshd[18013]: pam_unix(sshd:session): session opened for user root by (uid=0)

(again, use q to leave that screen)

I changed your user status, you should be able to put in a bit more within one post.

nyctopheliac · December 5, 2024, 7:43pm

Not with the machine right now, I’ll be back at it on monday but I saw your reply at the time and tried to boot it up through the hard drive. Next time, I can give you info on the Boot Options and the BIOS.
That being said, it showed me this when I tried to boot through the hard drive.

Hooverdan · December 5, 2024, 11:00pm

Very strange indeed.

What I have experienced in the past (and it’s probably somewhere on the forum, too) is that after the install and before reboot, remove the install media (e.g., USB stick), because for some reason the bootloader (grub2) gets confused and ends up not booting from hard disk correctly, it seems.

When you get back, see whether that might have been it, unless you already know you removed the USB stick before/while rebooting.

In case, you have to (yet again ) reinstall, post a screenshot of the devices it suggests to install to.

nyctopheliac · December 11, 2024, 11:13am

Hello, hope you’re doing well, Dan.

Today, I’ve redone the installation again. Through Etcher, this time.
You asked me for the devices it suggests and I took some screenshots, the first one does not have the flash drive plugged into the system and the second one does.

At the moment, I only have one disk inserted into the system. I removed the other one for caution and simplicity. I don’t think it’s a problem with the hard drive. It had an Ubuntu installation before. It was thoroughly wiped and checked before being inserted into the machine it’s in.
Either way, when I plug in the USB, any alternatives to the hard drive that is in the system are gone.
That’s happened every time, including that first time where the GUI worked.

I booted up the flash drive and made a new installation, as always. I haven’t removed the flash drive and I will try to keep it in without touching Rockstor until I get a reply.

It always prompts me to make the installation on the only disk I have, when I had two, it recognized both and asked me to decide.

After it installed, it gave me the usual errors but I was already expecting that.
I ran journal -xe and it returned the setup messages but, when I tried running tail -n200 /opt/rockstor/var/log/rockstor.log it returned this message.

On another note, I checked if I could SSH into it. I ran systemctl status sshd and it was running.
I got into PuTTY and SSH’d it like this

Weirdly enough, it does not let me log in to root.

But it does show me the logs on systemctl status sshd

Not sure if it should report to that port, since the default port is 22. I’ve never worked with SSH, we usually only learn that in college.

nyctopheliac · December 11, 2024, 11:23am

Also checked out a video by Nate Zone I used for the installation process before,

It doesn’t show me most of the lines shown after he logs in. He’s in an older version though.

Hooverdan · December 11, 2024, 4:05pm

I am traveling today so not close to any machine. @Tex1954 maybe you have some ideas on the BIOS behavior that’s seen here. Maybe it’s worthwhile to post the machine specs. Looking at the screenshot it looks like one from 2011/2012 timeframe?

The ssh failure I also have not seen, especially since you were able to connect (I assume, at the initial connection you were asked to “trust” the connection via a popup?

After the install did you reboot?

nyctopheliac · December 11, 2024, 6:34pm

No worries and yes, it does say it’s from 2007-2011. Pretty sure it’s this BIOS here (with a lot of updates missing) but I could be wrong, I can get more info on that tomorrow.

It did ask me to trust the connection, yes.

I did not reboot and asked my head teacher to leave it running until tomorrow since I wouldn’t return to the lab for the day. Now that I think about it, it’s unsafe and can go wrong but only trusted people are allowed in there.

Hope you have a good trip.

nyctopheliac · December 12, 2024, 10:49am

Quick update!!

I was finally able to load into the GUI.

I haven’t removed the drive yet. but I loaded systemctl start rockstor-bootstrap and systemctl start rockstor-bootstrap to then see that rockstor.service was running.
I tried opening the GUI and it didn’t work.

I went ahead and used systemctl restart rockstor to then log out and log in again.

This time, it showed me 2 IPs: the default DNS and its own IP.
I opened the DNS first and it didn’t work but then I tried its IP and it finally posted!

As I mentioned, I’ve yet to remove the flash drive but I’m glad you were able to help me through these steps.

I will probably make another thread if I have any other problems I don’t find a solution to, since the main issue has been solved.

nyctopheliac · December 12, 2024, 10:52am

I spoke too soon.

Traceback (most recent call last):
  File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 41, in _handle_exception
    yield
  File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 418, in post
    return self._update_disk_state()
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/contextlib.py", line 81, in inner
    return func(*args, **kwds)
           ^^^^^^^^^^^^^^^^^^^
  File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 115, in _update_disk_state
    attached_disks = scan_disks(MIN_DISK_SIZE)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/rockstor/src/rockstor/system/osi.py", line 330, in scan_disks
    blk_dev_properties: dict = {
                               ^
  File "/opt/rockstor/src/rockstor/system/osi.py", line 336, in <dictcomp>
    for key, value in (
        ^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

Pretty sure this has to do with the fact that I haven’t removed the flash drive and it’s running through that, I have a 160GB hard drive and I will try to restart it now.

Funnily enough, it still did not install on the hard drive. I have no idea what could cause this, really.

Hooverdan · December 12, 2024, 3:49pm

This is actually an issue that was fixed with 5.0.11-0 & improved on in 5.0.15-0 [phillxnet edit]. Here’s a corresponding thread on the forum:

So, if you can get to the update screen via the menu:

you could update (testing channel) to the latest version. This will likely make this error go away.

From the thread I referenced above, maybe you can also run this command, and post the output:

lsblk -P -p -o NAME,MODEL,SERIAL,SIZE,TRAN,VENDOR,HCTL,TYPE,FSTYPE,LABEL,UUID

phillxnet · December 19, 2024, 6:28pm

@nyctopheliac Hello there. Re:

If you got that Web-UI setup screen then it did install, but with boot issues associated with the install. I.e. at the end of the install it switched over to running that install: to avoid a reboot. But on reboot you run into a likely uefi related issue and assume there has been no install.

Try our latest downloadable installer as it comes with 5.0.15-0 pre-installed and don’t modify the installer at all. Just dump it to a USB key and don’t employ any ‘fixes’ via transfer programs. It likely doesn’t understand our installer.

What I think you are experiencing here is a UEFI boot incompatibility. The new installer may now have this sorted, but if it doesn’t and the reboot after install again fails, then try turning off all UEFI stuff in the BIOS and boot the installer in BIOS/legacy mode (i.e. non UEFI). We are awaiting developments upstream to fix some known issues with UEFI.

So in short you are getting an install and booting into it, but from the initial installer boot. And then setting it up. But on reboot, without the hdd instance able to boot, it looks like it hasn’t installed. Try the latest installer, and don’t bother with any UEFI stuff. It’s even more buggy backwhen this machine was made that it still is know. And there are differing implementations. So set everything to legacy boot (or whatever you bios calls it) and do a fresh install.

From one of your pics it reads “UEFI: PHILIPS 8.07” indicating your are booting that device in UEFI mode. Older UEFI is more of a mess.

Let us know how this goes. And remember not to mess with the installer image - it should not need it. The current installer has been installed on far older machines that this one you are trying.

Also note that the internet is required during the install process and for every update there-after (surprise). We have the following how-to which is more up-to-date than the video you linked to:

Rockstor’s “Built on openSUSE” installer — Rockstor documentation

Hope that helps. Oh and the latest installer (with 5.0.15-0 in) has a nice initial splash screen .

nyctopheliac · December 20, 2024, 6:43pm

Thank you for the explanation, Philip!

I made a VM with Rockstor the other day on Linux Mint since the issue was hogging so much of my time with this project. It has worked perfectly.

Nonetheless, thank you all for your help and happy holidays.