So I ran the upgrade Adsk upgrade script from Rocky 9.5 to 9.7 last night and it has really caused a bunch of headaches.
Had to jump through a few new hoops to get zfs up and running, but I’m still unable to mount a cifs network mount (eventually through fstab).
The command I’ve been using for many years no longer works and no matter what I try I can’t seem to get Rocky 9.7 to mount a cifs mount.
Anyone have any tricks? #missing95
David
I’ve setup a few systems with 9.7 recently and all are running CIFS/SMB.
Not sure which commands you are using, so can’t comment on the specifics.
Usually it just requires the installation of cifs-utils via dnf install.
Then adding the mount to /etc/fstab
//ipaddress/volume /mountdir cifs credentials=credenetialsfile,vers=3.0,uid=1000,gid=1000,file_mode=0660,dir_mode=0770,nofail 0 0
Some of these are of course user preference. I use a credentials file for the password.
Need to remember to set the credentials file to 600 or it will be ignored.
And after you edit fstab you need to run systemctl daemon-reload for everyone to see the changes.
That should do it. Including on 9.7
Thanks Jan.
I’ve got CIFS installed but can’t seem to get 9.7 to admit that! It keeps telling me it’s an unknown file system. My current mount line worked just fine in 9.5 fstab…
I also had issues installing zfs though. Something about how 9.7 handles things through dkms now? It’s all way above my pay grade. Seems like 9.7 just breaks stuff for me
I suspect that this has less to do with 9.7 and more with the update script.
My installs were fresh 9.7 installs.
I’ve only once attempted the update script, and it left my system in a state where it wouldn’t even boot and was unrecoverable.
I believe the update script is a good path if you made limited changes from the original ADSK ISO. But once you install all kinds of other things, the update script seems to do more harm than good. I say this with limited data points.
The only part of the system that requires DKMS that I know off is the BMD driver when you install it. It’s not needed for cifs.
Ever since my upgrade meltdown, I tend to hang on a Rocky release for as long as I can, and then start fresh. Which is of course hard, because you need to have a point of downtime that supports that. And copious notes of all the things you did over the months to refine your system to your needs.
And this is in no way an indictment of the update script. It works for what it was designed for. But many of us do use these system in other ways and customize them. ADSK doesn’t have responsibility for that, and it would be infinitely harder to write a script that accounts for all of that.