Just wondering why fans are loud and array did not start after reboot?

I had to manually start the array. Now array looks normal , but the fan are quiet for a little time then louder. I have not observe this before.

thecave-diagnostics-20260125-1540.zip

You have

Settings - Disk Settings - Enable autostart: no

Oh okay. Thanks. I will change that. I do not recall setting that to no. Then again, I am trying to correct some of my earlier Unraid missed items and not just unsure decisions. Fan seems to be fine not. Maybe there was a period of heavy processing on the server.

Edited January 26Jan 26 by ButchR

8 minutes ago, ButchR said:

I do not recall setting that to no.

That is the default so it would be no until you set it to yes.

Okay. I am discovering and learning a few new things (easter eggs) about Unraid. I was thinking I have in the past rebooted my server many times, it seems like the array would automatically start until my recent issue. Maybe it is different shutting down vs. reboot on the Unraid server array starting automatically. I do not often reboot, I shutdown and then , power on server.

You have

-rw-------  1 root root  11634 Jan 25 15:36 disk.cfg
-rw-------  1 root root  11643 Jan 15 17:05 disk.old

Any idea how the .old got created? Diagnostics just shows me it exists, it doesn't tell me its contents.

disk.cfg is where the autostart setting is stored. I can see its contents, that's how I knew you had autostart turned off.

22 minutes ago, ButchR said:

Maybe it is different shutting down vs. reboot on the Unraid server array starting automatically.

No difference, it just does what disk.cfg tells it to do.

That is very odd. I donot recall changing the disk.cfg . I wondering how that happen. I remember a few years ago setting up Unraid preference. All my restart's usually automatically would start the array. Every now and then I would have to change the sata cables and restart again to have the array start. After one time the server would start the drives automatically. This would happen occasionally, but many times after the server would be okay. I was thinking my 850 watts power supply just had issue with the amount of drives I had.

Then a few weeks ago (maybe around 1/15) nothing would help start the array. Now today i went in and changed the setting after you mention it to me. Maybe that is the reason for the disk.cfg post dated today's date.

I am wondering if a power outage could alter the Drive.cfg information or corrupted it. I had a power outage (while ago, not on UPS for a few days) that corrupted my Plex database. Maybe not, just was wondering if like that could have happen.

I just rebooted the server and it comes up with a started array..

Once again thanks for the help and explaining the interworking's of Unraid. The process is so fascinating.

Update on ongoing issues. I shutdown my Unraid server and connect my new replacement drive for failed (Disk 2) Then restarted server and array did not spin up. I am wondering what is going on with my server?

The replacement ( new drive just received today) is showing up as unassigned drive as normal.

thecave-diagnostics-20260203-1543.zip

None of those missing disks are seen in diagnostics. Only the disks connected to motherboard.

Probably better if you replaced that RAID controller anyway.

So maybe the old raid controller has some intermittent issues. Wow!! I just wondering the best way to swap out the old controller card with the new one. Last time I attempted to do that it did not go well.

3 minutes ago, ButchR said:

best way to swap out the old controller card with the new one

Make sure you have a current flash backup. Make sure you know what your disks assignments are. Go to Disk Settings and disable autostart.

Since you still need to rebuild disk2 we may have to use the method we discussed on the first page of this thread.

3 minutes ago, trurl said:

Make sure you know what your disks assignments are

            [name] => parity
            [id] => TOSHIBA_HDWG51JU_34X0A001FWQH_35000039d28d8684b

            [name] => disk1
            [id] => ST16000NT001-3LV101_ZRS1P4BE

            [name] => disk2
            [id] => ST16000NT001-3LV_ZRS268F2_35000c500ea6324dd

            [name] => disk3
            [id] => ST16000NE000-3UN_WVT07YYK_35000c500f715aaa5

            [name] => disk4
            [id] => ST16000NT001-3LV_WRS0A6EA_35000c500f6cce2f5

            [name] => disk5
            [id] => SEAGATE_ST6000NM_Z4D2BG6P_35000c5007b566474

            [name] => disk6
            [id] => ST4000DM004-2CV1_ZTT17LGL_35000c500c96d1d68

            [name] => disk7
            [id] => ST6000NM0024-1HT_Z4D2SEAG_35000c5007bce7f20

            [name] => cache_nvme
            [id] => Samsung_SSD_970_EVO_Plus_2TB_S59CNM0R419774J

            [name] => cache_ssd
            [id] => CT1000BX500SSD1_2110E583F484_3500a0751e583f484

            [name] => ssdpool_test
            [id] => Samsung_SSD_850_EVO_250GB_S3PZNF0JC10412H

            [name] => ssdpool_test2
            [id] => Samsung_SSD_850_EVO_250GB_S3PZNF0JC08916B

            [name] => vms_nvme
            [id] => WDBRPG0010BNC-WRSN_205348801911

            [name] => flash
            [id] => Flash_Drive_FIT

Disk 2 was rebuild with a unassigned 16TB drive that I had in unraid already. It when through the process successfully. ( I think so and running good for a few days.) I just cancel a parity-check that stared from one of my troubleshooting reboots. This was about a week ago and few days.

The old controller card is a Dell PERC H310 controller. Well the Supermicro X11SCA-F motherboard (can control 8 disks). Maybe I should switch over to the motherboard to control disk.

I reseeded the old controller card and restarted now the array is up.

thecave-diagnostics-20260203-1627.zip

3 minutes ago, ButchR said:

reseeded the old controller card and restarted now the array is up.

👍

I will plan my steps ( make should prep items: current flash backup available etc. ) out to swap out the controller card or motherboard sata controller.

I am still afraid that my server is not stable.

I still have to look at the controller information link you sent. Just looking at the replacement controller it is a HP H220 ver of LSI SAS9205-8i. Just when I thought I was over with this issue and "it pull me back in".

So disk 2 has been rebuild, I do not have to following the method outlined on the first page of the thread, right?

Should run a good parity check before I tackle this issue?

thecave-diagnostics-20260203-1649.zip

36 minutes ago, ButchR said:

disk 2 has been rebuild, I do not have to following the method outlined on the first page of the thread, right?

correct

37 minutes ago, ButchR said:

run a good parity check before

Not sure what that would gain. Might just cause problems again.

Okay no parity check for now. Just wanted to confirm a step by step outline to swap disk SAS/SATA controller. I know to mention. Want to make should I do the proper steps.

1 hour ago, trurl said:

Make sure you have a current flash backup. Make sure you know what your disks assignments are. Go to Disk Settings and disable autostart.