plugout.net

Posted: **Sun Feb 14, 2016 5:51 pm**

Background: 3tb white cloudbox with original, most current, firmware. The NAS console was still reachable but files were no longer readable in Lacie browser even though firmware was reporting disk usage at approx 1.4 TB. After some Googling and finding the fvdw-sl, found thread (http://forum.nas-central.org/viewtopic.php?f=277&t=17409&start=60) by dmiyabara and followed steps only to discover that partition 5 was corrupt.

I decided to install new firmware without further attempts to recover files (luckily there are other backups on a different NAS).

I was able to flash U-boot successfully and then install the fvdw-sl firmware, completely and successfully repartioning the drive. After completion, issued reboot -f command. This is where the problem begins. The NAS never appears on my network. I have used the fvdw-sl assistant to find the NAS, no luck. On my router, checked the DHCP client table and the NAS does appear (based on MAC address I can see the IP number it is getting). When I try to browse that address, no response. Tried to telnet that IP number and got no response.

So, any assistance, suggestions, commiseration, would be appreciated.

Posted: **Sun Feb 14, 2016 5:58 pm**

Hi ryandkg

ryandkg wrote:On my router, checked the DHCP client table and the NAS does appear (based on MAC address I can see the IP number it is getting). When I try to browse that address, no response. Tried to telnet that IP number and got no response.

Telnet server is only available with fvdw-sl console.
So try to get a SSH access (port 22 instead of 23). The default credentials are the same than with telnet

Posted: **Sun Feb 14, 2016 6:09 pm**

Using PuTTY, attempting to connect on port 22, "network error: connection timed out".

Also I was not able to ping the NAS on the same IP.

Posted: **Sun Feb 14, 2016 6:25 pm**

So I assume that the firmware is not loaded.

With fvdw-sl console, Use the action "Load a standalone kernel" to get a telnet access.

Then post

Code: Select all: gdisk -l /dev/sda mkdir /sda7 mount /dev/sda7 /sda7

Check if a boot.log exists on sda7 and post its content

Code: Select all: ls /sda7/boot.log cat /sda7/boot.log

Posted: **Sun Feb 14, 2016 6:41 pm**

Code: Select all: root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): 2AF8D378-680C-490D-AAC1-8AA7C45A0B51 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 2048-sector boundaries Total free space is 4062 sectors (2.0 MiB) Number Start (sector) End (sector) Size Code Name 1 4096 1052671 512.0 MiB 8300 Linux filesystem 2 1052672 2101247 512.0 MiB 8300 Linux filesystem 3 2101248 3149823 512.0 MiB 8200 Linux swap 4 3149824 3166207 8.0 MiB 8300 Linux filesystem 5 3166208 4739071 768.0 MiB 8300 Linux filesystem 6 4739072 4755455 8.0 MiB 8300 Linux filesystem 7 4755456 5804031 512.0 MiB 8300 Linux filesystem 8 5804032 5860533134 2.7 TiB 8300 Linux filesystem root@fvdw-sta-kirkwood:/ # mkdir /sda7 root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7 root@fvdw-sta-kirkwood:/ # ls /sda7/boot.log ls: /sda7/boot.log: No such file or directory root@fvdw-sta-kirkwood:/ #

Posted: **Sun Feb 14, 2016 6:56 pm**

partitions table on sda is ok.

Why did you flash your cloudbox

The 2big2, Cloudbox.
The u-boot images for 2big2, cloudbox are only needed in case you have a problem with u-boot on those devices.
Most of the 2big2 will already support gpt formatted disks, there is no reason to use these if you nas is running fine.
In case you have a 2big2 with old u-boot without gpt you could use it to get support for dsk > 2TB.

As you have a 3 TB with the lacie firmware then that means the original uboot already supported gpt partition.

otherwise, the firmware is not loaded when the NAS starts.

Go to check on the kernel side:

Still with fvdw-sl console use action "load an external kernel" and select the kirkwood version: UIMAGE-3142-NWSP2CL-14 (I assume that you use fvdw-sl version 6).

If you can see the NAS with fvdw-sl assistant that means there is an issue with the kernel stored on sda6

Posted: **Sun Feb 14, 2016 7:36 pm**

Why did you flash your cloudbox

I mistakenly believed that the fdvw firmware was required to support the fdvw web interface. My bad.

Still with fvdw-sl console use action "load an external kernel" and select the kirkwood version: UIMAGE-3142-NWSP2CL-14 (I assume that you use fvdw-sl version 6).

Yes, I am using version 6. I have loaded external kernel UIMAGE-3142-NWSP2CL-14 (located in tftp/firmware/kirkwood/, correct?). Load process appeared to be successful however, fvdw-sl-assistant cannot see NAS nor does an IP with its MAC appear in the DHCP client table.

Posted: **Sun Feb 14, 2016 7:49 pm**

ryandkg wrote:I have loaded external kernel UIMAGE-3142-NWSP2CL-14 (located in tftp/firmware/kirkwood/, correct?)

yes it is right.

So the bootloader seems not detect your disk. For this point you need to wait fvdw.

Posted: **Sun Feb 14, 2016 8:00 pm**

thank you for your help so far. I am looking forward to the additional functionality of the fvdw-sl firmware.

Posted: **Sun Feb 14, 2016 8:29 pm**

Which u-boot version did you put in flash?

Also repeat the step Jocko described, load the standalone kernel, create a folder with name sda7 and mount /dev/sda7 on it. Then do a directory listing and post the output.

Code: Select all: ls -al /sda7/

This to check if firmware is really installed. If that is the case will use the u-boot console to verify why loading of the firmware fails.

Ps the bootloader seems to be ok, otherwise you would not have been able to upload and start the standalone kernel

plugout.net

3TB Cloudbox - does not appear on network

3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network

Re: 3TB Cloudbox - does not appear on network