Have fun explaining how to support DebiaN armv5 on your LinkStation RaiD NaS !

2 way to install it

1/ on new hardisk (one is enough)

2/ on exiting one to be discard (could brick device)

UPDATE : DEBIAN-8 (JESSIE)

I am Looking for testers

I will share you file

07e96fcedd45c7713eca6ec1ac0085e6  /root/debian-8-armel-lsproduo2-20151124rzr.qcow2

1st please register new email to :

2d open this link :

INSTALL by DUMPING

Dump disk image to new disk (40GB+) on host or target device :

 file=/root/debian-8-armel-lsproduo2-20151124rzr.qcow2
 disk=/dev/disk/by-id/ata-SAMSUNG_SP0411C_00000000000000 # TODO: adapt with your disk
 sudo apt-get install qemu-image-tools time
 ls $disk && time sudo qemu-img convert -p -f qcow2 -O raw $file $disk && sync && sync && sync 

INSTALL by COPING : USAGE / SETUP RAID

Converting single disk setup to raid.

  • 1. Boot up from old image (single).
  • 2. Connect empty or/and wipe other disk data
  • 3. Create new partitions, partitions size doesn't matter as far all files fit:
  • 3.1 Build raid1 with one disk missing: You must use metadata 0.9
  • 4. Format raid partitions:
Partitions:
Device     Boot    Start        End    Sectors  Size Id Type
/dev/sda1           2048    1050623    1048576  512M fd Linux raid autodetect
/dev/sda2        1050624    2099199    1048576  512M fd Linux raid autodetect
/dev/sda3        2099200   44042239   41943040   20G fd Linux raid autodetect
# mdadm.conf
# This configuration was auto-generated on Sun, 01 Nov 2015 08:13:39 +0000 by mkconf
ARRAY /dev/md0 UUID=9c7f9c79:df701019:9d4deba6:47ca997f
ARRAY /dev/md1 UUID=44b75634:c4c5a5bb:9d4deba6:47ca997f
ARRAY /dev/md2 UUID=ec0c7687:3d1e0904:9d4deba6:47ca997f
  • 5. Mount these partitions somewhere in order first root and then boot.
  • 6. then I copied all files from your image to this mount point
  • 7. Chroot into it
  • 7. Edit fstab
# /etc/fstab: static file system information.
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/md2                /               ext4    errors=remount-ro       0 1
/dev/md0                /boot           ext2    defaults                0 2
/dev/md1                none            swap    sw                      0 0
  • 8. Change bootargs:
  • 8.1 First backup old info: fw_printenv
  • 8.2. Set new info: fw_setenv bootargs_root=root /dev/md2 rw initrd=0x00800040,15M panic=5

!! If fw_printenv is not working copy: cp /usr/share/doc/u-boot-tools/examples/linkstation_pro_live.conf ig /etc/fw_env.config

 !! If you change it then you can't boot from single disk setup. For fixit you must change fw env back, use the value from backup.
  • 9. Update-initramfs: update-initramfs -u
  • 10. If not booting debug via netconsole

!! You cannot connect this raid into other computer! If raid name change in other compter then buffalo can't boot from this disk. You names must stay md0, md1, md2

And if everything good be a happy raid buffalo nas user !

By Lugupidamisega thx

(OBSOLETE) DEBIAN-7 (Wheezy)

Can be adapted to use OpenMediaVault

(OBSOLETE) GET IMAGE

checking md5sum: from ”PuB” files

md5sum -c README.txt

Getting the image to an usbstick:

7z x rzr-hardisk-debian-wheezy-armel-lsproduo-2012.img.7z.part.001
mv rzr-hardisk-debian-wheezy-armel-lsproduo-2012.img.7z /media/usb/

(OBSOLETE) From LinuX Host :

cd rzr-hardisk-debian-wheezy-armel-lsproduo-2012.img # 253MB
md5sum -c README.txt 
disk=/dev/sdZ
archive=rzr-hardisk-debian-wheezy-armel-lsproduo-2012.img.7z.part.001
file=rzr-hardisk-debian-wheezy-armel-lsproduo-2012.img.7z

7z l $archive ; 7z t $archive
time 7z e -so $archive $file | sudo dd of=$disk bs=8MB oflag=dsync conv=sparse
# 2091909120 bytes (2,1 GB) copied, 69,5928 s, 30,1 MB/s # real    1m10.078s

