trurl
-
Content Count
25140 -
Joined
-
Last visited
-
Days Won
79
Posts posted by trurl
-
-
Tools - Diagnostics, attach ZIP to your NEXT post.
-
8 minutes ago, GalaxyBird said:suggested restarting but with only 7 drives active.
If you want to shrink the array, go to Tools - New Config, keep all assignments, then before starting the array, make any changes you want such as removing a drive. Then start the array and let it rebuild parity. Be sure you don't assign a data disk to a parity slot or it will be overwritten by parity.
-
-
Do you know how to use dockers on Unraid?
-
Shouldn't be any rebuild issues due to SSD, but you do want to get SSD out of the array. It would make a good cache.
Replace / rebuild parity first of course, then replace / rebuild the data disk.
-
1
-
-
Rebuild is not the way to fix unmountable. Likely the rebuild will also be unmountable. You need to repair the filesystem:
https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
Probably broken user shares is just a symptom of the corrupt disk. Fix that and your user shares should be back, since they are just the top level folders on all disks.
-
11 hours ago, ctviggen said:I have one "hot spare" 3TB cache drive.
The idea of using cache as a hot spare doesn't make as much sense as it did back in the pre V6 days of Unraid. Many will have SSD cache now, and cache is used for much more than just caching user share writes, such as fast data for dockers / VMs.
-
Unraid IS NOT RAID.
Each disk is an independent filesystem. Redundancy is provided by 1 or 2 parity drives.
No data drive can be larger than any parity drive.
-
3 hours ago, nos0n3 said:also how were you able to find which disks where the ones assigned to those ata slots
syslog
Sep 24 20:44:21 DLNQNT kernel: ata2.00: ATA-9: WDC WD100EMAZ-00WJTA0, JEGKNTAN, 83.H0A83, max UDMA/133 ... Sep 24 20:44:21 DLNQNT kernel: ata3.00: ATA-9: WDC WD100EMAZ-00WJTA0, 1EG8SH2Z, 83.H0A83, max UDMA/133
There were some reassignments and you can see all this in syslog, but that is the slots those serials ended up being assigned according to smart folder in diagnostics.
-
Shutdown, check connections on disk1 and disk3
-
Are you sure Windows isn't trying to install updates before shutdown?
-
41 minutes ago, nos0n3 said:rebuild fluctuates between 500KB - 1.5MB is this normal?
No
Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
-
Sounds like folklore passed on by people who don't know how things work.
Or maybe you just misinterpreted good advice.
If you schedule mover to run more often hoping it will fix the problem of filling cache, then the advice would be to reconsider what you are doing. No matter how frequently you move, you can't move from cache to slower array as fast as you can write to faster cache. Mover is intended for idle time.
-
Likely nothing wrong with the original disk. And nothing apparently wrong with this one.
An occasional small number of CRC errors, just go to the Dashboard, click on the warning, and acknowledge it. It will warn again if it increases. If it continues to increase, especially if it is not a small number, then try to fix the connection problem.
No need to replace the disk.
-
-
Your appdata will be fine but without the templates on Flash you'll have to setup all dockers again.
Did you have a Flash backup?
-
Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
-
28 minutes ago, DrBazUK said:I realise that the names of the folders I assigned in the container were what the GUI was expecting to have in the fields, not the *actual* paths
docker volume and port mapping is 90% of what you need to understand about setting up most dockers.
-
1
-
-
post docker run command as explained at the very first link in the Docker FAQ in the Docker Engine subforum
-
Seems like we are going back over things already discussed in this thread.
Possibly emulated disk8 is being corrupted by the errors on other disks and maybe the physical disk8 is mountable.
Still mounted disk9 is also showing corruption but that might just be the errors again.
SMART for each disk in question looks OK.
13 minutes ago, GTP said:I think I fixed the power/connection issues
I don't think so.
-
38 minutes ago, trurl said:Setting a share cache-no means new files will not be written to cache. It also means mover will ignore the share so if it has files on cache they will not be moved.
There is help in the webUI. The Help (?) button will toggle Help for the entire webUI on/off. You can also toggle help for a specific setting by clicking on its label.
Here is a FAQ that gives more details about the nuances of the Use cache setting:
-
I also recommend reconsidering your desire to have all data in one share. By doing that, you give up the ability of Unraid to manage different files differently with different user share settings.
If you really want "one share to rule them all" take a look at this:
-
Setting a share cache-no means new files will not be written to cache. It also means mover will ignore the share so if it has files on cache they will not be moved.
Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post in this thread.
-
Is that GoogleDrive the only thing in your Media share?
(SOLVED) MOBO Change unRaid 169 IP address
in General Support
Posted
yes