Install Debian on Toshiba Canvio Home NAS

Hi guys,

Firstly, thanks to everyone involved here. It is a great resource of info and files for these Marvell SoC devices.

I have a Kirkwood based “Toshiba Canvio Home NAS” that I want to update the stock Linux 2.6.31.8 kernel and found out that without a suitable DTS file it turned in to a much bigger project than I expected.

I tried a variety of DTS files from some similar Kirkwood devices but none of them were suitable. So I have created one now and sharing it here if anyone else can make use of it.

Some of the hardware models it covers include HDNB120XKEK1, HDNB120XKEG1, HDNB130XKEK1, HDNB130XKEG1, STOR.E CLOUD and maybe others.
Toshiba Canvio Home NAS product details webpage

It seems that Toshiba webpage with the GPL source code is offline at the moment so here is a backup copy I had saved.
GPL Source Code for Toshiba Canvio Home NAS

Some hardware details:
MARVELL BOARD: 88F6702A-TCC LE
Soc: 88F6702 A1 CPU running @ 1000Mhz
DRAM (DDR2) size 128MB
SPI Flash: 512 kB
Ethernet Marvell 88E1318
SATA x1
USB x1



Robert

Hi Robert,

Thanks for your contribution!

Do you have a serial console boot log that you can post here?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

Boot logs for 4.4.0, the stock install and the stock u-boot environment settings are attached. There are a couple of warnings, but from what I have read they are ok and common with this setup.

The SPI device looks like it still needs some tweaking.

I could not find much info about this model at all when I started working on it so I will add a couple of pictures here of the inside too. The case has to come apart to get to the UART connector.

Canvio NAS PCB
Canvio NAS UART connector

Great works Robert :)

Those pincontrols warnings are expected. We can get rid of them (the Pogo V4 had similar warnings).

I will incorporate your DTS to the next kernel realease.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hi,

After updating to linux-4.11.3 the ethernet stopped working with 'Failed to bring up eth0.' I have made some changes to the DTS and it is fixed now, and it is still working ok in 4.4.0 too. The updated DTS, DTB and 4.11.3 boot log are attached.

A couple of notes:
The pinctrll warnings are less and CESA device is registered ok now, thanks for the fixes.

The SPI partitions set out in the DTS would not work in 4.4 but they get setup ok on 4.11. They could be defined in uboot and added as boot args in 4.4 which may be the preferred option anyhow?

setenv mtdids 'nor0=spi0.0'
setenv mtdparts 'mtdparts=spi0.0:504k(uboot),4k(param),4k(param2)'

Esekeyd would not pick up the restart button by default. I had to edit /etc/default/esekeyd to input event0 to get it to work.

DAEMON_OPTS="/etc/esekeyd.conf /dev/input/event0"

The NAS has RTC hardware but no battery so the system time would get messed up when the power was disconnected. I could not find an ready-made way to get around it so ended up using 'fake-hwclock' software which saves the time on shutdown and just edited it slightly so the startup script would update the real hwclock on boot so at least it will have a sane time. It is not connected to the Internet so tvheadend does the time syncing over the DVB-T network.

DATE=$(< /etc/fake-hwclock.data)
hwclock --set --date="$DATE" --utc --noadjfile

I will donate this thing to a family member and not sure how they will treat it so I have set it to do a file check on each boot with boot arg fsck.mode=force and edit /etc/default/rcS with FSCKFIX=yes. I would look into creating a readonly boot image for it if I had more time.

But otherwise it is working ok and quite a good little gadget now with TV tuner and 2Tb storage shared over the network.


Robert

Robert,

> They coul
> d be defined in uboot and added as boot args in 4.
> 4 which may be the preferred option anyhow?
>

> setenv mtdids 'nor0=spi0.0'
> setenv mtdparts 'mtdparts=spi0.0:504k(uboot),4k(pa
> ram),4k(param2)'
>

It is prefered to use bootargs (more flexible)

> Esekeyd would not pick up the restart button by de
> fault. I had to edit /etc/default/esekeyd to input
> event0 to get it to work.
>

