loady

i thought i had, i had all my appdata folders on the cache, is it just a matter of setting the docker.img to cache only ?

But isn't that the way if you have high water set, won't I damage my docker if I delete it from disk 3 and 4?... Then how do I go about stopping disk 2 being spun up all the time

Sorry, i completly forgot this thread, just seen disk two is costantly spun up and found this thread again ! the docker.img seems to be on disk 2,3,4 only disk 2 remains spun up, parity seems to be constanly spun up too. With regard to file system check on disk 3, i have just rebuilt that drive today after repairing a corrupt filesystem, disk 2 and parity have been spun up ever since

Right i did it, it has finished already as it says done at the bottom...is that normal ?, when i was reading the guide for repair it was saying it can take a long time (hours) but it seems to have done the trick, i started the array and the 'unmountable' messages have gone and the disk is just disabled and contents emulated, does this mean i just rebuild that disk now ? EDIT: Disk is now rebuilding, fingers crossed it was a previous power issue to that disk. Thanks for the help and pointers to the info.

Yes, what i thought, but i was saying it can take hours where i was reading the checking phase, just want to be 100% i am doing it correctly. now i got this when i removed the -n prefix.... Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Now it says on the main page that the filesystem is unmountable, should i go straight in with -L option ?

Thanks, i read that through and started a check with 'n' prefix, i read that it can take a long time, not sure if its finished already though ? it was reeling lots of text then stopped, the read counts for drive dont seem to be moving. I just pasted the very last part entry "WeVILLAGE_DOOR_UNBREAK24_SF.xxx" at block 17 offset 3376 in directory inode 14068600723 references non-existent inode 13626909168 would clear inode number in entry at offset 3376... entry "WeWASP_QUEEN_HEAD_01_SF.xxx" at block 17 offset 3424 in directory inode 14068600723 references non-existent inode 13626909169 would clear inode number in entry at offset 3424... entry "WeWasp_Weapon_SF.xxx" at block 17 offset 3464 in directory inode 14068600723 references non-existent inode 13626909170 would clear inode number in entry at offset 3464... entry "WeWHISPER_STAFF_SF.xxx" at block 17 offset 3496 in directory inode 14068600723 references non-existent inode 13626909171 would clear inode number in entry at offset 3496... entry "WeWill_Users_Sceptre_SF.xxx" at block 17 offset 3536 in directory inode 14068600723 references non-existent inode 13626909172 would clear inode number in entry at offset 3536... entry "WeWINDMILL_SAILS_01_SF.xxx" at block 17 offset 3576 in directory inode 14068600723 references non-existent inode 13626909173 would clear inode number in entry at offset 3576... entry "WeWINE_SKIN_01_SF.xxx" at block 17 offset 3616 in directory inode 14068600723 references non-existent inode 13626909174 would clear inode number in entry at offset 3616... entry "WeWITCH_SPOON_01_SF.xxx" at block 17 offset 3648 in directory inode 14068600723 references non-existent inode 13626909175 would clear inode number in entry at offset 3648... entry "WeWOODEN_LAMP_01_OFF_SF.xxx" at block 17 offset 3688 in directory inode 14068600723 references non-existent inode 13626909176 would clear inode number in entry at offset 3688... entry "WeWOODEN_LAMP_01_ON_SF.xxx" at block 17 offset 3728 in directory inode 14068600723 references non-existent inode 13626909177 would clear inode number in entry at offset 3728... entry "WeYOUNGHERO_02_SF.xxx" at block 17 offset 3768 in directory inode 14068600723 references non-existent inode 13626909178 would clear inode number in entry at offset 3768... entry "WeYOUNG_SISTER_01_SF.xxx" at block 17 offset 3800 in directory inode 14068600723 references non-existent inode 13626909179 would clear inode number in entry at offset 3800... No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting.

i saw in that thread about credentials, i think that was the issue, i had logged in with wrong user and even though i was able to invoke a prompt to use another login it acted like it was wrong, when i deleted the credntial that windows had stored and then logged in again using the correct user i can now access the shares on both devices, thanks for the help..though i feel i might be back as mentioned by yourself, windows SMB has more to do with witchcraft and magic !

https://gyazo.com/cd3a38e9176a67e521cecac09649ea27 thats from my LAN, the server is .122 and is master, i tried just now and it asked for credentials, now the weird thing is and i say its weird because i dont ever remember setting it, its not the usual login i use, the password is the same but the user is admin and i did this before i automatically typed in the previous, last time i typed in the user/pass i use to log into unraid it asked me again and i selected a different account and tried the user as admin but it wouldnt let in still...seems like its held on to it until some time passes then you can try again and it works ?

Ah, looks like LAN scanner is scanning the LAN of the network i am connected to on the laptop and not my LAN which i am VPN into, i will do it from home tomorrow where i will be physically LAN side. Sitting here now, remotley VPN into my router, i can connect to the the shares on the server with filezilla, i assume that is because its FTP ?

That disk was the one that kept getting spat out and disabled when i had it in the 5.25 bay to 5x 3.5" HDD enclosure, i beleive it had issues, the disks now reside in a new 24 bay rack mount server running from a SAS raid card, everything had been running fine, i do turn the server on and off as i need it as it is mainly a media server, i am however thinking of using it to run a windows VM and get rid of my desktop taking up space. How do i fix the corrupt filesystem and go about getting the drive rebuilt ?

