SCST is not loaded

72 views
Skip to first unread message

Petr Hosek

unread,
Jul 5, 2024, 9:51:44 PM7/5/24
to esos-users
Hi, I'm having issue with SCST that is not loading after reboot.

There were no HW changes, just complete reboot. My ESOS is running as VM in Hyper-V and it's only as lab to test the functionality.

Has anyone had the same problem?

ESOS version 4.2.1

boot_log.png
dmesg.png
SCST.png

Marc Smith

unread,
Jul 5, 2024, 9:54:34 PM7/5/24
to esos-...@googlegroups.com
In your kernel log output, it says it can't find the file
"/mnt/vdisks/fs01/vdfs01" -- can you access that file from the root
shell? I assume not since SCST couldn't, so figure out why that is
(perhaps the file system isn't mounted).

--Marc


>
> --
> You received this message because you are subscribed to the Google Groups "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/cf0fbe58-85e8-4427-801c-e81f51df8dd1n%40googlegroups.com.

Petr Hosek

unread,
Jul 9, 2024, 8:32:43 AM7/9/24
to esos-users
There is not a single file inside "/mnt/vdisks/fs01" 
but why it is gone in the first place?

Dne sobota 6. července 2024 v 3:54:34 UTC+2 uživatel Marc Smith napsal:

Marc Smith

unread,
Jul 9, 2024, 8:33:51 AM7/9/24
to esos-...@googlegroups.com
On Tue, Jul 9, 2024 at 8:32 AM Petr Hosek <hosek...@gmail.com> wrote:
>
> There is not a single file inside "/mnt/vdisks/fs01"
> but why it is gone in the first place?

Is the file system mounted at that location?
> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/6348b218-90b6-4330-9899-2b81c68c97b2n%40googlegroups.com.

Petr Hosek

unread,
Apr 5, 2026, 7:36:12 PM (10 days ago) Apr 5
to esos-users
Hi,

I'm answering just to close this thread after nearly two years.
The issue was in missing array. I'm using now a VMware Workstation with physical disk passthru, so the array is being established via mdadm. The ESOS starting sequence is using mdadm in "/etc/rc.d/rc.mdraid start" command that will trigger mdadm --assemble --scan
The issue is that mdadm config file in /etc/mdadm.conf stays completely untouched even after sync configuration from TUI, so mdadm is not able to reassemble the raid/array.

My workaround was:
- recreate array via TUI (optionally you can run "/etc/rc.d/rc.scst start" to mount FS)
- export runing config in /proc/mdstat via command mdadm --examine --scan >> /etc/mdadm.conf
- check if config was saved into /etc/mdadm.conf file

I hope that this is a permanent workaround and it will not appear again.
Dne úterý 9. července 2024 v 14:33:51 UTC+2 uživatel Marc Smith napsal:
Reply all
Reply to author
Forward
0 new messages