> DAEMON_OPTS="/etc/esekeyd.conf /dev/input/event0"
>

>

This might have something to do with the DTS. I'll look to see if I can spot anything.

> But otherwise it is working ok and quite a good li
> ttle gadget now with TV tuner and 2Tb storage shar
> ed over the network.
>

Cool! thanks for the updates.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Robert,

The Reset button looks fine in DTS. So I don't see why it would not work. 2 items to doublecheck

1. Is the GPIO_ACTIVE_LOW correct?

reset {
			    label = "Reset Button";
			    linux,code = <KEY_RESTART>;
			    gpios = <&gpio0 21 GPIO_ACTIVE_LOW>;
			};
		};

2. Is the button key name correct?

cat /etc/esekeyd.conf | grep RESTART

RESTART:/usr/bin/logger -s -i "RESTART button pushed"

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hi Bodhi,

The reset button is working as expected so the DTS settings should be ok.

I got caught out because I thought esekeyd listened on all input/events but it just would not respond to the button push. Once I told it specifically event0 with the DAEMON_OPTS= then it worked as expected. Learnkeys finds RESTART(press): and RESTART(release):



Robert

Robert,

I understood that from what you said before. But I found it strange that esekeyd does not sense RESTART button where it should. This usually is related to the GPIO. You have the gpio_key and the button defined in the DTS. It looks fine to me.

reset {
			    label = "Reset Button";
			    linux,code = <KEY_RESTART>;
			    gpios = <&gpio0 21 GPIO_ACTIVE_LOW>;
			};
		};

	gpio_keys {
		compatible = "gpio-keys";
		#address-cells = <1>;
		#size-cells = <0>;
        pinctrl-0 = <&pmx_reset_button>;
		pinctrl-names = "default";
		
            reset {
			    label = "Reset Button";
			    linux,code = <KEY_RESTART>;
			    gpios = <&gpio0 21 GPIO_ACTIVE_LOW>;
			};
		};

So by this definition, esekeyd should have been triggered by the GPIO 21. And the RESTART button action should have executed some_script as esekeyd.conf specified. There should be no input event processing needed.

/etc/esekeyd.conf

RESTART:some_script

Have you tried playing with this GPIO?

gpios = <&gpio0 21 GPIO_ACTIVE_HIGH>;

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/09/2017 07:59PM by bodhi.

Hi Bodhi,


I made GPIO_ACTIVE_LOW because when initially testing the GPIO pin it was giving 0 in normal state and changed to 1 when pushed. With it set GPIO_ACTIVE_HIGH and the output was reversed with a normal state of 1.

I have done some tests and GPIO_ACTIVE_LOW is correct. With it set at HIGH learnkeys shows a RESTART press without even pushing the button. Then button push is shown as release... and then the release is shown as a push again.

One thing I noticed now though is that without specifying /dev/input/event0 it did show an error 'learnkeys: can`t open /dev/input/event65534'

And on boot with a clean install of 4.4 with only esekeyd installed shows:

root@debian:~# systemctl status esekeyd.service -l
* esekeyd.service - LSB: ESE Key Daemon
   Loaded: loaded (/etc/init.d/esekeyd)
   Active: failed (Result: exit-code) since Wed 2004-07-07 12:45:03 PDT; 13 years 0 months ago
  Process: 378 ExecStart=/etc/init.d/esekeyd start (code=exited, status=1/FAILURE)

