1000001101000/debian_on_buffalo

Tools for Installing/Running Debian on Buffalo ARM based Linkstation/Terastation/Kurobox/Cloudstor devices.

debian_on_buffalo's Issues

How to switch back original firmware?

I installed Debian 9 on my Ls421de , it's run fine. Then I want to test with original firmware,so I replace /boot initrd.buffalo and uImage.buffalo with orginal file. After reboot ,the Ls421de is dead.
I want konw the method that switch from Debian and original firmware ,thks!

Network Shut Down

I have tried this, using firmware 1.84, one hard drive in my 4 bay LS441DE. When it boots to installer and I ssh to it. The network card on the ls turns off. Only way to get it back on is to plug power plug on ls. Then start the process over only to have it do the same thing. Network card on the ls will not even stay on long enough to run installer

RAID Setup

Hi, I've done a few test installs using MDRAID and BTRFS (RAID10 with 4x4TB HDD). All work fine until I pull one of the drives to test breaking the RAID for recovery. At this stage I am unable to login to the NAS. Does anyone have any ideas about whats going wrong here?

I had a separate /boot and / partition as ext3 on all 4 disks, then created the raid on the remaining space on all 4 disks. I Tried pulling out a different disk each time with no difference in results.

Edit: I shutdown the NAS first when I pull one of the drives out. I cant login when it boots after that.

/

Can not install debian on buffalo LS410D

Hi Mr.1000001101000
I can not install debian on LS410D, my steps are below:

1. clear all partitions in HDD to get blank HDD
2. use TFTP to setup IP for LS410D (use DHCP)
3. install firmware 1.86 with re-partitions and format disk, NAS runs OK as usual
4. use acp_commander to setup SSH (this firmware does not has telnet service built-in) and I can ssh to LS410D ok
5. get 2 files initrd.buffalo, uImage.buffalo.ls410d from Debian_on_Buffalo/Buster/installer_images/armhf_devices/ then copy to /boot with name initrd.buffalo, uImage.buffalo (I already backup these old files in /boot) and with mode 775
6. run "sync" and reboot
   Then Nas can not boot, red light blinks, and Nas can get IP via DHCP. So I try run TFTP again, it comes back to normal Nas without user "installer" and if I restart again, red light blinks again without IP. I thinks your 2 files initrd.buffalo, uImage.buffalo.ls410d seems to be not compatible with my Nas. I try with 2 files in Debian_on_Buffalo/Stretch/installer_images/armhf_devices/ but the issue is the same.
   Please help me to install
   Thanks so much

LS220D - booting an installation image after Debian installation

Hi

I have Buffalo LS220D and tried to install Debian using your instructions.

Install went well but after reboot when I ssh to the box it does not accept my root password. I used only one letter password for simplicity. During installation I also created another user account (one letter password as well) and tried to log in using this user but also unsuccessful.
Then I tried log in using installation user - and it works but of course I was displayed with the installation menu :-(
So therefore I think that my Buffalo boots still using your installation image rather than the installed Debian.

Please can you help and advise what I missed and if there is a way to resolve?

Thanks a lot.

Built-in ethernet on LD410d0401 randomly shuts down

kern.log
By having the ethernet randomly shut down on me, it causes significant downtime that can only be solved either by rebooting my machine, or disconnecting its power source and connecting it back again. My only workarounds are to use a USB ethernet adapter or a different computer with different ethernet chipset entirely.
I have installed Debian 10 Buster, with kernel version 4.19.0-5-armmp.

I had this happen at least twice to me already, and most workarounds I specified will either take too long, or give worse performance:
Sep 4 17:16:37 ls410d0401 kernel: [253058.158786] mvneta d0074000.ethernet eth0: Link is Down
Sep 6 02:37:33 ls410d0401 kernel: [106025.969282] mvneta d0074000.ethernet eth0: Link is Down

Always boots to installer

Apologies - I'm a bit of a noob in this area. I followed the instructions step by step, but then I was left to fend for myself at the Debian install. When it asked me to partition the disk, I allowed it to use some free space at the end of the disk (I didn't want to lose all the content on my NAS) where it created 3 new partitions.
After install, it's rebooted back into the installer. I can only SSH in with installer/install.

Did I choose the correct option for partitions?
How do I now get my LS210 to boot to the newly-installed OS?

Cheers

ls210 partitioning scheme

