Hello, friends. A disk in my cluster that was on the storage system crashed. There are no violations in the storage system. All arrays are fine, this is what the monitoring panel shows. The logs are empty. When running Redundancy Check on the array, an error occurs and a pause. array RAID 6. This RAID has 2 logical disks. One disk (logical) does not work, and the second one works. How can I recover data using VESS tools?
Vess R2600Ti HDD HELP ME
- 127 Views
- Last Post 2 weeks ago
doctor38 doctor38
posted this
3 weeks ago
- Last edited 3 weeks ago
doctor38 doctor38
posted this
3 weeks ago
doctor38 doctor38
posted this
3 weeks ago
doctor38 doctor38
posted this
3 weeks ago
Are there any options for restoring the raid? There is a spare disk available, but it is not clear which one to replace it with to restore the raid, because all disks work according to the system report.
doctor38 doctor38
posted this
3 weeks ago
The disk was rebuilt but nothing happened. Please help me.
R P
posted this
3 weeks ago
- Last edited 3 weeks ago
Hi,
Be advised that the rebuild is not finished, the rebuild is currently at 90%.
------------------------------------------------------------------------------- Rebuild Progress: =============================================================================== DaId SeqNo State Type PdId PdPercentage LdId LdPercentage =============================================================================== 1 5 Running Rebuild 11 90 3 86
The rebuild is on LD3, but the problem seems to be the write check entries on LD1, which will result in the LD1 LUN being READ ONLY, which is probably the problem.
The only thing to do from here is to clear the checktable errors. You'll need to ssh to the Vess, the following commands can only be run from the CLI.
administrator@cli> checktable -a clear -l 1 -t rct
administrator@cli> checktable -a clear -l 1 -t wct
administrator@cli> checktable -a clear -l 1 -t ibt
Putty is a good tool to use to ssh to the Vess.
After than you will either have to reboot the Vess or the host computer. Most likely the host computer. The LUN names make it likely that the client computer is an X-SAN or Stornext server.
Also, if you need support, the best thing to do is email support@promise.com or to open a support ticket at support.promise.com. The forum is responded to on a time available basis and it is very unlikely that anyone will respond on a weekend.
doctor38 doctor38
posted this
3 weeks ago
Hello friend. Everything worked out. I am very grateful to you!!! Can you tell me why this happened and how to avoid it in the future?
R P
posted this
3 weeks ago
Hi,
It turns out that LD1 and LD3 are both in Disk Array 1. So it's possible that the failed disk was what caused the write table issue. In fact, it seems likely. So that issue may already have been solved.
But it would be a good idea to monitor the check table to see if more entries appear. If the volume goes offline again, the commands given will fix the problem.
doctor38 doctor38
posted this
2 weeks ago
doctor38 doctor38
posted this
2 weeks ago
As I understand it, I could do the same thing here as entering commands?
doctor38 doctor38
posted this
2 weeks ago
Or should I just view the table here without clearing it?
R P
posted this
2 weeks ago
You can view the checktables from WebPAM but I don't think you have an option to clear them.
