HELP - Snap 2000 - going into PANIC!

[bigkris74]

Hi,

I have been experiencing a problem with my Snap 2000 recently. I bought some new drives to upgrade but before I installed them, I backed up all the data (or was trying) using FTP to another external PC and USB drive.

I was only able to get about half way through before the Snap would got into PANIC, drop off the network and require pulling the plug to get it to restart. When it did, it would run a check of the drives and begin a mirror resysc. Obviously, this slowed my backup but I persisted and got the data off.

I have now replaced the drives with WD 320Gb (WD3200AAJB) but the Snap continues to go into PANIC while trying to sync the mirror. It seems to run for just under 6 hours each time before failing and locking up.

I have checked all fans and are operating fine, I've tried 2 different RAM modules with no change.

I have persisted with this since Saturday and seem to be getting nowhere, I would appreciate any help.

Thanks.

Here is a copy of the log from 1 instance -

Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 13/8/2007 13:25:34
F PANIC : Maximum yield time exceeded at $002BCEC4 System 13/8/2007 13:25:34
I SNTP : Update from time server 158.195.34.117 successful System 13/8/2007 7:33:05
I System Initialization : Initialization Complete! Memory to be released: 46859472 bytes. System 13/8/2007 7:32:59
I File System : Opened FDB for device 0x50000 Disk 50000
Mirror 13/8/2007 7:32:59
I File System Check : partition is clean. Disk 50000
Mirror 13/8/2007 7:32:59
I File System Check : Executing fsck /dev/rmirr0 Disk 50000
Mirror 13/8/2007 7:32:59
I File System : Opened FDB for device 0x10016 Disk (Priv) 13/8/2007 7:32:59
I File System Check : partition is clean. Disk (Priv) 13/8/2007 7:32:59
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 13/8/2007 7:32:59
I File System : Opened FDB for device 0x10006 Disk (Priv) 13/8/2007 7:32:59
I File System Check : partition is clean. Disk (Priv) 13/8/2007 7:32:59
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 13/8/2007 7:32:59
I INIT: Setting IP address to 192.168.1.3 Network 13/8/2007 7:32:54
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 15 System 13/8/2007 7:32:54

System Details -

Model Software Hardware Server # BIOS
2000 series 4.0.860 (US) 2.0.0 58xxx 2.0.282

[blue68f100]

Check your cooling fans and make sure they are working. The 2000v2 are temp controlled by the cpu, most users have set them up to run 24/7. The cpu controls allow the cpu to get real hot before kicking in. Re-seat the ram chip too.

When you swapped HD's, did you break the raid 1 or just installed them (both at the same time) ?

[bigkris74]

Thanks for your reply.

I have reseated RAM several times, including trying 2 different modules (original 64Mb and 256Mb).

I did break the Raid 1 before removing the original drives as that was the only way I could complete a full data backup. Drives seem to run fine in JBOD config, the problem only appears either while original 80Gb drives were in Raid 1 or while trying to sync new drives to Raid 1.

Both fans are working. The main fan I have replaced with an uprated CFM fan but the CPU fan is still the temp controlled original setup. I've checked and the CPU fan is cycling on and off but I will try rewiring it to run full time.

Any further ideas would be great.

Cheers,
Kris.

[bigkris74]

BTW, I did search this error and although a couple of people have experienced this same log error, no one seemed to come up with a solution.

Thanks again.

[Phoenix32]

David, drives have a different start point (init in different OS)?

my 2 cents

[blue68f100]

To find that out we need the resutls of "co de info" from debug

[bigkris74]

Pre-Mirror "co de info"

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

Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 31288 Private Mounted
Label:Private Contains system files only
Unique Id: 0x1850F9661B32B6C6 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): 312570880 Fixed

Logical Device: 10000 Position: 1 JBOD Size (KB): 306460800 Free (KB): 306154032 Public Mounted
Label: Drive1 Single disk
Unique Id: 0x28E79A8F034B7D7E Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 FS Size (KB): 310709464 Starting Blk: 232549 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 312570880 Fixed

Logical Device: 10010 Position: 2 JBOD Size (KB): 306653744 Free (KB): 306346768 Public Mounted
Label: Drive2 Single disk
Unique Id: 0x1850F9661B32B6C6 Mount: /2 Index: 2 Order: 3
Partition: 10010 Physical: 10017 FS Size (KB): 310905096 Starting Blk: 208095 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 312570880 Fixed

[bigkris74]

Hmmm .. The drives appear to be different sizes even though they are identical and purchased at the same time.

