The installation fails when I try to install to a 240 GB MSI Spatium S270 SSD. I tested the installation with 3 identical drives and 2 different computers (one has an H110 chipset and the other an H170 chipset)
Rockstore installed okay on a 1 TB Crucial SSD.
The 240 GB MSI Spatium S270 drives work with other operating systems so it’s an incompatibility issue with that model of drive and Rockstore.
[ok] Finished dracut pre-mount hook
[depend] Dependency failed for a File System Check on /dev/disk/by-label/ROOT.
[depend] Dependency failed for /sysroot.
[depend] Dependency failed for Initrd Root File System.
[depend] Dependency failed for Mountpoints Configured in the Real Root.
[ok] Stopped Dispatch Password Requests to Console Directory Watch.
[ok] Stopped target Basic System.
[ok] Stopped target Initrd File Systems.
[ok] Stopped target System Initialization.
[ok] Stopped dracut pre-mount hook.
[ok] Stopped dracut initqueue hook.
[ok] Stopped dracut pre-triger hook.
[ok] Stopped dracut pre-udev hook.
[ok] Stopped dracut cmdline hook.
[ok] Stopped dracut ask for additional cmdline parameters.
[ok] Started Emergency Shell.
[ok] Reached target Emergency Mode.
Warning: /dev/disk/by-label/root does not exist
Generating “/run/initramfs/rdsosreport.txt”
Entering emergency mode. Exit the shell to continue.
Type “journalctl” to view system logs.
You might want to save"/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a big report.
Press Enter for maintenance
(or press Control-D to continue):
Two questions, did you wipe the entire Spatium drive before attempting to install Rockstor to ensure there is no dangling conflict?
Did you attempt the install with the Slowroll or Tumbleweed flavor of Rockstor? Sometimes that handles specific chipset/drive/graphics (though not relevant here) better than Leap
Thanks for posting this issue, I had a MSI Spatium S270 installed as the OS drive but after a reboot it, would break the BTFRS, and when that happened WDSS would not work anymore, I had to destroy the pool and rebuild it.
I am wondering whether, since the bare-metal install of Rockstor builds on the JeOS image with minimal things there, there is a kernel module that’s required for the drive to work/be recognized. There were a few instances in the past, where that was the case.
It could be worthwhile to compare the loaded kernel modules between the full Leap install and Rockstor. Also, if you’re up for it to try, you could install Rockstor on a vanilla Leap installation (that recognizes the drive) and see whether you still run into the problem. If not, it would point to a firmware/kernel/product driver that would need to be installed on the bare-metal install of Rockstor. I think you could check/compare using something like:
zypper se -s kernel-firmware
But I am not entirely sure what specific firmware to look for, that might be another google search away.
EDIT (it was patently wrong what I said below. The kernel-default package is used by Rockstor and it is also the one at least required vs. the stripped down kernel-default-base package.) Another search seems to indicate that in some cases, the packagekernel-default-baseis required when NVMe drives are involved. I believe, the Rockstor base install "only" contains thekernel-default`.
@koniuszko welcome to the Rockstor community. In your case it’s the same type of drive you’re having the same issue with, or another type?
I still think the best bet (albeit a bit cumbersome) is to do a comparison with a vanilla LEAP install to see what might be missing on the JeOS based Rockstor image.
What was found over the years is that the wipe doesn’t always seems to work from within the Rockstor application for various reasons. It’s usually not a problem, when destroying an existing btrfs pool for example and then recreating it, however in some case, e.g. if multiple partitions are on the disk (and considering Rockstor does not support - at least not yet - the partition-based vs. device-based setup) the deletion method used is not effective.
Hence there is the Pre-install Best Practice section in the Installation section of Rockstor. See this chapter on disk wiping:
My first question above:
was referring to that approach of cleaning “foreign” disks first before attempting to install. I could have been more explicit about it.