Yes, i installed the dynamix master plugin, i have the yoda in SMB settings, the server and all devices i am using are set to workgroup KEVIN. I just ran that LAN scanner, however, right now i am on my laptop (matebook) connected to my network via openvpn connection running on router, i am accessing from laptop using openvpn connect https://gyazo.com/1eaad512ecdbf43e0652bc178b28cc71 I couldnt fins the yoda head but it is there, in settings/SMB

I started following and checking as i went along, i did have the allowguestauth in the registry to followed to ad that in, i have windows home so didnt have the gpedit.msc option, i also lossened the secuity in internet sharing, turned off password sharing etc etc, i managed to be able to browse the files in network, today i started up the PC and its back to no access again, the network address is invalid i went through the previous settings and they the same as i had changed them

I was getting issues with disks being disabled when i was using an internal caddy, i ended up buying a 24 bay rackmount server case and seemed to be fine, but my drive 3 has been disabled again, im thinking just let it rebuild ?...i hope its not the back plane, its a new case..maybe the drive is failing ? warptower-smart-20210418-1613 (1).zip warptower-diagnostics-20210418-1525.zip

I have not changed anything, windows wont let me access my server in network..propbably screwing it up on purpose in a bid to force people to use thier crap one drive https://gyazo.com/1288a7ded3c46e64bc629fce3e965f7c warptower-diagnostics-20210414-1225.zip

I have all my appdata folder on the cache drive, i have read that PLEX can cause a disk to remain spun up at all times, i cant see what if this is the issue with my setup, i had a look at open files but there are lots and possibly most are system files so i dont know what to do to find out whats doing it or how to stop it, i added a diags to this post. warptower-diagnostics-20200923-1025.zip

That seems to have worked, what was that all about, i didnt have to do this before. Where would i add that o n this file..at the end ? #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c /usr/local/sbin/cache_dirs -w -m 1 -M 10 -d 9999 unraid_notify start /boot/unmenu/uu

That seems to have worked, what was that all about, i didnt have to do this before

thats interesting...are you saying its possible to turn off UEFI and that might cure the issue?

I am not sure if this is relevant to UNraid itself or my hardware or a bit of both, i am using the same power supply that used to WOL my former set up. When shutting down UNraid the onboard NIC or add in NIC do not stay alive, there is no light on them when powered down, i have wake by PCI events enabled in the bios and have also tried toggling about PSU idle settings to no avail, the odd thing is though, if i shutdown unraid and then remove the power from PSU and leave for 30 seconds, when i plug it back in the NIC leds will be lit, obviously this is not possible for me to WOL remotely as i can't be here to do that when i am turning the server on and off. Is there a setting of UNraid when powering down that is completely powering everything off ? is there something i could try?

I am dumb, i have been moving them from slot to slot and have now just realised the SAS cable was not in properly so the top row was only getting power, plugged it in and now none of the drive are disabled, there is just one drive still disabled but i know this is ok, i was getting power issues with one of these 5 x sata into 3 x5.25 bay things and it would keep spitting out a drive, just did new config and set parity as correct and all is fine now thanks..as long as it dont get anymore dirves spat out i think i can safely say i have found the issue

I have upgraded my case to a 16 bay hot swap case, i have just moved everything into place and pushed the drives in. Now i have mutiiple missing drives, what should i do, i am sure i have the slot allocation picture somewhere but i dont think it will help, i have jiggled a few around and got four to show up now, prior to upgrading i did a full parity check andeverything was fine, it has been switched off since then so i am confident that parity is correct and no writes of importance have taken place. Can i initate 'new config' and check the box saying parity is correct, ideally i would like to keep the drives in number sequence in this case... PARITY---CACHE---DISK1---DISK2 DISK3---DISK4---DISK5---EMPTY EMPTY---EMPTY---EMPTY---EMPTY EMPTY---EMPTY---EMPTY---EMPTY above is basically the front of the case with the hot swappable bays, can i move the disks to those location and get it up and running again or do i HAVE to find the correct location, ALL the drives are no connected to the server card, prior to upgrading case the parity and cache were in SATA ports due to cable restrictions.

I specifically bought an asus tuff b450 for its WOL features, its enabled in the bios but i cant wake up/start the server, im using an asus router running asus merlin, set the mac address. I know my set up used to work, i used to VPN into server remotley and could wake the server, doing it this way is the same as being inside the network and doing WOL, i cant even WOL when i am physically on the network. I have seen some threads about people saying to enable 'allow magic packets' in windows, im not using windows so cant do this but surely this should work on this level. Does anyone have a solution ?

yes it did. Its set to write corrections to parity Last check completed on Fri 14 Aug 2020 09:58:21 PM BST (two days ago), finding 866 errors. Duration: 8 hours, 18 minutes, 41 seconds. Average speed: 100.3 MB/sec

Thanks for all your help and pointers, it seems to be ok now, i am sure the problem was power distribution which might explain the randomness of the drives being disabled, i think if one to many drives span up on that rail one of the other drives would suffer power shortage effectively causing UNraid to disable Now the problem is resolved should i completely rebuild parity from scratch, im happy with the contents of the disks

what ill do then is when the parity has finished ill set it up that way, if i get disks disabling i can just stop array and do new config and check the box for parity is valid, should stop the drive from rebuilding itself again ?