superloopy1

But will it rebuild it as per the drive it is replacing and NOT add it as a new empty drive, that's my question.

I have just increased one of my arrays 12TB drives with a larger drive. I now want to reuse this 12TB drive in my backup system and obviously it still has all of the 'old' outgoing data on it which is no longer needed. The drive is still in unraid format so i'm wondering do i just repeat the process i used to switch in a larger drive and replace any drive on my backup system with this 12TB WITHOUT the need to reformat or delete any of the 12TB contents. Will Unraid just rebuild the image of the existing backup drive onto my 12TB drive as if it didnt already have data on it? It would save a lot of time and effort if thats how it works. I'm concerned that it may just 'import' whats on the old drive at the expense of whats currently known to the backup system. That would be a disaster! Cheers!

Think this is a 'me too' moment. Just tried to run up my docker nextcloud instance and it fails saying that i need to go way back and upgrade manually -- 'Can't start Nextcloud because the version of the data (20.0.5.2) is more than one major version behind the docker image version (27.0.1.2) and upgrading more than one major version is not supported. Please run an image tagged for the major version 21 first' Any suggestions??

Well, we'll see soon hopefully. I pulled a 12TB drive and have replaced it with an 18TB. Expected rebuild time showed as 3days 5hrs'ish so away it went. 2 days into the rebuild the system rebooted (why??) overnight and i've had to restart it. On this second attempt i'm again 2 days into it, due to finish lunchtime tomorrow. Let's see what happens eh. The electric bill will be taking the hit again!

Yes, dual 18TB parity. Its that last bit confirming that filestore IS expanded that i was doubtful about. In the past i'm sure that i ended up with a 'like for like' copy of the smaller drive but on a larger drive and then needed to do some jiggery pokery to sort that out. Anyways thanks for confirming!

Guys, i've got a 16TB drive in my array and want to swap it for an 18TB, already precleared and tested. Is it just a simple removal of the smaller and swap in the larger after which that drive will be rebuild itself from parity? I think thats the way to do it but ist been a while and i have this worry that the drive will only be rebuilt to a maximum of 16TB ie the original sie of the removed drive? Or will i have at the end of the rebuild a rebuilt drive with an extra 2TB of available space? I've not touched Unraid for ages!! Thanks.

Guys, i have two servers, one of which, system A, has a smb remote share to the other machine, system B. How do i bring up the remote share manually on system A if it doesnt show due to system B being down? The system log on system A shows attempts to bring it up but never allows a 'Mount' prompt within unassigned devices on System B being powered up. All i see is a message when i hover over the smb tab which says 'remote share is offline' ? Whats the procedure to kick this remote smb share into life on system A?

Thanks but it wont help. Unbalance seems to work at the disk level when reorganising data. What i want is something which will take a share as input and consolidate its data correctly across a range of disks. Not sure Unbalance works that way. Could be wrong though.

Just received a few of these error messages in syslog? "nginx: 2023/05/26 16:21:57 [error] 7470#7470: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen." Any ideas? System is currently running Mover, might be important?

My latest system has got itself in a mess when it comes to what media, plex mainly, is where and i need to reorganise everything back on single disks for ease of access and backup consistency. Whats the quickest way to do this on lets say a tv show which has propagated itself across many disks due to, i assume, the wrong split level on the share. I need to tidy up ..... i cant be the first to have to do this across their disks.

Happened again ... i'm now on 6.12 rc6 lets see eh.

Thanks JorgeB but just too late unfortunately. It hung up altgether and needed a hard reset. Next time eh!

