R
Rob Nicholson
We currently have the following disk set-up in a Windows 2000 dev server
using IDE hard disks:
Disk 0: IDE channel 0, port 0, 8GB C: drive, 106GB E: drive (spanned)
Disk 1: IDE channel 0, port 1, 128GB E: drive (spanned)
Disk 2: IDE channel 1, port 0, 4GB F: drive (swap), 72GB E: drive
(spanned)
Now Disk 1 is actually a 256GB drive but due to BIOS limitations of the
motherboard, it can't recognise it correctly (137GB LBA limit) so half of it
isn't being used.
So we've ordered a PCA Promise IDE controller which will allow Windows 2000
Server to see all of the disk space. The question is, what will Windows 2000
do with the spanned volume when the disk moves onto another controller? Will
it realise it's move and carry on as normal or will we need to backup the
entire system?
Thanks, Rob.
PS. This server contains low-value data which is backed up just monthly.
It's not the end of the world if we loose it. But backing up 300GB of data
does take some time...
using IDE hard disks:
Disk 0: IDE channel 0, port 0, 8GB C: drive, 106GB E: drive (spanned)
Disk 1: IDE channel 0, port 1, 128GB E: drive (spanned)
Disk 2: IDE channel 1, port 0, 4GB F: drive (swap), 72GB E: drive
(spanned)
Now Disk 1 is actually a 256GB drive but due to BIOS limitations of the
motherboard, it can't recognise it correctly (137GB LBA limit) so half of it
isn't being used.
So we've ordered a PCA Promise IDE controller which will allow Windows 2000
Server to see all of the disk space. The question is, what will Windows 2000
do with the spanned volume when the disk moves onto another controller? Will
it realise it's move and carry on as normal or will we need to backup the
entire system?
Thanks, Rob.
PS. This server contains low-value data which is backed up just monthly.
It's not the end of the world if we loose it. But backing up 300GB of data
does take some time...