I am very slow with upgrading my TrueNAS Core 13.0-U6.8. I have a very basic NAS system with 4 users + root and I don’t have any jails or plug-ins. The only thing that is running that’s not “out-of-the-box” is a cron job running JoeSchmuck’s Multi-Report (and the scripts are in my pool). Should the cron-job and scripts be removed before I perform the upgrade of my NAS from Core 13 to Scale 24?
Since SCALE 24 is at least two major releases out of date, I wouldn’t recommend updating to it at all. The current recommended release for “general” use is 25.10.1.
I think the OP is just going by the Documentation for migrating from Core to Scale. It mentions version 24.
I think it mentioned not to bypass the upgrade to 24.04. The plan was upgrade to 24.04 then move forward to the latest. What I asked about is still in question.
@joeschmuck any advice on your script and upgrading from Core to Scale?
Thanks for flagging me.
The scripts are the same, however there is a few small thing that must change.
The most important: The CRON Job command line is different:
If your CORE command line is: /mnt/pool/scripts/multi_report.sh
then you new command line would be cd /mnt/pool/scripts && /.multi_report.sh
Due to new security rules, we not have to cd into the directory where the script is located, then open a shell && and run the script. You still need to be root.
While you should not need to do this, after migrating to SCALE, I’d open up the ./multi_rpeort.sh -config` and go into “Advanced” then “Write” and exit. This will update your config file.
If you find out you are not getting an email report, there are two things you can try, and I say try because I don’t know what your config file looks like after any changes you may have made.
At the bottom of the config file is truenas_sendmail_support="No" and if it doesn’t say “No”, then it must be changed to “No”.
If you still are having problems, send me a message here on the forum and attach your multi_report_config.txt file, I can then look at it and make any changes.
OR, you could just delete the config file and generate a new one using the -config switch.
Hope this helps.
1 Like
TrueNAS users wanting to migrate from the latest FreeBSD-based 13.0 or 13.3 CORE release to the Linux-based TrueNAS version 24.10 or later can migrate to 24.04 and earlier using the UI update process, but must clean install if migrating to later releases. Attempting to migrate directly to 24.10 or later using the UI is not supported.
Meaning that if you want to click update in the UI, you need to go to 24.04 because that is the last version validated for a direct update, and then sequentially update to something more current. Otherwise you can use an .iso to fresh install 25.10 and import your CORE config file.
2 Likes
Thanks Joe for this detailed help. I’m currently backing up all my data, 12TB of it, and will attempt a 24.04 update as indicated below. I’ve copied my Multi-Report and the config to an external drive and will probably have questions after the upgrade.
Thanks again.
Thanks @DjP-iX,
You have mensioned,
What does “sequentially update” mean. Do I have to update 24.04 to each of the version until I have caught up to current? Or can I move from 24.04 directly to 25.10.2.1.
If you look at TrueNAS Software Status | TrueNAS Documentation Hub, you can see the recommended upgrade paths. Generally we recommend upgrading from the last maintenance release of each major version to the next. So you’d want to go from 24.04.2.5 > 24.10.2.4 > 25.04.2.6 > 25.10.2.1.
Excellent link. Clearly shows the upgrade path. Will try as soon as my next thread gets answered.
Thanks for the help,
Rick
The requirements are the same between CORE and SCALE, however TrueNAS 24.x threw a wrench into the Email and CRON TAB, both of which I pointed out earlier. But if you do have any questions, please do ask. I will be out of town all of next week, driving, yuk. Visiting the daughter. I will have my laptop so I will check in.
-Cheers
Well I’ve upgraded to TrueNAS Scale 24.04 and it seems fine. The Multi-Report cron job appears to work OK without modifying anything except for an error that I get in a second Email after the Multi-Report output Email. The second Email says:
cp: cannot stat ‘7zzs’: No such file or directory
ln: failed to create symbolic link ‘/usr/local/bin/7z’: Read-only file system
I tried modifying the command as indicated above but then the entire job fails. Leaving the command as it was in TrueNAS Core 13 will run the job and I get the Email with the Multi-Report output only with a second Email with the error (above). Is that error part of the configuration of Multi-Report? Maybe I should embark on updating the Multi-Report version and re-configuring it.
@Macaroni323 what version of Multi-Report are you using? I ask because Multi-Report has not used this file in quite some time. I suspect you are running an older version, possibly a single script version as well. Multi-Report has been broken down into a few more manageable pieces, so two main scripts (Multi-Report and Drive-Selftest) and we also have (Sendemail.py) for sending emails once you go above the version of TrueNAS 24.04 as email support got hardened, and you have the (SMR check) script as well.
I recommend that if you have a heavily modified (by you) config file, backup the multi_report_config.txt file.
Then run: ./multi_report.sh -update
Once that is done, run ./multi_report.sh -update_all and answer yes to update every smaller script section, you do not have to answer yes to the first question of to grab a new copy of Multi-Report, since you already have it.
Or you can grab a copy off of GitHub and manually install it.
Thanks @joeschmuck ,
The upgrade appears to be functioning just fine. I opted for the removal of all multi_report files and I’ve downloaded the latest multi_report (v3.28) and drive_selftest (v1.07). I had disabled my cron job first and ran the multi_report config. That seemed to work OK and then I ran multi_report which gave me the report but there are two problems that showed up also.
./multi_report.sh: line 1530: lsscsi: command not found
./multi_report.sh: line 1452: lsscsi: command not found
These two errors come in a separate Email from the report.
My report apears the same as the old one but now it’s flagging max drive temps (51 deg C) as critical. I think these occured before I installed the drive in the server case. I think I will do an advanced config and set the specfic drives max temp so that it doesn’t show critical. I will need to pay attention to my drive burn-in case and limit the drive’s temperature (that’s where my drives get too warm). I probably have to clean the air intakes on my server also. 
- You need to ensure you are running as
root, this is the main cause for a command not found. - Also, for the CRON command line, it should be: Command (SCALE):
cd/mnt/pool/scripts && ./multi_report.shwherepoolis the location of your script. This is in the Quick Start guide. It should be on your system in the user manual, which gets downloaded when you do an update.
Sorry it took so long to reply, having WiFi router issues.
Might have found my issue with “lsscsi - command not found”. Acording to Google lsscsi command won’t work until TrueNAS v24.10 and I’m on 24.04 (having just upgraded from 13.0).
The cron-job is run under root user, and the manual testing of multi_report was performed under root user.
Thanks @joeschmuck ,
Looks like stability has been reached on Multi-Report. I see there was an update today (I’ll need to figure out how to do this). The upgrade to 24.10 has removed the errors (and also rebuilding the config file from the website may have had something to do with it… Not sure). I ran the cron job manually and it ran fine with no errors this morning. Now I am moving on to replacement of the one hard drive (expanding that mirror from 4TB to 8TB).
Again, Thanks for your help.
This is easy, run for the CLI, as root, the command ./multi_report.sh -update_all and you will be presented with your current version and the version on GitHub. Answer y to accept the update, anything else is a No. In this case, you would answer yes to the Multi-Report and Drive-Selftest, those are the only two files updated.
You could also update each individual file as well.
If you run ./multi_report.sh -h or -help then you will get the Help Screen. It provides the switches you can use.
Thanks @joeschmuck the update worked cleanly. A manually run cron-job has also worked cleanly.
This is “maintenance month” on the server and I’m trying to catch up on all my server to-dos. I have replaced the oldest drive which showed up with a CRC error on Multi-Report (I’ll scan it outside the server to see if it passes all the WD tests, it’s a WD RED Plus 4TB). I’m being bold and replacing the 4TB drive with an 8TB (it’s currently resilvering). When that’s done I’ll replace the other drive of that mirror with a second 8TB drive and allow it to resilver and then I’ll expand the mirror which if I do it correctly will add another 4TB of storage to my pool. I will remain on TrueNAS v24.10 for a week or so just to let the dust settle and let my “expansion project” finish. I’ve also re-setup my SMART tests so they’ll occur right before my Multi-Report reading.
Quick question… Does Multi-Report do any SMART tests itself? I was noticing test with a percentage left to run (this was in the test just now but my SMART tests weren’t rearranged until just before I updated Multi-Report so they may have been running due to the old SMART configs).