I install the 3.8.13 rockstor ,first I come in the system,the rockstor service is not up,I use command "systemctl start rockstor " it can up ,but when I reboot the system can not boot ??????
I find the progress all in "starting preprocess NFS configuration" ,can not go on..........
@ygd2013520 Is this a fresh install from the Rockstor iso, and does it happen on every boot? I have seen very infrequently a looping behaviour that looks like some kind of systemd race condition between 3 services during boot (non of them were rockstor services) but was not able to reproduce it.
Thanks for reply. YES,it happened on every boot, then I select the “rescue mode” to boot, it can boot sometimes,but most of times can not boot.I use this new ISO on 3 PCs, they are all the same(can not boot).Maybe it is a bug in 3.8.13 ISO ?
My Systems hang on nearly the same point. And I can not get a single system to boot reliably. Ich have tried different systems with different hardware.
The only system on which I did not run into this problem is a VM. On real hardware I can not get rockstor to boot reliably.
I get this too on physical hardware. Fails to boot perhaps 80% of the time on my two NASes, a HP MicroServer Gen8 G1610T and a self-build. Strangely it seems more reliable when selecting the debug boot option, then press e on keyboard to edit the boot options and remove the “quiet” parameter from the second-last line (then Ctrl-X to boot). Also it seems to do better when IPMI or HP iLO out-of-band remote control is not active, so I disconnect these during boot. Seems to be more like 50% success with this approach which I’ve been using ever since I started using Rockstor around six months ago. When it fails, it gets to a different message in the debug boot log each time. Would be great to get this fixed.
I finally found a solution for this on my system. I seems that it works fine now.
It seems the problem is NFS-related, but it is not directly related to nfs.service. So disabling this does not help.
The system hangs on nfs-config.service. And this is before nfs.service.
I modified /usr/lib/systemd/system/nfs-config.service
I modified the line:
Please try if this solution works for you too and report it here.
I think, nfs-config.service is simply startet to early. I came to this, because booting works reliably when network cable is disconnected.
Didn’t make any difference in my experience, still fails to boot most of the time. I take it disabling the NFS service doesn’t prevent the nfs-config.service starting then? If not, is there a way to prevent the nfs-config.service starting at all? That would at least establish whether this is the culprit.
My Rockstors have 20TB & 16TB of storage, appx 60% utilised. I’m wondering whether the devs have tested the boot process at this scale.