Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sun Jul 15, 2018 8:06 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 55 posts ]  Go to page 1 2 3 4 Next
Author Message
PostPosted: Tue Mar 26, 2013 6:15 pm 
Offline
Newbie

Joined: Wed Dec 12, 2012 10:25 am
Posts: 72
Hello all,

I would like to use this topic to share what I've learned getting Debian Squeeze on my LS-WVL with a vanilla kernel, patched to work with the LS-WVL. I wanted to give my NAS his brains back, and now I can run OpenVPN. I've been using this for a week now, and it's very stable and responsive. In short: I can recommend this guide to everyone!

If you are wondering: TFTP is available in case you screw up (Which I did very often). Just try it!

I tried to create a wiki, but I don't have any experience with wiki's and it already took me forevery to get my NAS up and running. If someone wants to copy everything over to the wiki, feel free to do so..

Here is the complete guide: http://pastebin.com/H6rEZ5ge This has everything you need for Debian + kernel 3.8.3.

* If you already have debian running, and only want to compile the kernel, go here: http://pastebin.com/9aKT3z3i
* If you bricked your LS-WVL, you can try to get it back by using this guide: http://pastebin.com/5sY24CTQ

Here you can see all the files you may need: http://members.ziggo.nl/roodgoudzilver/lswvl/ If just just follow the guide, you will be told what to download when.

I hope you have as much fun as doing this as I did (Although sometimes I felt like throwing everything out of the window)!

If there are any questions, feel free to reply!

Credits: hato and Phill Sutter, and the original creators of the 'Debian Squeeze on LS-WXL' wiki, I practically copied everything over to my guide.

Update: I have managed to get the fan control working (again thanks to hato & others): http://pastebin.com/ch7TuxED It is also linked in the total guide

Update 2: Updated link to files. Previous host went down. This one should stay up. See here.


Last edited by VolleMelk on Thu Sep 05, 2013 7:54 pm, edited 2 times in total.

Top
   
PostPosted: Sat Mar 30, 2013 5:55 pm 
Offline
Newbie

Joined: Sat Mar 23, 2013 3:31 am
Posts: 10
Will this work with a LS-VL? I guess so...


Top
   
PostPosted: Sat Mar 30, 2013 6:33 pm 
Offline
Newbie

Joined: Mon May 02, 2011 12:29 am
Posts: 6
Thanks a ton for your efforts and time to write all the precise steps down.
I had the same goal (installing an openVPN server on my LS-WVL, also setting the NAS as gateway for my LAN with traffic control so as to prioritize torrent after all other traffic) for a year, but never got the gourage to install debian / change kernel.

I read your guide and it seems pretty well documented to me, it seems I'll even learn a few new things about linux in the process !
Finally having a full blown debian with able kernel is going to be really cool.

The only notable drawback I read is :
# As of 21-03, I have no idea how to get the powerswitch and fancontrol to work.
# If you wish to shutdown the NAS with this kernel (and .config and patch):
# Put powerswitch on back of NAS to 'OFF'
# Login as root
# reboot
# This will power down the NAS.

Losing 'fancontrol' is unclear, and potentially worrying ! Do you mean the fan stops, or blows full speed all the time ? Both seem kinda problematic (the NAS is in my living-room)...

_________________
LS-WVL fw1.42 opened and ipkg-enabled


Top
   
PostPosted: Sat Mar 30, 2013 6:37 pm 
Offline
Newbie

Joined: Sat Mar 23, 2013 3:31 am
Posts: 10
I just tried with my LS-VL and a run into an endless loop.

My boot log is here:

http://pastebin.com/FUBxXd3y


Top
   
PostPosted: Sat Mar 30, 2013 7:01 pm 
Offline
Newbie

Joined: Sat Mar 23, 2013 3:31 am
Posts: 10
Forget about my previous post. It worked!!! Working in the LS-VL! Thanks!!


Top
   
PostPosted: Sun Mar 31, 2013 3:15 pm 
Offline
Newbie

