RobertP
Members
-
Joined
-
Last visited
-
WOPR - UR1: 126TB on my backup server (holds backups of multiple family systems), 11 data disks, 2 parity drives. using 75TB (at peak backup time) Xeon E3-1230 [email protected] memory. (Yes, some drives bays are not plugged in the picture. Some are empty, some contain pre-cleared empty drives that I can plug in on a failure or emergency.) WSPR - UR2: 18TB on my file server (holds shared files between family's systems), 3 data disks, 2 parity (overkill on parity!). Only using 4TB at present. i7 11th gen 32gb memory
-
Odd – on one system, Tools/Update Assistant reported no issues. I did the upgrade (a couple days ago) to 7.0.0 with no issues. Controlrd works fine. i7 11th gen 32gb memory. 3 drives plus 2 parity (5 total) for 18TB. Other system, a few days later (today), ran Update Assistant and it warned about Unbalanced and ControlRD. I de-installed both, did the upgrade (and rebooted of course) and reinstalled both, and they work fine. Xeon E3-1230 [email protected] memory. 9 drives plus 2 parity (11 total) for 126TB. Both running UnRAID OS Pro.
-
What if I have NO certs on my unRAID? Will I now need to set up a CERT? I've never done CERTIFICATES on home system, would not even know where to begin, what is process, is there a cost, etc, etc, etc. Can I continue to use the new version withOUT a cert? (And what is the value of having a cert?)
-
Working good for me also. Thanks for the fast fix. Bob
-
I understand, no rush. Don't kill yourself by debugging all day . . . lol ! I'll just keep ignoring the msg until you get a fix posted. Bob
-
See attached diag from both servers. Thanks, Bob ur2-wspr-diagnostics-20240428-0953.zip ur1-wopr-diagnostics-20240428-0954.zip
-
More on the error: I have no dockers running and I have no VMs running. My disk timeout is set to 90, same as it always has been. I did have Dynamix's Directory Cache plugin, which Fix-Common-Problems just reported is not compatible w newest unRAID. I de-installed the Directory cache, and have rebooted twice, but the error remains. Attached are my "syslog-previous" files. UR1-wopr-syslog-previous-2024-04-28 unclean shutdown.txt UR2-wspr-syslog-previous-2024-04-28 unclean shutdown.txt
-
Following the most recent update of Parity Check Tuning (2024.04.27), I'm now receiving an "Unclean shutdown detected". Doesn't matter if I do a shut-down or a reboot - the msg shows up the next time I log in. Happening on both my unRAID servers. If it matters - my Parity Checks run monthly on the evening of the 1st of the month - so I have NOT run a parity check since the update. Also rcving msgs that SAYS it kicked in an "Non-Correcting Parity Check" (zero errors), but I have not seen it actually running whenever I've looked. My larger system Parity check usually takes a couple days (16TB), but this "Non-Correcting" check only took 2.5 hrs!? The smaller system parity check usually takes 16 hrs and that matches the time for that system's "Non-Correcting" check.
-
I appreciate the new process, but I think you forgot about (or haven't gotten around to it) an item I suggested a while back (Limetech "liked" the post). I'd still like to see this added to the update process. Here's a copy of my post from July 3, 2023: It is so easy to forget to manually make a backup of a flash drive prior to an OS UPDATE. Granted, with the RESTORE button, one often does not need to use the manual FLASH BACKUP, but it is still a wise thing to do. For example, I had issues with the most recent backup, and the RESTORE option did not work. I ended up having to reformat the flash drive and used the FLASH BACKUP to get back up and running. To assist us, can you either: 1) Add an (optional) flash-drive backup to the UPDATE OS process OR 2) At least add a prompt to the UPDATE OS process – something like: “If you do not have a recent flash drive backup, we suggest you cancel this update and do a flash drive backup (click MAIN tab, the click FLASH, then click FLASH BACKUP and save the ZIP file to your PC). Once complete, begin the UPDATE OS again. CANCEL update CONTINUE update (I need to do a FLASH backup) (I already have a recent FLASH backup) BTW – in the FLASH BACKUP, it would be nice if you included the version in the filename. For example: ur1-wopr-flash-backup-20230703-0052-ver6_12_2.zip
-
Am I confused/mis-understanding something? Am I thinking of a different field? Or is this a bug? (Actually, even if I’m confused, I feel there IS a bug here.) THE ISSUE: MINIMUM FREE SPACE for a share unRAID 6.12.3 Drives in share formatted with xfs HISTORY I used a 3rd party backup program to back up my home PCs. I have the backup program (Macrium Reflect) write the backup files to a share on my unRAID server. YEARS AGO, I had the backup program write each backup as one big file. This caused issues – if unRAID started to write to drive 1 of the share, and that drive only had 1TB free, and the backup file ended up being 1.5TB, the backup would fail due to running out of free disk space on that drive since the one big file could not straddle two physical drives (even if both drives are in one share). I WAS TOLD to do two things: 1) Tell my backup software: Write the backups out in “chunks” (CHUNK is my word for it, that’s not the technical term!). I chose 250GB (yea, I played it overly conservative, bigger chunks would probably be easier to keep track of!). 2) Tell unRAID: Use the MINIMUM FREE SPACE field to tell unRAID to NOT write to a disk within a share if that disk has less than xxGB free – instead pick another disk in the share to write to. This way, no matter what unRAID allocation method was used (high-water, most-free, fill-up) and no matter what the disk size, unRAID would not try to put what MIGHT be a huge file onto an almost full drive. I think I did 500GB (or was it 1TB? Either way, I gave myself extra “elbow room” over-and-above the “chunk size” of 250GB) This worked great for years. THE PROBLEM DETAIL: I recently upgraded to unRAID 6.12.3. Not sure if this issue started with this version or an earlier version. Since the backups have been working OK, I have not looked at that share definition in a long time. I just now looked at the share definition that holds my backups. The MINIMUM FREE SPACE field now has a percentage, not an absolute number. I tried changing it back to a number: 500GB. I hit enter, and it changes that number to 500000000 (a.k.a. 500,000,000), just like it used to. But then it changes it to a percentage!?!? And the percentage does not make sense (to me). This share is made up of 4 physical drives: 12TB (currently 1.3TB free) 12TB (currently 2.6TB free) 6TB (currently 2.81TB free) 16TB (currently 15.2TB free) I put 500GB (or 500 GB) in the MINIMUM FREE SPACE field, and unRAID eventually turns it into 25.6% I don’t see ANY situation using ANY of those numbers above (max individual size, total size, free size) where 25.6% equals 500 GB!?!? If I put in 1000GB (also tried 1tb or 1TB or 1 tb or 1 TB), it expands the number to 1000000000, but then it changes it to 51.2%!?!?!? So is that saying if the entire share is more than half full, a file will not be written? Or if an individual drive is more than half full, a file won’t be written to that drive? That makes no sense at all – 1TB does NOT equal 51.2%!?!? Is this simply a formatting error of how that field is displayed? How can I be sure what the actual value is? Or is unRAID actually doing a bad calculation? FYI - In the attached diagnostics, the share that I'm working with is named: UR-BU-i9 BUT I tried some other shares and they are also showing a similar issue - MINIMUM FREE SPACE is being converted to a weird percentage. ur1-wopr-diagnostics-20230717-2002.zip
-
BTW - in case you have not already done this: Another important thing I found out about using Macrium to put backup's to unRAID - make sure you specify file size maximum! In My Macrium backup definition files, I went into ADVANCED OPTIONS, FILE SIZE, and put a FIXED FILE SIZE of 250GB. This saves the backup file as several files in 250GB chunks instead of one huge single whopping big file (the filenames are numbered, it is easy to see which file goes with which set). If you just do one big file, there is a risk it might fill up one disk and abend instead of putting part on one disk and then jumping to another disk in the share for the other part(s). Then, on the unRAID share, in the MINIMUM FREE SPACE, I put 500 GB. At least I think that's what I put, it was either that or 1000GB (to give myself some "elbow room"). Unfortunately, the most recent unRAID upgrade changed this value to a percentage (for example: 30% instead of xxxGB)! I tried changing it back to the absolute GB value, but it keeps reverting back to a BIG percentage! I'll be posting to the developers to see if there's a way to keep the setting at GB). In case you want to follow it, my report of this MINIMUM FREE SPACE bogus percentage issue has been posted. The subject is: MINIMUM FREE SPACE CHANGES TO A (BOGUS(?)) PERCENTAGE
-
Not sure if I'm understanding the issue, but I've been using Macrium to backup one unRAID server to another unRAID server for quite a while. Yes, I realize there are unRAID backup tools that would backup from one unRAID to another (and would cut out the middle-man - my Windows PC), but I prefer to use the same backup tool for all my backups (Macrium Reflect). I have a share on my unRAID: UR2-i9 In that share I have a folder: winGprog On my Win11 PC, I have a map: G: (\\UR2-WSPR\UR2-i9) In Macrium, I ADD SOURCE FOLDERS: \\UR2-WSPR\UR2-i9\ For my destination (a 2nd unRAID server): \\Ur1-wopr\UR-BU-UR2-WSPR-SELECT\UR-BU-i9-G-i9unique\ And on that 2nd unRAID, I have a share: UR-BU-UR2-WSPR-SELECT under that share I have a folder of: UR-BU-i9-G-i9unique Note that I don't actually use the drive G: mapping in Macrium, I use the UNC names. Also note that it becomes a FILE & FOLDER backup, NOT an IMAGE backup. A but slower, but it still works. This is because the Windows PC does not "own" the unRAID share, so it can't trust the file flags on the unRAID since it has no control over those flags (or so I assume) - so it has to scan/compare the files to see what has changed as part of the actual backup. Macrium backs it up with ALMOST no issue. The only issue I've run into, Macrium apparently has a maximum number of file/folder items it can "keep track of" - if I try to back up my entire drive F: (on same unRAID server, set up similar to above, but has MUCH more data), Macrium fails. So what I had to do was set up 4 backups of F: that ONLY grabbed certain root folders (and below folders). And then on the 5th F: backup, I select all folders EXCEPT for the previous 4. (Again, I used the UNC names in Macrium, not the F: map letter.) Unfortunately I do not know the "breaking point" - it was a matter of a trail and error. Originally I only had to do two chunks, but as I added more and more stuff, I've had to break it up to where I now have 5 chunks (5 different backups for the drive F: share).
-
Thank you JorgeB!
-
On the DASHBOARD tab, can you give us control over the columns that appear in the SHARES tile? In particular, I would like to see the PROTECTION STATUS ICONS in the SHARES tile on the DASHBOARD tab. But I suspect others might like to be able to turn on/off other columns in that tile. On the MAIN tab, can you include the SMART icons for each drive (like it appears in the ARRAY tile on the DASHBOARD)? Thanks, Bob
-
It is so easy to forget to manually make a backup of a flash drive prior to an OS UPDATE. Granted, with the RESTORE button, one often does not need to use the manual FLASH BACKUP, but it is still a wise thing to do. For example, I had issues with the most recent backup, and the RESTORE option did not work. I ended up having to reformat the flash drive and used the FLASH BACKUP to get back up and running. To assist us, can you either: 1) Add an (optional) flash-drive backup to the UPDATE OS process OR 2) At least add a prompt to the UPDATE OS process – something like: “If you do not have a recent flash drive backup, we suggest you cancel this update and do a flash drive backup (click MAIN tab, the click FLASH, then click FLASH BACKUP and save the ZIP file to your PC). Once complete, begin the UPDATE OS again. CANCEL update CONTINUE update (I need to do a FLASH backup) (I already have a recent FLASH backup) BTW – in the FLASH BACKUP, it would be nice if you included the version in the filename. For example: ur1-wopr-flash-backup-20230703-0052-ver6_12_2.zip Thanks, Bob
