Snap Server 2200 which drive?

[dhcernese]

I have a Snap Server 2200 originally with 2x WD 160GB drives. Fryes had a short sale on Seagate 400GB drives for $89 so I picked up two.

I did the dd of 25MB to both drives and installed both (as master on each cable).
The server booted and the web page works, but the primary drive is not "10000" as indicated in a lot of other threads:

10/24/2006 0:02:54 Command: co dev info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 31784 Private Mounted
Label:Private Contains system files only
Unique Id: 0x179C2C7F415FB318 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): 156290560 Fixed

Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 31288 Private Mounted
Label:Private Contains system files only
Unique Id: 0x179C2C7F415FB318 Mount: /pri2 Index: 13 Order: 1
Partition: 10016 Physical: 10017 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10017 Drive Slot: 2 IDE Size (KB): 156290560 Fixed

Logical Device: 10010 Position: 1 JBOD Size (KB): 153281104 Free (KB): 153127512 Public Mounted
Labelrive2 Single disk
Unique Id: 0x179C2C7F415FB318 Mount: /2 Index: 2 Order: 2
Partition: 10010 Physical: 10017 FS Size (KB): 155406176 Starting Blk: 110420 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 156290560 Fixed

Logical Device: 50000 Position: 2 MIRROR_CRACKED Size (KB): 153281104 Free (KB): 153127544 Public Mounted
Label:Mirror Data protection disk
Unique Id: 0x4EE7C6D0077E5280 Mount: /0 Index: 0 Order: 3
Partition: 10000 Physical: 10007 M 50000 Size (KB): 155406176 Starting Blk: 110420 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 156290560 Fixed


Which do I use?


10/24/2006 0:03:35 Command: co dev format 10000/reinit

Invalid device id 10000 requested

------------
Command returned with console error 1.

[dhcernese]

From the info, isn't the system file size 32MB? Not 25MB?

I found in another thread to use 10010 which I did, we'll see what happens after reboot.

[re3dyb0y]

Try
co dev format 10000 /reinit




It may be 32mb, but it really only needs the boot tracks and stuff



the easiest way with a working snap to move to new drives, is remove the 2nd drive, place in a enw one, let the snap init the drive, turn off, remove drive to primary, and repeat for 2nd drive


Sam

[Hallis]

Interesting. I did only 21mb on my drive and it worked fine. Try this. If you have an OS SUP file attempt to reinstall the OS.

Shane

[blue68f100]

Logical Device: 50000 Position: 2 MIRROR_CRACKED Size (KB): 153281104 Free (KB): 153127544 Public Mounted
Label:Mirror Data protection disk
Unique Id: 0x4EE7C6D0077E5280 Mount: /0 Index: 0 Order: 3
Partition: 10000 Physical: 10007 M 50000 Size (KB): 155406176 Starting Blk: 110420 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 156290560 Fixed

Did you use the same snap drive to copy the boot sectors to both drives? You should have a space between "10000 /renit"

The snap remembers the configuration of the drives. The reason it is showing a broken mirror.

There is a 10000 provided they are both set as MASTER. When you do the upgrades your doing. Get the first (TOP) up and working before adding the second drive.

Try the second drive (10010) and see it returns any errors. Verify the jumpers are set correctly, if so. Remove the drive ( should be top) and zero out the MBR. Reset jumpers, Re install. You only need one drive with the OS. It will auto format and transfer. If the second drive is formated to full capacity, so will the 1st one when installed if clean. The snap will not re-format (touch) a drive if it's reconizes the file structrure. The reason the drive must be clean. Seatools has a utility for a quick erase (MBR), that is all it needs.

Actually since you were in raid1, it would have been simpler letting the snap transfer the OS. All you needed to do was install 1 drive. the snap would have init and copied the os. The repalce the second one.

[dhcernese]

Maybe you missed it, I replied to my own post:

"I found in another thread to use 10010 which I did, we'll see what happens after reboot."

I was not clear: it works with 10010 (not 10000 as everyone keeps saying).
It was formatting when I left it last night, will get back to it this evening.

Thanks!

[dhcernese]

Originally Posted by Hallis

Interesting. I did only 21mb on my drive and it worked fine. Try this. If you have an OS SUP file attempt to reinstall the OS.

Shane

I do not, and I don't think it's on the CD that came with it. I'm running the version before the last update, where do I get a full .sup file?

[Hallis]

You can probably get it from Adaptec if your server is new enough. It will be about 12mb downloaded and about 30mb uncompressed. you want 3.4.807 Unless you're running Windows Server 2003 and use Active directory on your network.

shane

[dhcernese]

My warranty ran out, I'm not paying for anything at this point.. it's already running 4.something

[Hallis]

Ahh i see.

[shadowman]

Try setting your hard drive jumpers to CS (Cable Select). That works for me if it does not boot or format correctly.

[dhcernese]

Thanks for all the suggestions and everything, but it's all good. The mirror is building (taking overnight!). All I needed to change was 10000 --> 10010