Re-init drive capacity in 2000v2

[morrisonmorgan]

Tried to update my 2000 V2 with bigger drives, 2x30gb to 2x120gb, the new drives, only show 30gb capacity.

Tried doing "co de format 10000 /reinit" and i get an invalid device ID.

How can i reformat the drives to show their full capacity.
(Note; There is no data that needs to be saved on either drive).

here's a copy of my device information, and "info devices" if it helps;

Model Software Hardware Server # BIOS
2000 3.4.805 (US) 2.0.0 49 2.0.252


Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 31768 Private Mounted
Label:Private Contains system files only
Unique Id: 0x1BA4672E15C65ABD Mount: /priv Index: 12 Order: 0
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 33027584 Fixed

Logical Device: 1001E Position: 0 JBOD Size (KB): 32296 Free (KB): 32056 Private Mounted
Label:Private Contains system files only
Unique Id: 0x1A68A3C570FBD5F5 Mount: /pri2 Index: 13 Order: 1
Partition: 1001E Physical: 1001F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1001F Drive Slot: 3 IDE Size (KB): 33027584 Fixed

Logical Device: 10008 Position: 1 JBOD Size (KB): 32247200 Free (KB): 32214648 Public Mounted
Labelrive2 Single disk
Unique Id: 0x1BA4672E15C65ABD Mount: /1 Index: 1 Order: 2
Partition: 10008 Physical: 1000F FS Size (KB): 32694304 Starting Blk: 41532 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 33027584 Fixed

Logical Device: 10018 Position: 2 JBOD Size (KB): 32694304 Free (KB): 0 Public Unmounted
Labelrive2 Single disk
Unique Id: 0x1A68A3C570FBD5F5 Mount: /3 Index: 3 Order: 255
Partition: 10018 Physical: 1001F FS Size (KB): 32694304 Starting Blk: 41532 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 33027584 Fixed

[blue68f100]

Your 2000 is showing markers of a 4000 unit.

Click on the SnapAppliance logo on the admin page and post results less SN.

On problem units ....

First remove your slave drive. Make sure you have the drives (master and slave) are set up as CS. Some units require M/S, when used with some HD's.

Boot the unit with only the master hd (end connector). If you show any raid setup you must delete them. Try the disk utility, if that does not work. You must go into debug and enter "co de predict individual 10000" . a reboot is required. Once the HD shows up as a single HD and not part of a raid array. Enter the "co de info" see if it show up as a single HD. Then try formating the HD with "co de format 10000 /reinit" , then check capacity. If ok connect the slave. If it's part of an array follow the above procedure, using 10010 for the slave device.

[morrisonmorgan]

Hey, It was included in that first post,

Model Software Hardware Server # BIOS
2000 series 3.4.805 (US) 2.0.0 2.0.252

I'll try setting both to CS, the original drives were both set to Master. (so that's how i first tried it with these.

[blue68f100]

Most case you can not reinit if in raid. So you must set to JBOD. Or wipe both drives clean and re-install into snap. Allow 10 min for the os to be installed before trying to connect. But in either case you can not have a raid. The drive info is stored in non-volatile ram.

CS/MS is all dependent on hardware versions. 4100 and v1 models (1000, 2000) use MS, where the later models use CS.

I checked your platform byte with the bios table and it matches for a 2000.

[morrisonmorgan]

Ok, the drives are set as JBOD, I tried booting with one drive at a time connected, and I never saw the 10000, or 10010 drive identifiers in the device information.
How can i reset the drives? or Wipe them clear? It seems like even if the drives are formatted (blank), that the Snap is formatting them as 30GB partitions?




Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 31784 Private Mounted
Label:Private Contains system files only
Unique Id: 0x034A810D1753AF66 Mount: /priv Index: 12 Order: 0
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 33027584 Fixed

Logical Device: 1001E Position: 0 JBOD Size (KB): 32296 Free (KB): 31160 Private Mounted
Label:Private Contains system files only
Unique Id: 0x186F7E0768A636D9 Mount: /pri2 Index: 13 Order: 1
Partition: 1001E Physical: 1001F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1001F Drive Slot: 3 IDE Size (KB): 33027584 Fixed

Logical Device: 10008 Position: 1 JBOD Size (KB): 32247200 Free (KB): 32214632 Public Mounted
Labelrive2 Single disk
Unique Id: 0x034A810D1753AF66 Mount: /1 Index: 1 Order: 2
Partition: 10008 Physical: 1000F FS Size (KB): 32694304 Starting Blk: 41532 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 33027584 Fixed

Logical Device: 10018 Position: 2 JBOD Size (KB): 32247200 Free (KB): 32214648 Public Mounted
Labelrive2 Single disk
Unique Id: 0x186F7E0768A636D9 Mount: /3 Index: 3 Order: 3
Partition: 10018 Physical: 1001F FS Size (KB): 32694304 Starting Blk: 41532 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 33027584 Fixed

[blue68f100]

What I am seeing is, that the controllers are mounting all of the drives as slaves 10008, 10018. Either try forcing them to MASTER using the jumper block, or single drive. You apear to have a early v2000 mb which was also used in the 4000's.

If you have a copy of assist, do a factory reset.

Reload the OS, it's acting like it's a v2 or you have the jumper on the drive limiting the capacity.

Try using the mfg drive utility and do a quick MBR format. Some utilities allow you to set capacity. Have it read the drive settings and capacity.

You will get there, some just like being problem child.

If these are Mxtor drives, they have always caused problems.