Jul 07 12:45:03 debian esekeyd[378]: Starting a multimedia keyboard daemon for Linux : esekeydESE Key Deamon 1.2.7 (SVN-r63)
Jul 07 12:45:03 debian esekeyd[378]: /usr/sbin/esekeyd: can`t open /dev/input/event65534
Jul 07 12:45:03 debian esekeyd[378]: failed!
Jul 07 12:45:03 debian systemd[1]: esekeyd.service: control process exited, code=exited status=1
Jul 07 12:45:03 debian systemd[1]: Failed to start LSB: ESE Key Daemon.
Jul 07 12:45:03 debian systemd[1]: Unit esekeyd.service entered failed state.

/dev/input has:

root@debian:~# ls -al /dev/input
total 0
drwxr-xr-x  3 root root     100 Jul  7  2004 .
drwxr-xr-x 14 root root    2780 Jul  7  2004 ..
drwxr-xr-x  2 root root      60 Jul  7  2004 by-path
crw-rw----  1 root input 13, 64 Jul  7  2004 event0
crw-rw----  1 root input 13, 63 Jul  7  2004 mice

The thing is the button press is working ok, I currently have it flashing the red LED a few times before it goes and does a reboot as expected. But I just don't know why esekeyd needed event0 specified. Only made a note of it because it took a while to get it going and it may help others?

I think it is more to do with esekeyd, but if you have any other ideas I am happy to test.


Robert

Robert,

What about your /etc/esekeyd.conf? does it have any content, such as

POWER:some_script
RESTART:some_script

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

currently just has

RESTART(press):echo timer > /sys/class/leds/canvio\:red\:05/trigger
RESTART(release):sleep 8 && /sbin/shutdown -r now

and runs ok at button press.

Hi Robert,

I see. So it means you need to specify RESTART(press): and RESTART(release):

but RESTART: will not work?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hi Bodhi,

It will restart just fine fine with RESTART:/sbin/shutdown -r now.
The RESTART(press): and RESTART(release): were how the config was described when running 'learnkeys /etc/esekeyd.conf /dev/input/event0'.

root@debian:~# learnkeys /etc/esekeyd.conf /dev/input/event0
learnkeys (ESE Key Deamon 1.2.7, SVN-r63)

Pres ANY (fun)key... or Ctrl-C to exit...

key RESTART stored in config file
key RESTART stored in config file
^C
Caught signal 2, writing config file and exiting...
root@debian:~#

I have been over the DTS again and made some subtle changes but it still has the esekeyd can`t open /dev/input/event65534 if /dev/input/event0 is not included. I was hopeful by adding #include <dt-bindings/input/input.h> but alas no difference. The slightly changed file is attached anyhow.

I don't know the relevance of event65534. I am beginning to wonder if it is related to the 'kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group' error these kirkwood-6192 have. I had a look online for the pogoplug v4 with esekeyd and the one I found actually had set the event0 added too in the config ! link.

Do you know of any kirkwood-88f6702/6192 that are running esekeyd?


Robert

Robert,

> I don't know the relevance of event65534. I am beg
> inning to wonder if it is related to the 'kirkwood
> -pinctrl f1010000.pin-controller: unknown pinctrl
> group' error these kirkwood-6192 has

Now it might be a clue there. My Pogo V4 does not have these errors anymore.

>
> Do you know of any kirkwood-88f6702/6192 that are
> running esekeyd?

I do! I have 3 Pogo V4 (6192) running 24/7 with esekeyd working (same version that you have). And one NSA310S (6702) running esekeyd. That's why I thought something is not righ. The Pogo V4 has one button: EJECT. The NSA310S has 3 buttons (Power, Restart, Copy), all working with esekeyd.

Let me get the data points and post here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/11/2017 02:40AM by bodhi.

Pogo V4:

cat /etc/esekeyd.conf

# Pogo V4 keys
#
EJECTCD:/usr/bin/logger -s -i "EJECT button pushed"

Jul  9 18:29:08 pogov4p user.notice logger[2528]: EJECT button pushed

cat /etc/default/esekeyd

# Defaults for esekeyd initscript

# Start esekeyd on boot (set it to "true" to enable)
START_ESEKEYD=true

# Daemon options, at last config location must be present
DAEMON_OPTS=/etc/esekeyd.conf

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Pogo V4 DTS

cat /usr/src/linux-4.11.3-tld/arch/arm/boot/dts/kirkwood-pogoplug_v4.dts