Whilst trying to install on ls210 it struck me I don't know which partitions I can change from the default:
SCSI1 (0,0,0) (sda) - 2.0 TB ATA WDC WD20EZRZ-22Z (1) 1.0 GB ext3 primary
458.2 kB FREE SPACE
(2) 5.1 GB ext3 primary
(3) 393.7 kB K biosgrub primary
(4) 512.0 B primary
(5) 1.0 GB F swap primary swap
65.0 kB FREE SPACE
(6) 2.0 TB xfs primary
8.4 GB FREE SPACE
I believe (1) is the partition where the initrd.buffalo and uImage.buffalo reside. (2) seems to be where the original operating system from buffalo is installed, (4) is swap, (6) is presumably the "data" partition. Question is which ones of these do I need to leave as-is, which can I wipe clean of data and which can I remove completely and repartition as I see fit? What sort of partitioning scheme is recommended here?

Terastation Pro II Debian Install Fails (runs out of space)

Running the debian installer fails at the Select and Install Software stage.
I have tried with both the stretch and buster images and get the same issue.
The terastation is left without boot image (E06 TFTP Mode) and then needs to be recovered with a stock firmware to be usable.

Installing on LS-WVL

I'm hoping to try this on a LS-WVL. The mainline kernel has the device tree (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/kirkwood-linkstation-lswvl.dts). Is it only a matter of building the dtb file and following the "hard way" in https://github.com/1000001101000/Debian_on_Buffalo/blob/master/1-Obtain%20install%20files with the provided armel image? I've already got ssh root access on the LS.

Not Issue - Sord of... Request - Wake on Lan

HI there, is me again !
Device is working awesome !

However, is it possible to enable wake on lan ?
The storage during the night has no activities, and was wondering as a home user, to "relief" fan noise or even... cool down processor, disks and so on...

Thaks.

Effective usage of RTC clock in LS421D

The post-installation section suggests to build module RS5C372 to use the device RTC as it is not enabled natively in debian kernel.
However at boot time the module is enabled after the kernel tries to pick up the HW clock time, so system time is not updated until fake-hwclock or ntp come into play:
[ 6.448247] hctosys: unable to open rtc device (rtc0)
[...]
[ 7.926074] rtc_rs5c372: loading out-of-tree module taints kernel.
[ 8.001860] rtc-rs5c372 0-0032: rs5c372a found, 24hr

ref:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855203

I circumvented this problem by adding the following udev rule as suggested in this forum post

KERNEL=="rtc0", RUN+="/sbin/hwclock --rtc=$root/$name --hctosys"

It may be worth mentioning it in the post-install steps doc.

update debian stretch to Buster

hi, copied files DTB in your source Debian_on_Buffalo-master\Buster\device_trees to /etc/flash-kernel/dtbs, but the version not change

Cannot install on LS421de, network disconnects

Hi 1000001101000,

First of all, thanks for your work on enabling the use of Debian on Buffalo NAS.

I have a LS421de for quite some time, and I want to upgrade its software. I follow your instructions to update to Debian Linux, but when I'm installing Debian, the network disconnects. I tried at least 10 times with the same result. And it happens in different screens of the installation process. I have the LS421de connected directly to the router (gigabit ethernet) with the network cable it came with. I tried changing the cable, changing the port it is connected in, and same result. I also tried to limit the ethernet speed to 100M before starting the installation, but still it disconnects from the network. I tried with the Stretch version, same result. And with the stock firmware it works fine. I checked the Issues in the repository, read every forum I could find but can't find the solution. So my last resort is to contact you. Any help you can provide will be greatly appreciated. Thanks.

Need more explanation in steps 3 and 4

For the record, I'm working with a LS220D.

I've gotten up through running the installer, but now I'm stuck. Actually I was stuck before the installer but checked out the link to OpenLinkstation and discovered that the password to get to the installer was 'install', something not mentioned in this project.

So, I've made it through the install and supposedly gave it a root password and an admin account, and then at the end it says to remove the install media. Of course there is no separate install media so when I reboot it just returns to the installer. Then, if I go to a shell it says that the drive is mounted in /target which doesn't exist, there is nothing I recognize as a disk block device in /dev, and when I exit it doesn't return to the installer but to a console log listing my failed attempts to login with the root or admin I set.

I guess the question is what do I do now to boot to the new Debian system? If you can give me an answer, it needs to be put in the step instructions.

Terastation System Error E04 can't load kernel. Then EM mode panic!

Having succeeded with getting Debian Buster onto my Linkstation LS-VL, my efforts with Terastation(s) are not yet fruitful. I have enough working parts for one between two castoffs (a HS-DHTGL & a TS-HTGL).

