Hello, I shut down my array, and when went to reboot, my cache drive, and disk 3, are no where to be found.

I have rebooted a few times, with no luck. 

 

Here is my diagnostic, any help would be greatly appreciated.

 

 

 

syslog.txt

Edited December 28, 20232 yr by Cambridge

That is not the Diagnostics. 

 

Attach Diagnostics to your NEXT post in this thread. 

 

Can you see the disks in BIOS? 

Im sorry about that. here it is. I have replaced the Disk 3, and it is rebuilding, I cannot see the SSD in bios. Can see 4 out of 5 WD in bios. Rearranged some SATA cables on the MB and now I see the old disk 3 in unassigned devices, but it was showing emulated when I tried adding it the the array.

tower-diagnostics-20231227-2221 (1).zip

Don't see anything rebuilding in those. and since the array isn't started, can't tell if emulated disk3 is mountable. Start the array in normal mode and post new diagnostics.

Apologize again, a bit new to all this, but learning. I must have downloaded diagnostics prior to starting array and uploaded incorrect one. I am rebuilding disk 3, on a spare 12Tb I had sitting around. the "old" disk 3, is showing in disk devices and appears mountable. When it is finished rebuilding the array, I will run pre clear on old disk 3, and hopefully be able to add back to the array. Still no cache disk ssd showing. Thank you for your help.

 

tower-diagnostics-20231228-1501.zip

7 hours ago, Cambridge said:

cannot see the SSD in bios

Then Unraid will not see it either.

 

2 hours ago, Cambridge said:

the "old" disk 3, is showing in disk devices and appears mountable

Not really what I was asking about though.

4 hours ago, trurl said:

can't tell if emulated disk3 is mountable

I was wondering if you were rebuilding an unmountable filesystem. Emulated disk3 is mounted so should be OK after rebuild.

Ideally, appdata, domains, system shares would have no files on the array. Docker/VM performance will be impacted by slower array unless these are completely on cache or other fast pool. And array disks won't be able to spin down since these files are always open.

Thank you, you recommend moving appdata, domains and system shares to cache pool? I am waiting on a new ssd for cache. hopefully tomorrow. how do I go about putting those on cache? selecting cache pool in settings for those shares?

Edited December 29, 20232 yr by Cambridge

Just changing the share settings won't be enough.

 

Since you aren't on 6.12 yet the use cache settings for you would be to set these to cache:prefer so mover will move them to cache.

 

But, nothing can move open files, so you have to disable Docker and VM Manager in Settings before running Mover.

Thank you, will try that. Appreciate it

Turns out it appears my cache drive was the cause of my issues. new cache disk. Moved appdata, domains and system back on cache. All systems back online. Thank you for your help.

Post diagnostics if you want us to take a look.

tower-diagnostics-20240101-0200.zip

Looks good!