Snap 4400 major help requested - Please!

[xponet]

So my Story ...

I have a SnapAppliance 4400, was working great. Few days ago it started acting up. It would work ... then it would hang, and then I could no longer even ping it. Last night it kept booting into the recovery console mode. Sometimes it would boot to where it would come up normally, I could log in, and then it would just hang ... and I would not be able to ping it again.

This morning I was able to boot it up, I made a quick backup for recovery ... and I started to resync the drives. Things seemed to be going well. I just remoted into my computer to check on the progress to find that it lost connectivity again.

Previous to this, I had, and backed up the newest GuardianOS image so I could reinstall if something like this ever happened ... and of course, now I cant find it.

If I downgrade to the free version of the OS, am I going to lose everything?!?

Can someone please help me in trying to see what is wrong? Has this ever happened to anyone? I am starting to freak because I have a lot of information on this that I need....

I have the debug, which I will post below, but not sure if that helps with anything....

Diagnostics
This page shows some basic hardware information which may be useful in diagnosing problems with your Snap Server.
Kernel Version

5.0.133
200807301131


Attached Hard Disks
hda WDC WD3200AAJB-56WGA0
hdc WDC WD3200AAJB-56WGA0
hde WDC WD3200AAJB-00J3A0
hdg WDC WD3200AAKB-00WHA0

Attached devices:

Disk Partitions

major minor #blocks name

3 0 312571224 hda
3 1 16041 hda1
3 2 546210 hda2
3 3 1 hda3
3 4 311462739 hda4
3 5 273104 hda5
3 6 273104 hda6
22 0 312571224 hdc
22 1 16041 hdc1
22 2 546210 hdc2
22 3 1 hdc3
22 4 311462739 hdc4
22 5 273104 hdc5
22 6 273104 hdc6
33 0 312571224 hde
33 1 16041 hde1
33 2 546210 hde2
33 3 1 hde3
33 4 311462739 hde4
33 5 273104 hde5
33 6 273104 hde6
34 0 312571224 hdg
34 1 16041 hdg1
34 2 546210 hdg2
34 3 1 hdg3
34 4 311462739 hdg4
34 5 273104 hdg5
34 6 273104 hdg6
9 100 546112 md100
9 101 273024 md101
240 0 150000 trd

Platform Bytes

05.00.00


Model Byte

06


Bios Stamp

SN1Q3A01


Failsafe Stamp


BackplaneHW

BackplaneSW

Key

0


RawE2

Network devices

eth0 Link encap:Ethernet HWaddr 00:C0:9F:21:6B:88
inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:995953 errors:0 dropped:0 overruns:0 frame:0
TX packets:995933 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:77687643 (74.0 Mb) TX bytes:63758688 (60.8 Mb)
Interrupt:10

eth1 Link encap:Ethernet HWaddr 00:C0:9F:21:6B:89
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:9

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.50 0.0.0.0 UG 0 0 0 eth0


CPU Info

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Pentium(R) III CPU family 1266MHz
stepping : 1
cpu MHz : 1262.938
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 2529.10



PCI Devices

00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
00:0d.0 Ethernet controller: BROADCOM Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)
00:0e.0 Ethernet controller: BROADCOM Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)
00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05)
00:0f.3 Host bridge: ServerWorks GCLE Host Bridge
01:0b.0 Unknown mass storage controller: Promise Technology, Inc. PDC20275 (rev 01)
01:0c.0 Unknown mass storage controller: Promise Technology, Inc. PDC20275 (rev 01)
01:0d.0 SCSI storage controller: Adaptec AIC-7892A U160/m (rev 02)


Kernel Boot Messages

