Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Debian on Qnap TS-109

175 views
Skip to first unread message

[ftp83plus]

unread,
Sep 13, 2016, 2:00:02 PM9/13/16
to
Hello all, 

I am a bit new to Debian, and when I laid my hands on an older Qnap TS-109, I decided to install it to overcome Qnap's firmware limitations. I followed the guide put up by Martin Michlmayr, but currently face three issues:
  1. I can't log in through SSH using root user. It denies me access even when I use the password set during setup. I can log in using the standard user, and perform "su" to get to root. How come root can't log in directly?
  2. More annoyingly, it beeps every two minutes for unknown reasons. 
  3. The "status" LED is flashing red. LAN LED is off, although the NAS does receive a valid IP address on the LAN.
I shut down the NAS, disconnected network cable, then turned it back on using the button, and connected the network cable. 

What can be happening?
Pat

Lennart Sorensen

unread,
Sep 13, 2016, 2:10:02 PM9/13/16
to
There is a setting by default in /etc/ssh/sshd_config:

PermitRootLogin prohibit-password

That means root user can only login with a key, not with a password.
Other users can login either way.

If you want the old behaviour that used to be the default, you would
have to change the setting to yes.

--
Len Sorensen

Uwe Kleine-König

unread,
Sep 13, 2016, 2:10:02 PM9/13/16
to
Hello,

On 09/13/2016 07:57 PM, [ftp83plus] wrote:
> 1. I can't log in through SSH using root user. It denies me access even
> when I use the password set during setup. I can log in using the
> standard user, and perform "su" to get to root. How come root can't
> log in directly?

check your /etc/ssh/sshd_config. It has something like

PermitRootLogin without-password

which should explain the failure nicely.

> 2. More annoyingly, it beeps every two minutes for unknown reasons.

something in dmesg?

> 3. The "status" LED is flashing red. LAN LED is off, although the NAS
> does receive a valid IP address on the LAN.

Look into /sys/class/leds, there is a directory for each led which
contains a file trigger which defines how the led behave.

Which kernel version are you using?

Best regards
Uwe

Mauricio Tavares

unread,
Sep 13, 2016, 2:10:02 PM9/13/16
to
On Tue, Sep 13, 2016 at 1:57 PM, [ftp83plus] <ges...@ftp83plus.net> wrote:
> Hello all,
>
> I am a bit new to Debian, and when I laid my hands on an older Qnap TS-109,
> I decided to install it to overcome Qnap's firmware limitations. I followed
> the guide put up by Martin Michlmayr, but currently face three issues:
>
> I can't log in through SSH using root user. It denies me access even when I
> use the password set during setup. I can log in using the standard user, and
> perform "su" to get to root. How come root can't log in directly?

It is good practice not to login into a device as root, instead
ssh'ing as a lame user and then su'ing as needed. With that said, you
should be able to edit /etc/ssh/sshd_config and look for the line that
says something about root login and then turn that on.

> More annoyingly, it beeps every two minutes for unknown reasons.
> The "status" LED is flashing red. LAN LED is off, although the NAS does
> receive a valid IP address on the LAN.
>

As root, check /var/log/syslog

[ftp83plus]

unread,
Sep 13, 2016, 2:30:02 PM9/13/16
to
Thanks for this hint, what about this annoying beep? I could always desolder the buzzer, but that's not a "clean" solution.

tail /var/log/syslog reports
Sep 13 14:08:49 NASAD13D6 qcontrol[226]: ts209: fan error

So I killed qcontrol, which stopped the beep, but not the logging of the error. Is there a clean fix for this bug?

Kernel is:
Linux NASAD13D6 3.16.0-4-orion5x #1 Debian 3.16.36-1+deb8u1 (2016-09-03) armv5tel GNU/Linux

New: I wanted to instal openmediavault on this TS-109 II (not TS-109, sorry for the mistake), but I get error:

"Unable to correct problems, you have held broken packages"

At the same time
dpkg --get-selections | grep hold
returns nothing.

Ideas?

Mauricio Tavares

unread,
Sep 13, 2016, 3:20:03 PM9/13/16
to
On Tue, Sep 13, 2016 at 2:29 PM, [ftp83plus] <ges...@ftp83plus.net> wrote:
> Thanks for this hint, what about this annoying beep? I could always desolder
> the buzzer, but that's not a "clean" solution.
>
> tail /var/log/syslog reports
> Sep 13 14:08:49 NASAD13D6 qcontrol[226]: ts209: fan error

Well, I would try to find out why it is reporting an issue with
the fan. Can it find (detect) the fan? How does it do that? Where I am
getting is that maybe the fan is indeed boink, or the OS is not
detecting the fan.

I have in a Centos box a program to control the different -- cpu, case
-- fans, turning them faster or slower depending on the need. Because
of my motherboard not being the most common I had to edit the fan
config file a bit so program would find it and probe the cpu and
motherboard and then adjust fan speed accordingly.

>
> So I killed qcontrol, which stopped the beep, but not the logging of the
> error. Is there a clean fix for this bug?
>
> Kernel is:
> Linux NASAD13D6 3.16.0-4-orion5x #1 Debian 3.16.36-1+deb8u1 (2016-09-03)
> armv5tel GNU/Linux
>
> New: I wanted to instal openmediavault on this TS-109 II (not TS-109, sorry
> for the mistake), but I get error:
>
> "Unable to correct problems, you have held broken packages"
>
> At the same time
> dpkg --get-selections | grep hold
> returns nothing.
>
> Ideas?
>
I think there probably were other messageswhen you trying to
install that package. Can you post them here?

[ftp83plus]

unread,
Sep 13, 2016, 3:40:02 PM9/13/16
to
From what I could find on Google, the problem comes from the fact the Debian installer can't tell the TS-109 from the TS 209 from one another. The TS-109 series don't have any fan, while the TS-209 does.
Sure:
openmediavault : Dépend: php5-pam mais ne sera pas installé
Dépend: proftpd-mod-vroot mais ne sera pas installé
Dépend: php5-proctitle mais ne sera pas installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».

Roughly translated to: needs packages php5-pam, etc, but they can't be installed.

Rainer H. Rauschenberg

unread,
Sep 13, 2016, 5:10:02 PM9/13/16
to
On Tue, 13 Sep 2016, Mauricio Tavares wrote:

> On Tue, Sep 13, 2016 at 2:29 PM, [ftp83plus] <ges...@ftp83plus.net> wrote:

> > tail /var/log/syslog reports
> > Sep 13 14:08:49 NASAD13D6 qcontrol[226]: ts209: fan error
>
> Well, I would try to find out why it is reporting an issue with
> the fan. Can it find (detect) the fan? How does it do that?

Qnap TS-109 has no fan. Period.

And I am sure that I read about this before on this list.

Martin Michlmayr

unread,
Sep 13, 2016, 7:20:02 PM9/13/16
to
* [ftp83plus] <ges...@ftp83plus.net> [2016-09-13 15:21]:
> From what I could find on Google, the problem comes from the fact
> the Debian installer can't tell the TS-109 from the TS 209 from one
> another. The TS-109 series don't have any fan, while the TS-209
> does.

This is correct. Fow now, you have to edit the qcontrol config file
to avoid this issue.

Here's the relevant bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712841

--
Martin Michlmayr
http://www.cyrius.com/

[ftp83plus]

unread,
Sep 13, 2016, 8:00:02 PM9/13/16
to
In that case, wouldn't it be easier if the script asked wether it's a 109 or 209 during setup? That would avoid this annoying bug.

What about OMV and packages reported as broken? Should I open a new thread for this different problem?

Pat

Enviado desde mi iPhone
0 new messages