DivideBy0

So I still have appdata and system folders on the cache drive. The appdata have some empty folders which I think is ok but the system folder I still have libvirt.img in the /mnt/cache/system/libvirt folder. Mover didn't move that. Should I still proceed with stoping array and unasign the old cache drive to make room for the new cache drive? I don't wanna scare this simple hardware swap up LOL

I have a 4TB SSD single drive I want to use for cache. Can I use one drive only for cache? And if yes what is the procedures to replace my existing 2 x 500GB with the single 4TB SSD ? Thanks in advance

I feel the same way I usually allow 6-12 months for all the bugs to iron out and beta test to continue

Yeap that's the link I used

Any file integrity checks during transfer? Making sure nothing gets corrupted?

This is my home spare cold standby, never used in production, still in the original box, unsealed as I had to make sure it works and not DOA. Purchased 3 months ago from UI so still under warranty.I will throw a 5TB in there. I prefer a local pickup at Houston / 77002 but I will ship as well. $350 + Shipping & Insurance via PayPal

Runs Unraid 6.11.5 - Priced to sell $750 + shipping. PayPal or local pickup in Houston / 77002 I would prefer a local pickup and would also consider discount for local pickup. I'm willing to ship as well but shipping cost will be extra depending on your zip code. Thanks for your time and consideration. Pictures: https://imgur.com/a/n6srqZC Case - SUPERMICRO CSE-721TQ-250B Black Mini-Tower Server Case with 250W Flex ATX Multi-output Bronze Power Supply - 4 HD Bays https://www.supermicro.com/en/products/chassis/tower/721/SC721TQ-250B - Supermicro MBD-X11SCV-Q-O - Mini-ITX Motherboard https://www.supermicro.com/en/products/motherboard/X11SCV-Q - CPUs x Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz - 6 Cores / 12 Threads with vPRO-Support for Remote Access (similar with IPMI) - Heatsink: Supermicro - SNK-P0073A4 - 1u Enhanced Performance Active Cpu Hs For Socket H Series - Memory - 64GB Hynix - 2 X 32GB 260-Pin DDR4 SO-DIMM DDR4 2666 - 2 x SanDisk 1TB drives (used for cache and OS)

I won't bite. It took me a while to upgrade from 6.9.2 to 6.11.1 and that didn't go very well, as I had to redo and fight a lot of problems. I guess see you at 6.12.X branch

I had the same issue with a Suprmicro mobo and downgrading bios was also the solution. Strange. The mobo will boot just fine with many Linux distort including Ubuntu 22 but UnRaid no go.

Agreed and the QA is lacking at best. I will be holding off to any other upgrades. My 6.9.2 to 6.11.1 was a bit shaky and it broke some stuff. I will let you guys jump in front of it and test and iron all the bugs for me

Glad it worked. It took a lot of trial and error on my end but it was worth. Lest hope the next major upgrade don't break it I have like 6 or 7 Mac's backing up. Just as an FYI I did a full restore in 2 machines make sure the backups are reliable And they were reliable

cp /etc/samba/smb-fruit.conf /boot/config Edit your /boot/config/smb-fruit.conf and make sure you only have these 6 lines: # global parameters are defined in /etc/samba/smb.conf # current per-share Unraid OS defaults fruit:metadata = stream vfs objects = catia fruit streams_xattr fruit:encoding = native fruit:posix_rename = yes samba restart

I will make a separate post but I got to the bottom of my Time Machine issues with 6.11.1. And I have all flavors of MacOS backing up properly but I had to redo everything and start all backups from scratch. The trick is to do one by one, not all at the same time. I am backing up 6 different Macs to the same file share. Edit your /boot/config/smb-fruit.conf and make sure you only have these 6 lines: # global parameters are defined in /etc/samba/smb.conf # current per-share Unraid OS defaults fruit:metadata = stream vfs objects = catia fruit streams_xattr fruit:encoding = native fruit:posix_rename = yes

Battery on the UPS, yes that could be one issue, perhaps will cause a sudden shutdown without giving the UnRaid time to shutdown graciously. Good call on that and I will check them as soon as this parity check is over. I like the 30 seconds rule, might as well go for it. Really appreciated it mate...

I have 2 identical UnRaid boxes, everything the same including the UPS's, the UnRaid version, the settings, everything. I had a power failure yesterday for like 1 hour but one of the UnRaids didn't behave as expected. When power came back that UnRaid booted and started a parity check which tells me it didn't shutdown clean as the UPS should do it. The other UnRaid did shutdown properly as per the UPS settings. What am I missing here? See my diagnostic file. nas-unraid-2-diagnostics-20221104-1410.zip

DONE

I get the same thing? "Unable to get Volume" Any idea?

Is this still an issue? I am in 6.11.1 and I got this stale issue twice, with Safari and Firefox. What's going one here? Reboot fixed the problem. I got it when I stopped the array to make some changes and had to restart the array.

Well the question is where exactly do I add this line? What file do I need to edit?

Crap, I am in the same situation, deleted everything and still don;t work. I need to add this line and see if it makes a diference fruit:metadata = stream

Yeah 24 hours later and I am still fighting the same issue. My new M1 16" Macbook Pro finished its backup in one shot over wireless, 800GB, but I have other 4 Macs that are constantly getting disconnected from the Time Machine share during the backup. Something is very wrong and inconsistent here and I have no idea how and where to start troubleshooting it

Yeah is 6.11.1 I booted back on 6.9.2 and did a full 400Gb backup on the same MacBook with ZERO issues. I am absolutely annoyed when things don't work

After upgrading from 6.9.2 to 6.11.1 my entire Time Machine setup got majorly screwed up. I have 6 Macs backing up to this time machine share and outta of all 6 only the Sierra one continue to work under 6.11.1 All other 5 stopped working. I even started with a brand new Time Machine share from scratch, it works somehow, but all machines at some point during the backup they just get disconnected. Tried different settings on the share as well. am 1000% is not the network as I plugged one of my macbooks next to the UnRaid port, so I know that is switch rock solid. It is something in 6.11.1 like Samba or other settings that could screw this up? Anyone else with this sort of issues or is just me? I am super irritated as I have to put in so much work and get this back and running. I should've stay with 6.9.2

This is all over the places. I just deleted and created some shares and now I get this in my syslog root@NAS-UNRAID-1:/mnt/user# tail -f /var/log/syslog Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: Samba name server NAS-UNRAID-1 is now a local master browser for workgroup CHILA on subnet 172.17.0.1 Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: ***** Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: [2022/10/25 14:47:31.647226, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: ***** Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: Samba name server NAS-UNRAID-1 is now a local master browser for workgroup CHILA on subnet 192.168.122.1 Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: Oct 25 14:47:31 NAS-UNRAID-1 nmbd[32514]: *****

I am fighting some Time Machine issues since the upgrade to 6.11.1 As I configure a new Time Machine shares I get this in Syslog and 192.168.122.1 is not this UnRaid's IP. My IP is actually 192.168.0.12 What's going on here and why on the wrong subnet? root@NAS-UNRAID-1:/mnt/user/TimeMachine# tail -f /var/log/syslog Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: ***** Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: [2022/10/25 14:06:18.173906, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: ***** Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: Samba name server NAS-UNRAID-1 is now a local master browser for workgroup CHILA on subnet 192.168.122.1 Oct 25 14:06:18 NAS-UNRAID-1 nmbd[6866]: