VESS Other Discussions

VesaRAID 1840i faulty backplain board

2017-12-12T11:38:08.0770000

Hi,
In the company i am working, i have inherited one not working VesaRaid 1840i device (totally out of warranty), according the legend, old admin trayed to upgrade FW and bricked the device.
I have powered up it. Managed to connect via serial cable. All looked good except, hdd lights were of. No physical disc detected. I have found the only critical error in the logs, that backplain FW update failed.
The question is could it be that previous FW upgrade some how "bricked" backplain board? Same error even now, if i am trying to upgrade FW.

1830i login problem

2017-10-16T16:39:34.6130000

I don't know the IP address of the VessRAID’s Management Port. I was trying to login by serial port, but after I press <ENTER> I only got

cli>

and that's it.

Manual says:
2. Press Enter once to launch the CLI.
3. At the Login prompt, type administrator and press Enter.
4. At the Password prompt, type password and press Enter.

Wher is "Login prompt"?

I found in manual:

Logging Back Into the CLI and CLU
To log into the CLI and CLU after a manual logout:
1. At the cli> prompt, type login followed by your user name and press Enter.
2. At the Password: prompt, type your password and press Enter.
3. At the username@cli> prompt, type menu and press Enter to open the CLU

but after that (I mean cli> login administrator <ENTER>) I got "invalid command" message.

VessRaid 1840i Dead

2017-05-03T18:00:47.2930000

I have 2 VessRaid 1840i systems. They have been running great for 5 years. Today 1 system is dead. I have swapped 1 of the power supplies with the second system . The "bad" power supply worked in the second system and the swapped power didn't work in the first system.

Any Ideas?

vess 1840i how to recover NO web interface, CLI indicates swmgmt.xml file is empty

2017-03-16T16:17:12.4670000

HOw does one fix the issue when the cli reports swmgmt xml file empty

the UNIT is in production, but we cannot access the WEB interface

can this file be rebuilt by setting a restore option?

2600i Lost indexing

2017-02-02T16:45:04.0670000

I have a 2600i and it lost its indexing and I can't see any data. How can I recover this? I also need the admin documentation as I can't find it on your site.

Array Rebuilding Issue

2017-01-31T16:49:45.6300000

We have a VessRAID 1840i enclosure, running with 12 drives via RAID6, and the remaining four designated as global spares. The For the last two weeks, the controller has reported the array as "OK, Rebuilding." In short, it seems to be rebuilding FROM Drive 6 TO drive 6, and has been "stuck" at 96%. Any attempt to pause the rebuilding process times out.

Thinking the drive itself was to blame, the rebuild was "stopped," only to have it kick us out of WebPAM and indefinitely gives a "the requested service is busy" error after any login attempt is made. We have daily backups performed to two additional locations (following the 3-2-1 rule). We had two drives go bad (one at a time), and the bad drives were replaced after the previous rebuilds had completed. The following steps have been taken:

The entire enclosure was turned off and turned back on.

The array was deleted and recreated, and the volume was reinitialized. The backup was then restored to the empty volume. (this cannot be repeated during business hours, as the network users need access to the files the volume contains)

The PDM service has been disabled temporarily, which has made no difference in the "rebuild" freeze.

Other than reflashing the firmware or replacing the drive that is currently stuck rebuilding at 96%, I am at a loss for how to correct this issue. The reason we chose the VessRAID enclosure was for the unparalleled data availability and redundency the enclosure provides, so this issue is very frustrating. It is out of warrenty, and our finance manager is insisting we exhaust every option before purchasing an extended support contract from Promise.

Any help/advice would be appreciated.

kernel reported iSCSI connection 1:0 error (1022-Invalid or unknown error code) state (3)

2017-01-26T22:01:13.2870000

On Fedora 25 with the 4.9 kernel, we run a VessRAID 1840i connected by iSCSI. Using rsnapshot and sync with nice and ionice, towards the end of the backup there are memory and kernel errors including:

kernel: connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 76580624, last ping 76585814, now 76591204
kernel: connection1:0: detected conn error (1022)
iscsid: Kernel reported iSCSI connection 1:0 error (1022 - Invalid or unknown error code) state (3)
iscsid: connection1:0 is operational after recovery (1 attempts)

I posted on serverfault but wanted to see if anyone has any ideas?

VessRaid 1840s not booting after power failure

2017-01-20T00:03:44.8300000

Hello.

After power failure DAS not booted (cicle rebooting). WebPam not available.

Log - http://pastebin.com/ZRhngsbC

Problem while booting 1830i, constant rebooting with crash dump

2017-01-17T08:50:59.6930000

Hi,

We have old 1830i which has worked fine. It has 12 disks which organized into two independent arrays. Recently we started a process of reorganizing a raid in the first arrays. Today it can’t boot and goes into process of constant rebooting.

We tried to remove all disks from the first volume (first 6 disks) and the server started successfully. All disks in the second arrays were visible. Then we tried to hot plug other 6 disks – and the server went into process of constant rebooting.

In the web log we see a line:

Jan 17, 2017 10:48:02 0x00040009 3F206A883F066904 0000000000000000 0000000000000000 0000000000000000 The controller has new crash information

Here is the part of the console log during boot process:

*** Special RedBoot Ver 3.06.0000.00 ***

