I will also add that on the new setup being bench tested now, I discovered ALL the brand new SATA cables I purchased were bad! I will never buy that brand again… they looked very good with clips to hold them in, but somehow simply didn’t perform with SSDs at all!
Obviously I filed them in the bin outside…
Thanks to @Hooverdan and @Tex1954
Before I try to unpick @Hoverdam’s comments, perhaps it would be better to explain in as much detail as I remember, the install process used for the Supermicro X10 board.
Downloaded the latest version of Rockstor and created an Install usb “disc” with Rufus as balenaEtcher wouldn’t function.
With remote monitor, usb keyboard and Network cable connected, the OS drive connected to the Sata 3 socket 0, the install process was initiateed when the splash screen appeared.
There was no prompt for a user name and password, unless when asked for the user name and password that was the request for a user name etc, however the original name etc were entered.
Tha system Then pronounced that Rockstor was installed.
Continuing with the process the docker fail note was displayed and notes for Zypper appeared.
No request for a root password was made at any point.
Using the previous user credentials and root password Zypper was deployed, both commands as suggested with a note that all was up to date with the first and a series of what appeared to be updates followed.
Moving to a W11 laptop, (after shutdown and reconnection of data drives, removal of usb etc) the GUI login appeared and initiated (after the new ip address was discovered by interrogating the router as no info for the ip had been displayed on the monitor during installation).
The dashboard showed the pool and shares with cpu active, a small amount of Ram in use so it appeared that nothing further was required except starting the docker which was attempted both through the Services, on the Rockons screen and the CLI, all without success.
Question
Is it possible that a fresh install wasn’t achieved and the system was still running on the earlier install?
But
The newer cpu was recognised, as was the increase in Ram
At the next opportunity a check on the pool and discs page will be made to ensure correct importing has been achieved, but wouldn’t the dashboard not show their presence if they hadn’t?
Will deploy at the next available opportunity on return
Thanks @Hooverdan, in answer to your question
Just thought, the last entry in the tail log might be of interest. (seeing as i’ve discovered how to get a copy and edit it.)
I am surprised, it appears to me that the new installation did not wipe the original OS. Because the “admin” WebUI User should only be created after the installation has been completed, and during the first login to the WebUI. So, maybe the disk needs to be explicitly wiped before the installation (though it should have, by all my experience killed the previous one).
I would delete both, create a new one, and the attach it to the Rockstor service as the Rockon Root. This also means, that you created each of them on the Pool that you have (I’ve been doing it in the past on on the OS disk and not the pool, but in more recent installs set up the share on my pool as well).
so that’s good, indicating that the pools are consistent, etc.
I believe, that message is related to the speed/frequency of attempts to start the docker service, not a network connection.
The tail you posted does not give any further indications, on why it failed the docker service start. And it seems the command
journalctl -xeu docker.service
might not give any better indication either (other than saying too many attempts too fast, etc.).
So, if the first item in my post about the old install not really being overwritten is correct, then it might have just continued to carry the problem forward. If not, then I am not sure what else to look for at this moment.
Since you’ve tried to manually restart docker, after the network was up, and it still didn’t want to do it, I’m fresh out of ideas …
Once again thanks to all dare I say “colleagues” for help in this issue as we now have solved it.
After the successful boot with the Supermicro X10 board, I began to think that the os disc was a good candidate for causing problems, the only replacement hardware to hand was a 64Gb (Intenso) usb thumb drive, as the board has an on board usb socket, that seemed the most obvious route, so, the boot process was correctly carried out with keyboard and language selections, plus passwords etc, all looking very reassuring (also confirming the previous attempts had failed).
Whilst Rockstore “functioned”, performance could be related to a 1960’s 4 cylinder engine with Ignition lead problems, missing, backfiring with intermittent periods of running like a Swiss watch.
Decision time, what should be purchased (or adapted) to provide a reliable os drive. Failure of the Kingstone SA400S37/240G after 2 years (3 and a bit yrs less 12 mths or so downtime) is a bit disconcerting.
I do have a couple of 40Gb IDE 3.5 drives that could be utilised but possibly the introduction of an IDE to SART card just adds to possible problems 
(KISS comes to mind) and would they provide the performance and durability?
So, an upgrade on the A400 to a Kingston KC600 SSD SKC600/256G Internal SSD 2.5" SATA Rev 3.0, 3D TLC, XTS-AES 256-bit encryption was the decision.
Reinstallation went well, all required rockons implemented including the Web Service Directory for Windows which is a boon as linking the W11 laptop was increasingly frustrating as it was previously working fine.
Thanks to @anchit02 (not entirely sure how @anchit02’s post appeared on my diatribe but it gave me the idea of WSDfW.
(No doubt the forces of Kibble at play here).
The only problem left to provide a solution is getting the Samsung TV (QE50QN90AAT) to “see” Jellyfin, which is also increasingly frustrating as on the initial installation (2021 Dec) Jellyfin (the Jellyfin logo and all the libraries) popped up as a Source on the tv, later to change to a folder structure (no Jellyfin logo or libraries) but still viewable files, now it seems impossible to get any connection to Rockstor without serious coding within the Tizan OS.
Any ideas are most welcome.
Congrats for getting that all to work.
I can’t really test this, but inside jellyfin you have to have the DLNA plugin activated (somewhere in the settings?).
I saw this thread, where it seemed in recent jellyfin versions (May 2024) you had to explicitly bind to the local address of the jellyfin server in addition to the DLNA being active. Take a read here:
and maybe the posts above and below this (ignore the mention of MACVLAN networks, the Rockon uses the net=host option, so no need for that at this time, and it only means that when using a MACVLAN network, the jellyfin docker would get its own network address, independent of the one that Rockstor has. Whereas with the net=host option enabled on the docker container, it will have the same IP as Rockstor).
Maybe it will help or trigger some other thoughts on where the challenge might be
Hello @Mike-B , thanks for the tag.
Does this mean you got the Rockstor NAS to show up in the Network Section of your W11 laptop? I’m running the RockOn Web Service Directory for Windows installed and running but I still can’t get my Rockstor NAS to show up on the “Network” in W11.
What is WSDfW and did it help in solving the issue of W11 seeing the Rockstor NAS in Network?
Hello @anchit02
WSDfW is a simple Rockon
Oh yeah! I already have that Rock-On installed and running but still no luck in getting the Rockstor-NAS to show up on W11 for me. @Hooverdan and I tried to troubleshoot this issue for a while but and tried all sorts of settings with Windows services and firewall but still no joy; if you are interested, you can see our discussions on the other post here. I eventually gave up since I can still access the Rockstor_NAS using RUN and going to the NAS IP address.
I’m glad things worked out for you! Cheers
Ohh well hopefully it might help another windows victim 
Thanks @Hooverdan
Cant think how or why i missed the DLNA plugin, however, it is now fully functional and shows up on the TV source with all libraries selectable.
Thanks again
I had the same issue and found that restarting the WDDfetc Rockon helps.