The install went well (after learning the hard way, see PS below). The resulting installer logs look good. I can’t find any logs for the failing boot attempts.

Following install, the system ends up in EM Mode panic. Once after loading kernel for some time and then throwing "System Error E04 can’t load kernel".

I have tried multiple times with multiple disk numbers (1, 2 and all 4) and partition formats.

The latest and most apparently successful incantation is as follows.

The folder /boot exists on the first partition which is formatted as ext3 and marked boot.

[root@sysresccd /mnt/sda1/boot]# ls -al

drwxr-xr-x  2 root root    4096 May 26 07:23 .
drwxr-xr-x 18 root root    4096 May 26 07:18 ..
-rw-r--r--  1 root root  164677 Oct 13  2019 config-4.12.13
-rw-r--r--  1 root root 5674948 May 26 07:23 initrd.buffalo
-rw-r--r--  1 root root 5674884 May 26 07:23 initrd.img-4.12.13
-rw-r--r--  1 root root 1549363 Oct 13  2019 System.map-4.12.13
-rw-r--r--  1 root root 2063608 May 26 07:23 uImage.buffalo
-rwxr-xr-x  1 root root 2063536 Oct 13  2019 vmlinuz-4.12.13

/etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>   	<dump>  <pass>
# / was on /dev/sda1 during installation
UUID=43f3a284-1eec-4aa9-877c-2f3077dc15f7 /           	ext3	errors=remount-ro 0   	1
# swap was on /dev/sda5 during installation
UUID=867f5c7d-aa4e-4302-b6b5-82bec686db04 none        	swap	sw          	0   	0

Any ideas on what I might do next?

PS It may help others to know that when the installer doesn’t complete, it leaves the ‘installer’ initrd.buffalo & uimage.buffalo. The login is therefore user: installer and password: install. I wasted quite some time investigating why root or [user] logins weren’t working, thinking the SSH login was to a resulting Debian system rather then the installer.

LS441DE

Still having network issues. Sorry It has been a while. I had to replace my hard drive PCB. It took a crash.
I have used the updated files you put on here, now all the network does is blink then shuts off. I can not even start installer. The zip file I received from you worked for a moment, then went back to shutting off. Any suggestions. I have no stock firmware on drive it is blank and formatted with the files in /

Stretch on LS210DC35 boots without network

Hello,
Installer for Stretch seemed to work flawlessly on LS210D but after rebooting at end of install, I can't find any open ports at the address I used during the installation, nor do I find any new DHCP slots taken in the 192.168.1.1/24 subnet. Network lights are lit on the box and the router.

I have a nice solid white status light but no way of shutting down other than pulling the power plug.

I took the hard drive out of the box and mounted it directly on another machine, found this is syslog:

Mar 10 12:48:44 unknown8857ee571c35 systemd[1]: Started ifup for eth0.
Mar 10 12:48:44 unknown8857ee571c35 systemd[1]: Starting Raise network interfaces...
Mar 10 12:48:44 unknown8857ee571c35 systemd[1]: Starting Create Volatile Files and Directories...
Mar 10 12:48:44 unknown8857ee571c35 sh[228]: /bin/sh: 2: ether: not found
Mar 10 12:48:44 unknown8857ee571c35 sh[228]: ifup: failed to bring up eth0
Mar 10 12:48:44 unknown8857ee571c35 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE

What else should I look for?

Installation of Jessie works and boots up just fine, but I'd rather run the latest stable.

Thanks.

Looks like I bricked mine, any suggestion/recommendations

Hello,

I have the ls420d, started the process following wiki and the linked youtube video, while partitioning the system, it kept showing error that it could not partition the two 1 TB each drive, looks like apart from the hard drives that we can remove, it has some storage, I removed all the partitions from the two drives, planning to add them later from linux, then moved forward with creating the necessary /boot, / and swap. The installation moved forward normally and seem to have completed successfully.
After that I am not able to access the drives, it is not responding to pings or ssh. What are my options? I am able to put the stock firmware again, but how since now I cannot get to the thing?

Checked to see if the IP may have changed by checking all the IPs in my home network, not able to find Buffalo drive.

Please recommend how I can move forward.

Best Regards
Pankaj

LS441D - Failed to see fan in sensor

When I run sensor, it is missing the fan.

root@ls441db64:~# sensors
armada_thermal-virtual-0
Adapter: Virtual device
temp1:        +70.4°C

