-
Posts
480 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by DivideBy0
-
Is this the first step toward a subscription based licensing model? Is this where UnRaid is heading? Or this is purely a security play?
-
This is a beast for my needs and I need to downsize as I have 2 more of these running next to it. What would a decent price for this entire setup be? And of course I don’t plan to recover my initial cost, there is always depreciation involved. I listed individual prices just for the purpose of reference. I run 5 OS’s on this plus UnRaid with about 40TB. It runs really smooth. PICS: The guy to the left: https://imgur.com/a/zeSlcce SPECS: Supermicro X11SPM-TF - $600 https://www.supermicro.com/en/products/motherboard/x11spm-tf CPU - Intel Confidential Xeon Gold 5218 ES QQ8M 16C/32T 2.1GHz LGA3647 125W - $200 DYNATRON B18 CASCADE LAKE XEON 1U CPU HEATSINK AND FAN, FCLGA 3647 NARROW ILM - $45 https://www.amazon.com/Dynatron-Blade-Server-Narrow-Cooler/dp/B07D7VJ6JV https://mitxpc.com/products/b18 NVME - Western Digital 2TB WD Blue SN550 NVMe Internal SSD - Gen3 - $195 https://www.amazon.com/Western-Digital-Blue-SN550-Internal/dp/B08K4NP5DQ SSD - SanDisk Ultra 3D NAND 2TB Internal SSD - $119 https://www.amazon.com/SanDisk-Ultra-NAND-Internal-SDSSDH3-2T00-G25/dp/B071KGS72Q?th=1 Memory - Micron 18ASF2G72PDZ-2G6H1R - 16G x 6 = 96GB - $400 https://www.amazon.com/Micron-MTA18ASF2G72PDZ-2G6H1R-16GB-DDR4-2666-RDIMM/dp/B073GBPBK2 MegaRAID SAS 9361-16i IT Mode - $500 https://www.newegg.com/lsi-05-25708-00-sas/p/1B4-013F-00014 SilverStone Technology 350 Watt Flex ATX Power Supply -$76 https://www.amazon.com/dp/B07QGMX5DW?psc=1&ref=ppx_yo2ov_dt_b_product_details Case 8 Bays - U-NAS NSC-810A - $219 https://pcpartpicker.com/b/Zmr6Mp https://caseend.com/data/u-nas/u-nas-nsc-810a
-
I tried EVERYTHING and I think I am pretty fluent with IT. Nothing worked and all my Ventura machines stoped working after 6.11.1 upgrade. Several posts here and reddit are calling the same issues. I wish UnRaid will put some focus on this issue and I understand we're the mercy of Apple here as they constantly changing their code.
-
Yes the TimeMachine not working is a deal killer for me but I am already invested in UnRaid, can't just switch. Really disappointing as I have around 7 Macs in my house. I switch back to an old MacMini with an external 8TB drive that I backup to UnRaid.
-
Docker Update Patch not installed - Fix Common Problems
DivideBy0 replied to DivideBy0's topic in General Support
Thank you Sir. That worked -
This CLI will work as well. docker exec -it nextcloud updater.phar
-
-
(SOLVED) Upgrade from 6.9.2 to 6.11.1 stuck at bzroot, now what?
DivideBy0 replied to DivideBy0's topic in General Support
Yeah I was about to let you guys know. Some dude on reddit just told me I tested and it work fine with 1.7a -
Since my upgrade to 6.11.1 my TimeMachine stoped working, completely for the Ventura OSX, and very unstable for the other OSX versions. I have 7 Macs in my house. I ended up resurrecting an old MacMini with a 10TB drive attached as TimeMachine share and got it all back in running. Really really disappointed with this whole affair as it worked rock solid before 6.11. I tried absolutely everything for months, and nothing worked. One of the main reason I moved to UnRaid is because the ability to use Time Machine. And to rub it in, FreeNAS works just fine with TimeMachine
-
I usually change the admin password and I and extra admin user as a backup just in case. But you can always reset the password if you have physical access to the mobo You're a fast learner
-
Team Work
-
It worked for me. Try to do it via the IPMI GUI which works as good as the command line.
-
Here is the 1.6 version. If you email SuperMicro support they will send it to you. A2SDi-4C-HLN4F.BIOS.1.6-A2SDICH1.zip
-
How do I setup my UnRaid as the NUT master. I change the UPS mode to net server but I can't change the IP from 127.0.0.1 to actually the IP of this UnRaid? I need this to be the master so I can have a client setup to this master.
-
Help : Parity check finding 88 errors. What to do?
DivideBy0 replied to publicENEMY's topic in General Support
@trurl Well the non-correcting check was finished and no errors found. That means I am good? The correcting check found and fixed 2 sync errors as per above post. Anything I need to worry about it? I am in process of replacing my UPS batteries so I should be covered for the next power hick up. -
Help : Parity check finding 88 errors. What to do?
DivideBy0 replied to publicENEMY's topic in General Support
Ok I will save the syslogs for correcting and none-correcting. I will do the full diagnostic as well just in case. So far is 100% into correcting parity check and I only have 2 errors as per below. Saved the syslog and diagnostic, rebooted and started a non-correcting parity check. Will keep you updated. From #dmesg I get this [104634.736525] md: recovery thread: P corrected, sector=4362239800 [119130.066796] md: recovery thread: P corrected, sector=6442670392 And from cat /var/log/syslog.1 I get this Jan 18 00:07:47 NAS-UNRAID-1 kernel: md: recovery thread: P corrected, sector=4362239800 Jan 18 04:09:23 NAS-UNRAID-1 kernel: md: recovery thread: P corrected, sector=6442670392 -
Help : Parity check finding 88 errors. What to do?
DivideBy0 replied to publicENEMY's topic in General Support
Well funny you say that. I think when my second power snag hit, the UnRaid was in middle of the automated parity check after the first power failure forced reboot. How is that into the mix now? Should I stop this correcting parity check and do a diagnostic first? Or let this one finish, do a non-correcting one after and if I don't have any more errors then I am good to go? I hate when this happens and you think your UPC will cover your butt -
Help : Parity check finding 88 errors. What to do?
DivideBy0 replied to publicENEMY's topic in General Support
So I am in a similar situation with the OP. My power went off 2 or 3 times yesterday and I learned the hard way that my UPS batteries are kaput, done. I am getting new batteries as we speak. Because of that my UnRaid kept bouncing with dirty shutdowns and it came back with an automated parity check. It was about 40% done and I noticed 2 errors I think sync and is perhaps due to the unclean shutdowns. U stooped the parity check and manually start another one with "Write corrections to parity" enabled. That's the right procedure, correct? Anything else I should do? I hope there won't be many errors, but who knows. Otherwise the disks are healthy and no other damage that I can see in logs from these hard / unclean reboots. -
I've been fighting this issue since my upgrade from 6.9.2 to 6.11.1. My Ventura OSX stoped backing up to my TimeMachine share. I tried absolutely EVERYTHING on this earth available here on this forum or reddit, but no luck. Even tried the TimeMachine docker and still no luck. It works for a while and then it stops working. I even redone may backups from scratch several times, even moved my TimeMachine to a second UnRaid, but I have with the same disappointing results. All other Mac versions work fine except the Ventura OSX. I am so pissed off with the amount of time I've spent on this. Absolutely ridiculous I am officially giving up on UnRaid to backup my 8 Macs and moving back to my Mac Mini with a thunderbolt enclosure and raid. s just reliable and it works.
-
And b00m goes to dynamite
-
Despite my "System Data" share setup as Prefer : Cache for some reason when the dockers starts, the docker.img always ends up on the array disk 2 rather than the cache / pool ssd drive. I have 2 perfectly identical UnRaid boxes and one works and the other doesn't. How do I prevent the docker.img to start and stay on the array drive? I tried everything, stop dockers, kick off mover, done a full parity check, you name it. No matter what I do it just stays on the array disk
-
Time Machine backups failing 6.10 rc8 "Failed to attach using DiskImages2"
DivideBy0 commented on wgstarks's report in Prereleases
I am absolutely HATING this TimeMachine issue since my upgrade to 6.11.1 ABSOLUTELY HATE IT I got it to work for a while and now it stoped again. I deleted my entire backup and redo another one, it worked for few days and now stoped again. I NEVER EVER had these issues in 6.9.2 and I am seriously contemplating to going back to 6.9.2 just for this major issue. This is what I get on my client side, MacBook 16 running Ventura 13.1 eXile:~ root# log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999 2022-12-27 22:26:18al] Starting manual backup 2022-12-27 22:26:18ing] Rejecting candidate mount point: /Volumes/TimeMachine, not owned by root 2022-12-27 22:26:18ing] Attempting to mount 'smb://exile@NAS-UNRAID-1._smb._tcp.local/TimeMachine' 2022-12-27 22:26:21al] Initial network volume options for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 0, QoS: 0x0, attributes: 0x1C} 2022-12-27 22:26:21al] Configured network volume options for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-12-27 22:26:21ing] Mounted 'smb://exile@NAS-UNRAID-1._smb._tcp.local/TimeMachine' at '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine' (34.87 TB of 40 TB available) 2022-12-27 22:26:22al] Skipping periodic backup verification: not needed for an APFS sparsebundle 2022-12-27 22:26:23al] 'eXiled.sparsebundle' does not need resizing - current logical size is 38 TB (37,997,448,629,248 bytes), size limit is 38 TB (37,997,448,629,657 bytes) 2022-12-27 22:26:23al] Mountpoint '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine' is still valid 2022-12-27 22:26:23al] Checking for runtime corruption on '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine/eXiled.sparsebundle' 2022-12-27 22:27:06ight] Waiting for Spotlight to finish indexing '/Volumes/Backups of eXiled' 2022-12-27 22:27:10mages] Failed to attach using DiskImages2 to url '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine/eXiled.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-12-27 22:27:10al] Failed to unmount '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine', Disk Management error: { 2022-12-27 22:27:10al] Failed to unmount '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-12-27 22:27:10al] Waiting 60 seconds and trying again. 2022-12-27 22:27:10llation] Cancelling backup because volume '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine' was unmounted. 2022-12-27 22:27:10llation] Requested backup cancellation or termination 2022-12-27 22:27:11llation] Backup cancelled (22: BACKUP_CANCELED) 2022-12-27 22:27:11al] Failed to unmount '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine', Disk Management error: { 2022-12-27 22:27:11al] Failed to unmount '/Volumes/.timemachine/NAS-UNRAID-1._smb._tcp.local/33BC8F3D-CD01-4C98-813F-A6F208765B20/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-12-27 22:27:11llation] Cleared pending cancellation request eXile:~ root# -
(SOLVED) Unraid cache drive - single drive ok?
DivideBy0 replied to DivideBy0's topic in General Support
Never mind, I actually had an extra SATA port and added the 4TB as an extra cache pool, so nothing to undo or redo