/* 
 * Device tree file for the Pogoplug V4/Mobile
 *
 * Copyright (c) 2016, bodhi <mibodhi@gmail.com>
 *
 */

/dts-v1/;

#include "kirkwood.dtsi"
#include "kirkwood-6192.dtsi"

/ {
	model = "Pogoplug v4";
	compatible = "cloudengines,pogoplug-v4", "cloudengines,pogoplug-mobile", "marvell,kirkwood-88f6192", "marvell,kirkwood";

	memory {
		device_type = "memory";
		reg = <0x00000000 0x8000000>;
	};

	chosen {
		bootargs = "console=ttyS0,115200";
		stdout-path = &uart0;
	};

	ocp@f1000000 {
		pinctrl: pin-controller@10000 {
			pmx_led_green: pmx-led-green {
				marvell,pins = "mpp22";
				marvell,function = "gpio";
			};
			pmx_led_red: pmx-led-red {
				marvell,pins = "mpp24";
				marvell,function = "gpio";
			};
			pmx_button_eject: pmx-button-eject {
				marvell,pins = "mpp29";
				marvell,function = "gpio";
			};
			/*pmx_usb_power_enable: pmx-usb-power-enable {
				marvell,pins = "mpp29";
				marvell,function = "gpio";
			};*/
		};

		serial@12000 {
			status = "ok";
		};

		sata@80000 {
			status = "okay";
			nr-ports = <2>;
		};

		mvsdio@90000 {
			pinctrl-0 = <&pmx_sdio>;
			pinctrl-names = "default";
			status = "okay";
			cd-gpios = <&gpio0 27 GPIO_ACTIVE_HIGH>;
			/* No WP GPIO */
		};
	};

	gpio-leds {
		compatible = "gpio-leds";
		pinctrl-0 = <&pmx_led_red &pmx_led_green>;
		pinctrl-names = "default";

		health {
			label = "status:green:health";
			gpios = <&gpio0 22 GPIO_ACTIVE_LOW>;
			default-state = "keep";
		};
		fault {
			label = "status:red:fault";
			gpios = <&gpio0 24 GPIO_ACTIVE_LOW>;
		};
	};

	gpio_keys {
		compatible = "gpio-keys";
		#address-cells = <1>;
		#size-cells = <0>;
		pinctrl-0 = <&pmx_button_eject>;
		pinctrl-names = "default";

		button@1 {
			label = "Eject Button";
			linux,code = <KEY_EJECTCD>;
			gpios = <&gpio0 29 GPIO_ACTIVE_LOW>;
		};
	};

	/*regulators {
		compatible = "simple-bus";
		#address-cells = <1>;
		#size-cells = <0>;
		pinctrl-0 = <&pmx_usb_power_enable>;
		pinctrl-names = "default";

		usb_power: regulator@1 {
			compatible = "regulator-fixed";
			reg = <1>;
			regulator-name = "USB Power";
			regulator-min-microvolt = <5000000>;
			regulator-max-microvolt = <5000000>;
			enable-active-high;
			regulator-always-on;
			regulator-boot-on;
			gpio = <&gpio0 29 GPIO_ACTIVE_HIGH>;
		};
	};*/
};

&nand {
	status = "okay";

	partition@0 {
		label = "u-boot";
		reg = <0x0000000 0x200000>;
	};

	partition@200000 {
		label = "uImage";
		reg = <0x200000 0x300000>;
	};

	partition@500000 {
		label = "uImage2";
		reg = <0x500000 0x300000>;
	};

	partition@800000 {
		label = "failsafe";
		reg = <0x800000 0x800000>;
	};

	partition@1000000 {
		label = "root";
		reg = <0x1000000 0x7000000>;
	};
};

&mdio {
	status = "okay";

	ethphy0: ethernet-phy@0 {
		reg = <0>;
	};
};

&eth0 {
	status = "okay";
	ethernet0-port@0 {
		phy-handle = <&ethphy0>;
	};
};

&pciec {
	status = "okay";
};

&pcie0 {
	status = "okay";
};

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hi Bodhi,