Came back to my PC after a few hours and for the n'th recently time the webgui was again inaccessible bar the top Unraid banner. Only tool i could think of was ssh so in i went, quick 'top' later and this is what i see ,,, 344 root 20 0 0 0 0 R 100.0 0.0 134:17.62 kcompactd0 1640 root 20 0 4232 2384 2072 R 100.0 0.0 35:33.28 pgrep 1892 root 20 0 4364 2600 2016 R 100.0 0.0 35:33.29 pkill 11147 root 20 0 0 0 0 R 100.0 0.0 36:05.60 kworker/10:0+rcu_par_gp 13769 root 20 0 4232 2336 2012 R 100.0 0.0 35:33.29 pgrep 15144 root 20 0 4232 2336 2024 R 100.0 0.0 35:33.29 pgrep 50671 root 20 0 4232 2292 1972 R 100.0 0.0 129:47.71 pgrep 50908 root 20 0 4232 2296 1976 R 100.0 0.0 129:27.74 pgrep 55244 root 20 0 4168 1136 984 R 100.0 0.0 35:33.30 ps 12442 root 20 0 4232 2336 2020 R 100.0 0.0 35:33.29 pgrep 13379 root 20 0 4232 2264 1940 R 100.0 0.0 35:33.29 pgrep 50515 root 20 0 3836 2392 2004 R 100.0 0.0 129:58.44 sensors 65421 root 20 0 4232 2328 2012 R 100.0 0.0 35:33.29 pgrep Just repeating on these processes, everything below is at next to no CPU usage, obvious really. System IS still up and running at 100% cpu but how do i recover this without just hitting the buttopn, which is how i would normally have to do to fix this. Is there any way of stopping those 'processes' cleanly and restoring a usable system? I'll just leave things for now, see how any responses go (but electricity is expensive here in the UK ;-)))

aarghh. thats the way i had it originally before it stopped delivering the goods. i'll change it back when i get a minute. i've also changed a lot of SMB and UD settings in my attempts to get this working. Guessing i'll have to rgress these at some point if i can remember what they were set to ie defaults. Thanks again!

Thank Thanks guys, i am now sorted, and yes, it wasset up originally as you lay out Squid. Problem was of my own making (possibly). When the share last worked it was set up using the IP address 192.168.1.5, when i recreated it i used the server name xxTOWER. Seems the mismatch doesnt resolve very well and didnt match the docker paths which were still pointing at the IP address. I'm still unsure as to which is most efficient, IP or servername? Once corrected it place a xxTOWER share on the receiving machine and after a scan all folders are now showing. Problem is it WAS working perfectly then it didnt and I never went anywhere near the configs hence the reason for forgetting what was in place when i deleted and attempted to reset it. Honest guv ;>) it wasnt me !

Thanks. yes I did but i'm not sure i did it correctly. is it the case that for server B to access server As files then the share needs setup on BOTH servers or just SERVER B? and, ive moreorless activated all smb settings in UD settings and still my shares are not populating on either emby or plex whereas they used to do so no problems. Which diagnostics do you need?

I used to have a couple of SMB network shares between my two servers but recently they stopped working and i deleted them. No i have no idea how i set them up in the first place, permissions etc and cant seem to 'see' the servers at all, d'oh! If i want to shae from server1 to server2 which machine gets the 'share' set up and as permissions seemed to be my downfall last time around what's needed here? Just need to see the shares on the other machine. Seem to remember i set it up from the main page thats all . Cheers ...

Thanks for that. Unassign is a simple as that eh, It can all be done without a powerdown?

I should know this but its solong since i touched this particular array and i need someone to explain the procedure. Disk1 eg is almost full with no prospect of relocating the contents elsewhere. I have no spare disk slots but DO have a larger drive withing the capacity of the overall parity. Is it a simple drag the old drive out and swap the new drive in or is there some unassign process needed? My minds just not remembering the 'good' procedure any more ... thanks guys.

Well now. I'm on 6.5 and can no longer 'see' the plugin in the appstore. Has it been pulled from the production ie stable release line?

I got fed up with seeing the prompt that disklocation app could not be loaded against my 6.11.5 system until i had 6.11.9 at least. Surely this prompt should not be being shown on a system running the most stable release 6.11.5 when i check for app updates. So ... i just removed the app, too much of a pita. Suggest others who find this a distraction ie 'when is an update not an update', answer being when its being offerref up in error and not corrected, just delete the app.

Ah, so there's the catch then. I'll need to raid10 the ssds outside of the array which to all intents and purposes is just a front to enable my dockers to run. Trim CAN be used against those cache pools external to the array. I'm learning i think .... thanks again, very prompt!

Is TRIM available within the array if parity is NOT being used?

That sounds promising. So if i exclude in global share settings all activity will only be to cache pool shares and will run at the speed of the slowest ssd in the system? No parity drive needed anywhere? Really need to understand cache pools now before i drop an awful lot of cash on hardware. Thanks!