broken 2/3 2200 snaps :0(

[magnets]

Hi,
I have three 2200 snaps, two worked and one never did. edit: turns out i have 2000 snaps not 2200
A had two 40Gb drives in it and is happy
B had two 20Gb drives in is and was full
C (we'll cross that bridge later)

i ran out of space on B and basically did very silly things and buggered it up.
Then...

I got two 40gb drives and used G4U to copy bit for bit from the A snap onto the two 40gb drives.

then i shoved the drives into B and turned it on, then i reset it and turned it on again.
All was happy for about 10 minutes, then my mirror died. Disk status is this:

now the other thing that is odd here is the size of the disk. i think that's a bit odd. interestingly before it died, i copied about 18Mb of data over.
Anyway, i have a whole bunch of dodgy 40Gb maxtor so i stuck another in and that's where i'm upto. the wiki suggest i run the code:

co de format 100DD /reinit

where dd is the dodgy drive (number 2 (or IDE1)), but when i type
info device 0
It gives me this:

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32232 Private Mounted
Label:Private partiti Contains system information
Mount: /priv Index: 0 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000

Logical Device: 50000 Position: 1 MIRROR_CRACKED Size (KB): 6431648 Free (KB): 6431624 Public Mounted
Label:Primary disk 1 40Gb Maxtor
Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 MIRROR (Logical: 50000) Size (KB): 6521318 Starting Blk: 8707 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000
** Invalid Partition Id: 7FFFFFFF

So my questions are:

How can i get it to report 40Gb
What is my DD?

sorry i'm such a noob.
Here are some other screenshots which may help you

not sure why only 1 disk appears..presumably becuase the secondary is not formatted...


hmmm lots of errors there...
The About page says:
Software Hardware Serial# BIOS
2.0.279 2.0.0 39978 2.0.252

[re3dyb0y]

Thanks for all the info

David usually remembers drive stuff off the top of his head.

However, in the debug, type config devices info and that will make a full drive list and we can work out whats going on

I believe the drive Numbers at 10008 and 10010 or something


Report back Please

[magnets]

Hi, thanks for getting back.
config devices info gives me:

Command: config devices info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32232 Private Mounted
Label:Private partiti Contains system information
Mount: /priv Index: 0 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000

Logical Device: 50000 Position: 1 MIRROR_CRACKED Size (KB): 6431648 Free (KB): 6431624 Public Mounted
Label:Primary disk 1 40Gb Maxtor
Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 MIRROR (Logical: 50000) Size (KB): 6521318 Starting Blk: 8707 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000
** Invalid Partition Id: 7FFFFFFF


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

[blue68f100]

Blues back,

The 2x00 have 10000 and 10010 physical drive id's.

The log say member 1 is missing.
10000 say mirror cracked, but shows invalid partition. Size is wrong 6 gig????

10010 is non existance, MIA.

Quick test to verify that 10010 is MIA is to un-plug the power to the bottom drive.

Remember the jumpers for the drives should be set to master on both.

Once verfied, let me know what you are needing to do. Then we will set up an easy way to attack it.

Some how the partition table is not the correct size, on the 40gig drive. Should be around 36gig for 50000 slice (raid 1)

Is data backed-up ???????
It may change what we do.

[magnets]

Hi Blues,

Thanks for getting back.
The data has been moved accross to my main PC for the moment, no danger of loosing stuff (touches wood*)
this is my puppy:


so i'm not sure which one is lower, I reckon left (No.1 IDE0) will be primary Master and the one on the right (No.2) will be Secondary Master IDE1.
Working on that, i figured Disk 2 is the kaput one.
Swapped it over for another and then posted above. However, i've realised i already know how to fix this:
Re-image both drives from the working Snap server again.
so that's what i'm doing, i'll post again when they are back in the snap and i've run that device info command.
I'll also run the command with just Disk1 in.

I think what could be upsetting it is i'm using G4U to go from a Quantum 39Gb disk to a Maxtor EIDE 41Gb disk (basically the 40Gb has more sectors), i'm wondering if that's confusing it, as it's looking at the last sector expecting to see a copy of the FAT and just sees garbage (all the 40Gb drives wiped to Russian DOD standard prior to use)

I'll post when G4U finishes, it's doing the second disk now.

Magnets



*Gets tissue

[blue68f100]

THESE OLD UNITS DO NOT LIKE EIDE DRIVES.

I thought I read a 2200. the 2000 is different. Look at the jumpers some were M/S and some CS. The drive on the front should be the 10000 end of cable.

This model store the OS in flashram. All you need to do in install a new drive. Snaps prefer identical drives, at least within 2% of each other.

The easiest way to get it back up is change the drive config to JBOD (single). All data will be save on 10000 (front) if a working raid 1. Install the new 2nd drive 10010. The snap should auto format and prepare the drive for use. Once finished, Change the drive config back to RAID 1, should be good to go. The Snap uses a Modified XFS Unix file system. Can not read data in nothing but a snap. As long as the drive does not have a unix file system structure the snap will use the drive.

The best program to use is dd from knoppix. What ever program you use, must be able to read and transfter RAW data, other wise it will fail. Not really required since this model stores everthing it needs in flashram.

Good Luck

[magnets]

ah sorry, I thought I had 2200.
you read right.
Ok so I’ve got these 2000 snap servers....


The Maxtor’s are Eide but I thought if you just use a 40 core cable rather than 80 they will be backward compatible.

I looked at my working 40Gb snap and both drives are set as master on separate channels (primary ide and secondary). I have duplicated this setting on the maxtors.

Anyway, I have copied it across from a mirror set, so I think I should have broken the mirror first? Then copied the discs. If I can't get any joy I will have to use knoppix and the dd thingy (can you guess I’m a windows chap? )

So I’ve reimaged two more 40gb Maxtor’s based on the working snap.
I reset problem Snap and found it with the software tool.

Set date and time and name, restarted, it's found both drives (yay) and is now running a check.

Top tip: when you're changing the drives on these things, don't forget to unplug it completely!, that switch is a soft switch, it does not isolate you from the mains like a normal computer power supply switch. That big transformer you can see in the picture (post above) is live! My arm is still numb. I won't be doing that again. Should you be wondering why I would even be doing something as strange as leaving it plugged in: On your home computer many of the chips are static sensitive, if you build up enough charge in you, you can fry your computer. If you leave the lead in, but the switch on the power supply (not the button on the front) off, the Earth lead in the cable is still connected, same difference as wearing an earthing strap. IMHO

Right check is finished:

Yay, two drives, happy.
Still only 6Gb though
Hmmm, ok lets try mapping it in windows:

Hmm ok windows also feels it’s 6 gb.
I’m going to try and copy more than 6 gb into it
5.7Gb ok….

OOOOoo cockbadgers, I just got a message saying the disk is full. It really does appear to be 6gb partitions, how strange.


Ok, off to debug:

Command: config devices info

Logical Device: 10000 Position: 1 JBOD Size (KB): 6431648 Free (KB): 172712 Public Mounted
Label:
Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 6521318 Starting Blk: 8707 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32248 Private Mounted
Label:Private partiti Contains system information
Mount: /priv Index: 0 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000

Logical Device: 10010 Position: 2 JBOD Size (KB): 6431648 Free (KB): 6431632 Public Mounted
Label:
Mount: /1 Index: 2 Order: 2
Partition: 10010 Physical: 10017 FS Size (KB): 6521318 Starting Blk: 8707 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 6592000


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

So, any idea’s how I can make it see 40gb?

Thanks in advance.

[re3dyb0y]

Its amazing how much the interface has changed from V2

[blue68f100]

Magnets, It pretty easy to expand the size to actual, we do it all the time when we use an image to restore a dead one. Since you said you have your data backed up.

From debug enter "co de format 10000 /reinit" this will do the master.
Then " co de format 10010 /reinit" this will do the slave. These should be done seperately, a reboot is required between cmds. this should correct it.

I'm wondering if using the other program you have messed up the boot sector and mbr. At worst case you will need to do a format/erase all of sector 0. then install the drive into the snap, and let it do its thing. Lets see if the cmds above correct the problem.

[blue68f100]

Magnets, you seam to be over working the problem. Slow down and read some of these posts. With the 2000, NO EXTERNAL PROGRAM IS NEEDED. Everything needed is stored in flashram. You may want to consider moving up to v3 os.

As for the other (3rd) 2000, if no lights come on check the fuse (2A) on the power supply. If blown, look very closely at the shielding where the connection to the drives are made. It is thin and sharp enough to cut through the insulation and short it out.

[magnets]

Overworking moi?



yes, others may have commented something similar.

We'll worry about the third one later, the reason i ended up using external software to copy images was because i kept getting an error when trying to do it with the debug command (though i'm sure it was me doing something wrong).
So at present i have the two drives in the snap that both say 6gb, and i'd like to try and resize them.
From your advice
I go to debug and enter

co de format 10000 /reinit

and i get

Command: co de format 10000 /reinit

Device 10000 is currently mounted.
The requested operation will be executed after the next reboot.

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

well, Hot Piss! i didn't get that before. You're some sort of genius, or possibly i'm some sort of spanner.

I've restarted it via the restart command under Server Settings.

I'd love to upgrade to version 3.0 but i don't have any support aggreement with adaptec. I will have a search through the posts and see if i can find how others have done it. Not that worried at the moment though.

Ok right back into disc status, it says everything is ok, but still 6gb. The log is OK:



Now you mentioned:

I'm wondering if using the other program you have messed up the boot sector and mbr. At worst case you will need to do a format/erase all of sector 0. then install the drive into the snap, and let it do its thing. Lets see if the cmds above correct the problem.

I think you are correct!
Rather than bugger about, i'll go and get two more Maxtors and shove em in...

(goes on rummage)
(gets screwdriver)
(Goes to remove current drives)
(screams)
(unplugs snap)
(removes current drives)
(installs 'new' maxtors)

Ok complelety blank non partitioned drives are in the snap. Hmm double flashing.
lots of disk activity, ok normal flashing.
ok off to check disc status
hmmm it says exactly the same thing, both disks OK at 6gb. wierd.
i'll do another disk check


nope, no change, disks ok at 6gb, dispite them being blank when i put them in, i'm assumming it configured them at startup.

I was going to try and see what would happen if i started the server without any drives in, but i'll wait for your advice.

here is the info

Command: config devices info

Logical Device: 10000 Position: 1 JBOD Size (KB): 6431648 Free (KB): 6431632 Public Mounted
Label:
Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 6521318 Starting Blk: 8707 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32256 Private Mounted
Label:Private partiti Contains system information
Mount: /priv Index: 0 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 6592000

Logical Device: 10010 Position: 2 JBOD Size (KB): 6431648 Free (KB): 6431632 Public Mounted
Label:
Mount: /1 Index: 2 Order: 2
Partition: 10010 Physical: 10017 FS Size (KB): 6521318 Starting Blk: 8707 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 6592000

I'm wondering if the Snap doesn't like the Maxtor drives i'm using.
I'm using these:

Maxtor DiamondMax PLus 8
PDF data sheet from Maxtor

I notice one of the Jumper settings i can have is cap limit... it's not on thought (both drives are set to master). I think maybe they are not EIDE but UIDE.

I'm a bit confused to be honest.





A slight aside:
I'd like to say big thanks to everyone (espeically Blue and RB) who have helped me on this forum, without resources like this, people such as myself, and i daresay cleverer ones, would have no choice but to spend a stupid amount of time figuring it out or simply give up.

[magnets]

ok i'm impatient.
i decided to do a test. I took the two original drives out of the working 40gb snap2000 and place them in this problem one, it came straight up and i went striaght to disk status and saw this:



Now i don't know about you but surly this isn't expexted behaiviour?
There was nothign wrong wiht these two drives, thye had 40gb of data mirrored on them. (not any more!)

the only thing i can think of is that the 40gb snap is running a slightly different OS to the 20gb snap.

lets see, the problem one is:

Software Hardware Serial# BIOS
2.0.279 2.0.0 39978 2.0.252

and the orignal 40gb Snap is:

Model Software Hardware Serial# BIOS
2000 series 3.1.603 (UK) 2.0.0 55284 2.0.282

hmmm fair bit different.
i just put the orignal drives back in the orginal working 40gb snap server.
it says both drives are fine, sitting pretty with 6Gb capacity

*cry*

gonna try that co de format thingy

06/18/2006 16:23:57 Command: co de format 10000 /reinit

The requested operation will be executed after the next reboot.
Look in log for progress...

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

reboot....

OOOOOooooo



hello, i think i'm onto something.
OK, same to the other one...

it's formatting.

so, ok i guess the next step is to try that with the 40gb maxtors in that box.
If they work then the issue is simply the os on the 20gb snap.


SOrry, i should also qualify that when i refer to the size of the snaps i'm always meaning in mirrored config. so a 20gb snap has 2X20gb drives in it.

[magnets]

right.

handy tip:

Software Hardware Serial# BIOS
2.0.279 2.0.0 39978 2.0.252

is not able to format 40gb maxtor drives

the working 40gb snap running

Model Software Hardware Serial# BIOS
2000 series 3.1.603 (UK) 2.0.0 55284 2.0.282

formatted and is running the 40gb maxtors without issue.
i'm going to see what happens if i move both drives into Captain Dodgy

both drives appear perfectly happy
running at 6Gb capacity

i think we can safely say that the OS really does matter.
OK so next up...upgrading the OS on a snap 2000
(off to search the forums)

[magnets]

aHAHAHHhaaaaaaaaaaaaa

ok, one of my snaps was running version 3 and the other 2 was on version 2.

Followed the instructions on the cd that came with V3 to upgrade the other two to version V3

did the co de config thingy.

OOOO lovley 3 X 40Gb snaps.

yay
I am a happy camper.


Anyone know for sure weather these 40gb 7200 maxtors will toast the box? they have a running temp of up to 60 Celsius, and that's in a normaly case, let alone a snap 2000 box.
The devices won't be on for more than 12 hours at a time usually.

[magnets]

right i'm all done. Thanks for all your help.
I updated the snaps using the file called
snap_sys.sup
which came on the the snap version 3 CD.

To anyone else reading this:
Don't try to upgrade your Hard drives unless you are running 3 or above!

[jontz]

Thanks for all the info along your journey. This should be some good info for the Wiki section.

Maxtors do tend to run a little hotter than the seagates or wester digitals...I would look at upgrading the fan in your snap 2000 to something that moves more air than the stock one. Better safe than sorry!

[magnets]

agreed, the one that's going to be on all the time (nasmusic) is using the stock 40gb drives. i'll get some more fans for the two with maxtors in.

the other thing i was thinking of was cutting a port in the side of the case, using some thermal compound and sticking some stupidly large heatsinks onto it.

Also, if i change the IDE cable to 80 core and stick another two drives on (as slaves) will it see it do you think?
not sure the power supply would cope though.

[blue68f100]

The 2000 should have drives set as Master/slave. Some of the v2 were set to Cable select.

So if I read all of your notes, you were able to get the 40 gigs to work with v3. Snaps have had a history of not playing well with Maxtor's EIDE drives. And some times depending on the system, the capacity is set by the master.

If you are still having problems remove the slave (closes to the power supply) and work with jusst one drive. Once it sees everything corectly you can install the slave.

60 C is a little hot. Is your cooling fan running??? But these units were not design with 7200 rpm drive is mind. Most all original drives are 5400 rpm. If the fan fails your 2000 will end up like mine, fried. My fan would start up then shutdown after it got hot, being so quite I did not detect the problem in time. One morning I just got a message unable to connect to Snap#####. Damage done, lost 2 hd and system board.

Well if here is anything else you may need were here. Even though the time is almost 12 hr difference.

[re3dyb0y]

Originally Posted by jontz

Thanks for all the info along your journey. This should be some good info for the Wiki section.

Maxtors do tend to run a little hotter than the seagates or wester digitals...I would look at upgrading the fan in your snap 2000 to something that moves more air than the stock one. Better safe than sorry!

re3dyb0y looks over his shoulder

:P

[jontz]

Originally Posted by magnets

agreed, the one that's going to be on all the time (nasmusic) is using the stock 40gb drives. i'll get some more fans for the two with maxtors in.

the other thing i was thinking of was cutting a port in the side of the case, using some thermal compound and sticking some stupidly large heatsinks onto it.

Also, if i change the IDE cable to 80 core and stick another two drives on (as slaves) will it see it do you think?
not sure the power supply would cope though.

I believe that it won't see the other two drives, however even if it could the power supply wouldn't take the load, and you would be destroying the beauty that is a snap server: compact, network attatched storage. No one wants to see a Frankenstein snap server in their basement

[jontz]

Originally Posted by re3dyb0y

re3dyb0y looks over his shoulder

:P

Thats right mister, I'm talking to YOU!!!

[blue68f100]

Well maybe not.

I know a 2200 can be converted into a 4000. Uses the same MB if I recall. May require a BIOS flag change, though. The 2200 has 2 ide controllers. I have not seen the cabling of a v2 2000, I know a v1 has 1 ide controllers.

I recall a while back that a user had a 4000 that thought it was 2 drive unit. Got hung and couldn't reset.

[re3dyb0y]

Originally Posted by jontz

Thats right mister, I'm talking to YOU!!!

Ho Hum

If someone summerises, or gets it together, i will get it all done

[re3dyb0y]

Magnets: Have you got any problem if i use your pictures on the wiki?

And to accompany it, the stuff you've posted.

I will have to write it up into an article sorta going through what you've done



Cheers



Sam

[jontz]

Originally Posted by re3dyb0y

Ho Hum

If someone summerises, or gets it together, i will get it all done

I'm just messing with you. We all appreciate the work you have put into the Wiki section!