As a result, after I installed fancontrol and run pwmconfig, it throws the following error:

root@ls441db64:~# pwmconfig
# pwmconfig revision 6166 (2013-05-01)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed

Is it possible to control the fan in 441D, please?

LS441D - Failed to boot when manually create RAID10 array for Disk #1 with metaversion 0.9

Hi,

I have bricked my NAS a few times but still couldn't get it working.

I am a bit fussy and want to get my disk partitions to look clean.

What I did is that I removed all stock arrays and partitions and used the installer partition disks to re-create the arrays and partition in a nice way and manually created Disk #1 RAID10 array with mdadm with version 0.9 as per mentioned in #6 (comment)

The way how I created the array is the same as #5 (comment)

Just that mine is RAID10 arrays with 4 disks

I couldn't trigger the error message about the GRUB when the installation finished.

My NAS bricks after the reboot.

I think my next step is to repartition the arrays using the stock firmware and remove everything except the Disk #1 Array which would be where the /boot mount to.

I think in that case, I will have a RAID 1 array Disk #1 for /boot and the rest for other RAID10 arrays (i.e. / and swap)

Just want to post my idea here so I can get some recommendations to have nice looking arrays and partitions.

Cheers

LS220D login issues after installation

First, thank you for all of your work to make the Buffalo NAS a lot more useful!
I'm facing a strange issue at the moment...
After completion of the installation on an LS220D the device restarts and after a few minutes the ssh entrance is back open. However I'm just not able to log in with the users that I've set up during the installation. I thought maybe I've mistyped something and went through the installation once again. But no... The device is still not allowing to let me in. Neither with the created user nor with the root user (I used the username 'test' and password 'test' to avoid some strange things happening on my second try). Also I've checked whether the installation process might have crashed or restarted by trying the installation login and my old original buffalo admin login. Currently I'm out of ideas... Maybe someone has a clou what I'm doing wrong. Thanks for your help!

sockettimeoutexception on acp_commander

Hello 1000001101000 - I messaged you on buffalo forums awhile back, now i'm trying to get debian running again on my LS441DE while keeping my raid arrays intact. I believe last time I was able to use your acp_commander to get the the images onto the drive. But now every time I get this sockettimeoutexception

from admin command prompt:

C:\Windows\System32\acp-commander-master>java -jar acp_commander.jar -f
LS441DE93       192.168.1.4     LS441D(HORIKAWA)        ID=00643        mac: xxx  FW=  1.860
Found 1 device(s).

C:\Windows\System32\acp-commander-master>java -jar acp_commander.jar -t 192.168.1.4 -pw mypassword -o
A SocketTimeoutException usually indicates bad firewall settings.
Check especially for *UDP* port 22936 and make sure that the connection to your LS is working.
ERROR: Exception: SocketTimeoutException (Receive timed out) [ACP Send/Receive (Packet:80A0 = SPECIAL_CMD_EN_ONECMD)]

C:\Windows\System32\acp-commander-master>

LS441D - Issue `shutdown -r now` command will power off the NAS but then it power on again by itself.

I installed the latest installer image of Stretch.

After I issue shutdown -r now, it will turn off the NAS but straight away it is turned on again by itself.

It leaves me no choice but to unplug and plug again to power it off.

Would be appreciated if I can get some help :D

Cheers

Trying this out soon on new LS220DE

Hey!
Really nice that this project exists!

Just wanted to give feedback and tell that I'll be testing this out on new LS220DE when it arrives and I find some spare time.

The USB should work normally with debian? The aim is to create wireless home-NAS just because there seems to be no ready made solutions with raid capability floating around. Going with TP-LINK TL-WN821N MINI wlan stick because I read it works nicely with raspberry pi etc using debian based software.

Buffalo LS-Q6.0TL/R5 Compatibility

Hi,

I've just had a go at installing Debian on a Buffalo LS-Q6.0TL/R5, but when I reboot after copying across the installer files, the device displays the four green drive lights and a blue flashing power light for around a minute, then shuts down.

I've used the uImage.buffalo.lsgl Buster installer since it apparently shares the same architecture as the LS-GL.

Is it possible to install Debian on the LS-QL and if so, is shutting down on boot a known issue?

Many thanks, Andy

(LS220D) Can't boot up if root and swap is encoded in setup

