Delete Array - Stuck at 50%

[KingBubbaTruck]

Linkstation LS420DF34, 8 terabyte model, Firmware 1.30.

Brand new device, never used, no data at all on the box.

I wanted to configure it as raid 1, so following the instructions I deleted the existing array.

The configuration interface now gives me a message saying 'Executing job: Delete Array - 50% finished'.

It has been displaying that message for 12 hours now.  I can understand building an array might take a long time, but I thought the delete should go pretty quickly.

[davo]

Shouldnt take anymore than 5 minutes, does the Nas Navigator detect it and if so does it report 2 individual disk or still a RAID0?

[KingBubbaTruck]

Yep, The Nas Navigator detects it and shows 2 disks on it.

It doesn't show any shares on it.

[KingBubbaTruck]

Here's a screenshot.

[davo]

The deletion has finished and the page has just hung, you should be able to open a new tab, enter the IP and successfully create a new RAID.

If youre still getting the same message on the GUI, then just reboot the NAS.

[KingBubbaTruck]

Thanks so much for helping me.

Rebooting got me past that 50% progress indication, except now if I go and look at the RAID Array List, I can see that Array1, RAID Mode of RAID0, Status = Failed.

Now When I try to delete the array, the delete job just fails.

[KingBubbaTruck]

Tried to format the Array, that fails.
Rebooted a few times.
Raid Scan wont run because 'Target array does not exist'.

[davo]

Sounds like one of the disk is faulty.

[KingBubbaTruck]

Nothing to lose.  I suppose I can try the 'Erase' function and see what happens.

[KingBubbaTruck]

Took a couple days to do the erase, but once it finished, the NAS shut down.

I started it back up.

The setup tried to create a couple of shares, I let it do what it wanted.

Went to the Raid section, it said something like the raid array was not created.  I clicked on 'Array1', set it to be Raid 1, a little job ran for a few minutes.

I'm now able to create shares, copy files, etc.

Must have been just a weird initialization glitch, cause it all seems fine now.

Thanks for your help!