Joined: Wed Dec 12, 2012 10:25 am
Posts: 72
SamuelK wrote:
Thanks a ton for your efforts and time to write all the precise steps down.
I had the same goal (installing an openVPN server on my LS-WVL, also setting the NAS as gateway for my LAN with traffic control so as to prioritize torrent after all other traffic) for a year, but never got the gourage to install debian / change kernel.

I read your guide and it seems pretty well documented to me, it seems I'll even learn a few new things about linux in the process !
Finally having a full blown debian with able kernel is going to be really cool.

The only notable drawback I read is :
# As of 21-03, I have no idea how to get the powerswitch and fancontrol to work.
# If you wish to shutdown the NAS with this kernel (and .config and patch):
# Put powerswitch on back of NAS to 'OFF'
# Login as root
# reboot
# This will power down the NAS.

Losing 'fancontrol' is unclear, and potentially worrying ! Do you mean the fan stops, or blows full speed all the time ? Both seem kinda problematic (the NAS is in my living-room)...


Yes, having the NAS blowing at full speed is annoying. Mine is under the floor of the living room, so I have not made the fan control a high priority. But there is a solution already. I've looked at it quickly, but they are not working for me. I can can control the fan using SSH, so it's just a matter of the script.

See here: viewtopic.php?f=73&t=25943 and viewtopic.php?f=73&t=25947

This will only be a matter of time before it all works.

katossi wrote:
Forget about my previous post. It worked!!! Working in the LS-VL! Thanks!!

Great! Congrats! Did you also manage to compile the kernel with the patches for the LS-WVL?


Top
   
PostPosted: Sun Mar 31, 2013 11:08 pm 
Offline
Newbie

Joined: Sat Mar 23, 2013 3:31 am
Posts: 10
Yes I did without any modification and it worked perfect.

I´m not using any lsmonitor now (I deleted it and that made the trick), but I know about using this modified script by fjen:

http://neboola.de/fjen/lschlv2/lsmonitor/

Thanks a lot again. The ls-vl runs so much better and much more smooth that with the old 2.6....


Top
   
PostPosted: Mon Apr 01, 2013 12:39 pm 
Offline
Newbie

Joined: Mon May 02, 2011 12:29 am
Posts: 6
VolleMelk wrote:
I can can control the fan using SSH, so it's just a matter of the script.


Oh, I thought it was a deeper issue of the actual fan control/temperature sensor hardware support missing from mainline linux kernels. If it's just a matter of setting up scripts properly that doesn't scare me.
Now that you pointed me to these dev forum threads, there are no issues left in the way - except the fact that doing all this requires a quiet day at home to move my 2TB of data around and follow the steps carefully :)

_________________
LS-WVL fw1.42 opened and ipkg-enabled


Top
   
PostPosted: Mon Apr 15, 2013 10:14 pm 
Offline
Newbie

Joined: Sat Mar 23, 2013 3:31 am
Posts: 10
Hi,

An update on this topic. I did compile 3.8.7 with the same patches and worked well. But I'm suffering xfs corruption in sda6 all the time!

Is it possible/recommended to use ext4 for this partition?

Regards,

Guillermo


Top
   
PostPosted: Wed Apr 17, 2013 12:30 pm 
Offline
Newbie

Joined: Fri Mar 21, 2008 3:04 am
Posts: 61
Don't use xfs with mainline kernel on an arm machine, it will be a disaster. Use anything else that is available and you like.


Top
   
PostPosted: Fri Apr 26, 2013 7:41 am 
Offline
Newbie

Joined: Fri Apr 26, 2013 7:34 am
Posts: 9
Dear Vollemelk,

Your guide seems very good but despite this fact I cannot install debian.
The system enters an infinite loop at reboot, line 19 of step 5.
I reformatted the disk, and reinstalled the stock software.

--edit-- By reformatting both disks I managed to recover the buffalo
now working with stock software and both disks functioning in raid 0.
So now I could retry your procedure. The fact that I got a non bootable
station the first time frightens me. Have you heard of the "infinite boot
loop" problem before? Any explanation/suggestion?
--end edit--

Thanks for help.
mnatiello


Top
   
PostPosted: Sun Apr 28, 2013 3:58 pm 
Offline
Newbie

Joined: Wed Dec 12, 2012 10:25 am
Posts: 72
mnatiello wrote:
Dear Vollemelk,

