large disk support

[gmcdermott]

We have just put 2 WD2500 250GB drives in one of our 2 snap 2000. Upgraded the os to 3.4.805. The unit has hardware version 2.0.0
Formated disck but still only shows 128GB on each disk.

Redid the os upgrade and reformnated - same thing.
Checked the jumpers. Old drives were both set as masters so set thes the same.

I looked at the threads but did not see anything on this.
Did I miss something?

[gmcdermott]

Also just tried Debug command
ide 48bitLBACounter get results 0
48bitLBACounter reset
then co de format 10000/reinit

same results.
Starts out prior to form showing 130Gb then to 128GB after format.

[gmcdermott]

Just as info - I have used this os file worked on my 1100

[blue68f100]

On trouble units, remove all HD's except the MASTER. Make sure you are in JBOD then use the "co de format 10000 /reinit" . Then check the capacity. If good you can install the 2nd HD.

If this does not work post hardware info (co de info).

[gmcdermott]

Thanks for your help.

Only master drive installed - jumpered as master. Ran co de format 10000/reint.
Same results 128GB
Following is hardware info

04/17/2007 18:38:07 Command: co de info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 24432 Private Mounted
Label:Private Contains system files only
Unique Id: 0x177351ED03537BF4 Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

Logical Device: 10000 Position: 1 JBOD Size (KB): 131554136 Free (KB): 131422528 Public Mounted
Labelrive1 Single disk
Unique Id: 0x177351ED03537BF4 Mount: /0 Index: 0 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 133377992 Starting Blk: 104775 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed


------------
Command executed without error.

[blue68f100]

Connect to the snap admin page then click on the SnapAppliance Logo, post results. Need to make sure your not working on a v1.

Since the OS is in flashram for v2, wipe the HD clean. Then reinstall the drive. Give it a clean start.

[gmcdermott]

gif attached.

Can the disk be loaded in a pc and fdisk?

[blue68f100]

The page you posted is not from the SnapAppliance Logo, generaly located on the left side of the main admin page.

[gmcdermott]

I'll try again in the am - can't access the server from home.
Thanks

[gmcdermott]

Image from clicking on snap logo attached

[blue68f100]

3 things to try.

That is a very early SN for your 2000.

1. Using the MFG utility make sure the size has not been reduced to 137gig. Some drives have a jumper that can control the cap. Do a quick format with the mfg utility, Which OS you use doesn't matter. Install letting the Snap prepare the HD. It take approx 10 min before you will be able to connect, while it copies the OS to the HD. OK ???
2. Set the jumpers to CS. * and try the /reinit agian. (WD has a singel drive jumper setting.)

Once the Master HD has it capacity correct the slave HD will be fine.

* Some of the older units were particular on the jumper settings.

[gmcdermott]

Success!
I installed each drive in a externat USB enclosure and ran Western Digital's setup/format program. Put one back in the 2000 and formatted it - shows up as 233GB each (guess that's close enough). I was going to run WD's low level format "000 program" but that would have taken forever.
They are both set up as JBOD for now with "cs" jumpers.
I'll worry about setting up to mirror later.
In case someone else is having similar problems, I trie to us Knoppix "shred" command last night but it wouldn't even mount the hd. Installed it as a slave on windows XP, bios say the drive but nothing would format, even fdisk.
Many thanks to blue68f100 for staying with me on this one.
I have another 2000 yet to do but it shopuld be a "snap" now (pun intended.

[blue68f100]

Snap has had a mix of drive configurations. Some of the early ones were M/S. While some of there early ones were C/S. I would not bother with the M/S. If it does not like M/S it may drop back to the 137gig.

[gmcdermott]

We set both drives as cs and Mirror - Raid 1. Seems to be humming along.
Question.
Is there a way to verify that Disk 1 (mirror) is actually capturing all the info stored and undated on Dist 2? That is, short of having a disk failure and needing it.
Thanks again for all the valuable information this forum provides.

[blue68f100]

You can run the disk utility from the gui or the debug cmd "co de fsck dev [[/fix /fixfatal /altsb]] (check device's filesystem)" .

[gmcdermott]

Thanks
I'll have a go at it.

[gmcdermott]

command returns
"Invalid device number requested"

[blue68f100]

What Dev number did you use?

50000 is the raid1 drive, where you HD are 10000, 10010

post your cmd that failed " co de fsck dev /fix

[gmcdermott]

I'm a true Neophyte

Exactly what string should I enter to check share1 and share2 (mirror)?
Thanks for your patience

[blue68f100]

If your showing 2 share you may not be in raid 1.

Remove one drive and see if you can read it, OK. Power down and try agian with the other.

actually the cmd should be something like this. "co de fsck 5000 /fix"

The snap does this cmd every time it is started. powerdown then look at the log files when it comes up.

[Soraz]

where find 3.4.805 ?
Thanks

lsorato@alice.it

[likemagic]

isohunt.com

look for snap os