Buffalo Forums
Products => Storage => : GMAN73 July 10, 2019, 05:23:42 AM
-
Im getting a bit sick of the fan noise on my LS220D its way too loud, I feel like getting rid of it and buying another NAS, then I read about installing Debian which has the software to control the fans. I have a look at the guide over at Github from 1000001101000.
I removed my current 3TB and 2TB drives and took a spare 1TB and hooked it up to Ubuntu, I partitioned it to 1GB formated it to EXT3, mounted it and copied over the files initrd.buffalo and uImage.buffalo. I slotted the 1TB into my LS220D, it booted up with the white light flashing then the other light went to Red (is this EM mode).
I then followed the guide from this website https://herzig-net.de/?page=unbrick_ls-wxl by running LSupdater on a Windows 10 machine, but once it does all the updates Im still on the normal firmware 1.70 and not debian. So what Im I doing wrong?
The LS220D is at the default, now if I put in my original (3TB and 2TB drives) will they read okay or will they get wiped and I will have to copy over everything from backups.
Thanks
G
-
Good to hear from you!
I'm not sure where your Debian install went wrong but I'm sure we can figure out a way to get it working. From your description is sounds like something didn't work correctly either with your partitioning or with the install files. It appears that when the device failed to boot the installer image it then booted from the on-board NAND into EM mode (either that or you loaded buffalo's *.buffalo files instead of the ones from GitHub).
Now that the firmware updater has re-partitioned/reformatted the drives you could try again. You can be certain those partitions work with the boot loader which should narrow down where your first attempt went wrong. If you still have trouble I can probably help troubleshoot though I'll need detail about what commands you are using at each step.
To answer your other questions:
The Debian install process doesn't make any changes to the device itself, everything is stored on the hard drive(s). You should be able to put your old drives back in and boot back into the stock firmware without any issues.
As you mentioned, you can control the fan speed from Debian and can use the pwmconfig utility to set the temperatures at which the fan changes speed. Be careful when using this ability, drives can heat up pretty quickly in these smaller devices which could be an issue if you set the fan too low.
-
Hi 1000001101000,
Not sure what is going on, I may attempt to copy the files over to the boot partion using the commands in the github guide. Would prefer using Windows to do this as I have no experience of Ubuntu.
I obtained the two files from the Buster location at github. If I dont have much luck then I will probably sell the NAS on Gumtree and buy something else.
Thanks for the response.
G
-
Well I’ve managed to get to this bit :
6. Navigate to the /boot directory.
cd /boot
Terminal is sitting at [admin@LS220DEABF boot]
Then I have realised how do I copy the files that are stored in my directory “/home/gerry/gman” to the boot folder of the LS220D. I’m a total novice when it comes to Ubuntu Linux commands.
Thanks
G
-
I usually use sftp at that point. The commands will be similar to:
[admin@LS220DEABF boot]: sftp <your user>@<your PC's IP>
> cd “/home/gerry/gman”
> get *.buffalo
-
Think I’m gonna call it a day with this.
After I go to cd / boot
I enter
sftp Gerry@192.168.0.11 (my computer IP from NIC)
Comes up about ECDSA key finger print
Are you sure you want to connect - I select Yes
Cones up Gerry@192.168.0.11 password
I enter 1973 that’s the password I use to logon
Cones up permissions denied.
Shame as I really wanted to try this firmware
G
-
I just ran through it on my ls220de without using sftp, instead I used wget and the python simple http server. here are the commands I used:
$ java -jar acp_commander_cli.jar -t 192.168.1.131 -ip 192.168.1.131 -pw password -c "/bin/busybox telnetd&"
$ java -jar acp_commander_cli.jar -t 192.168.1.131 -ip 192.168.1.131 -pw password -c "chmod -R 777 /boot"
$ cd ..
$ cd Buster/installer_images/
$ python -m SimpleHTTPServer 8000 >/dev/null 2>&1 &
[1] 31817
$ telnet 192.168.1.131
Trying 192.168.1.131...
Connected to ls220de.
Escape character is '^]'.
BUFFALO INC. LinkStation series
LS220DED26 login: admin
Password:
[admin@LS220DED26 ~]$ cd /boot
[admin@LS220DED26 boot]$ mv uImage.buffalo uImage.buffalo.bak
[admin@LS220DED26 boot]$ mv initrd.buffalo initrd.buffalo.bak
[admin@LS220DED26 boot]$ wget http://192.168.1.146:8000/initrd.buffalo
--2019-07-11 08:51:02-- http://192.168.1.146:8000/initrd.buffalo
Connecting to 192.168.1.146:8000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 31138868 (30M) [application/octet-stream]
Saving to: `initrd.buffalo'
100%[=============================================================================================================>] 31,138,868 20.4M/s in 1.5s
2019-07-11 08:51:03 (20.4 MB/s) - `initrd.buffalo' saved [31138868/31138868]
[admin@LS220DED26 boot]$ wget http://192.168.1.146:8000/uImage.buffalo.ls220d
--2019-07-11 08:51:37-- http://192.168.1.146:8000/uImage.buffalo.ls220d
Connecting to 192.168.1.146:8000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4251893 (4.1M) [application/octet-stream]
Saving to: `uImage.buffalo.ls220d'
100%[=============================================================================================================>] 4,251,893 --.-K/s in 0.1s
2019-07-11 08:51:37 (28.0 MB/s) - `uImage.buffalo.ls220d' saved [4251893/4251893]
[admin@LS220DED26 boot]$ mv uImage.buffalo.ls220d uImage.buffalo
[admin@LS220DED26 boot]$ sync
[admin@LS220DED26 boot]$ exit
logout
Connection closed by foreign host.
$ java -jar acp_commander_cli.jar -t 192.168.1.131 -ip 192.168.1.131 -pw password -c "reboot"
$ ssh installer@192.168.1.131
The authenticity of host '192.168.1.131 (192.168.1.131)' can't be established.
RSA key fingerprint is SHA256:f58ol5GJgIp+D8cPGkgqW8ZVpoq0cgnKOyHpfbMOE+M.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.131' (RSA) to the list of known hosts.
installer@192.168.1.131's password:
-
thanks for the post, I'll give it another try tomorrow. Ive reset the SSH and Ive now getting a warning about hosts someone could be doing something nasty, offending ECDSA key in home/.ssh/known-hosts:1 host key verification failed connection reset by peer
I'll try tomorrow thanks for the posts.
G
-
Think that I might buy another NAS I don’t know what’s going on I can connect to the LS220D do the prompt cd /boot but when I do sftp gerry@192.168.0.11 I get the message connection closed by 192.168.0.11 Couldn’t read packet: Connection reset by peer
So looks like that’s stopping me from copying files to the boot folder
-
SSH/SFTP/HTTPS don’t work well within the stock firmware because the tools are old and don’t support the current cyphers/protocols. That is why I provided that example that only uses telnet/HTTP.
Try using the commands from my post, that should get you up and running.
-
Thanks for that info I will give that a go.
Cheers
G
-
Hi 1000001101000,
Well i followed your instructions with my settings : Please see queries in Red
$ java -jar acp_commander_cli.jar -f
$ java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw <password> -c "/bin/busybox telnetd&"
$ java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw <password> -c "chmod -R 777 /boot"
$ cd ..
$ cd home/gerry/ --- (Now does this make a difference to what folder I point too, do the two files need to be present in this folder also)
python -m SimpleHTTPServer 8000 >/dev/null 2>&1 &cd /boot
[1] 31817
$telnet 192.168.0.34
Trying 192.168.0.34...
Connected to ls220de.
Escape character is '^]'.
BUFFALO INC. LinkStation series
LS220DED26 login: admin
Password:
[admin@LS220DED26 ~]$ cd /boot
[admin@LS220DED26 boot]$ mv uImage.buffalo uImage.buffalo.bak
[admin@LS220DED26 boot]$ mv initrd.buffalo initrd.buffalo.bak
wget http://192.168.0.34:9000/axs/u:4c8a94ce61d54943fbb8750110520fd9/initrd.buffalo (I stored this file on my NAS as I got OpenSSL errors with github)
[admin@LS220DED26 boot]$ wget http://192.168.0.34:9000/axs/u:4c8a94ce61d54943fbb8750110520fd9/initrd.buffalo
-- wget http://192.168.0.34:9000/axs/u:4c8a94ce61d54943fbb8750110520fd9/initrd.buffalo
Saving to: `initrd.buffalo'
100%[=============================================================================================================>] 31,138,868 20.4M/s in 1.5s
(20.4 MB/s) - `initrd.buffalo' saved [31138868/31138868]
admin@LS220DED26 boot]$ wget http://192.168.0.34:9000/axs/u:01d062271680162687203aecfb0779da/uImage.buffalo.ls220d (I stored this file on my NAS as I got OpenSSL errors with github)
wget http://192.168.0.34:9000/axs/u:01d062271680162687203aecfb0779da/uImage.buffalo.ls220d
Saving to: `uImage.buffalo.ls220d'
100%[=============================================================================================================>] 4,251,893 --.-K/s in 0.1s
(28.0 MB/s) - `uImage.buffalo.ls220d' saved [4251893/4251893]
[admin@LS220DED26 boot]$ mv uImage.buffalo.ls220d uImage.buffalo
[admin@LS220DED26 boot]$ sync
[admin@LS220DED26 boot]$ exit
logout
Connection closed by foreign host.
$ java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw <password> -c "reboot"
$ ssh installer@192.168.0.34 (This was the only part that failed I got ""ssh installer@192.168.0.34
ssh: connect to host 192.168.0.34 port 22: Connection refused"" Now is this the command that installs the Debian as I rebooted the LS220D and when I went to the IP on my browser the same config page is there, I dont see anything about Debian same goes for the Advanced Settings section.
-
howdy,
question 1: The exact folder doesn't matter at all, it merely needs to be the directory with the *.buffalo files.
question 2: I should have been more specific about the last part, though I show the commands one right after the other between issuing the reboot command and attempting an ssh connection you need to wait 5 minutes or so for the device to shutdown and then boot into the installer image and start the ssh connection. that error could indicate that you merely didn't wait long enough.
it looks like you're really close to getting it working.
-
Hi 1000001101000,
Done all the commands
gerry@dell:~$ java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw <password> -c "reboot"
ACP_commander out of the nas-central.org (linkstationwiki.net) project.
Used to send ACP-commands to Buffalo linkstation(R) LS-PRO.
WARNING: This is experimental software that might brick your linkstation!
Using random connID value = 8********A
Using target: 192.168.0.34/192.168.0.34
Starting authentication procedure...
Sending Discover packet...
Found: LS220DEABF (/192.168.0.34) LS220DE(GOICHIJO) (ID=004814) mac: **:**:**:**:**:** Firmware= 1.700 Key=*********
Trying to authenticate EnOneCmd... ACP_STATE_OK
Trying to authenticate with admin password... ACP_STATE_OK
>reboot
OK (ACP_STATE_OK)
Changeing IP: ACP_STATE_PASSWORD_ERROR
Please note, that the current support for the change of the IP is currently very rudimentary.
The IP has been set to the given, fixed IP, however DNS and gateway have not been set. Use the WebGUI to make appropriate settings.
At this point the LS220D reboots so I have done it right, I will wait for 10mins and then I do the following below with the same terminal open that I used for all the other commands
gerry@dell:~$ ssh installer@192.168.0.34
ssh: connect to host 192.168.0.34 port 22: Connection refused
So the Port 22 Connection refused bit is stopping me from installing, this is the only stumbling block. Will the initrd.buffalo and initrd.buffalo still remain on the boot folder even if I switch it off or will I have to redo the whole scripts.
Just wish I could get this port 22 connection sorted I get the impression that its my ISP Virgin Media thats blocking it with their crap Superhub 3, though when I run ShieldsUp at grc.com and it gives me a green box (stealth) for SSH 22 when I probe it the port shows as closed
So looks like my ISP is the culprit for the last part :(
-
1. Yes, the files will stay in place between reboots.
2. All the connections involved in this process are on your local network, your ISP won't be involved at all.
if it still doesn't come up if you try too boot it I'd guess the *.buffalo files could be bad (perhaps improperly downloaded from github or otherwise corrupted). Could you run md5sum *.buffalo* in the folder where those files are and post the result?
-
uImage.buffalo.ls220d - C76D2BFF42E942B453722F749C517724
initrd.buffalo - 0EFF3BF6BC8418300E18A2FCAAFC9B99
I decided to connect the LS220D LAN cable directly to my PC NIC, set an IP for my NIC. Linkstation was recognised when I input the Linkstation IP address 192.168.0.34 into my browser and it takes me to the Linkstation settings page, but still the same error message ssh: connect to host 192.168.0.34 port 22: Connection refused
So it must be something to do with my PC and nothing to do with the Superhub 3.
Just to check that the command is ssh installer@192.168.0.34 I dont have to put anything else in like Admin hostname password etc.
Thanks.
-
uImage.buffalo.ls220d - C76D2BFF42E942B453722F749C517724
initrd.buffalo - 0EFF3BF6BC8418300E18A2FCAAFC9B99
I decided to connect the LS220D LAN cable directly to my PC NIC, set an IP for my NIC. Linkstation was recognised when I input the Linkstation IP address 192.168.0.34 into my browser and it takes me to the Linkstation settings page, but still the same error message ssh: connect to host 192.168.0.34 port 22: Connection refused
So it must be something to do with my PC and nothing to do with the Superhub 3.
Just to check that the command is ssh installer@192.168.0.34 I dont have to put anything else in like Admin hostname password etc.
I tried using a program called ACP Commander GUI for Windows and it connects to the LS220D using Enable SSH on port 22936 and it seems to recognise it, but if I change it to port 22 then it does not, so I may need to change the SSH config for port 22936 on ubuntu sshd config.
https://nerdkey.co.uk/guides/enable-ssh-linkstation-stock-firmware/
BTW - Im on V1.70 FW
Thanks.
-
Open SSH
https://forum.nas-hilfe.de/buffalo-technology-nas-anleitungen/ssh-freischalten-auf-einer-ls210d-t2408.html (https://forum.nas-hilfe.de/buffalo-technology-nas-anleitungen/ssh-freischalten-auf-einer-ls210d-t2408.html)
Do NOT use the ssh command from Windows 10. The LS is to old.
Use Putty.
-
Oxygen8 I’ve ran the commands that you linked too with my settings and now I run putty with the ip and it’s connects which it would not before
I enter admin and nas password and now when I do ssh using putty in Ubuntu it now actually does something instead of refusing to connect,
Is ssh installer@ip the command to actually install the Debian FW or should it install once it reboots I already have the two files sitting in the boot dir or do I run another command instead.
-
I checked those hashes against mine and they are correct. This must be really close to working.
Could you try again and post your full terminal output from the attempt? If you’re missing a step or something we should be able to spot it that way.
-
Hey there,
I did a video of what ive done right up until I use the reboot command and wait 5 mins.
See the playlist on youtube.
https://www.youtube.com/playlist?list=PLGFsAkG6spGE8QFDzmaHtHuKFB7Xl2su4
java -jar acp_commander_cli.jar -f
java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw password -c "/bin/busybox telnetd&"
java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw password -c "chmod -R 777 /boot"
cd ..
cd /gman/
python -m SimpleHTTPServer 8000 >/dev/null 2>&1 &cd /boot
[1] 31817
telnet 192.168.0.34
Trying 192.168.0.34...
Connected to ls220de.
Escape character is '^]'.
BUFFALO INC. LinkStation series
LS220DED26 login: admin
Password:
[admin@LS220DED26 ~]$ cd /boot
[admin@LS220DED26 boot]$ mv uImage.buffalo uImage.buffalo.bak
[admin@LS220DED26 boot]$ mv initrd.buffalo initrd.buffalo.bak
wget http://192.168.0.34:9000/axs/u:dfed1e5c82defa6fd5aa78953443df73/initrd.buffalo
wget http://192.168.0.34:9000/axs/u:0303b00b7e5690a30a2b35d36ce56cc9/uImage.buffalo.ls220d
[admin@LS220DED26 boot]$ mv uImage.buffalo.ls220d uImage.buffalo
[admin@LS220DED26 boot]$ sync
[admin@LS220DED26 boot]$ exit
logout
Connection closed by foreign host.
$ java -jar acp_commander_cli.jar -t 192.168.0.34 -ip 192.168.0.34 -pw password -c "reboot"
-
okay, I think I see the problem now.... possibly.
change your wget to pull from the python http server you started rather than from the copy you put on the nas share.
it should be:
wget http://<ip of your desktop>:9000/initrd.buffalo
etc.
I don't see specifically why your method wouldn't work but I'd like to try it the other way to be sure.
-
I get a connection error when doing wget myipaddress this must involve configuring wget to pull files from my folder on my PC which I don’t know how to do. :(
Anyway I pulled the two files over did sync and then ls to list folder to make sure they were sitting there with the buffalo bak files, they were I used the reboot command and it rebooted well no Debian showing in the webpage for the NAS, did all the commands again up until I got into the boot folder and the 4 files were still there 2 buffalo and the 2 bak. So it’s not booting them for some reason.
I switched it off and I took out the 2TB HDD in bay 2 and turned it back on did all the commands again and I notice that in the boot folder the 2 bak files are not there so that got me thinking has the boot folder I’ve been seeing been for the 2TB in bay 2 and not the 3TB in bay 1.
So I’ve done all the commands again and transferred the files over and done the reboot command. It started flashing for a minute and now it’s just staying white with no hdd loading, getting page not displayed when using the IP address in the browser and it’s recognising it in my router devices by its MAC address and not the name of the device, so think it’s start to call it a day.
Thanks for all your advice everyone
-
That sounds like the behavior you should see if it’s working.
Try connecting via ssh again (ssh installer@<ip address>)
-
Hey 1000001101000
So I decided to test it with a fresh HDD that I have spare.
Done all the usual commands, transfered the files, done sync, done ls to make sure the files are loaded on cd /boot of the LS220d.
gman@gman-XPS-8300:~$ ssh installer@192.168.0.11
The authenticity of host '192.168.0.11 (192.168.0.11)' can't be established.
RSA key fingerprint is SHA256:vst+Dz12epdYOkHfyEhRe6kvtaFO47yJCwN+TowIr5s.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.11' (RSA) to the list of known hosts.
installer@192.168.0.11's password:
Permission denied, please try again.
installer@192.168.0.11's password:
So when I do ssh@192.168.0.11 its asking for a password which I dont know how can I find out the password, this is the bit thats always puzzling me the password, when you did ssh@yourip what password did you put it, your user password for your linux logon, your NAS password or a password that you created for this , this password bit has been a stumbling block for me.
Update - The password is install so now going to attempt install. :) :) :) :) :) :)
-
Excellent! You can go back to the github instructions from this point.
The username is installer and the password is install
-
Wow cannot believe ive got this far, so many options to chose from. Its confusing, but will see how it goes.
-
Awesome.
Just remember the first partition/array needs to be formatted ext3 and mounted as /boot
If you’d like, take a screenshot of the partition screen before you save your changes and I can verify if it looks ok.
-
Hi 1000001101000,
So 1st partition set to ext 3 and mount is set to /boot also selected format, though it’s came up about root file system which partition mount is set to /
If you don’t use raid take it you just use the scsi disks further down.
Thanks
-
You can do it either way, though if you don’t use raid you should delete the arrays first.
You can use the first array as /boot as long as it’s formatted ext3
-
Well it finished the installation and the NAS then rebooted. Should I not have a different webpage menu for the NAS or will changes like fan speed etc need to be done via ssh / terminal etc.
Thanks
-
The installer just sets up a basic debian install which includes the ssh server. Anything else you need to install yourself, such as fancontrol to control the fan speed.
If you want a web interface you can try installing openmediavault which I found works reasonably well on these devices.
-
One thing I did notice though is last night it came up finished installation even though the bar was only at 95%.
I decided to try again with a different fresh 1TB hdd in , one thing I was reading over at https://wiki.debian.org/InstallingDebianOn/Seagate/PersonalCloud
is that it also mentions using a DTB file for you device. So decided to put the LS220 version on the boot folder along with the other two files. I did the install, but it never gave me those confusing different options and the install seemed to be differnet from that of the 1st attempt on the 500Gb drive which gave me different options. I got the Finish the Installation message, selected continue and then it started installing other stuff then it came up Finishing the Installation, but once again it ended at 95% followed by connection closed by myip.
On the partition bit cannot remember what option I used, but the option created, the partitions for me i.e boot, swap etc.
https://imgur.com/Kdv0ArG
https://imgur.com/WgCsXym
The device rebooted and its not booting up lol, though I can still access the ls220d via ssh installer@myip
Would be great a see a full video of the install of Debian and how it looks running on the buffalo NAS.
Im going to give it another go anyway.
-
1. These device load DTBs differently than the Seagate Device you read about. The DTB is actually appended to the kernel file before it is packaged for the bootloader. Loading the file into /boot won't affect anything.
2. Make sure to get a picture of your partition screen this time, that is almost certainly where things are going wrong. The installer doesn't have anything in it to verify whether you've selected a configuration that will actually work or not. I may try to add that to a future version but that'd be a tough thing make work reliably.
3. I believe there is a youtube video of someone installing Debian on an older device that should be basically the same process. If I get some time in the next few days I'll try recording a video while running through an install.
4. I've never noticed the progress bar ending at 95% before but I doubt it's an actual problem. I'd guess that it closes the ssh connection at 95% and updates it to 100% when it finishes other shutdown tasks but you don't get to see it because the connection ends.
-
Partition installer screen.
https://youtu.be/3qEo-bu0l3M
-
That looks like it should work if you make the first raid device (#0) /boot and the second one (#1) /
-
Hey 1000001101000,
Well tried this with the spare 1TB HDD (this wont be the actuall HDD im using, just using this to test it, raid is not setup on my NAS as I dont use it) I have selected manual for the partition and did device #0 /boot and device #1 / (root), but eventually got an error message after a bit "the target file system contains the files from past installation", i hit yes and eventually i got error base system installation error. It is a new 1TB HDD setup from scratch and with the 2 images copied over why do i get "target file system contains files from past installation.
One thing I did notice though on the /boot folder of the LS220D it mentions u-boot-ls210.buffalo even though its not a LS210?
https://imgur.com/vPRwRVT
I installed Kazam and did a screen capture of this process and uploaded it to youtube if you get the time at somepoint it would be great if you could review the video to see where im going wrong, dont see me ever getting this working
https://www.youtube.com/watch?v=rb9jIoWzFk0&t=
Cheers for everything.
-
I believe you'll want to be sure to answer "yes" to reformatting when you specify the arrays as ext3 and used for "/" and "/boot". I beleive this is just what happens if you don't reformat and it detects a previous OS installed there.
-
Well looks like I finally got this working, I formatted the two partitions and it started the install. I got no errors what so ever. The device rebooted, left it for 5 mins, went to log onto my IP, but not connecting, checked on my router page and I saw that the NAS IP was connected and its now called debian. Did ssh username@myip it asked me for password I entered the one created during the install process and I got this so looks like its been installed. So this is where I log on to install all the goodies.
https://imgur.com/a/odGyQIg
Now to figure out how to install a debian menu or another custom menu so I can see my NAS webpage when I go to the IP on my browser. I notice when I turn it off at the back switch it still remains on, Im sure there are scripts to re-enable that to power down.
Uploaded a video of it to Youtube here - https://www.youtube.com/watch?v=5L7frjOxPcM
Will record a part one with the java commands etc.
All I can say is 1000001101000 thank you so much for the advice its been so helpful.
-
Sounds like you’ve done it.
If you want a web interface to control most things, openmediavault works reasonably well on these devices. Otherwise there are guides online to do just about anything you can think of in Debian.