Hey there,
first of all thank you soooo much for these awesome software it works really great, now I can spindown my drives can close unused ports and can use it only as SMB server :D
Because you can easily pull out the drives I just want a bit extra safety, so I tested the whole day to set up an encoded drive but it didn't work:
In the Partition Setup I have set up the /boot as not encoded drive as first drive.
then i have cerated a Raid 0 Array
After these I created a 1000MB encoded disk
and a 4TB encoded disk
after these i enabled encoding and set the 1000MB to Swap and the 4TB for the root directory.
So the /boot is not on the raid and is not encoded.
So it should boot but there is some trouble with the encoding due the linkstation just blinking white (endless). If there was an error with the /boot the Linkstation should blink red 7 times so I guess the boot partition is fine but it can't get go further due the encoding.
Sadly this thing doesn't have a displayport to debug the startup...

Not an issue - USB ethernet compatibility

Hi,

I'm planning to buys an LS210D, due to the fact that there is a working linux firmware for it.
I'd like to use two ethernet ports, so I'm plannig to use it with an USB ethernet adapter.
This is the linux driver for the adapter that I'm planning to use with it:
https://github.com/rickhofstede/linksys_usb3gigv1_linux

What are my chances to get it working on an LS210D?

Thanks.

Better Instructions

Hi, sorry about this kind of topic, but, I think I'm not the only one with installations informations problems.
I acquired this device LS441D 6 months ago supposing to be able to use rsync, nfs server, smb server (I have at home linux, mac and windows devices), but I got so disappointed and want to use "a linux based" kernel.
I'm not a guru like you guys, I know the basics. I'm trying to get this working fine, but the step-by-step in the main page, for me at least is too complicated:
Steps 1 to 4, for a not Linux developer guru is a little bit complicated, I appreciate if the steps could me be more.... easier and detailed - have no idea how to obtain the DTB or transfer the installer...
Once again... I'm very sorry to post this message here.
I was so excited when plug the device on, put the 4 4TB disks, but after created the raid, transfer the files then... the daily basis stuffs such as sync files, copy files and so on, eveything using windows explorer, copy from raid to usb disk must be made.... over the lan.. oh it is crazy...

Thanks.

Marco

Installer Stuck - Setting debconf\language to en

I might be missing something here but I ssh into installer@IP with password install. The session connects but I get stuck at

debconf: setting debconf/language to en

I can halt this and get to a busybox prompt but there isn't really anywhere to go from there.
Buffalo TS-XE4.0 -- using initrd and buffalo-ff... images for "Buster" from the repo. So I believe I have everything right here. Any suggetions/ideas?

[LS421D] Cannot allocate skb on queue 0

Hi there!

On LS421D I observed various issues in dmesg after noticing the NAS was going completely stuck after random time, even sometimes few hours.

ksoftirqd/0: page allocation failure: order:0, mode:0x480020(GFP_ATOMIC)
Seems similar to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901420

