plugout.net

I have 5 drives installed. 4 of them are identical and one of them is different.

Disk-A
1860.24 GB Is a raid member
Disk-C
1859.88 GB Is a raid member
Disk-D
1859.88 GB Is a raid member
Disk-E
2791.75 GB

I can't find Disk-B but I do see
Other detected Disks - An uninitialized disk called sdb with only 3.86 GB that I believe to be Disk-B possibly.

If I initialize this will it destroy the NAS as the firmware is possibly there?

Hi

Yes you can initialize sdb disk without losing the firmware. This one is stored only on sda.

Jocko wrote:Hi

Yes you can initialize sdb disk without losing the firmware. This one is stored only on sda.

I just tried it.....it seems to have wiped out all my files and I can't log in to the NAS anymore :(

Hi

Well it is not the expected behaviour ! :shocked
First you did not lose your data but I need more information.

So at what step you lost access ? and did you see some error messages when you ran the setup script ?
Currently, do you check if you can still get a ssh access?

Jocko wrote:Hi

Well it is not the expected behaviour ! :shocked
First you did not lose your data but I need more information.

So at what step you lost access ? and did you see some error messages when you ran the setup script ?
Currently, do you check if you can still get a ssh access?

Ok so I am not able to get ssh access and there was an error when attempting to initialize the disk but I don't remember what it was. error 5 maybe? *shrugs*

I tried late last night to reload the kernel and it won't connect at the telnet step.

Hi

As soon as you are able to get a telnet access by loading the standalone kernel version we will go to deepen your issue.

So on your side the first step is to get the telnet access

It's resolved. Looks like sdb is a dead drive. Just ordered a replacement. I just need to figure out how to the new one to work with the raid that has already been created.

Hi

It is quiet easy...
- first step, initialize the disk from the main disk setup menu like you tried with your previous sdb disk
- then, open the edit volume menu (click on the volume-name link) and here you will be able to add the new sdb disk to restore the redundancy of the raid.

Note: I advise to leave the NAS on until the resynchronization job is complete

Partition table:
GPT (EFI) MBR (ms-dos)

Format Type:
FAT32 exFAT (FAT64) Native Ext3 Ext4


Which selections should I make on this replacement drive? I tried with GPT+Ext4 and got this error...

Setup task reset.sh is restarting
Found disk: sdb(Z4Z77CY6)
Create a new partiton gpt table on sdb:
=>Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
Fail (creating gpt partition table failed) Error is 5

Hi

is it the new disk or the former ?

Looks like sdb is a dead drive. Just ordered a replacement

Currently your issue is not not on the fs level but partition table. Please to post

Code: Select all

gdisk -l /dev/sdb