• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

dynamic disks

S

SlickJesus

Guest
i will be adding an 80GB drive to it, and i was wondering, would making the existing drive and the new 80GB drive a volume set be worth it? will i see any slow down? speed gain? anything? i'm interested in this so it will look like one drive and it will be easier to manage. what do i need to know about this BEFORE i do it?

thanx

P.S. Server specs are in my sig.

P.P.S. already read the links in the FAQ, i just want more info.
 
If anything goes wrong, you're SOL for those drives, basically nothing can touch dynamic drives except windows, which doesn't leave much room for data recovery.
 
Vertigo Acid said:
If anything goes wrong, you're SOL for those drives, basically nothing can touch dynamic drives except windows, which doesn't leave much room for data recovery.

actually there are a few
its just assbackwards :p

If youve read the links in the FAQs, you know there arent a whole lot of reasons to adopt Dynamic Disks, that cant be addressed more reliably in a different way, by spanning 2 drives, your effectively put the disks at nearly the same level of risk as a RAID 0

why dont you explain why you want to do this, there may be another way ;)
 
basicly what i want is a single drive letter for the 2 drives.
a) it's easier to manage files.
b) easier to set up a FTP (which i have in place, but it's out of space)
c) so i can add space to my FTP without making a new directory
d) so i can map 1 drive to my PC instead of 2

does that make sense?

P.S. I just found out it already is a dynamic disk..i bought it off a friend of mine, how do i make it a basic disk again?
 
SlickJesus said:
how do i make it a basic disk again?

youd reformat it
there are a few 3rd party aps that will revert a dynamic disk with the data intact but they $$$

any reason you couldnt mount the new drive as a folder in the old partition?
http://www.microsoft.com/windows2000/en/server/help/to_use_volume_mount_points.htm
there would be reliability\recovery advatages that way (no LDM, both drives basic disks, normal set of recovery tools,
neither drive dependent on the other for access once reconfigured after a failure of one of them)
basicly Id recommend dynamic disks only if your running software RAID
(and Id recommend Hardware RAID if you could swing it :p )
or you really need to dynamically reconfigure the partition sizes
(enterprise disk allocation nightmares)

Using NTFS mounted drives

If you're a member of the Administrators group, you can use Disk Management to connect, or mount, a local drive at any empty folder on a local NTFS volume. You can format a mounted drive with any file system supported by Windows 2000.

When you mount a local drive at an empty NTFS folder, Windows 2000 assigns a path to the drive rather than a drive letter. Mounted drives are not subject to the 26-drive limit imposed by drive letters, so you can use mounted drives to access more than 26 drives on your computer. Windows 2000 ensures that drive paths retain their association to the drive, so you can add or rearrange storage devices without the drive path failing.

For example, if you have a CD-ROM drive with the drive letter D, and an NTFS-formatted volume with the drive letter C, you could mount the CD-ROM drive at an empty folder C:\CD-ROM, and then access the CD-ROM drive directly through the path C:\CD-ROM. If desired, you can remove the drive letter D and continue to access the CD-ROM through the mounted drive path.

Mounted drives make data more accessible and give you the flexibility to manage data storage based on your work environment and system usage. For example, you can:

Make the C:\Users folder a mounted drive with NTFS disk quotas and fault tolerance enabled, so you can track or constrain disk usage and protect user data on the mounted drive, without doing the same on the C: drive.
Make the C:\Temp folder a mounted drive to provide additional disk space for temporary files.
Move program files to another, larger drive when space is low on the C: drive, and mount it as C:\Program Files.
 
ok i got it working...i had a bad IDE cable as well, and i mounted it in the ol partition.
One last question...If the drive it is mounted in fails, do i just have to assign the new drive a drive letter to access it?
 
Back
Top