logical set 60000, error -1

[calval35]

Hi,
I am getting this error " File System : Failed to resynchronize logical set 60000, error -1". I am assuming I have a bad disk?
But to replace a bad disk I need OS3.4 (At least that is my understanding)
If I am way off the mark here, please let me know. I don't have much experience with SNAP's. If I am not, I would really appreciate info on how to get 3.4.

thanks

Snap 4100
3.1.603
hardware:2.2.1
Bios:2.4.437

[blue68f100]

60000 is a raid5 partation.

You need to locate in the error log as to which drive is generating the error. Then replace that drive. Set as hot spare and it should then resync the set.

[calval35]

would I do this by entering debug mode? debug info?
You will have to excuse my SNAP ignorance.

Thanks again.

[blue68f100]

Once you get into the admin section there is gui at the bottom rt of the screen, above close.

or from debug try "in lo p -l" and "in de"

[calval35]

Great. Thanks.
I didn't see any disk or raid errors. File system error was reported though.
"File System Check : Failed to allocate 83841028 bytes for rcd_backlinks!!"

I will keep fumbling around.

Thanks for your assistance

[blue68f100]

Have you thought about resyncing the drives?

[calval35]

nope. how is that done?
Do you think upgrading the OS is good idea to?

Thanks again.

[blue68f100]

UP GRADEING IS NOT A GOOD IDEA WHEN YOU ARE HAVING PROBLEMS.

I think the cmd is "co de resync 6000"

[redrob]

What is the best course of action when this error occurs ? this is happening on a clients snapdrive and i am totally unfamiliar with these
TIA

BTW
It is a 4100 ,

[blue68f100]

That error is give when a drive is failing.

If you can still access the data, you should back it up and take the unit off line.

The course of action would be to look in the error log and see if you can determine which drive is failing. Replace the drive, set as hot spare, it shoud then rebuild the array.

[redrob]

where is the log that will be more specific about which it is only log i see is the "Server Log" , does the "-1" mean its the drive on channel 1

[blue68f100]

from debug "in de" will give details on devices
or "in lo p -1 " may help

60000 refers to the raid 5 array.

Drives are identified as 10000, 10007, 10010, 10017

[jontz]

To get to debug, in case you don't know, just add /debug to the end of the web address (ie, //(snapserver)/config/debug)

[calval35]

I can't figure out if there is actually anything wrong. The 4 drives are all listed. No errors?

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

Logical Device: 60000 Position: 1 RAID Size (KB): 220516096 Free (KB): 74287416 Public Mounted
Label:RAID5 Large data protection disk
Unique Id: 0x0D0BBF1266F233D8 Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 R 60000 Size (KB): 74524432 Starting Blk: 67806 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 75067904 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 74524432 Starting Blk: 67806 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 75067904 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 74524432 Starting Blk: 67806 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 75067904 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 74524432 Starting Blk: 67806 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 75067904 Fixed

[jontz]

Looks similar to the page I get when I debug mine, doesn't seem to indicate any drive failure. If you go into the normal config screen, go to disk utilities, and then view disk status, you should see the raid 5 array status. If you click on the array icon it should show you any disk failures/problems. Let me know what you see when you do that. If there isn't a drive failure you might need to re-sync the drives.

[calval35]

here goes:

E File System : Failed to resynchronize logical set 60000, error -1 Disk 1 5/10/2006 1:17:43 PM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/10/2006 12:18:50 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/10/2006 12:08:56 AM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/9/2006 12:18:25 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/9/2006 12:08:31 AM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/8/2006 12:18:04 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/8/2006 12:08:06 AM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/7/2006 12:17:26 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/7/2006 12:07:41 AM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/6/2006 12:17:17 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/6/2006 12:07:15 AM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/5/2006 12:16:42 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/5/2006 12:06:51 AM
I File System : Extended Rights Backup for device 0x60000 has completed successfully Disk 1 5/4/2006 12:16:18 AM
I File System : Extended Rights Backup for device 0x60000 has begun Disk 1 5/4/2006 12:06:25 AM
E File System : Failed to resynchronize logical set 60000, error -1 Disk 1 5/3/2006 11:37:52 AM