Or From LinkStation :

GET ROOT

The information that I needed was: Getting telnet root acces with acp commander, listed here:

(OBSOLETE) DUMP TO USB

USB-Sticks gets auto-mounted on the lsproduo, then executing

dd if=/mnt/usbdisk1/rzr-hardisk-debian-wheezy-armel-lsproduo-2012.img.7z of=/dev/sda
reboot

(Note this can be done also using SsH and pipes)

BooT SysteM

BooT SysteM :

sudo tcpdump "ether[6:2] == 0x001d"   # TODO CHECK 
ssh root@$host # passwd=root

passwd

cat /proc/version 
Linux version 3.1.1lsproduo-00009-g4d27e1c (rzr@lap) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 PREEMPT Sat Dec 3 23:43:17 CET 2011

cat /README.txt
Package: rzr-host-lsproduo-debian-wheezy
URL: http://rzr.online.fr/q/armv5
Description: rootfs for nas linkstation ls pro duo v2
Version: 0.0.20111204
(...)


df 
/dev/sda2       1.2G 1008M  102M  91% /
/dev/sda1       236M   34M  190M  16% /boot

md5sum /boot/*.buffalo
470d97a2a4c1df2ba25b3487b1faefaf  /boot/initrd.buffalo
470d97a2a4c1df2ba25b3487b1faefaf  /boot/initrd.img-3.1.1lsproduo-00009-g4d27e1c.initrd.buffalo
9ea540514afd4a74560a18e003341bca  /boot/uImage.buffalo
9ea540514afd4a74560a18e003341bca  /boot/vmlinuz-3.1.1lsproduo-00009-g4d27e1c.uImage.buffalo

cat /etc/debian_version 
wheezy/sid

RESIZE DISK ?

When doing aptitude update & upgrade, I had the problem that with the default partition layout there wasn't enough space on the root partition for the update.

So next step for me was to remove the disk, put it in my desktop computer and change the partition tables around.

ie: Use gparted

Could have done everything like this from the beginning without fiddling with the usbstick…

HARDWARE SUPPORT

After that, upgrading worked fine except aptitude had problems with something called micro-evtd. I get:

Setting up micro-evtd (3.4-2) ...        
[FAIL] micro-evtd error: device is not supported ... failed!
invoke-rc.d: initscript micro-evtd, action "start" failed.
dpkg: error processing micro-evtd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 micro-evtd

That one can be safely removed for now … and use custom Script :

https://gist.github.com/3230293

Execute the script every 5 minutes to automatically adjust the fan speed: Enter in /etc/crontab

# start fanctrl every 5 minutes to regulate the fan
*/5 *   * * *   root    /root/local/bin/fanctrl.sh auto

SOFTWARE SUPPORT

then :

sudo apt-get install owncloud-sqlite  owncloud # nxing? lighthttpd ?

ToDo: explain how to optimize this bloatware :-)

TODO

Then you can upgrade kernel

http://rzr.online.fr/q/orion5x# Published #LinuxKerneL 3.2.41lsproduo-00019-g6e228b for #ArmV5 #LsProDuo #RaiD# #NaS match #DebiaN #Wheezy

And why not rebuild it orion5x Kernel on Target ?

GET HARDDISKS

May not needed if you have some already

HARDWARE / IO / SATA : (REPLACE DISKS)

About Disk size larger than 2TB : the kernel does not manage 4096 bytes per sector drives.

Do not use disks with 4096 as hardware sector size. Use 512 disks instead.

Supported and tested

Untested

MISC

/dev/disk/by-id/ata-WDC_WD1003FZEX-00MK2A0_WD-WCC3F131....

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048      499711      248832   83  Linux
/dev/sda2          499712     2930687     1215488   83  Linux
/dev/sda3         2930688     4085759      577536    f  W95 Ext'd (LBA)
/dev/sda5         2932736     4085759      576512   82  Linux swap / Solaris


cat /sys/block/sda/queue/physical_block_size
4096

http://johannes-bauer.com/linux/wdc/?menuid=3

http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/2926

if you use a kernel linux-kernel >= 2.6.31 and util-linux >= 2.17,

LinkS :

@TaG: Samsung sata SeaGate WesternDigital HardDisk WD

MISC

MORE

lsproduo.txt · Last modified: 2015/12/14 00:18 by rzr
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki