Unknown Disk Operation Error (4100 & 705N)

[Tlester]

Hi all! I'm hoping you can help me with this error...

I now own both a Snap Server 4100 and a Dell PowerVault 705N. I have recently upgraded the OS to 3.4.805, BIOS 2.4.437, along with JAVA VM. Upgraded each to 256MB ram as spec'd here.

Here's the deal. On the 4100, I purchased it with 160GB Maxtor drives. It was working perfectly. Well, one of the drives failed. You may have seen a previous post regarding the same. So I purchased the 705N with 40GB Drives. Now, I needed another 160GB drive for the 4100 and 4 more for to replace the 40s in the 705n. So, I purchased the EXACT same models of Maxtors as were in the 4100 to begin with. I reformated each disk and configured each for raid 5. I did this via the web interface and not through the debug menu as specified in the field service guide.

Everything is working fine on both units, EXCEPT when I look at the disk status, it shows RAID 5, "Unknown Disk Operation Error"--on both units. My jumpers are all set to Master on the drives. Everytime I reboot it tries to rebuild the RAID and gets to somewhere beyond 30% before it goes to the error.

I have not run a REPAIR ALL ERRORS because last time I did I lost a drive while running in degraded mode--and we all know what hat means. This time, because I can copy all my data to the second unit, I could simply reformat everything and rebuild the raid, then copy it back.

Any suggestions?

[Hallis]

Can you copy and paste the error log here?

Shane

[Tlester]

System Initialization : Server v3.4.805
Build Date: Apr 21 2003 14:00:44
Boot Count: 55 System 10/5/2006 8:51:42 AM
S System Initialization : Server v3.4.805
Build Date: Apr 21 2003 14:00:44
Boot Count: 54 System 10/5/2006 7:51:43 AM
S System Initialization : Server v3.4.805
Build Date: Apr 21 2003 14:00:44
Boot Count: 53 System 10/5/2006 7:44:36 AM
E File System : Failed to resynchronize logical set 60000, error -1 Disk 60000
RAID 5 10/4/2006 8:11:23 PM
S System Initialization : Server v3.4.805
Build Date: Apr 21 2003 14:00:44
Boot Count: 52 System 10/4/2006 6:07:39 PM


Same for both units.

Here's the CO DE INFO:
10/05/2006 10:00:00 Command: co de info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22352 Private Mounted
Label:Private Contains system files only
Unique Id: 0x56F831CF396A5F18 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: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 21952 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2CC05B68259FD727 Mount: /pri2 Index: 13 Order: 1
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed

Logical Device: 60000 Position: 1 RAID_RESYNC Size (KB): 394855488 Free (KB): 359206824 Public Mounted
Label:RAID5 Large data protection disk
Unique Id: 0x3B8DD98B72DEE37A Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 134217216 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 134217216 Fixed

[Hallis]

When you put the origonal drives back in does the system behave normally?

Shane

[Tlester]

Haven't tried that. I'll try this evening.

-Tim

[Hallis]

That will tell us weather or not it's drive size specific.

Shane

[jontz]

I can almost guarantee you that Maxtor has changed something with the drive. Even though it is the same model number, there is something different about the controller on the drive that your snap does not like. Just out of curiosity, try putting a seagate 160 in your snap 4100, leaving the other maxtors in and see what happens.

[blue68f100]

Check to see if the Maxtor's drive is a ATA133. Snaps have a history of not playing well with this interface. If so see if the maxtor's utilities gives you an option to set the speed.

You may also try setting the jumpers to single drive. I think it gives you that option besides master/slave/CS.

[jontz]

I believe that Maxtors are just master/slave. WD is the only one I know of with the master/slave/single option.

[re3dyb0y]

Its funny, mine worked fine with the Maxtor ATA133 i had

Except the problems that its had with multiple different drives... But thats beyond the point as it didnt like the other board either


Believe Maxtors should have CS... Can dig one out of my spares draw

[jontz]

No, Maxtors ARE CS: Chicken Shi....er....stuff

[re3dyb0y]

Seagate FTW

[soapypotatoes]

There's no way a hard drive is causing this sort of controller issue...but yes...seagate FTW indeed....

[Hallis]

Maybe all the 4100's are falling apart?

[jontz]

Mine's fine...I think...holy crap I'd better check it....

[jontz]

Originally Posted by soapypotatoes

I'm getting the same error on my 4100 "Failed to resynchronize logical set 60000, error -1 Disk 60000" and have completely reformatted everything, swapped out one fo the drives, switched the position of the drives (shuffled them) and still nothing. Every time I use "co de resync 60000" it fails almost immediately. I've formatted numerous times and rebuilt the array from scratch several times as well, so I don't know whats going on.

Your mobo is TOAST. Sorry to be the bearer of bad tidings....

[re3dyb0y]

You mean Adaptec enabled the 4100 Kill Switch?

[soapypotatoes]

does anyone even know what the error "Failed to resynchronize logical set 60000, error -1 Disk 60000" means? What is actually failing on this guy's board?

[re3dyb0y]

I think its the reference number related to the raid set...

[soapypotatoes]

Any luck anywhere?

[blue68f100]

It could be a power supply. They can cause strange problems. Errors are the side affect.

[Phoenix32]

Originally Posted by blue68f100

It could be a power supply. They can cause strange problems. Errors are the side affect.

Tell me about it! LOL

This is what my 4000 (with bad power supply) was doing...

[soapypotatoes]

Try a set with only 3 drives at a time and shift it all around to remove the powersupply from the problem.......

[blue68f100]

Don't count the PS out unless all 4 drives work without errors. Phoenix has been chasing random errors on his, all due to a bad PS.

[Phoenix32]

Originally Posted by blue68f100

Don't count the PS out unless all 4 drives work without errors. Phoenix has been chasing random errors on his, all due to a bad PS.

YUP YUP!