Your guide seems very good but despite this fact I cannot install debian.
The system enters an infinite loop at reboot, line 19 of step 5.
I reformatted the disk, and reinstalled the stock software.

--edit-- By reformatting both disks I managed to recover the buffalo
now working with stock software and both disks functioning in raid 0.
So now I could retry your procedure. The fact that I got a non bootable
station the first time frightens me. Have you heard of the "infinite boot
loop" problem before? Any explanation/suggestion?
--end edit--

Thanks for help.
mnatiello

Yes, I have heard of the infinite boot loop. In fact, I have experienced it countless times :) Do not worry. You can safely recover the devices if it happens with TFTP (Link provided in my guide). It's all good! ;)

I see you are using RAID0. I used RAID1. I think the problem is that the initrd file tries to boot from the wrong partition.

Here you can see the partitions on my NAS: viewtopic.php?f=50&t=26775&start=15#p161745

Can you post the output of parted, fdisk and /etc/fstab?

* parted
Start parted in ssh (I assume it also works in telnet):

Code:
parted
print

* fdisk
Code:
fdisk -l

* /etc/fstab contents
Code:
cat /etc/fstab


Top
   
PostPosted: Tue Apr 30, 2013 11:33 am 
Offline
Newbie

Joined: Fri Apr 26, 2013 7:34 am
Posts: 9
Thank you for your time.
I've got overconfident and retried the procedure. It failed, but in a different way.
I follow the guide in http://pastebin.com/H6rEZ5ge word by word until completion
of step 4. Two things are different however:
a. The debian that is downloaded is debootstrap_1.0.48_all.deb, not 46 as in your
1-month-old guide. I suppose this difference is not relevant.
b. On lines 178-187 when fstab is constructed, it says that / will be on /dev/md2 with type xfs.
This differs from the NAS default configuration (see below) where / has type ext3. I don't
know if this is relevant.
Then I carried out step 5, all the way to line 19: reboot. The system never recovers from
reboot. The blue light is blinking and there is no network contact with the nas. This time it is
not an infinite boot-loop: The system starts booting, it gets past the moment when the
infinite loop restarted, one hears the disk running for almost one minute, but the light keeps
blinking and nothing else happens.

I reformatted the disks (copying your information from parted), and recovered a newly
unbricked box. I am sending you the ouput of parted, fdisk and fstab on my NAS BEFORE step
2 in the guide: This information is recorded before that, i.e., with the raid0 arrangement that comes
with the box+standard software. At the moment I have a "default" nas with raid0 and root access
via ssh.
Code:
(parted) print 
Number  Start   End     Size    File system  Name     Flags
 1      1049kB  1026MB  1024MB  ext3         primary       
 2      1026MB  6146MB  5120MB  ext3         primary       
 3      6146MB  6147MB  1049kB               primary       
 4      6147MB  6148MB  1049kB               primary       
 5      6148MB  7172MB  1024MB  linux-swap   primary       
 6      7172MB  1992GB  1985GB               primary       

(parted) unit s                                                           
(parted) print                                                           
Model: Seagate ST2000DM001-9YN1 (scsi)
Disk /dev/sda: 3907029168s
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start      End          Size         File system  Name     Flags
 1      2048s      2002943s     2000896s     ext3         primary       
 2      2002944s   12003327s    10000384s    ext3         primary       
 3      12003328s  12005375s    2048s                     primary       
 4      12005376s  12007423s    2048s                     primary       
 5      12007424s  14008319s    2000896s     linux-swap   primary       
 6      14008320s  3890633319s  3876625000s               primary     

root@Nas:~# fdisk -l

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      243202  1953514583+ ee EFI GPT

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1      243202  1953514583+ ee EFI GPT

root@Nas:~# cat /etc/fstab
/dev/root       /               ext3    defaults        1 1
proc            /proc           proc    defaults        0 0
devpts         /dev/pts    devpts     gid=4,mode=620 0    0


In step 2 one creates the raid1 array, then load linux, etc. I don't want to do that again without
some advice, since the procedure already failed once. I should modify something before giving
it a new try, shouldn't I?.

Any suggestions are welcome. Thanks again.