Thanks for the details, no surprises there though. The Pogoplug v4 was one of the first DTS files I tried to boot this machine from because of the CPU and ram similarities, but it would kernel panic with the nand/spi differences. But it was one of the templates I used for starting the current canvio DTS.

Can you tell me how you got rid of the pntctrl messages in your 6702/6192? I had a look through the 4.11.3 patch but could not see any obvious changes in pinctrl-kirkwood.c or pinctrl-mvebu.c. Edit: I see there was a patch added to mainline about v4.5.

This Canvio still has 2 errors with 4.11.3 which is strange since it should be similar hardware with the same group of pins (36-49) not included across all of these models.

[    6.251567] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[    6.258849] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49

According to the esekeyd man page if input_device_name is given it turns off autodetection of 1st keyboard device, so there is something different here that is confusing that autodetect function.


Robert



Edited 1 time(s). Last edit at 07/11/2017 09:32PM by R0B3r7.

Robert,

It's been a while, I can't quite remember how pin control 47 and 49 errors were gone :) If I can find the log, I'll let you know.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

I have found the culprit! It is having a lone <KEY_RESTART> in the DTS. For some reason the restart key is treated differently and is not assigned the keyboard handler.

Esekeyd is looking at /proc/bus/input/devices for H: Handlers=kbd but it is not there with KEY_RESTART. I tried it with KEY_EJECTCD as with your Pogoplug and it worked as you expected.

The solution as this stage is to change KEY_RESTART with KEY_POWER in the DTS and it works ok.
'H: Handlers=kbd event0' and esekeyd is happy and it still has the same result with 'POWER:/sbin/shutdown -r now' instead in /etc/esekeyd.conf.

<KEY_RESTART>

root@debian:~# cat /proc/bus/input/devices
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=3
B: KEY=1000000 0 0 0 0 0 0 0 0 0 0 0 0

root@debian:~# evtest /dev/input/event0
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 408 (KEY_RESTART)
Properties:
Testing ... (interrupt to exit)

<KEY_POWER>

root@debian:~# cat /proc/bus/input/devices
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

root@debian:~# evtest /dev/input/event0
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 116 (KEY_POWER)
Properties:
Testing ... (interrupt to exit)

DTS with that change added now.

I expect KEY_RESTART would be ok to use if other regular key were also defined in the DTS so that the keyboard handler would then be assigned with /dev/input/event0
It seems the previous setup was working ok and the input was available with gpio-keys, just not as a keyboard :)


Robert

Robert,

Good troubleshooting :)

It is certainly strange, that esekeyd behave that way. It might be a bug.

Quote

I expect KEY_RESTART would be ok to use if other regular key were also defined in the DTS so that the keyboard handler would then be assigned with /dev/input/event0

I think you are right assuming the above!!!

This is the kirkwood-nsa325 gpio_keys

gpio_keys {
		compatible = "gpio-keys";
		#address-cells = <1>;
		#size-cells = <0>;
		pinctrl-0 = <&pmx_btn_power &pmx_btn_copy &pmx_btn_reset>;
		pinctrl-names = "default";

		button@1 {
			label = "Power Button";
			linux,code = <KEY_POWER>;
			gpios = <&gpio1 14 GPIO_ACTIVE_HIGH>;
		};

		button@2 {
			label = "Copy Button";
			linux,code = <KEY_COPY>;
			gpios = <&gpio1 5 GPIO_ACTIVE_LOW>;
		};

		button@3 {
			label = "Reset Button";
			linux,code = <KEY_RESTART>;
			gpios = <&gpio1 4 GPIO_ACTIVE_LOW>;
		};
	};

What if you add 2 keys: POWER and RESTART using the above format (button 1 is Power, and button 2 is Restart)? does this box have POWER button GPIO?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Robert,

I sent you PM.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hi Bodhi,

Sorry, the PM notice went to spam, fixed now.

With esekeyd I think it is behaving as expected. Although the error 'can`t open /dev/input/event65534' when it cannot find any keyboard handler is quite cryptic and could be improved.

