Quote:
|
Originally Posted by kalex
I recently upgraded my drives to 300gb x 3. yesterday i added 4th 300gb drive and system picked it up and format it with no problems.
I removed my current raid 5 configuration which consisted of 3 disks and created new one. formating of the disks took over 2 hours but it was done. right now its already been 10 hours and its still rebuilding backup disk at 1%. Is this normal or should it be faster? anyway to check the logs to see if there is anything wrong?
here is what the log says right now:
I System Database : SDB has been written to flash at 2005/10/11 10:48:03. System 10/11/2005 10:48:03 AM
I System Initialization : Initialization Complete! Memory to be released: 70716864 bytes. System 10/11/2005 10:42:16 AM
I File System : Format complete Disk 60000
RAID 5 10/11/2005 10:42:16 AM
I System Database : Added share Java$. System 10/11/2005 10:42:16 AM
I System Database : Added share WebRoot$. System 10/11/2005 10:42:16 AM
I System Database : Added share SHARE1. System 10/11/2005 10:42:16 AM
I File System : Opened FDB for device 0x60000 Disk 60000
RAID 5 10/11/2005 10:42:16 AM
I File System : All ACLs for device 0x60000, reset to defaults Disk 60000
RAID 5 10/11/2005 10:42:16 AM
I File System : Successfully initialized empty FDB for device 0x60000 Disk 60000
RAID 5 10/11/2005 10:42:16 AM
I File System : 853779MB in 106723 cyl groups (16 c/g, 8MB/g, 768 i/g) Disk 60000
RAID 5 10/11/2005 8:52:06 AM
I File System : /dev/rraid0: 1748541312 sectors in 1707560 cylinders of 16 tracks, 64 sectors Disk 60000
RAID 5 10/11/2005 8:52:06 AM
I File System : Warning: 128 sectors in last cylinder unallocated Disk 60000
RAID 5 10/11/2005 8:52:06 AM
I File System : Formatting /dev/rraid0 Disk 60000
RAID 5 10/11/2005 8:52:06 AM
I File System : Process formatting device /dev/rraid0 Disk 60000
RAID 5 10/11/2005 8:52:06 AM
I File System : Opened FDB for device 0x1000E Disk (Priv) 10/11/2005 8:52:06 AM
I File System Check : partition is clean. Disk (Priv) 10/11/2005 8:52:06 AM
I File System Check : Executing fsck /dev/ride1g /fix /fixfatal Disk (Priv) 10/11/2005 8:52:05 AM
I File System : Opened FDB for device 0x10006 Disk (Priv) 10/11/2005 8:52:05 AM
I File System Check : partition is clean. Disk (Priv) 10/11/2005 8:52:05 AM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 10/11/2005 8:52:05 AM
I INIT: Setting IP address to 192.168.0.3 Network 10/11/2005 8:52:00 AM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 23 System 10/11/2005 8:52:00 AM
thanks
alex
|
There has been several reports of this happening in the 4000 models. The bad news is that most have given up, with no resolve
There was one resent post a couple of weeks ago of one installing 300gigs, but do not recall if he was runing RAID5.
I believe it is a problem with LBA48bit. Large drive >137gig. Snap locked it out in the 4000, so not to compete against the 4100. This bit need to be turned on.
Did you check the capacity of the RAID5 with just 3 drives?
Good Luck
Blue68F100