+NAND flash ID = ad f1 00 1d

Ethernet eth0: MAC address 00:01:55:13:ab:d5

IP: 192.168.0.16/255.255.255.0, Gateway: 0.0.0.0

Default server: 0.0.0.0, DNS server IP: 192.168.0.5

RedBoot with SAS , Ver 3.06.0000.00

Built 15:26:16, Oct 24 2011

Platform: IOP348 (XScale) Core1, DDR2-533

IF_PCIX: 1, PCIe(x4) RC,

C1-step, IB Speed: 400MHz, Core Speed: 1200MHz

RAM: 0x00000000-0x20000000, [0x00058208-0x0f7b1000] available

FLASH: 0xf0000000 - 0xf0400000, 32 blocks of 0x00020000 bytes each.

== Executing boot script in 1.000 seconds - enter ^C to abort

RedBoot> fis load -t fs;fis load -t kernel

RedBoot> exec 0x01008000 -r 0x00800000 -s 0x800000 -c "console=ttyS0,115200 root=/dev/ram0"

Using base address 0x01008000 and length 0x0016f098

Uncompressing Linux................................................................................................. done, booting the kernel.

Using /islavista/fw/be_bbm.ko

Using /islavista/fw/isc813xx.ko

[ 57.680000] Internal error: Oops: 17 [#1]

[ 57.680000] Modules linked in: isc813xx be_bbm raid_core prom_osal

[ 57.680000] CPU: 0

[ 57.680000] PC is at InstallMigrationShadowStructures+0x110/0x16d4 [raid_core]

[ 57.680000] LR is at mgtSwapU16Ret+0x20/0x28 [raid_core]

Promise VessRaid 1840i - "hangs" on bootup - Booting Kernel

2016-12-11T15:58:10.7070000

Hi,

I brought the "old" VessRaid 1840i from my boss.

In the beginning everything was running fine: Made two raid 5 partitions and start to move importend files to it.

There the VessRaid is for privat use, I'm shutting it down everytime I'm not ussing it.

Now it don't start-up anymore and the managment port is on RED-Led.

When I check with the IOIOI-port I see it "hangs" on booting kernel (See attached file).

Also I see that the AX99796B - reset failed!

Mabey its because it was shut-down in a wrong way?

Can someone help me out to get the Vessraid start-up again or what to do.

Thanks in advanced - Rob.

VessRaid 1840i w/ Fedora 24 fdisk shows The backup GPT table is corrupt, but the primary appears OK,

2016-11-22T20:12:28.9970000

We are running Fedora 24 w/ a VessRAID 1840i and we are seeing these errors from the file system:

fdisk -l

The backup GPT table is corrupt, but the primary appears OK, so that will be used.

Disk /dev/sdc: 10.9 TiB, 11999999164416 bytes, 23437498368 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: gpt

Disk identifier: 50A8A779-6283-407D-9381-DF6F9872CC33

gdisk /dev/sdc1

GPT fdisk (gdisk) version 1.0.1

Warning! Read error 22; strange behavior now likely!

Partition table scan:

MBR: not present

BSD: not present

APM: not present

GPT: not present

Creating new GPT entries.

Command (? for help): >

b back up GPT data to a file

c change a partition's name

d delete a partition

i show detailed information on a partition

l list known partition types

n add a new partition

o create a new empty GUID partition table (GPT)

p print the partition table

q quit without saving changes

r recovery and transformation options (experts only)

s sort partitions

t change a partition's type code

v verify disk

w write table to disk and exit

x extra functionality (experts only)

? print this menu

Command (? for help): v

No problems found. 23437496220 free sectors (10.9 TiB) available in 1

segments, the largest of which is 23437496220 (10.9 TiB) in size.

Running fsck I get this:

fsck /dev/sdc1

fsck from util-linux 2.28.2

e2fsck 1.42.13 (17-May-2015)

/dev/sdc1: clean, 4555342/366211072 files, 634306700/2929687035 blocks

Is there any other utility that I can run to fix this error?

Thanks so much.

I need PROMISE VessRAID 1840i RJ11 –DB9 cable's specification

2016-11-08T16:22:52.3200000

I need PROMISE VessRAID 1840i RJ11 –DB9 cable's specification,

what's is the line sequence?

vess RAID 1830s , i can't reach to ethernet port always bcome Unidentified !!!!

2016-09-22T12:02:20.3100000

the machine become out of raid and 6 hdd going out of matrix !!!!!

also i can get authentication from ethernet even i put the DHCP and Getway and DNS with all ways unidentified !!!!!!

i can't read and write on the RAID !!!! any help here please !!!!!?

new hard drives not recognized

2016-07-27T20:19:05.7800000

Hello:

I would appreciate any help and/or suggestions on how to proceed here. Our company's 16-bay VessRAID 1840i device has two arrays configured, using 11 drives with 1 spare drive. This leaves 4 empty slots in the enclosure. We want to create a new array using 2 of the empty slots. When I insert two new 2TB drives into empty slots, the WebPAM PROe interface states that there are no drives on the slots. The new drives are not being recognized as physical drives. The drives are the same model numbers as existing already in the enclosure. The power/activity light on the drive trays displays green, and the disk status light is out. How can these new drives be configured and made available for use?

Andrew