M. Natiello


Top
   
PostPosted: Wed May 01, 2013 7:09 pm 
Offline
Newbie

Joined: Wed Dec 12, 2012 10:25 am
Posts: 72
Can you also give me the output of the mdadm.conf file (with cat)?

It's either located at /etc/mdadm.conf or /etc/mdadm/mdadm.conf

The bootstrap new bootstrap should not be an issue. I read a guide which used 1.0.38, but substituted it with 1.0.46.

On lines 178-187, the fstab file you mentioned, can you remember what the content was you gave in before you rebooted? Can you confirm you actually want your NAS in RAID0? If you want to run it different, it's easiest to change with the buffalo web interface.

What firmware are you running? I am surprised to read that your stock firmware is using ext3 instead of xfs. As far as I know, xfs is default on the LS-WVL.

Also, please cat /etc/mdstat


Top
   
PostPosted: Thu May 02, 2013 7:53 am 
Offline
Newbie

Joined: Fri Apr 26, 2013 7:34 am
Posts: 9
Hallo

Thank you for your answer. I'm glad to have you listening on the other side.

Quote:
On lines 178-187, the fstab file you mentioned, can you remember what the content was you gave in before you rebooted? Can you confirm you actually want your NAS in RAID0? If you want to run it different, it's easiest to change with the buffalo web interface.

No, no. My mistake. I want RAID1. I explain the whole procedure here below.

Quote:
What firmware are you running? I am surprised to read that your stock firmware is using ext3 instead of xfs. As far as I know, xfs is default on the LS-WVL.


OK, here there might be something, hope you discover it for me...
After bricking my NAS I formatted the disks on another computer with gparted as suggested by
kenatonline in post 4 of viewtopic.php?f=77&t=24581
Actually, the partitions I have now are copied from your suggestion at
viewtopic.php?f=50&t=26775&start=15#p161745
I configure both disks exactly the same.
Then I reinstall the firmware 164mod1a downloaded from the site you suggested on disk 1.
I also follow kenatonline here.
Next, reboot the NAS and run LSUpdater.exe under wine on my unix machine.
After that I have a new working NAS with 1.64 firmware, Raid0 and root access.
However, I want to install debian on a RAID1 configuration. Here I start following your guide.
In Step 1 one initiates the RAID1 setup, interupts it to skip the 980 minutes wait, and restarts the
NAS with disk 2 removed. I am in that situation right now: I've done lines 102-104 of your guide
http://pastebin.com/H6rEZ5ge
and I am ready to start step 3.
Now, to the files:

Quote:
Can you also give me the output of the mdadm.conf file (with cat)?

Code:
root@Nas:~# cat /etc/mdadm.conf
ARRAY /dev/md0 UUID=efa653c5:5643d352:b78fdf7e:1eae21f5
ARRAY /dev/md/1 metadata=1.2 UUID=ed9ac047:86b49608:2380fe0b:2169e16a name=LS-WVL-EM44E:1
ARRAY /dev/md/10 metadata=1.2 UUID=4768c187:c02d02c3:77e273b0:5e26b024 name=LS-WVL-EM44E:10
ARRAY /dev/md/2 metadata=1.2 UUID=7d5ccedc:af32d432:27aa3914:17a032ff name=Nas:2

The file /etc/mdadm/mdadm.conf contains just one line:
PROGRAM /usr/local/sbin/handle-mdadm-events.sh

Code:
root@Nas:~# cat /etc/fstab
/dev/root       /               ext3    defaults        1 1
proc            /proc           proc    defaults        0 0
devpts         /dev/pts    devpts     gid=4,mode=620 0    0


Code:
root@Nas:~# ls -l /dev/root /dev/md1
brw-r-----    1 root     disk       9,   1 May  2  2013 /dev/md1
lrwxrwxrwx    1 root     root            3 May  2  2013 /dev/root -> md1


Quote:
Also, please cat /etc/mdstat

My NAS does not have that file:
Code:
cat: can't open '/etc/mdstat': No such file or directory


I do hope you find out what I'm doing wrong.
Thanks again
MNatiello


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 55 posts ]  Go to page 1 2 3 4 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited