Help with 4100 Cracked Raid - Trying to replace 1 Drive

[blue68f100]

With the hardware not supporting LBA48bit addressing the Software will not have any impact. But it is possiable they added a check to correct the error. Not likely being a snap. They did not plan on having these units upgraded.

[rpmurray]

I was just thinking of something slightly off topic.

On the 705N where I had a drive fail, it was drive 1 that failed. The new drive that I replaced it with formatted to about 32MB more than the original. Elsewhere in the forum, it was posted that the size of drive 1 is critical. Could the reason that the unit fails to rebuild the raid be because drive 1 is slightly larger than the other drives? If so, is there a way to use the format command to force it to format to the same size as the other drives?

I was just thinking that this unknown disk operation may be caused if drive 1 is slightly larger that any of the other three. Just an idea that popped into my head, may mean nothing.

[Phoenix32]

Is this 4100 a KNOWN GOOD unit? I agree here in what has been said about it not being a OS version issue. I have not done it myself, but there have been users here who have reported 160 GB drives used with no problems.

My suggestions at this point are

1- A bad 4100?
2- Some issue with the Maxtor Drives
3- Or maybe the OS is corrupt and just needs reloaded

In other words, pretty much what has already been said here. Something is not right here. This shoul dbe working, so I have to suspect the 4100 itself, either the hardware or the OS being corrupted.

[blue68f100]

Depending on mfg, some have utilitys to adjust the capacity. I know Hatichi has one for that. I would contact the mfg and see if they have a utility. It may be somthing not released to public, just for mfg of hardware. I bet if they have it, they will give it to you. Normally Snap has always said if it's with in 2% they work with out a problem. May be true if not drive 1. As history as shown.

[frankb3910]

The 160GB Maxtor's all formatted to exactly the same size, which surprised me after the problems I had with the 705 and the Quantum drives. To be honest, the drives are a little different, the labels of 2 of the drives are different but the model number and capacity are all the same and the physical appearance is identical. Hence my surprise when they all formatted to EXACTLY the same size.

I looked in the old posts on this forum and found another person with the same problem. He was able to make a raid-5 using THREE of the four drives with no problem. From reading his posts it sounds as if he was having the exact same problem I am having!

http://forums.procooling.com/vbb/showthread.php?t=13528

I am going to try building a RAID-5 out of 3 of the drives, and see what happens.

[rpmurray]

Before you try building the raid out of three drives, could you do an "info log t" from the command line? I'd like to see exactly where in the build it's dying.

[frankb3910]

I had already started trying to build a raid-5 from discs 1,2 and 3. Well I got the same result, here is the info log t:

Requested: Log=Temporary, Boot=N/A Direction=Fwd Types=All Source=All

10/27/2006 0:47:43 90 S SYS | System Initialization : Server v3.4.803
Build Date: Jan 15 2003 18:04:19
Boot Count: 90
10/27/2006 0:47:43 90 D SYS | Executable built by KEVIN
10/27/2006 0:47:43 90 D SYS | Hardware platform:2.2.1 Model:2 (256 MBytes) S/N:552180
10/27/2006 0:47:43 90 D SYS | ETH: Reset- Eaddr set to 00 C0 B6 08 6C F4
10/27/2006 0:47:43 90 D SYS | Update IP...
10/27/2006 0:47:43 90 I NET | INIT: Setting IP address to 192.168.168.103
10/27/2006 0:47:43 90 D SYS | Update IP...
10/27/2006 0:47:43 90 D SYS | Initial file system BIO cache size is 26838528 bytes, 3232 buffers
10/27/2006 0:47:43 90 D SYS | DISK: Initial ARBs: 3232 Memory: 530048
10/27/2006 0:47:43 90 D SYS | Code Page set to 437
10/27/2006 0:47:43 90 D SYS | QDL System is DISABLED
10/27/2006 0:47:43 90 D SYS | Disk cache flush enabled
10/27/2006 0:47:43 90 D SYS | SNMP agent disabled.
10/27/2006 0:47:43 90 D SYS | AFP: started
10/27/2006 0:47:43 90 D SYS | FTPD: 'FTPD' not started.
10/27/2006 0:47:48 90 D SYS | Intf: 0, dev: 0: Model: Maxtor 4G160J8
10/27/2006 0:47:48 90 D SYS | Firmware Rev: GAK819K0 Serial #: G80G9K5E
10/27/2006 0:47:48 90 D SYS | Intf: 1, dev: 0: Model: Maxtor 4G160J8
10/27/2006 0:47:48 90 D SYS | Firmware Rev: GAK819K0 Serial #: G8045FTE
10/27/2006 0:47:48 90 D SYS | Intf: 2, dev: 0: Model: Maxtor 4G160J8
10/27/2006 0:47:48 90 D SYS | Firmware Rev: GAK819K0 Serial #: G805HX6E
10/27/2006 0:47:48 90 D SYS | Intf: 3, dev: 0: Model: Maxtor 4R160L0
10/27/2006 0:47:48 90 D SYS | Firmware Rev: RAMB1TU0 Serial #: R40FZ6BE
10/27/2006 0:47:48 90 D SYS | RAID5Initialize: creating 64 worker threads
10/27/2006 0:47:48 90 D SYS | RAID5InitializeCache: allocated cache of 65526KB
10/27/2006 0:47:48 90 I L00 | File System Check : Executing fsck /dev/ride0g /fix /fixfatal
10/27/2006 0:47:48 90 I L00 | File System Check : partition is clean.
10/27/2006 0:47:49 90 D SYS | Update FDB 0x10006...
10/27/2006 0:47:49 90 I L00 | File System : Opened FDB for device 0x10006
10/27/2006 0:47:49 90 D SYS | Scheduled ACL Set and Propagate at /priv/os_private for FDB_ID_12
10/27/2006 0:47:49 90 I L00 | File System Check : Executing fsck /dev/ride1g /fix /fixfatal
10/27/2006 0:47:49 90 D SYS | Propagate on /priv/os_private: Success - 8 files, 0 dirs; Errors - 0 files, 0 dirs
10/27/2006 0:47:49 90 I L00 | File System Check : partition is clean.
10/27/2006 0:47:49 90 D SYS | Update FDB 0x1000E...
10/27/2006 0:47:49 90 I L00 | File System : Opened FDB for device 0x1000E
10/27/2006 0:47:49 90 D SYS | Scheduled ACL Set and Propagate at /pri2/os_private for FDB_ID_13
10/27/2006 0:47:49 90 I L01 | File System Check : Executing fsck /dev/ride3a
10/27/2006 0:47:49 90 D SYS | Propagate on /pri2/os_private: Success - 8 files, 0 dirs; Errors - 0 files, 0 dirs
10/27/2006 0:47:49 90 I L01 | File System Check : partition is clean.
10/27/2006 0:47:49 90 D SYS | Update FDB 0x10018...
10/27/2006 0:47:49 90 I L01 | File System : Opened FDB for device 0x10018
10/27/2006 0:47:49 90 D SYS | Scheduled ACL Set and Propagate at /3/os_private for FDB_ID_3
10/27/2006 0:47:49 90 I L02 | File System : Process formatting device /dev/rraid0
10/27/2006 0:47:49 90 D SYS | Propagate on /3/os_private: Success - 8 files, 0 dirs; Errors - 0 files, 0 dirs
10/27/2006 0:47:49 90 I D[80060000] | File System : Formatting /dev/rraid0
10/27/2006 0:47:49 90 I D[80060000] | File System : Warning: 768 sectors in last cylinder unallocated
10/27/2006 0:47:49 90 I D[80060000] | File System : /dev/rraid0: 532990208 sectors in 520499 cylinders of 16 tracks, 64 sectors
10/27/2006 0:47:49 90 I D[80060000] | File System : 260249MB in 32532 cyl groups (16 c/g, 8MB/g, 768 i/g)
10/27/2006 0:47:50 90 D SYS | AFP: Registering "SNAPPER". Net 65280, Node 244, Socket 40
10/27/2006 0:47:55 90 D SYS | AFP: Allocated 63 volumes, 16384 files, 256 users
10/27/2006 0:47:55 90 D SYS | AFP: initialization complete
10/27/2006 1:18:16 90 D SYS | No FDB, or FDB corrupt. Reverting to shadow FDB
10/27/2006 1:18:16 90 D SYS | Reverting to Default FDB: FDB missing or invalid
10/27/2006 1:18:16 90 D SYS | Reverting to Default FDB: Quotas have been turned Off
10/27/2006 1:18:16 90 I L02 | File System : Successfully initialized empty FDB for device 0x60000
10/27/2006 1:18:16 90 D SYS | Reverting to Default FDB: ACLs will be set to default
10/27/2006 1:18:16 90 I L02 | File System : All ACLs for device 0x60000, reset to defaults
10/27/2006 1:18:16 90 D SYS | Scheduled ACL Set and Propagate at /0 for FDB_ID_0
10/27/2006 1:18:16 90 I L02 | File System : Opened FDB for device 0x60000
10/27/2006 1:18:16 90 D SYS | Scheduled ACL Set and Propagate at /0/os_private for FDB_ID_0
10/27/2006 1:18:16 90 I SYS | System Database : Added share SHARE1.
10/27/2006 1:18:16 90 D SYS | System Database : Created path /0/os_private/Java
10/27/2006 1:18:16 90 I SYS | System Database : Added share Java$.
10/27/2006 1:18:16 90 I L02 | File System : Format complete
10/27/2006 1:18:16 90 D SYS | Propagate on /0: Success - 4 files, 3 dirs; Errors - 0 files, 0 dirs
10/27/2006 1:18:16 90 D SYS | Propagate on /0/os_private: Success - 4 files, 1 dirs; Errors - 0 files, 0 dirs
10/27/2006 1:18:16 90 D SYS | NFS: The hash table has been initialized.
10/27/2006 1:18:16 90 D SYS | NFS: the NFSID <--->FDBID cache has been initialised.
10/27/2006 1:18:16 90 D SYS | NFS Server Disabled.
10/27/2006 1:18:16 90 D SYS | suspend_factor = 1C7246
10/27/2006 1:18:16 90 D SYS | DISK: Additional ARBs: 18730 (Mem: 3071720) Total Arbs: 21962 (Mem: 3601768)
10/27/2006 1:18:16 90 I SYS | System Initialization : Initialization Complete! Memory to be released: 155533920 bytes.
10/27/2006 1:18:16 90 D SYS | Restarted process timing
10/27/2006 1:18:16 90 D SYS | RAID5Resync on array 0: started
10/27/2006 1:22:41 90 D SYS | RAID5Resync on array 0: 1% done
10/27/2006 1:23:43 90 I SYS | System Database : SDB has been written to flash at 2006/10/26 23:23:43.
10/27/2006 1:23:44 90 D SYS | fsd: The SDB is being burned... Complete!
10/27/2006 1:23:44 90 D SYS | fsd: The SDB Shadow is being burned... Complete!
10/27/2006 1:27:02 90 D SYS | RAID5Resync on array 0: 2% done
10/27/2006 1:31:24 90 D SYS | RAID5Resync on array 0: 3% done
10/27/2006 1:35:45 90 D SYS | RAID5Resync on array 0: 4% done
10/27/2006 1:40:05 90 D SYS | RAID5Resync on array 0: 5% done
10/27/2006 1:44:26 90 D SYS | RAID5Resync on array 0: 6% done
10/27/2006 11:52:54 90 D NET | INET: sendit: send err 39
10/27/2006 11:55:32 90 D SYS | RAID5Resync on array 0: 7% done
10/27/2006 11:58:20 90 I SYS | System Database : SDB has been written to flash at 2006/10/27 11:58:20.
10/27/2006 11:58:21 90 D SYS | fsd: The SDB is being burned... Complete!
10/27/2006 11:58:21 90 D SYS | fsd: The SDB Shadow is being burned... Complete!
10/27/2006 11:59:54 90 D SYS | RAID5Resync on array 0: 8% done
10/27/2006 12:04:15 90 D SYS | RAID5Resync on array 0: 9% done
10/27/2006 12:08:40 90 D SYS | RAID5Resync on array 0: 10% done
10/27/2006 12:13:03 90 D SYS | RAID5Resync on array 0: 11% done
10/27/2006 12:17:27 90 D SYS | RAID5Resync on array 0: 12% done
10/27/2006 12:21:48 90 D SYS | RAID5Resync on array 0: 13% done
10/27/2006 12:26:14 90 D SYS | RAID5Resync on array 0: 14% done
10/27/2006 12:30:37 90 D SYS | RAID5Resync on array 0: 15% done
10/27/2006 12:35:01 90 D SYS | RAID5Resync on array 0: 16% done
10/27/2006 12:39:26 90 D SYS | RAID5Resync on array 0: 17% done
10/27/2006 12:43:47 90 D SYS | RAID5Resync on array 0: 18% done
10/27/2006 12:48:11 90 D SYS | RAID5Resync on array 0: 19% done
10/27/2006 12:52:30 90 D SYS | RAID5Resync on array 0: 20% done
10/27/2006 12:57:04 90 D SYS | RAID5Resync on array 0: 21% done
10/27/2006 13:01:24 90 D SYS | RAID5Resync on array 0: 22% done
10/27/2006 13:05:55 90 D SYS | RAID5Resync on array 0: 23% done
10/27/2006 13:10:23 90 D SYS | RAID5Resync on array 0: 24% done
10/27/2006 13:14:41 90 D SYS | RAID5Resync on array 0: 25% done
10/27/2006 13:19:06 90 D SYS | RAID5Resync on array 0: 26% done
10/27/2006 13:23:41 90 D SYS | RAID5Resync on array 0: 27% done
10/27/2006 13:28:12 90 D SYS | RAID5Resync on array 0: 28% done
10/27/2006 13:32:37 90 D SYS | RAID5Resync on array 0: 29% done
10/27/2006 13:37:06 90 D SYS | RAID5Resync on array 0: 30% done
10/27/2006 13:41:36 90 D SYS | RAID5Resync on array 0: 31% done
10/27/2006 13:46:06 90 D SYS | RAID5Resync on array 0: 32% done
10/27/2006 13:50:29 90 D SYS | RAID5Resync on array 0: 33% done
10/27/2006 13:55:02 90 D SYS | RAID5Resync on array 0: 34% done
10/27/2006 13:59:33 90 D SYS | RAID5Resync on array 0: 35% done
10/27/2006 14:03:57 90 D SYS | RAID5Resync on array 0: 36% done
10/27/2006 14:08:27 90 D SYS | RAID5Resync on array 0: 37% done
10/27/2006 14:12:59 90 D SYS | RAID5Resync on array 0: 38% done
10/27/2006 14:17:32 90 D SYS | RAID5Resync on array 0: 39% done
10/27/2006 14:22:07 90 D SYS | RAID5Resync on array 0: 40% done
10/27/2006 14:26:44 90 D SYS | RAID5Resync on array 0: 41% done
10/27/2006 14:31:18 90 D SYS | RAID5Resync on array 0: 42% done
10/27/2006 14:32:33 90 D SYS | DISK: req=0x68EC9A0 dev=0xC0000 fn=1 blk=0x6D3FD60 sts=20
10/27/2006 14:32:37 90 D SYS | DISK: req=0x68EC9A0 dev=0x80000 fn=1 blk=0x6D3FD60 sts=20
10/27/2006 14:32:37 90 D SYS | RAID5Resync on array 0: read to cache failed (20)
10/27/2006 14:32:38 90 D SYS | RAID5Resync on array 0: failed
10/27/2006 14:32:38 90 E L02 | File System : Failed to resynchronize logical set 60000, error -1

eventLogGetRecord() printed 128 records at 10/27/2006 16:15:31


It appeared that the drives 1,2 and 3 all have the same Firmware.
**** Does ANYONE know the meaning of "Failed to resychronize logical set 60000, error -1 ???

[snap-tech]

There was 2 version of the AS 60 drive that snap used. One has approx 2 million more sectors than the other.

You would need to run a special disk written by quantum to resize the smaller drive and regain the sectors.

I have the disk but will not be easy to locate and might take a few days. In the mean time you can use a larger drive if you have one.

Let me know where you stand at this time and how you would like to proceed.

The original

Snap-Tech [TECHNICAL SUPPORT LEAD ENGINEER] For snap Appliances.

Douglas (dfullersnap@yahoo.com)

[rpmurray]

Originally Posted by frankb3910

**** Does ANYONE know the meaning of "Failed to resychronize logical set 60000, error -1 ???

That's just a generic error indicating that it was unable to create the raid5. The stuff that would tell you why are the lines above it, specifically:

10/27/2006 14:32:33 90 D SYS | DISK: req=0x68EC9A0 dev=0xC0000 fn=1 blk=0x6D3FD60 sts=20
10/27/2006 14:32:37 90 D SYS | DISK: req=0x68EC9A0 dev=0x80000 fn=1 blk=0x6D3FD60 sts=20
10/27/2006 14:32:37 90 D SYS | RAID5Resync on array 0: read to cache failed (20)
10/27/2006 14:32:38 90 D SYS | RAID5Resync on array 0: failed

