o.orcinu158202db
New member
- Joined
- Aug 19, 2023
- Messages
- 6
I've finished setting up my somewhat overly complicated storage setup, and have some observations and questions.
First of all, an old issue and a possible solution...
As has been reported many times before, AMD RAID drivers and RAIDXpert2 are extremely buggy, and there's a bug with SATA RAID that has remained unfixed for approximately 4 years now. Traditional (spinning) HDDs that are NOT part of the array do not get recognized by RAIDXpert2 at logon time until you open RAIDXpert2 GUI and hit Rescan, at which point they just magically reappear as if nothing happened. Same thing occurs if you're patient enough to wait 1-5 minutes for some timeout to occur and trigger a RAID driver reinit and rescan.
Additionally, even with the drive showing up, occasionally, presumably after some power management event, they'll disappear again and produce more IO errors until another driver reinit, unless RAIDXpert2 GUI is running in the background all the time. There are many variations of this issue reported - sometimes it's traditional drives in a RAID array, sometimes "legacy" (i.e. not part of an array), hard drive brands differ from case to case, ports don't matter, cables don't matter... The commonality is that drive does not get properly initialized by RAIDXpert2, reappears as if nothing happened after a rescan, and most importantly, the drive itself and all the hardware components are okay.
I'm experiencing the same issue, and i think i finally found the permafix (knock on wood) based in part on previous solutions mentioned here and on other forums:
1) open Task Scheduler
2) create a FIRST task that starts RAIDXpert2, trigger at startup, run even if user not logged in, run at full privileges
3) create a SECOND task (this one's important), same settings as the first task, but have it run "rcadm.exe" from the RAIDXpert2 folder, with parameters -M -rsc
4) reboot and everything should work fine now, on first logon
What this does:
- runs RAIDXpert2 in background, as previously suggested by others
- runs the command line RAIDXpert2 interface, and tells it to rescan the arrays
- all of this happens before logon, so by the time you're logged in, all disks should be working and showing up
It's ridiculous that this is necessary, but it is what it is.
First of all, an old issue and a possible solution...
As has been reported many times before, AMD RAID drivers and RAIDXpert2 are extremely buggy, and there's a bug with SATA RAID that has remained unfixed for approximately 4 years now. Traditional (spinning) HDDs that are NOT part of the array do not get recognized by RAIDXpert2 at logon time until you open RAIDXpert2 GUI and hit Rescan, at which point they just magically reappear as if nothing happened. Same thing occurs if you're patient enough to wait 1-5 minutes for some timeout to occur and trigger a RAID driver reinit and rescan.
Additionally, even with the drive showing up, occasionally, presumably after some power management event, they'll disappear again and produce more IO errors until another driver reinit, unless RAIDXpert2 GUI is running in the background all the time. There are many variations of this issue reported - sometimes it's traditional drives in a RAID array, sometimes "legacy" (i.e. not part of an array), hard drive brands differ from case to case, ports don't matter, cables don't matter... The commonality is that drive does not get properly initialized by RAIDXpert2, reappears as if nothing happened after a rescan, and most importantly, the drive itself and all the hardware components are okay.
I'm experiencing the same issue, and i think i finally found the permafix (knock on wood) based in part on previous solutions mentioned here and on other forums:
1) open Task Scheduler
2) create a FIRST task that starts RAIDXpert2, trigger at startup, run even if user not logged in, run at full privileges
3) create a SECOND task (this one's important), same settings as the first task, but have it run "rcadm.exe" from the RAIDXpert2 folder, with parameters -M -rsc
4) reboot and everything should work fine now, on first logon
What this does:
- runs RAIDXpert2 in background, as previously suggested by others
- runs the command line RAIDXpert2 interface, and tells it to rescan the arrays
- all of this happens before logon, so by the time you're logged in, all disks should be working and showing up
It's ridiculous that this is necessary, but it is what it is.