Using the Western Digital Diag tool, I ran a sector scan on the drives to detect bad sectors but it came up passed with no errors. Could it have marked some sectors bad without telling me? ... I'm sure they were reporting the same size earlier.

What have I done wrong?

[bigkris74]

I tried reformatting a couple of times to see what happened.

The log shows a few warning about cyl counts, etc ... are these something to be worried about?

I File System : Format complete Disk 10010
Individual 8/14/2007 6:47:18 PM
I File System : 303618MB in 37953 cyl groups (16 c/g, 8MB/g, 768 i/g) Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : /dev/ride2a: 621810192 sectors in 607237 cylinders of 16 tracks, 64 sectors Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : Warning: 496 sectors in last cylinder unallocated Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : Formatting /dev/ride2a Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : Process formatting device /dev/ride2a Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : Format complete Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : Opened FDB for device 0x10010 Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : All ACLs for device 0x10010, reset to defaults Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : Successfully initialized empty FDB for device 0x10010 Disk 10010
Individual 8/14/2007 6:37:30 PM
I File System : 303618MB in 37953 cyl groups (16 c/g, 8MB/g, 768 i/g) Disk 10010
Individual 8/14/2007 6:27:40 PM
I File System : /dev/ride2a: 621810192 sectors in 607237 cylinders of 16 tracks, 64 sectors Disk 10010
Individual 8/14/2007 6:27:40 PM
I File System : Warning: 496 sectors in last cylinder unallocated Disk 10010
Individual 8/14/2007 6:27:40 PM
I File System : Formatting /dev/ride2a Disk 10010
Individual 8/14/2007 6:27:40 PM
I File System : Process formatting device /dev/ride2a Disk 10010
Individual 8/14/2007 6:27:40 PM
I File System : Format complete Disk 10000
Individual 8/14/2007 6:27:40 PM
I File System : Opened FDB for device 0x10000 Disk 10000
Individual 8/14/2007 6:27:40 PM
I File System : All ACLs for device 0x10000, reset to defaults Disk 10000
Individual 8/14/2007 6:27:40 PM
I File System : Successfully initialized empty FDB for device 0x10000 Disk 10000
Individual 8/14/2007 6:27:40 PM
I File System : Closed FDB for device 0x10010 Disk 10010
Individual 8/14/2007 6:17:40 PM
I File System : 303427MB in 37929 cyl groups (16 c/g, 8MB/g, 768 i/g) Disk 10000
Individual 8/14/2007 6:17:30 PM
I File System : /dev/ride0a: 621418928 sectors in 606855 cylinders of 16 tracks, 64 sectors Disk 10000
Individual 8/14/2007 6:17:30 PM
I File System : Warning: 592 sectors in last cylinder unallocated Disk 10000
Individual 8/14/2007 6:17:30 PM
I File System : Formatting /dev/ride0a Disk 10000
Individual 8/14/2007 6:17:30 PM
I File System : Process formatting device /dev/ride0a Disk 10000
Individual 8/14/2007 6:17:30 PM
I File System : Closed FDB for device 0x10000 Disk 10000
Individual 8/14/2007 6:17:30 PM
I System Database : SDB has been written to flash at 2007/08/14 18:11:30. System 8/14/2007 6:11:30 PM
I System Initialization : Initialization Complete! Memory to be released: 221010960 bytes. System 8/14/2007 6:03:36 PM
I File System : Opened FDB for device 0x10010 Disk 10010
Individual 8/14/2007 6:03:35 PM
I File System Check : partition is clean. Disk 10010
Individual 8/14/2007 6:03:35 PM
I File System Check : Executing fsck /dev/ride2a /fix Disk 10010
Individual 8/14/2007 6:03:35 PM
I File System : Opened FDB for device 0x10000 Disk 10000
Individual 8/14/2007 6:03:35 PM
I File System Check : partition is clean. Disk 10000
Individual 8/14/2007 6:03:35 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000
Individual 8/14/2007 6:03:35 PM
I File System : Opened FDB for device 0x10016 Disk (Priv) 8/14/2007 6:03:35 PM
I File System Check : partition is clean. Disk (Priv) 8/14/2007 6:03:35 PM
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 8/14/2007 6:03:35 PM
I File System : Opened FDB for device 0x10006 Disk (Priv) 8/14/2007 6:03:35 PM
I File System Check : partition is clean. Disk (Priv) 8/14/2007 6:03:35 PM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 8/14/2007 6:03:35 PM
I INIT: Setting IP address to 192.168.1.3 Network 8/14/2007 6:03:30 PM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 3 System 8/14/2007 6:03:29 PM