For now solved by increasing in sysctl.conf vm.min_free_kbytes = 8192
I will monitor & report but the default 2000 & something (can't recall exact value) seems too low.

Thanks for this great work 1000001101000!

LS420D image sets random mac address at boot

I tried the images you built, under Stretch folder, but I cannot find the device on my network after booted some time.

Since I saw there's another report stating not working, could you kindly list the models you tested, and another list for un-tested devices?
Thank you!

LS-X1.0TL

I know this is a longshot, but I was curious if there was a way to install Debian to the subject device? It has no USB / power switch but it would be a lot more useful running Debian than the stock firmware.

Thanks!

Debian Buster on LS 220D

Hello,
some days ago I installed Debian Buster on my LS 220 D Linkstation. Installation worked out pretty well after using the right acp_commander.jar.

Then, I installed Openmediavault 5.
This started the problem as after reboot of the linkstation, I wasn't able to ssh to the machine anymore. Could be, I messed up the network interface through the OMV interface.
Even worse, I can't find the linkstation, neither through my router nor through nmap. Ping says (buffalo used to be the hostname):

ping: buffalo: Name or service not known

I'd go back one step and reinstall Debian 10 again from scratch and get rid of OMV, but I'm out of ideas, how to access the Linkstation at all.

Does anyone around have an idea?

Any ideas are very welcome!

Debian in Buffalo LS-CHL-v2

Hi
I don't see LS-CHL-v2 firmware in your list of files.
Is it possible to install Debian in it ? I see some guide lines in Google search but they are too old and seem to be not ok now
Thanks so much

button is not useable

After I installed the images step by step, I found that the power button did not respond. I can only shut down through the command line.
In addition, this image has some other problems, such as nodejs can not be used, reported illegal instructions; using aria2 may cause the kernel to crash

so how to enable the button

my device is LS 420d

ls-qvl doesn't boot after update & upgrade

ls-qvl doesn't boot after update & upgrade

i don't know how to restore it without reinstall

Users Account

Hi, use the configuration of the raid of linkstattion ls220D, I start with the normal debian installation, but once it finishes, I do not create my user account and do not set the password in root or in my account, which could be

Power Button Detection

Thank you for a most excellent project.

I have it up and running on an LS210. I'd like to sense when the power button is switched to the "off" position. On the stock firmware the location /proc/buffalo/gpio/switch/power holds the power switch position (on/off). Is there a way to read that switch in Debian, or has this problem already been solved?

SORRY AFTER POSTING THIS I FOUND THE DOCUMENTATION.

Sorry for the noise.

• Bob Coffman

Reinstallation and other questions

Hi,
first of all thank you for this fantastic porting that you have done to use a Debian environment on Buffalo NAS.
I have installed the system on a Buffalo LS220D device, installation completed successfully and everything seems to work.
I have trouble using OpenMediaVault system, the RAID array isn't managed corrrectly from OMV and when I try to edit the fstab the system always crashes (ssh access is no more available) and I'm forced to re-edit the fstab manually connecting the hard drives to my PC and re-editing...
My question is:

1. Have you any experience in running OMV on these devices?
2. how should I edit the fstab to not cause system crash?
3. if I want to re-install Debian system from scratch, should I just copy the initial initrd.buffalo and uImage.buffalo or should I follow another procedure?

Thanks again for your software.
BR,
Samuele.

Will it work on Buffalo LinkStation 520 LS520?

Hi, I am curious if it will work on LS520.
Beside that, is LS220 powerful enough to run Docker?

Regards, Alex

No Path To Host

wget http://192.168.1.146:8000/initrd.buffalo
--2019-07-11 08:51:02-- http://192.168.1.146:8000/initrd.buffalo

Gives no path to host error, I am replacing the IP with my own.

TeraStation 5810 Compatibility?

Hey!

This is more a question than a feature request, but I'm curious what's blocking compatibility for the 5x10 series. In particular, I'm interested in whether it might be possible to get Debian installed on my 5810DN, since I believe it uses the same architecture (armv7-a) as the 3400, which is supported.

Many thanks!

Incorrect Password?

I'm trying to get the latest installer running on my LS441D but the password listing in the wiki ('password') is not being accepted.

Debian Buster LS-QVL Ethernet Speed

Hi,
with the original buffalo firmware the network speed was up to 100mb/s, the debian speed is 40mb/s mostly.

Is there a limit on the debian network drivers ?

HDD leds definition on LS421D

In LS421D device tree the HDD leds are classified as hdd1 and hdd2 and the white function led has no default trigger defined.
Actually the two red HDD leds are marked as "Error" led and are hidden behind the front door.

To be consistent with the documentation the two HDD leds should be marked as hdd1err and hdd2err and the white function led have "disk-activity" trigger defined in the device tree

Buffalo LS-500 GL issues on Stretch

Hi "binary"! Thanks a lot for your work!

I had LS-500 GL on Wheezy and then on Jessie for years. Jessie got to EoL.
Couple of days ago I've upgraded it to Stretch. It upgraded well, it works.
But. After couple of hours it starts beeping one separate beep.
After couple of min it turns on fan. Then after couple of min it beeps 1bps.
Then after couple of min it beeps solid, gets unavailable on network and I have to turn it off pressing button.
Logs show nothing. SMART and hddtemp show HDD temp 43C until hang.
lmsensors cant find any mobo/SIC thermal sensors. I look into SIC specs, could not find it. But something turns on the fan (is it just electronic?).
I've turned off smbd, nmbd services I don't use (I use NFS). No help.

I've opened box, the SIC is quite hot for my finger even when there is no activity. Just `top'.

Do you know any way to fix it?
Does it worth to upgrade to Buster? Will it work?
Will it be better, I mean not loading SIC this much when idle?

Is it possible to power on/off schedully?

Is it possible to make the debian on my linkstation power on/off schedully as the stock firmware?

Support for TS-HTGL6FE

Hi @1000001101000

any chance this will run on this model?
the CPU is a ARM926EJ-Sid(wb) rev 0 (v5l)
Hardware: MV-88fxx81
MemTotal: 126280 kB

I would just try it, but i don't know how to unbrick the device if something fails