DireWolf

Apologies, I was referring to 'data protection' in context to the topic. Maybe a poor choice of wording on my behalf.

I was also thinking a sort of rolling/sectional parity check for 'off-peak' periods. I would say that you would still require a full parity check at a given schedule but a rolling/sectional check would allow us to decrease the frequency of full parity checks and still give us peace of mind our data is still protected, primarily for the purpose of optimizing system resources. I gather there is probably a lot more to this than I initially suspect and it may not even be viable, but I thought I comment anyway in hopes that someone, more educated than I in this area, could give me an answer to satisfy my curiosity

+1 Said feature would make my life easier. Perhaps each cache pool could have an independent mover schedule?

I have since realized that a few of my unassigned devices have, somehow, lost their 'unassigned device configuration / preferences'. Strangely, the drives are showing up underneath as configure but disconnected despite also being present in the 'unassigned device' section (identical identifications). I have a feeling this issue, as well as the initial sloowwww / delayed reboot, could be related to what Frank1940 and others mentioned earlier about the boot order changing in the BIOS: It was easy enough to reconfigure my unassigned drives so no real drama, but I want to get to the bottom of this, in case it causes me any issues later on (and in case there is actually a bug / issue that could potentially effect others upgrading to 6.3.4). I really have no idea but i'm thinking the drive mapping / ordering is getting messed up somehow? Being the noob I am, I am not sure what I should be looking for regarding my suspicions. (note, I'm a proper newby so please feel free to pull me up on any incorrect terminology and/or general stupidity )

How long did you wait before assuming it wasn't working? I also had a similar issue on both my machines when upgrading from 6.3.3 to 6.3.4 After about 5 minutes, after the initial restart, I had no access to the web ui or via SSH... so I decided to grab a coffee, then come back to figure the issue out, but when I came back they were both running and accessible... I will dig through my logs after work to see if there is anything unusual but so far have been on 6.4.4 for a day with no dramas