[bigkris74]

OK, I've hard wired the CPU fan and started the mirror sync again, we'll see what happens ...

[bigkris74]

Well that's that, 3 minutes and 36 seconds shy of 6 hours, PANIC. Seems to be a time limited thing to me.

I System Initialization : Initialization Complete! Memory to be released: 221608848 bytes. System 8/15/2007 1:21:27 AM
I File System : Opened FDB for device 0x50000 Disk 50000
Mirror 8/15/2007 1:21:27 AM
I File System Check : partition is clean. Disk 50000
Mirror 8/15/2007 1:21:27 AM
I File System Check : Executing fsck /dev/rmirr0 /fix Disk 50000
Mirror 8/15/2007 1:21:27 AM
I File System : Opened FDB for device 0x10016 Disk (Priv) 8/15/2007 1:21:27 AM
I File System Check : partition is clean. Disk (Priv) 8/15/2007 1:21:27 AM
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 8/15/2007 1:21:27 AM
I File System : Opened FDB for device 0x10006 Disk (Priv) 8/15/2007 1:21:27 AM
I File System Check : Cleanup completed... Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : 18 files, 61 used, 3976 free (0 frags, 3976 blocks, 0.0%% fragmentation) Disk (Priv) 8/15/2007 1:21:26 AM
W File System Check : Clean flag not set in superblock (Fixed) Disk (Priv) 8/15/2007 1:21:26 AM
W File System Check : Modified flag set in superblock (Fixed) Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 5 - Check cylinder groups Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 4b - Check backlinks Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 4 - Check reference counts Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 3 - Check connectivity Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 2 - Check pathnames Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk (Priv) 8/15/2007 1:21:26 AM
I File System Check : ** Phase 1 - Check blocks and sizes Disk (Priv) 8/15/2007 1:21:26 AM
W File System Check : partition is NOT clean. Disk (Priv) 8/15/2007 1:21:24 AM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 8/15/2007 1:21:24 AM
I INIT: Setting IP address to 192.168.1.3 Network 8/15/2007 1:21:19 AM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 4 System 8/15/2007 1:21:18 AM
F Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 8/15/2007 1:04:34 AM
F PANIC : Maximum yield time exceeded at $002BCEC4 System 8/15/2007 1:04:34 AM
I System Database : SDB has been written to flash at 2007/08/14 19:13:32. System 8/14/2007 7:13:32 PM
I File System : Opened FDB for device 0x50000 Disk 50000
Mirror 8/14/2007 7:08:12 PM
I File System Check : partition is clean. Disk 50000
Mirror 8/14/2007 7:08:12 PM
I File System Check : Executing fsck /dev/rmirr0 /fix Disk 50000
Mirror 8/14/2007 7:08:12 PM
I File System : Opened FDB for device 0x10016 Disk (Priv) 8/14/2007 7:08:12 PM
I File System Check : partition is clean. Disk (Priv) 8/14/2007 7:08:12 PM
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 8/14/2007 7:08:12 PM
I File System : Opened FDB for device 0x10006 Disk (Priv) 8/14/2007 7:08:12 PM
I File System Check : partition is clean. Disk (Priv) 8/14/2007 7:08:12 PM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 8/14/2007 7:08:12 PM
I File System : Closed FDB for device 0x10016 Disk (Priv) 8/14/2007 7:08:09 PM
I File System : Closed FDB for device 0x10006 Disk (Priv) 8/14/2007 7:08:08 PM
I File System : Closed FDB for device 0x10010 Disk 50000
Mirror 8/14/2007 7:08:08 PM
I File System : Closed FDB for device 0x10000 Disk 50000
Mirror 8/14/2007 7:08:08 PM
I File System : Logical set device 50000 configured Disk 50000
Mirror 8/14/2007 7:08:08 PM
I File System : Device 10010 reconfigured as secondary member of mirror set 50000 Disk 50000
Mirror 8/14/2007 7:08:08 PM
I File System : Device 10000 reconfigured as primary member of mirror set 50000 Disk 50000
Mirror 8/14/2007 7:08:08

[blue68f100]

If you formatted under v3 then upgraded to v4, then installed the second drive, you must /reinit both drives. The 2 versions calculate the starting point dfferently. Then re check the starting points. Must be the same.

You may need to use the drive utility by WD and set the drive capacity so they match.

