L
Lucy
On our system, C: drive is the system drive on compact flash. We protect it
with FBWF. If you do the command line fbwfmgr command, you can see the
protected volume is \Device\HarddiskVolume1, with a exclusion list under it.
After adding some RAID drives for data, C: drive is pushed to be enumerated
as \Device\HarddiskVolume3 or later, which makes the prior FBWF setting
"disappear" for C:. Because drives may be added and removed with different
configurations, the FBWF setting is impossible to be set correctly.
Here is my question. If FBWF is associated with a disk volume name, not with
a physical drive letter, is there a way that I can make sure the system drive
C: is always HarddiskVolume1? What can I do to make sure the non-system
drives to be enumerated after the system drive? Is there any settings in XP
Embedded image for this?
If you have experience in this, please give help.
If you understand how the disk volumes are enumerated at boot time, please
shed some light too.
Any help is greatly appreciated.
with FBWF. If you do the command line fbwfmgr command, you can see the
protected volume is \Device\HarddiskVolume1, with a exclusion list under it.
After adding some RAID drives for data, C: drive is pushed to be enumerated
as \Device\HarddiskVolume3 or later, which makes the prior FBWF setting
"disappear" for C:. Because drives may be added and removed with different
configurations, the FBWF setting is impossible to be set correctly.
Here is my question. If FBWF is associated with a disk volume name, not with
a physical drive letter, is there a way that I can make sure the system drive
C: is always HarddiskVolume1? What can I do to make sure the non-system
drives to be enumerated after the system drive? Is there any settings in XP
Embedded image for this?
If you have experience in this, please give help.
If you understand how the disk volumes are enumerated at boot time, please
shed some light too.
Any help is greatly appreciated.