Thanks a bunch as the plot thickens.

[blue68f100]

DISK 1 has a problem.

If you have another 80 gig, hd, replace disk 1, set as spare. And let it do its think. All snap os can handle this.

Do you have a copy of SpinRite by GRC. I would remove disk 1 and seen if spinrite can repair it.

If I have some free time, I may pull one of my 2200 drives out and use it as a test.

You do have the data backed up don't you ???????????????

[calval35]

great thanks. Yes data is backed up daily!!!
As far as spinnrite is concerned, no I don't.
In the mean time I will order another 80gb hd. I actually have 4 120's, how much of a hassle would it be tor rebuild it all together?

[blue68f100]

The 4100 has OS stored in flashram. Just install the new drives and turn it on. Give it 5 min to copy the OS to HD before you connect. Let it finish formating, then build you Raid5 array. What could be easier.

[jontz]

Raid 5 array will take about 4 hours to build, FYI. When it is done just copy all of your data back over to it.

[ShrewLWD]

Hi everyone,

I have a 4100 (4.0.860, HW 2.2.1, BIOS 2.4.437) that was in RAID 5 (4x120Gig Maxtor). One of the drives crashed, so I shipped it off to Adaptec. They sent me a 160gig WD. When it rebuilds, I get the 60000 error -1 message.
In the log its;
File System: Failed to resynchronize logical set 60000 Disk 60000

When I run in lo p -1 it shows it gets to 71% done on RAID5Resync then shows 3 identical lines;
DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20
DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20
DISK: req=0x515EC60 dev=0xc0003 fn=1 blk=0xA39AD70 sts=20

followed by;
read to cache failed (20)

in de shows all 4 drives with their respective assigned names; 10007, 1000F, 10017, 1001F but no errors or issues.

What am I missing here to determine a) if it's a drive issue and therefore b) which drive?

I shut it down and reboot it, which causes it to go through its 4+ hours of resyncing, but it still stops at 71%

Any assistance would be appreciated!


UPDATE: This thread discusses it, and it appears dev=0xc0003 means drive 3? That's the replacement drive they sent me.

[blue68f100]

Can you currently read the data on the snap? If so back it up. If not what is the drive utility showing?

If the unit was upgraded it's possiable to have a different starting point. Snap changed the way they calculated the starting point. If you look at the "co de info" or "in de" closely the starting points should be the same. If not you have limited options. You need to pre-format the drive with the OS version used for the original ones.

Did the snap set the capacity to match the originals drives? If not use WD utility to set the size.

You may need to wipe the drives clean and start over.

[ShrewLWD]

We decommisioned this snap, and were in the process of reconfiguring it for a new job in our infrastructure when the drive crashed, so when I got the new drive I just broke the RAID and recreated it. We can do whatever we want to it at this point.
co de info shows the new drive does *not* have the same starting block.
So you are saying, break the raid, individually format the drive (using the format in the snap appliance?) then rebuild the raid?

When I built the raid with the new drive, it popped up saying like it was only going to use 119Gig of the drive to stay in compliance with Raid, so I assumed it formatted it at 119.

[blue68f100]

What you need to do is break the array. Then from debug issue "co de format XXXXX /reinit" . Where XXXXX is the drive ID's, 10000, 10008, 10010, 10018. Then recheck the starting points all should be the same and capacity may differ. If so the smallest drive must be in position 1.

[ShrewLWD]

OK, I broke the array, then sent that command to the 10010 drive (drive 3). While it's formatting, I did notice that upon breaking the array it formatted and reinitialized all the drives (or at least it said it was in the Disk Config view). Is the command you gave me going to do something different than what it did?

UPDATE: After running that command and re-running in de, the start block is still different than the others (the 3 originals are starting at 95927, this last one starts at 104776)

I don't see how formatting the others will make them jump up to that block, since he didn't bother to ask the others what block they are starting at.

Is there a different command to use?