This machine has just the one button. It was initially probably a reset button for clearing passwords or maybe a factory restore so not actually a restart button anyhow. I suppose at the end of the day it doesn't really matter too much what Linux key code it is assigned to it, as long as it is configurable once the system has booted.



Robert

Hi Robert

Please feel free to contribute you dts file to mainline Linux. Please email To: linux-arm-kernel@lists.infradead.org and Cc:
Jason Cooper <jason@lakedaemon.net>
Andrew Lunn <andrew@lunn.ch>
Gregory Clement <gregory.clement@free-electrons.com>

Andrew Lunn Wrote:
-------------------------------------------------------
> Hi Robert
>
> Please feel free to contribute you dts file to mai
> nline Linux. Please email To: linux-arm-kernel@lis
> ts.infradead.org and Cc:
> Jason Cooper <jason@lakedaemon.net>
> Andrew Lunn <andrew@lunn.ch>
> Gregory Clement <gregory.clement@free-electrons.co
> m>

Hi Andrew!

Good to see you stopping by the forum :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Andrew,

OK, will do.

The machine is still here so I will set it up with Bodhi's latest version first just to make sure all is still consistent when running 4.12.1.



Robert

Hi everyone

Robert, could you explain to an entire novice how to do the installation in a HDNB120XKEK1 Toshiba Canvio Home? I have one with firmware failure Toshiba dont provides a firmware fix method and I'm stuck with an expensive paperweight :)
I haven't even found how to open it if necessary. So, any information is welcome.

PD: Excuse my faults, english is not my first language.

wzaldivar,

If it bricked that bad. You need a serial console connected. See this post for the pinout:

http://forum.doozan.com/read.php?2,35095,35098#msg-35098

And you can read this thread to see which serial module converter to buy:

http://forum.doozan.com/read.php?8,13263

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I'm not shure if so bricked, it starts the OS to an state where I can't use it (no ssh, no web login)

The story:

Power off (from the web control panel) for furniture change and the hell started.

When power on, access from my computers start to fail all the time. The problem, samba locking.tdb grows without control and breaks samba server. Ok, I have backup of my data, lets go with factory reset.

Ohh no!!!! After factory reset cant create any volume, I have 2 TB that can't use. You think I have enought bad ideas? Nop. Factory reset again and now cant log into de NAS from the web panel

In the web page shows:

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0, (factory reset #1)

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0, (factory reset #2)

If try to login... well, I can't.

Is posible to install without opening? I think I will need to extract the HDD and install your Debian image in. Then pray for start OK with a real OS, not a Toshiba toy :)

wzaldivar Wrote:
-------------------------------------------------------
> I'm not shure if so bricked, it starts the OS to a
> n state where I can't use it (no ssh, no web login
> )
>
> The story:
>
> Power off (from the web control panel) for furnitu
> re change and the hell started.
>
> When power on, access from my computers start to f
> ail all the time. The problem, samba locking.tdb g
> rows without control and breaks samba server. Ok,
> I have backup of my data, lets go with factory res
> et.
>
> Ohh no!!!! After factory reset cant create any vol
> ume, I have 2 TB that can't use. You think I have
> enought bad ideas? Nop. Factory reset again and no
> w cant log into de NAS from the web panel
>
> In the web page shows:
>
> Warning: Unknown: write failed: No space left on d
> evice (28) in Unknown on line 0, (factory reset #1
> )
>
> Warning: Unknown: Failed to write session data (fi
> les). Please verify that the current setting of se
> ssion.save_path is correct () in Unknown on line 0
> , (factory reset #2)
>
> If try to login... well, I can't.
>
> Is posible to install without opening?

No. If factory reset did not work then you need serial console.

> think I w
> ill need to extract the HDD and install your Debia
> n image in. Then pray for start OK with a real OS,
> not a Toshiba toy :)

You coud try, but I'd not hope too much. You will need to change uboot envs to boot a differrent OS. As a matter of fact, stock envs can boots only stock OS.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)