NWSP Constantly flashing blue / red

[flashback]

Hi there,

I'm having trobule with my NWSP 2. It's running version16 but just recently won't boot up correctly it just flashes blue then red continuously.

I can't find it using the assistant or connect on the web page for it. Please can you give me some support on how to get it back working without losing files?

[fvdw]

A red light means that the bootloader cannot find a disk. That could mean your harddisk is defective or is corrupt
To investigate if the disk has a problem you could use the fvdw-sl console that runs on your pc under windows and load the standalone kernel. That kernel runs from RAM even if the hdd is broken and let you connect with telnet client enabling you to give linux commands from command line to investigate the harddisk.
The fvdw-sl console can be found in the download section of the forum

[flashback]

Thank you for the advice. I have a NSWP2 and can load the standalone kernel, this stops the red flashing and I get a blue solid light.
I don't really know linux in any detail though. Is there a useful resource that you could point me to that would give me the correct commands to run the queries and identify the issues?

[flashback]

Hi there, I can now log in using the standalone kernel, but I get this when I use fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 242252 1953514583+ ee EFI GPT

What do I need to do to get this working again?

Many thanks,
Steve

[fvdw]

Is the disk you have inside a disk with lacie firmware or fvdw-sl firmware ?
It is a disk with gpt partition table.
To see what table is on it give this command.

Code: Select all

gdisk -l /dev/sda

Ps. If it is not a disk with lacie firmware and you do not need data present on the disk then what you can do is install fvdw-sl firmware using the fvdw-sl console that should bring it online assuming your disk is ok

[flashback]

Hi FVDW,

I have issues the gdisk commands and it comes back with this:

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Problem opening /dev/sda for reading! Error is 6.
root@fvdw-sta-kirkwood:/ #

Any ideas? Not sure what this means.

The disk was running FVDW 16 previously. I've tried to upgrade using the console to 17 but it must have failed as still not working....

Also if I try fdisk -l now I get this:

root@fvdw-sta-kirkwood:/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

[fvdw]

I am afraid that your hard disk is dead. Or that your nwsp2 has a defective sata controller. You can test that by inserting another hard disk and test again if the new disk can be read.

[flashback]

Hi. I went out and bought a new HDD 4TB. I have then flashed uboot so that I an use GPT., however when I try to start hr NAS it seems to go through boot cycle, but always ends up on a solid blue after some time.

Nothing seems to let me use the standalone kernel now as whenever I try it always say waiting for uboot and goes no further. Is there something obvious I'm missing to make this work?

[fvdw]

What kind nwsp2 do you have? A classic or lite
If it is lite then you have put a wrong uboot version in flash.
For the lite there is no flash required for uboot it already support gpt. Only classic version needs flash for support gpt (clearly mentioned on several places)

To find out which version you have go here viewtopic.php?f=11&t=213

[fvdw]

In addition to my previous post.
Reading again earlier post from you in this topic I read that the original disk had a GPT partition table. If that is the case then most likely you have a lite version and flashing uboot was useless as your bootloader already supported gpt.
Why did you flash uboot. :dontknow :pound

Anyhow if you have used the uboot for the classic version and your nwsp2 is a lite version it will not be able to boot anymore. I need to look in other posts, if I remember well we found a way to help some other user that bricked his nswp2 lite by putting wrong uboot version in flash and restore the correct uboot version.