thirtythreemangos

Out of the blue I get this error that its not available now. I haven't touched settings at all, it just has always worked correcly. Any idea what's going on?

Rsync looks super handy. But when I went to this page I just got super overwhelmed at the prospect of actually ensuring all the right options were (or weren't) actually going to be utilized and employed. I dig some digging into Carbon Copy Cloner and figured out a way for it to use an SMB volume (if that's even the best way to refer to that) after creating a new User on unRAID that has read/write permissions. CCC was able to save the username/password to access that volume/share through my Macbook Pro and over the network. Tested the functionality and it actually works! But I imagine its going to be super slow, so the initial clone sounds like a nightmare. I'm gonna figure out a way to use Rsync (or even just like Krusader?) for a local-to-local clone when plugging the external drive directly into the server, then for subsequent backups that can just be done plugged into the MBP and through the network. Hopefully that ends up working But at least with this method I retain the SafetyNet feature and the userfriendliness that CCC gives over just command line approach.

@ConnerVT I appreciate the effort in that response. Do you just then go manually run the script whenever you feel like doing a backup/sync?

Hi all, I need some suggestions for workflow. I'm a photographer, and before my recent NAS + unRAID build I have been using external hard drives for archiving, initially unloading memory cards to a folder in my Macbook Pro internal drive, offloading to a master archive as needed, then using Carbon Copy Cloner to duplicate that external drive to a second external drive for redundancy. Now that I have my NAS w/unRAID built, I need help on best workflow suggestions. Here's my goal: I want to use the unRAID NAS as primary photo archive storage (also have 1 parity drive in use, but I know that's not "backup") I SMB over wifi LAN from my MBP to the server to access the archive (I don't plan to use things like Lightroom or any library-building type software with the *archive* files, that's specifically done locally on my MBP before copying over to the array) for viewing and copying/downloading as needed. I need some sort of cloning method within unRAID to create a true backup to the array. Initially I had thought "maybe there is an unRAID version of Carbon Copy Cloner that would work via Unassigned Devices" but naturally there is not, at least not yet. I need a software solution that can clone the photoarchive share (or if not cloning the share itself, all the folders and files within it) WITH the same sort of functionality that I had within Carbon Copy Clone (ie, incremental-only updates, meaning it will only scan for changes and only spend time copying over additions and modifications instead of cloning every sector and byte) To create my third copy in 3-2-1 to send to the safe deposit box I can easily just plug both externals into my MBP and use CCC as usual and clone one to the other Does anyone have good suggestions for accomplishing this? Ideally within an app since I'm not the GREATEST with command line? Thanks!

'Preciate the input!

@RyszSounds good. I'll probably just ignore it for now, like I mentioned I only happened to stumble across the logs, not really part of my normal workflow. Perhaps if something changes to the workflow in the future then I'll set up those filter rule things. Thank you!!!

@Rysz I've done one test with it, where I picked settings, pulled the UPS power cord from the wall to test battery functioning, and then ultimately the graceful shutdown. It did shutdown properly 1 minute later, and the data/stats do show on the Dashboard page of unRAID, so yeah I think it still works fine. I just was unsure of what the error messages meant and if I was set up for an issue down the road or something.

Hi all, seems I'm having a similar issue. I only happened to randomly look at system logs to even notice it to begin with, but after noticing and scanning back through it seems ever since I first implemented the NUT app a couple days ago the same thing has been occurring regularly. Screenshot of the system log page attached below. I'm using the USB cable that was included with the UPS (CyberPower 1350VA - CST135UC2) and it is plugged in to a 2.0 port on the back of my NAS. Any advice? NUT Debug also attached. nut-debug-20240604091516.zip

@trurl So I got it figured out, more or less. I removed that drive, reapplied the kapton tape to the 3.3v pin making extra effort to be thorough and complete and have it stick well and appropriately, reinstalled the drive, booted into safe mode, ran another SMART check on the drive (which again produced no error messages), started the array in maintenance mode and added the drive to the array, performed an XFS filesystem check first with the -nv and then again without, and then again re-built the drive onto itself. I can only guess that the original kapton tape was the true culprit, as when initially trying to re-build the drive produced a slew of UDMA CRC errors and an array failure, but booting in safe mode, starting array in maintenance mode, running the checks, and then re-building in that mode seemed to fix it. When rebuilding the drive, I DID get maybe another 10 UDMA CRC errors, but nothing like the 4744 of them that caused this whole debacle. But thank you everyone for the input. Hopefully anyone finding this post may consider the kapton tape as a potential culprit for similar issues. I'll eventually phase out those shucked drives that require the 3.3v pin fix (or perhaps there is an actually reliable adapter out there for this specific type use?), but the budget is not there presently.

@trurl @itimpi Well, I just re-did the kapton taping of the 3.3v pin. Reinstalled the drive. Rebooted. The drive shows in unassigned devices, but this time around I'm getting the "Device '/dev/sdg' failed to mount. Check the syslog for details" error message. It mounted just fine before I tried to rebuild it, but now after the round of error messages/failures that brought me here to the forum, it won't mount. Wnat should I do?

@trurl We're good there, no significant tension, just have had to carefully route the cables. I specifically bought the 2' cables to avoid that in routing from one side of the machine where the drives nest to the other side where where the motherboard ports are. No splitters. Although if I DO end up filling the case completely with all 8 drives that it accommodates then I'll have to figure out something, though. I went a tier up on the PSU I picked in part because this one includes 8 SATA power connectors as opposed to 6 on the first PSU I was looking at, and I had to use up one of the SATA power spots for the cases external fan speed switch (which passes through power to 3 of the fans in the case). The more I think about it, the more I wonder if I just did an inadequate job of inappropriately kapton taping the 3.3v pin on the drive. My understanding is that if that pin receives power, it shuts the drive down/prevents it from turning on or spinning up, so you have to tape the pin to prevent the connection in order to permit internal use (its a shucked external WD drive.) The cables and connections all looked good when I opened it up so I think the most likely thing is that the pin just wasn't perfectly covered and it was getting little connections every so often and the issues resulted from the drive trying to shut itself off (or whatever actually occurs electromechanically when that pin receives power).

@trurlThank you! I really appreciate the input.

@itimpi Just shut everything down and took the drive out. Everything looked to be seated nice and tight, and it's a brand new set of SATA cables and PSU, so i really dont have any idea why anything would have happened. The only even potential ideas is maybe when I kapton taped the 3.3v pin on the drive I either didn't cover it enough or covered a slight hair of an adjacent pin? Or maybe the way the cable is bent to fit everything in the case caused a short or something? It's a Fractal Design Node 804 so there's decent space and I'm not doing anything that's not intended to be done, so I don't know.

@trurl I mean in terms of unRAID specific stuff. I'm still unfamiliar with the OS and am learning as I go. I know RAID is not backup, and I don't have anything irreplaceable in the array, just digital media so far. I know theres some sort of backup option for the unRAID thumb drive, but I haven't gotten into that yet. But at least for now it seems like I can stop the array and shut off the machine and such without any increased worry. I'll check and replace cables. As far as making free space, I know there is a setting somewhere to change the level of reserve space or something? I know I set them up as "fill up" instead of "high water" or whatever those modes are called. What's the best way of shifting some files from one physical drive to another? Just move on Krusader? Will that affect hardlinking or anything? I assume Plex will be able to find them just fine with a rescan, but I've learned that what I know about computers hasn't really translated a whole lot to this Linux/unRAID world, so I appreciate all the tips.

@itimpi I can try swapping a new data cable. What's the best next step right now? Am I ok to stop the array and shut it all down so I get in to the drives? Do I need to do any diagnostics tests before anything? Or backup anything? I'm operating under the assumption that despite a repeat "drive disabled" thing the data is still intact in parity and I won't lose anything just shutting down and unplugging stuff?