I really like the work you are putting into Rockstor. Its steadily improving. For me it has been rock solid stable for the last many releases. I only see small usability bugs, but the basic job of a NAS is being done very reliably.
The new disk naming setup seems to work well, and if it prevents problems, its even better.
Only complaint is that the disk names get very long, like “ata-SAMSUNG_HD154UI_S1XWJ9BZA03197”, which as a result makes the disk activity dashboard look a little crowded:
You cant possibly read which disk is doing what
Mostly a cosmetic thing, but should be fixed.
I see philxnet noted it too in the pull request
Yup, it’s in works. Thanks for your kind words @KarstenV!
Rockstor 3.8-14.03 is now available! Like the previous two updates in this new cycle, this is also a big one. @Flyer has contributed a pincard based password recovery system for users including root(with a bit of extra security). The system is pretty interesting to me and something security conscious users may like a lot! The UI side of it has the signature @Flyer snappy-ness which is pretty cool.
I made the samba service independent of rockstor-bootstrap which was giving grief to some users and proved hard to debug. I’ve also enhanced a few other samba related stuff. Enjoy the update and please post your feedback!
it seems I had a particularly sloppy day and did not test enough on the last update. My samba improvements did more harm than good. Mea culpa.
On the bright side, it’s great that you quickly caught the regression and @phillxnet even prepared a partial fix. I’ve tested them, added one more commit and we are good… for now… I think…
Thanks a lot. Samba seems to work again on my system.
I dont thin k its a question of being sloppy. We are on the testing channel, and things like this will happen.
I see you have added system time to the web ui. Sadly on my system it shows “System Time: 15:45 (-0500 CDT)”, where it is really 22:45 (CET) where I live.
Where do I set it up to show the correct time? Sorry if I missed some instructions, but cant seem to find where to set it up.
Future plans: add some funcs to allow rockstor users manage system date/time and other little things
3.8-14.05 is out now! and we are breaking the trend of pushing major updates temporarily. @Flyer has fixed a couple of issues quicker than anyone else could get to. Enjoy!
Meanwhile, an inline news update : Rockstor at position 72 on Distrowatch , we are on fire!
There’s no stopping @Flyer! I just merged his shellinabox feature that gives terminal access to your Rockstor system, securely from the UI. This is very useful for a client-platform independent CLI, especially for those that are not Linux heads like the rest of us here. Also, this makes it easy to help users troubleshoot in many cases. Grazie!
I’ve also fixed a Rock-on related issue(hi there @henfri) . Now there’s a script
/opt/rockstor/bin/delete-rockon to delete a Rock-on, its metadata, containers and images. This is useful for more advanced users who may like to start fresh on a Rock-on they are tinkering with. Now you can use @Flyer’s shellinabox feature to run this script and others from the UI.
Yeah, so 3.8-14.06 is now available! There’s a deployment related bug due to which you may see an error while accessing shellinabox. Just restart the rockstor-pre service with
systemctl restart rockstor-pre or reboot the machine to get around it. We’ll fix it up in the next update. Other than that, this is a great update. Enjoy!
My rockstor is telling me there is a 3.8-14.08 update.
But no news has been posted here.
Is it safe to push update?
Probably @suman working on latest adds and just missing annoucement, so go on
Yup, just about to post.
Hello everyone! and @KarstenV
3.8-14.08 is now available. I’ve merged two pull requests in this update, both are nice enhancements to the e-mail notification setup and both are contributed by @Flyer. Thank you!
Howdy Rockstors! 3.8-14.09 is now available. This is a special update as we have a new contributor @grebnek, bringing our contributor count to 18! I’d like to highlight that @grebnek reported an issue in this post and went ahead to fix it with his pr. Thank you!
I’ve also merged another pr from @Flyer who promptly fixed a regression that slipped in the last update.