[1;32;40m****************************************** **********************
************************************************** **************
[1;33;40mLoad Guardian OS...
[1;37;40mVERSION: 5.0.133
DATE: 200807301131
[1;32;40m****************************************** **********************
************************************************** **************
[0;37;40mLinux version 2.6.16.21-gos-up (snap@BuildSys) (gcc version 4.1.0 (SUSE Linux)) #1 Wed Jul 30 11:32:35 PDT 2008
[1;32;40m****************************************** **********************
************************************************** **************
[0;37;40m<6>BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 000000000009f400 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001ffff000 (ACPI data)
BIOS-e820: 000000001ffff000 - 0000000020000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec02000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
On node 0 totalpages: 131056
DMA zone: 4096 pages, LIFO batch:0
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 126960 pages, LIFO batch:31
HighMem zone: 0 pages, LIFO batch:0
DMI 2.3 present.
Allocating PCI resources starting at 30000000 (gap: 20000000:dec00000)
Built 1 zonelists
Kernel command line: root=/dev/ram ramdisk=16384 vmalloc=256M console=ttyS0,115200n8 rw
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 1262.938 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 511176k/524224k available (2602k kernel code, 12576k reserved, 935k data, 152k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2529.10 BogoMIPS (lpj=5058206)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) III CPU family 1266MHz stepping 01
Checking 'hlt' instruction... OK.
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 3521k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfdb31, last bus=1
PCI: Using configuration type 1
qscsi init: Initializing qscsi internal data structures.
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Discovered peer bus 01
Setting up standard PCI resources
Qhwif: Found Platform MANTARAY,(ID=4020101)
Qhwif_ACPI: ----- Completed ACPI Initialization -----
Qhwif: Qhwif proc entries installed OK
Qhwif: qinfo proc entries installed OK
EXP_UNIT: 0x04020101 does not support Remora ExpUnits
EXP_UNIT: ExpPorts 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15, available for attached unit
Qhwif: Qhwif driver successfully loaded as manta driver
LEDdrv: LED driver successfully loaded for MantaType
audit: initializing netlink socket (disabled)
audit(1271720077.724:1): initialized
Enabling auto tuning proc hooks
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SGI XFS with ACLs, security attributes, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
SGI XFS Data Management API subsystem
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
xnvram: initializing platform Base=4020100
xnvram: xnvram installed OK
Real Time Clock Driver v1.12ac
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.3 $ 1 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Guessed IRQ 10 for device 0000:00:0f.2
ohci_hcd 0000:00:0f.2: OHCI Host Controller
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:0f.2: irq 10, io mem 0xfeadf000
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.16.21-gos-up ohci_hcd
usb usb1: SerialNumber: 0000:00:0f.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v2.3
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
snapfp: Snap Appliance Front Panel USB driver
usbcore: registered new driver snapfp
i2c /dev entries driver
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 3001.000 MB/sec
raid5: using function: pIII_sse (3001.000 MB/sec)
md: spare personality registered for level -5
md: md driver 0.91.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP route cache hash table entries: 8192 (order: 3, 32768 bytes)
TCP established hash table entries: 32768 (order: 5, 131072 bytes)
TCP bind hash table entries: 32768 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
TCP reno registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 5
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 152k freed
init_guardianflash_mtd: Starting...
platform = 4020101

init_guardianflash_mtd: Found Quanta Platform

init_guardianflash_mtd: Starting the Snap map
start_scan_addr = 98880000
init_guardianflash_mtd: chip probing idx=0
CFI: Found no Guardian.0 device at location zero
Found: AMD AM29F004BT
Guardian.0: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
SST Probe init_guardianflash_mtd:bank1 name:Guardian.0 size:80000
init_guardianflash_mtd: registering 1 whole flash banks at once
PDC20275: IDE controller at PCI slot 0000:01:0b.0
PDC20275: chipset revision 1
PDC20275: 100% native mode on irq 11
ide0: BM-DMA at 0xa400-0xa407, BIOS settings: hdaio, hdbio
ide1: BM-DMA at 0xa408-0xa40f, BIOS settings: hdcio, hddio
Probing IDE interface ide0...
hda: WDC WD3200AAJB-56WGA0, WD-WCARW6775315, ATA DISK drive
ide0 at 0xb800-0xb807,0xb402 on irq 11
hda: max request size: 512KiB
hda: 625142448 sectors (320072 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 hda3 < hda5 hda6 > hda4
Probing IDE interface ide1...
hdc: WDC WD3200AAJB-56WGA0, WD-WCARW6840234, ATA DISK drive
ide1 at 0xb000-0xb007,0xa802 on irq 11
hdc: max request size: 512KiB
hdc: 625142448 sectors (320072 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
hdc: cache flushes supported
hdc: hdc1 hdc2 hdc3 < hdc5 hdc6 > hdc4
PDC20275: IDE controller at PCI slot 0000:01:0c.0
PDC20275: chipset revision 1
PDC20275: 100% native mode on irq 5
ide2: BM-DMA at 0x8800-0x8807, BIOS settings: hdeio, hdfio
ide3: BM-DMA at 0x8808-0x880f, BIOS settings: hdgio, hdhio
Probing IDE interface ide2...
hde: WDC WD3200AAJB-00J3A0, WD-WCAV21271840, ATA DISK drive
ide2 at 0xa000-0xa007,0x9802 on irq 5
hde: max request size: 512KiB
hde: 625142448 sectors (320072 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
hde: cache flushes supported
hde: hde1 hde2 hde3 < hde5 hde6 > hde4
Probing IDE interface ide3...
hdg: WDC WD3200AAKB-00WHA0, WD-WCARW6351347, ATA DISK drive
ide3 at 0x9400-0x9407,0x9002 on irq 5
hdg: max request size: 512KiB
hdg: 625142448 sectors (320072 MB) w/16384KiB Cache, CHS=38913/255/63, UDMA(100)
hdg: cache flushes supported
hdg: hdg1 hdg2 hdg3 < hdg5 hdg6 > hdg4
Qhwmon: proc entries installed OK
drivers/misc/Qhwif/SnapExpUnit.c: 1285: Qhwmon ops initialized
expunit_process_initial_setup(): Pre-installed expansion Units!! Portmap: 0x00000000
Qhwmon: Hardware monitor driver successfully loaded as Manta driver
Qinfo: setup for MANTARAY
Qinfo: Reading from QinfoDB... CheckSum = 0000
Qinfo:0000: 00 c0 9f 21 6b 88 00 00 00 00 01 02 01 47 00 00 ...!k........G..
Qinfo:0010: 05 00 00 06 01 40 ed fe 0d f0 02 53 69 6c 6f 00 .....@.....Silo.
Qinfo:0020: 00 00 00 00 00 00 00 00 00 00 00 c0 a8 01 fa ff ................
Qinfo:0030: ff ff 00 c0 a8 01 32 c0 a8 01 32 00 00 00 00 a7 ......2...2.....
Qinfo:0040: ce fb 81 00 c0 a8 01 6e ff ff ff 00 c0 a8 01 32 .......n.......2
Qinfo:0050: 00 00 00 00 c0 a8 01 0a 01 64 6d 4c 49 a4 c4 4b .........dmLI..K
Qinfo:0060: 49 34 43 4c 49 01 00 00 00 ff 00 00 00 00 00 00 I4CLI...........
Qinfo:0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9f 63 ...............c
Qinfo: BIOS ByteString: START_ADDR=ffffffe0 LENGTH=32
Qinfo: BIOS ByteString: Raw="SN1Q3A01.........[...11/07/02...", 32 chars (isBiosStrChr filter)
Qinfo: start at 0, find an ascii BIOS string: "SN1Q3A01", 8 chars
Qinfo: Bios Version: :SN1Q3A01:
md: md100 stopped.
md: bind
md: bind
md: bind
md: bind
md: md100: raid array is not clean -- starting background reconstruction
raid1: raid set md100 active with 4 out of 4 mirrors
md: syncing RAID array md100
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
md: using 128k window, over a total of 546112 blocks.
md: md101 stopped.
md: bind
md: bind
md: bind
md: bind
raid1: raid set md101 active with 4 out of 4 mirrors
Filesystem "md100": Disabling barriers, not supported by the underlying device
XFS mounting filesystem md100
Starting XFS recovery on filesystem: md100 (logdev: internal)
Ending XFS recovery on filesystem: md100 (logdev: internal)
gosNIC: found MAC 0xc09f216b88
gosNIC: found MAC 0xc09f216b89
gosNIC: Found all NICs (2)
gosNIC: Register 2 NIC devices sorted by MAC
tg3.c:v3.49 (Feb 2, 2006)
eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:c0:9f:21:6b:88
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[763f0000] dma_mask[64-bit]
eth1: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:c0:9f:21:6b:89
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[763f0000] dma_mask[64-bit]
Qhwif: Detected transition to NORMAL, or RAMDISK. Enable watchdog management
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
spurious 8259A interrupt: IRQ7.
md: md100: sync done.
RAID1 conf printout:
--- wd:4 rd:4
disk 0, wo:0, o:1, dev:hda2
disk 1, wo:0, o:1, dev:hde2
disk 2, wo:0, o:1, dev:hdg2
disk 3, wo:0, o:1, dev:hdc2
trd: Ram disk of 150000k, as 300000 sectors of 512 bytes

[willPower]

.

[blue68f100]

Are any led's on the front panel indicate any problem when it fails. Like rapid flashing of the system, or no flashing? From what you describe indicates maybe a Power supply problem or other hardware failure.

If I recall GOS will not ALLOW you to install an older OS. So you should continue looking for yours. Or if you have a service contract just re-download it.

[willPower]

.

[xponet]

Originally Posted by blue68f100

Are any led's on the front panel indicate any problem when it fails. Like rapid flashing of the system, or no flashing? From what you describe indicates maybe a Power supply problem or other hardware failure.

If I recall GOS will not ALLOW you to install an older OS. So you should continue looking for yours. Or if you have a service contract just re-download it.

Yeah, thats the problem. Dont have service contract anymore... was part of one at a time, thats when I was able to download the software, thought I backed it up... and now that contact is expired and I am using this at home, cant shell out 700$+ or whatever it is. If they had a 1-time cost of like 50$ for the Software, with no support included ,that might be one thing ... but cant justify spending that.

I will look for lights, but I dont remember any flashing or anything. I think the first LED just stays green, and nothing else. Also, the HDD lights stay green with no flashing activity light.


BTW - How do I run the debug commands? When I get to the recovery console website, there isnt much I can do there except reboot ....

Thanks for all the responses so far!

[xponet]

Originally Posted by willPower

Forgot to mention that the URL for the recovery mode debug console is http://<snapserver>/debug.html

Thanks.


Also, can I run commands from the recovery console like to resync or check the drives? run any tests? etc?

I was thinking powersupply issue, however, if I boot to the recovery console and leave it there... I dont think it ever turns off or becomes unresponsive from the network. I would have to test to see.

[willPower]

.

[xponet]

Originally Posted by willPower

Yes, you can. Here's some commands that will help you resolve this problem:

mount: tells you if md100root is mounted. If it isn't, then there is a problem with either the root file system or the RAID1 set that it's on. Since GOS boots from drive 1 (hda), you might be able to get it to boot by removing drive 1 and restarting, which forces the boot from drive 2 (hdc).

cat /proc/mdstat: shows the active and inactive RAID sets.

mdadm (mdctl in GOS 4.x): assemble/start/stop/rebuild RAID sets. Use this to manually start a RAID if it doesn't start automatically. Might need to be used in the case of a failed drive or two or three. Note that md100root and md101swap are the only RAIDs that need to be active for the server to boot.

From here out, you're going to have to perform somewhat advanced Linux troubleshooting. I think you're experiencing a failing drive though.

Great, thank you. I will be trying this tonight.

so, if I run 'mount' and I see that both md100root and md100swap are mounted, then I am going to want to try mdadm and rebuild the raid? (rebuild as in what? I dont want to lose any data.....)

if I run mount, and md100root is not mounted, I will try removing drive 1 and letting it boot off drive two. If that works, then I will put in my spare HDD i have back in drive 1, so it can rebuild itself, and RMA drive 1 .... correct?

what would I be looking for in the cat /proc/mdstat command? Just to make sure md100root is active (if it does show as mounted) ?

Lastly, what is md100root is shown, and md101swap isnt?

Thanks for all your help so far!!!

-X

Thanks so far for every ones help!

[Max8]

Originally Posted by xponet

cant shell out 700$+ or whatever it is. If they had a 1-time cost of like 50$ for the Software, with no support included ,that might be one thing ... but cant justify spending that.

not sure what currency you are using but a 12 month software maintinance for a 4xxx model is a small percentage of what you would have paiod a few years ago...


Pricing is in USD
12 Months Phone/Tech Support any unit at any age + Software entitlement;
SWMAIN1E-S4000
1-Yr Software Maintenance, Snap 4000 Series
$98.00

Register yourself and your Snapserver on overland storages's support portal.

[xponet]

Originally Posted by Max8

not sure what currency you are using but a 12 month software maintinance for a 4xxx model is a small percentage of what you would have paiod a few years ago...


Pricing is in USD
12 Months Phone/Tech Support any unit at any age + Software entitlement;
SWMAIN1E-S4000
1-Yr Software Maintenance, Snap 4000 Series
$98.00

Register yourself and your Snapserver on overland storages's support portal.

Oh wow... 98$ ? ok, now thats something I can work with. I did actually try and put in my serial number, but it didnt take it. I will have to email them perhaps ...

[xponet]

One more question ... My drives keep trying to resync .... but it starts, maybe gets a few%, then stops responding again. I dont want to keep turning it on/off .... just want to get into recovery console so I can trying doing those debug commands. Thoughts/comments?

Its trying to "resync" now ... but can I put it off, pull drive 1 so it forced it to boot off drive 2, and be ok? Again ... I dont want to lose this data....

Thanks.

- One thing I have noticed, I am watching the HDD lights. Drive 2 pretty much just stays a solid Green and Orange while 1,3, and 4 keep blinking. The Snap Server reports every drive is good. Do you think there might be a problem on Drive 2? Should I try booting it up with that drive and see what happens?

Sorry for so many questions .... I have just never really had to troubleshoot this, ever.

One more thing I have noticed from the few times its trying to resync.... It takes FOREVER. I mean, I have done resycning before and I know it takes a while, but this is like a long time for maybe, 1%. It then goes to 150hours, then back to 10, then to 120, etc. Does that give an indication to a disk being bad? or something internal?

[Max8]

Originally Posted by xponet

Oh wow... 98$ ? ok, now thats something I can work with. I did actually try and put in my serial number, but it didnt take it. I will have to email them perhaps ...

Email to warranty@overlandstorage.com with your serial number & if you can log-in do an "cRTL + pRNT sCRN" and send the system status page that show the serial number...

If that email address does not work try warranties@ - not sure which one as it comes up in my email clients memory now and I am away from that PC atm...

Between the SnapAppliance to Adaptec change over many units went unrecorded untill the owners went to register them... or in many cases till they had their first issue and support was requested...

[willPower]

.

[xponet]

Thanks. Actually, these are still IDE drives . I just took out the hdd from drive2, so lets see what happens. I had a feeling that drive was bad from that orange light remaining on ... but never saw any error reports. Everything you said makes perfect sense.

Now to try and RMA this drive. I will let you know any updates.

Thanks again for all your help.

Btw Max8, I sent the picture in, thanks a lot.

[willPower]

.

[xponet]

=)

Btw, GREAT news (I hope I am not speaking to early) however, the RAID is now rebuilding, already at 5% after only like 20 minutes!!!

Before replacing that HDD, i was lucky to be at 1% after 20 minutes!... Then it never made it past 2% before it died.

So Yes, I think I can say it was a bad drive.

However, better that, then something major

BAD Drive is already RMA'd with WD. Their Advanced RMA process is so nice.

Thank you everyone for all your help, especially you willPower!

[blue68f100]

Info on the GOS purchase. Overland will not sell you the OS without them testing your hardware confirming it's good. Which is another $200?+ S&H. I wish they would do a GOS sale with no support for these old units and home users.

Glad you located the problem.

[xponet]

Really? What if I have a WORKING unit running GOS already?
I have been running "OS Version: GuardianOS 5.0.133 SP1" for a really long time now .... I would just like to have a backup copy (Which I had and I must have deleted? )

[willPower]

.

[xponet]

I see.

Well, great news on all fronts. Appliance is back up and running, Rebuilding of RAID has finished, I was able to register my Appliance because the "serial number" was actually the "Server Number", AND I found my backup of all my GOS images!

Thanks again everyone!

[Phoenix32]

Originally Posted by blue68f100

Info on the GOS purchase. Overland will not sell you the OS without them testing your hardware confirming it's good. Which is another $200?+ S&H. I wish they would do a GOS sale with no support for these old units and home users.

Glad you located the problem.

Yup, that is what I got told by them...

[Phoenix32]

Well, looks like I am a little late on this one (sorry, just been real busy), but I would have said it sounded like a bad or flakey drive to me...