This would require a Technical Support Lead Engineer from Snap Appliances to decipher it.

I blame everything on KEVIN

10/27/2006 0:47:43 90 D SYS | Executable built by KEVIN

[rpmurray]

frankb3910, just to be a completist, try creating the raid5 using disks 1, 2, and 4 since they all have the same firmware. If this works that would help firm up my conviction that snaps just don't like drives in a raid5 unless they all have the same firmware.

Edit: Whoops, ignore this. It looks like you already changed the drives around based on the listing you posted, and drives 1, 2, and 3 now have the same firmware. Oh well, back to the drawing board. But you still might want to try it using different combinations of the drives just to see if one of them might be having some problems with some sectors.

[re3dyb0y]

Originally Posted by rpmurray

I blame everything on KEVIN

10/27/2006 0:47:43 90 D SYS | Executable built by KEVIN

Damn right

[blue68f100]

This KEVIN name alway show up in the Snap OS logs.

YES ..... He's the one that caused all of the problems.

[Phoenix32]

P-L-E-A-S-E tell me Snap-Tech's name is not Kevin.

(Snap-Tech, I am just having fun, don't get upset)

[snap-tech]

Nope, My name is not Kevin. It's Douglas. Thank God.

To be Honest, we always joked around in the support department as to who Kevin was. Nobody knew. I think he was someone who was there when snap was meridian data before quantum purchased it.

To make this more simple for me to help at this point rather than going through all these posts.

You are able to gain access to data correct, but raid is running in degraded mode or is this incorrect.

email me the following logs please

in dev
in dev pa
in dev ph
i l p -1

save all of them as html only.

There are no issues with drives that do not have same firmware. or even not the same size. Of course it will only build raid using size of the smallest drive.

The following error is a disk error but I cannot remember how to decifer which drive it is coming from. The only way we were able to fix this issue was by replacing the drive which is having the issue. what we called a Fru (field replacemet unit) in other words just a single drive that the customer would put in snap and send the bad one back to us.

DISK: req=0x68EC9A0 dev=0xC0000 fn=1 blk=0x6D3FD60 sts=20
DISK: req=0x68EC9A0 dev=0x80000 fn=1 blk=0x6D3FD60 sts=20

I will look through my support stuff and see if I can find that info. may take me a day to find it.

also, can you look at that long sticker in front of the memory stick and tell me exactly what is says. even the rev letter at end which may have been writen in with a marker?

Douglas