Buffalo Forums

Products => Storage => Topic started by: engelsepiet on August 23, 2018, 09:03:48 AM

Title: LS420D degraded raid
Post by: engelsepiet on August 23, 2018, 09:03:48 AM
Hi,
My LS420D has two 4TB disks Configured as RAID1. NAS Navigator 2 is reporting that the RAID array is in degraded mode, and this is also shown by the flashing amber light indicating fault I12, which I assume means that one of the disks is defunct. However,  neither of the drive indicators is glowing red, so I have no way of knowing which disk to replace. I am using Windows 10 Pro. The LS420D does not show up in Explorer or in Disk Management. Any advice gratefully received.
Title: Re: LS420D degraded raid
Post by: Texturtle on August 23, 2018, 09:30:48 AM
Do you have NAS Navigator installed? Have you logged in to the UI for the LinkStation?
Title: Re: LS420D degraded raid
Post by: davo on August 23, 2018, 09:58:40 AM
Log onto the admin page -> Drives -> Drives. This should show which disk has failed.
Title: Re: LS420D degraded raid
Post by: engelsepiet on August 25, 2018, 10:08:39 AM
Thanks, Davo, I now know that it is disk 1 that has failed. I assume that that will be the disk on the left looking from the front. Awaiting delivery of a replacement.
Title: Re: LS420D degraded raid
Post by: engelsepiet on August 26, 2018, 06:46:16 AM
Supplementary question: should I not be able toaccess the remaining good disk? It doesn't show up in Explorer or in Disk Management.
Title: Re: LS420D degraded raid
Post by: Texturtle on August 27, 2018, 09:09:13 AM
It will not show up in disk management ever, it's not a local drive. In file explorer if you type in \\<IP Address> of the unit does it show you the shared folders?
Title: Re: LS420D degraded raid
Post by: engelsepiet on August 28, 2018, 06:43:32 AM
No, can't access it via file explorer. I can, though, use the NAS IP address in a browser to access the root, where changes can be made: Getting Started; Web Access, etc.. Also, I can see the NAS in NAS Navigator 2, but it has a tendency to vanish spasmodically.
Title: Re: LS420D degraded raid
Post by: davo on August 28, 2018, 06:45:13 AM
what OS are you using?

What error do you get if you try to access it on \\IP-Address (assume you know where/how to do this?)
Title: Re: LS420D degraded raid
Post by: engelsepiet on August 28, 2018, 07:32:55 AM
I am using Windows 10 Pro 64-bit. Texturtle said to use file explorer, so I typed \\192.168.1.84 in the location box. I mentioned earlier that the NAS icon disappears spasmodically from Navigator 2.  It must have been absent when I typed the ip address into file explorer and couldn't connect. I just did it again with the icon present and it immediately switched to the browser with the URL box showing 192.168.1.84/root.html and displaying the UI with Getting Started, Web Access, etc..
Title: Re: LS420D degraded raid
Post by: davo on August 28, 2018, 08:01:27 AM
Click the search icon in Windows 10, then type \\192.168.1.84

Then press enter and let us know what the error mesassge is. Example of what to do is below.

(https://i.imgur.com/STAplQU.png)
Title: Re: LS420D degraded raid
Post by: engelsepiet on August 28, 2018, 02:19:46 PM
You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol which is unsafe and could expose your system to attack.
Your system requires SMB2 or higher. For more info on resolving this issue. see
https://go.microsoft.com/fwlink/?linkid=852747
Title: Re: LS420D degraded raid
Post by: davo on August 28, 2018, 03:13:16 PM
Log onto the setting page of the Linkstation.

Go to advances settings - file server - SMB - to the right hand side is a black arrow - click it - edit - enable smb2 - save the setting.

Reboot the PC.

Done.
Title: Re: LS420D degraded raid
Post by: engelsepiet on August 28, 2018, 03:50:07 PM
As you say, Done. Many thanks. Much appreciated.
Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 105 (show)
Files included: 27 - 1055KB. (show)
Memory used: 734KB.
Tokens: post-login.
Queries used: 10.

[Show Queries]