Then re-format the drives using the /init cmd. Drives should not be in raid. the SNAP OS does not like drives that are different capacty.

This is a MAJOR problem on 4x00 units. Don't see it very often on 2000.

[bigkris74]

OK, ran a low level format on both drives using an XP machine.

I have got both drives to match all the important numbers now so I'm going to give it one more try, if it doesn't work this time, I think the lot will be going on ebay!!!

08/16/2007 0:08:22 Command: co de info

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

Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 31976 Private Mounted
Label: Private Contains system files only
Unique Id: 0x512BC08F654820A1 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): 312570880 Fixed

Logical Device: 10000 Position: 1 JBOD Size (KB): 306460800 Free (KB): 306154048 Public Mounted
Label: Drive1 Single disk
Unique Id: 0x5C18B0EF57BA15FE Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 FS Size (KB): 310709464 Starting Blk: 232549 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 312570880 Fixed

Logical Device: 10010 Position: 2 JBOD Size (KB): 306460800 Free (KB): 306154064 Public Mounted
Label: Drive2 Single disk
Unique Id: 0x512BC08F654820A1 Mount: /2 Index: 2 Order: 3
Partition: 10010 Physical: 10017 FS Size (KB): 310709464 Starting Blk: 232549 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 312570880 Fixed

[blue68f100]

Starting blocks are now the same and you have the smaller drive in the correct position 10000. See what happens, should work now.

[bigkris74]

Grrrrr ... same thing. Just on 6 hours, PANIC!

I reckon it's software/OS problem. Can I downgrade the OS to an erlier version without bricking the unit?

I think the version I have around here somwhere is 3.4.805.

[blue68f100]

Have you tried re-loading the OS? (use Assist)

The 2000 has the OS in flashram and not be reversed.

Normally this is a hardware problem.

Do you have a different set of drives you can try? (250 or smaller)

[bigkris74]

Nup, reloaded OS from Assist. Resync, 6 hours later, PANIC!

I don't have any other drives to test, other than the original 80Gb drives I bought it with. I think because of the whole 6 hour thing, it must be a setting or software bug/"feature" that no one is aware of.

Me thinks I've had enough O' this shiat ...

System Initialization : Initialization Complete! Memory to be released: 221608848 bytes. System 8/16/2007 7:58:30 PM
I File System : Opened FDB for device 0x50000 Disk 50000
Mirror 8/16/2007 7:58:30 PM
I File System Check : partition is clean. Disk 50000
Mirror 8/16/2007 7:58:29 PM
I File System Check : Executing fsck /dev/rmirr0 /fix Disk 50000
Mirror 8/16/2007 7:58:29 PM
I File System : Opened FDB for device 0x10016 Disk (Priv) 8/16/2007 7:58:29 PM
I File System Check : partition is clean. Disk (Priv) 8/16/2007 7:58:26 PM
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 8/16/2007 7:58:26 PM
I File System : Opened FDB for device 0x10006 Disk (Priv) 8/16/2007 7:58:26 PM
I File System Check : partition is clean. Disk (Priv) 8/16/2007 7:58:26 PM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 8/16/2007 7:58:26 PM
I INIT: Setting IP address to 192.168.1.3 Network 8/16/2007 7:58:21 PM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 11 System 8/16/2007 7:58:20 PM
F Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 8/16/2007 7:42:59 PM
F PANIC : Maximum yield time exceeded at $002BCEC4 System 8/16/2007 7:42:59 PM
I System Database : SDB has been written to flash at 2007/08/16 13:45:59. System 8/16/2007 1:45:59 PM
I File System : Opened FDB for device 0x50000 Disk 50000
Mirror 8/16/2007 1:40:17 PM
I File System Check : partition is clean. Disk 50000
Mirror 8/16/2007 1:40:17 PM
I File System Check : Executing fsck /dev/rmirr0 /fix Disk 50000
Mirror 8/16/2007 1:40:17 PM
I File System : Opened FDB for device 0x10016 Disk (Priv) 8/16/2007 1:40:17 PM
I File System Check : partition is clean. Disk (Priv) 8/16/2007 1:40:17 PM
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 8/16/2007 1:40:17 PM
I File System : Opened FDB for device 0x10006 Disk (Priv) 8/16/2007 1:40:17 PM
I File System Check : partition is clean. Disk (Priv) 8/16/2007 1:40:17 PM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 8/16/2007 1:40:17 PM
I File System : Closed FDB for device 0x10016 Disk (Priv) 8/16/2007 1:40:13 PM
I File System : Closed FDB for device 0x10006 Disk (Priv) 8/16/2007 1:40:09 PM
I File System : Closed FDB for device 0x10010 Disk 50000
Mirror 8/16/2007 1:40:09 PM
I File System : Closed FDB for device 0x10000 Disk 50000
Mirror 8/16/2007 1:40:09 PM
I File System : Logical set device 50000 configured Disk 50000
Mirror 8/16/2007 1:40:09 PM
I File System : Device 10010 reconfigured as secondary member of mirror set 50000 Disk 50000
Mirror 8/16/2007 1:40:09 PM
I File System : Device 10000 reconfigured as primary member of mirror set 50000 Disk 50000
Mirror 8/16/2007 1:40:09 PM
I System Initialization : Initialization Complete! Memory to be released: 221010960 bytes. System 8/16/2007 1:38:05 PM
I File System : Opened FDB for device 0x10010 Disk 50000
Mirror 8/16/2007 1:38:04 PM
I File System Check : partition is clean. Disk 50000
Mirror 8/16/2007 1:38:04 PM
I File System Check : Executing fsck /dev/ride2a /fix Disk 50000
Mirror 8/16/2007 1:38:04 PM
I File System : Opened FDB for device 0x10000 Disk 50000
Mirror 8/16/2007 1:38:04 PM
I File System Check : partition is clean. Disk 50000
Mirror 8/16/2007 1:38:04 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 50000
Mirror 8/16/2007 1:38:04 PM
I File System : Opened FDB for device 0x10016 Disk (Priv) 8/16/2007 1:38:04 PM
I File System Check : partition is clean. Disk (Priv) 8/16/2007 1:38:04 PM
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 8/16/2007 1:38:04 PM
I File System : Opened FDB for device 0x10006 Disk (Priv) 8/16/2007 1:38:04 PM
I File System Check : partition is clean. Disk (Priv) 8/16/2007 1:38:04 PM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 8/16/2007 1:38:04 PM
I INIT: Setting IP address to 192.168.1.3 Network 8/16/2007 1:37:59 PM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 10 System 8/16/2007 1:37

