urbanracer34

None at all. I have a UPS.

Decided to start a parity check and my Parity Drive has 28 errors holding steady. Should I be worried? Diagnostics attached. Parity check is still in progress. gibson-diagnostics-20230402-1322.zip

Redid my backup overnight to my server. Hopefully that will fix this for now.

appdata Cache 14.4GB

I don't think so, but I just looked under the cache drive and there was the appdata folder.

All of my docker containers and appdata are on the cache drive under pool devices (/mnt/cache/appdata). That is where I want to put it, unless this is the wrong way

Does this look correct now?

Positive. I never changed them as far as I can remember.

CRAP! I don't have a flash backup handy. Where do I go from here?

I installed the new version and now it's saying Source Must Be Specified Source cannot be /mnt/user or /mnt/disk Destination is /mnt/user/CommunityApplicationsAppdataBackup I don't think it ever did this on V2. Where do I go from here?

I'm not quite sure what to do with UD and rootshare (may not require it anymore,) but the logs are clear! Both W11 and MACOS! Thanks for the help!

Accessing same share on MacOS Monterey gives me this error: Jan 12 11:38:08 GIBSON smbd[13491]: [2023/01/12 11:38:08.790154, 0] ../../lib/param/loadparm.c:1815(lpcfg_do_service_parameter) Jan 12 11:38:08 GIBSON smbd[13491]: Global parameter logging found in service section! Jan 12 11:40:36 GIBSON smbd[14487]: [2023/01/12 11:40:36.155899, 0] ../../lib/param/loadparm.c:1815(lpcfg_do_service_parameter) Jan 12 11:40:36 GIBSON smbd[14487]: Global parameter logging found in service section! Jan 12 11:43:07 GIBSON smbd[15781]: [2023/01/12 11:43:07.614127, 0] ../../lib/param/loadparm.c:1815(lpcfg_do_service_parameter) Jan 12 11:43:07 GIBSON smbd[15781]: Global parameter logging found in service section!

I got this in the logs, should the entry for logging be at the top? Jan 12 11:21:44 GIBSON smbd[7222]: [2023/01/12 11:21:44.413507, 0] ../../lib/param/loadparm.c:1815(lpcfg_do_service_parameter) Jan 12 11:21:44 GIBSON smbd[7222]: Global parameter logging found in service section! Jan 12 11:21:55 GIBSON smbd[7222]: [2023/01/12 11:21:55.940422, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Jan 12 11:21:55 GIBSON smbd[7222]: synthetic_pathref: opening [Final Fantasy XII (USA).7z] failed

Where do I enter this? Can I enter it somewhere in the GUI?

BUMP?

So I decided to copy some valuable data from my Windows 11 Machine to my unRAID server over SMB. I just upgraded unRAID to 6.11.5. Almost immediately, I got pathref errors in the syslog. TONS. I attached my diagnostics below. What is going on?! gibson-diagnostics-20230108-1526.zip

Do you happen to have a list on where and when these changes were implemented?

Will they at least continue to support it for those who do? Would like someone to give me a concrete answer; the higher up the food chain the better.

I also use an external drive every few days. It perplexes me why it stops working on the network. Also, in the survey they sent out, time machine was at the bottom of the list. https://unraid.net/blog/unraid-customer-survey-results

After deleting the sparsebundle and giving it a day to do its thing, we are backing up to the server again! Why is it like this?!

It's been a few months since I last reported back. The honeymoon is over. It no longer wants to back up my Monterey mac to my server.

Just thought I would report back. My Monterey mac has been backing up very well. I will still keep this open for those who are having problems.

Changed Status to Open

My Monterey mac successfully backed up! No server tweaking was required. I will not marked this as solved, as I'm not sure how long this backup "honeymoon" will last, but also because others have issues.