[blue68f100]

It's a hardware problem. Software is not the problem. How do you have the drives setup as Both Master or CS?

Should be set to Master for a 2000v2. But if its not working try CS and see what happens.

[bigkris74]

I did a full rollback of the OS to 4.0.830.

The unit no longer goes into panic but still fails the sync on the 80Gb drives after about 1 hour 15 mins. At least the unit doesn't lock up and drop off the network.

Not sure I've got any further though, really.

I've changed to CS and restarted the sync. Only thing left to try is change the IDE cables to see if they are a problem, then it becomes a missle through a window ... lol

I File System : Closed FDB for device 0x10006 Disk (Priv) 17/8/2007 1:33:46
I File System : Closed FDB for device 0x50000 Disk 50000
Mirror 17/8/2007 1:33:46
I System Shutdown : In Progress... System 17/8/2007 1:33:30
I System Shutdown : in 3 seconds System 17/8/2007 1:33:27
E File System : Failed to resynchronize logical set 50000, error -1 Disk 50000
Mirror 17/8/2007 1:33:27
W File System : Device 0x00050000 busy - abort devSet Disk 50000
Mirror 17/8/2007 1:33:27
I System Initialization : Initialization Complete! Memory to be released: 47772912 bytes. System 17/8/2007 1:28:37
I File System : Opened FDB for device 0x50000 Disk 50000
Mirror 17/8/2007 1:28:37
I File System Check : partition is clean. Disk 50000
Mirror 17/8/2007 1:28:37
I File System Check : Executing fsck /dev/rmirr0 /fix Disk 50000
Mirror 17/8/2007 1:28:37
I File System : Opened FDB for device 0x10016 Disk (Priv) 17/8/2007 1:28:37
I File System Check : partition is clean. Disk (Priv) 17/8/2007 1:28:37
I File System Check : Executing fsck /dev/ride2g /fix /fixfatal Disk (Priv) 17/8/2007 1:28:37
I File System : Opened FDB for device 0x10006 Disk (Priv) 17/8/2007 1:28:37
I File System Check : partition is clean. Disk (Priv) 17/8/2007 1:28:37
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 17/8/2007 1:28:37
I INIT: Setting IP address to 192.168.1.3 Network 17/8/2007 1:27:56
S System Initialization : Server v4.0.830
Build Date: Dec 24 2003 19:04:13
Boot Count: 4 System 17/8/2007 1:27