Author Topic: LS441D: Definitive YES/NO answer for possible Linux Debian instead of stock FW?  (Read 5843 times)

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 725
  • There's no problem so bad you cannot make it worse
ah, ok. I've heard of mixed results running the latest installer with devices running 64mb ram.

I've been working on customizing my installer to deal with this as part of adding support for ls-xl. This has been slow work since I keep running into roadblocks but I should get it working eventually.

In the meantime you may have better luck if you start with Stretch and then upgrade to Buster (I think that installer will require less memory)

laksjan

  • Calf
  • *
  • Posts: 19
Hello,
I tried from another machine with more memory and it went past the "scanning the disks" part. But, now after scanning, it listed out the drives available to search for the installation ISO and I picked /dev/sda1 (guessing it would be the /boot partition of my first disk). It came back with the screen asking me to locate the installer ISO Image.
I thought we uploaded the image files. Do i need to download an iso from the debian site?


┤ [!!] Scan hard drives for an installer ISO image ├────────────────────────┐
   │                                                                                                   │
   │                                     Installation step failed                                      │
   │ An installation step failed. You can try to run the failing item again from the menu, or skip it  │
   │ and choose something else. The failing step is: Scan hard drives for an installer ISO image       │
   │                                                                                                   │
   │                                            <Continue>                                             │
   │                                                           

laksjan

  • Calf
  • *
  • Posts: 19
Hello,

Is there a way to update samba alone on the LS-WTGL stock firmware. Currently trying to get this working on SMB2 as a 1st step on another Linkstation Pro Duo, while I try building this on this LS-WTGL.
Thank you for all your help...
laksjan

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 725
  • There's no problem so bad you cannot make it worse
Quote
Hello,
I tried from another machine with more memory and it went past the "scanning the disks" part. But, now after scanning, it listed out the drives available to search for the installation ISO and I picked /dev/sda1 (guessing it would be the /boot partition of my first disk). It came back with the screen asking me to locate the installer ISO Image.
I thought we uploaded the image files. Do i need to download an iso from the debian site?
What are you trying to accomplish by doing this?

Quote
s there a way to update samba alone on the LS-WTGL stock firmware. Currently trying to get this working on SMB2 as a 1st step on another Linkstation Pro Duo, while I try building this on this LS-WTGL.
Thank you for all your help...

Other folks on this forum have modified devices newer than this to enable SMB2, I do not know if that would work with this model or not.

laksjan

  • Calf
  • *
  • Posts: 19
Hi,

Yes, I have made changes to smb.sh to make it work with both SMB2 & SMB3 on my another Ls-WVL NAS. It works fine, no issues. Whereas, this LS-WTGL is not reading the smb.conf file and they say that this could be because of the Samba version (3.x). I am sure it works with Samba (v4.x or above) like a charm.

Going to this thread, I will start with Stretch and see it helps.. Will keep you posted.

Thank you,
laksjan

laksjan

  • Calf
  • *
  • Posts: 19
Hello,
I again had the same error OoM while partitioning the disks... Please let me know if I am making any mistake.. would love to get this working. Appreciate your help...

May 15 18:32:42 kernel: [ 1004.727647] active_anon:6691 inactive_anon:14 isolated_anon:0
May 15 18:32:42 kernel: [ 1004.727647]  active_file:0 inactive_file:0 isolated_file:0
May 15 18:32:42 kernel: [ 1004.727647]  unevictable:20214 dirty:0 writeback:0 unstable:0
May 15 18:32:42 kernel: [ 1004.727647]  slab_reclaimable:799 slab_unreclaimable:708
May 15 18:32:42 kernel: [ 1004.727647]  mapped:2099 shmem:16 pagetables:167 bounce:0
May 15 18:32:42 kernel: [ 1004.727647]  free:1269 free_pcp:36 free_cma:0
May 15 18:32:42 kernel: [ 1004.727693] Node 0 active_anon:26764kB inactive_anon:56kB active_file:0kB inactive_file:0kB unevictable:80856kB isolated(anon):0kB isolated(file):0kB mapped:8396kB dirty:0kB writeback:0kB shmem:64kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 15 18:32:42 kernel: [ 1004.727758] Normal free:5076kB min:5408kB low:5736kB high:6064kB reserved_highatomic:0KB active_anon:26764kB inactive_anon:56kB active_file:0kB inactive_file:0kB unevictable:80856kB writepending:0kB present:131072kB managed:123604kB mlocked:0kB kernel_stack:488kB pagetables:668kB bounce:0kB free_pcp:144kB local_pcp:144kB free_cma:0kB
May 15 18:32:42 kernel: [ 1004.727764] lowmem_reserve[]: 0 0 0
May 15 18:32:42 kernel: [ 1004.727789] Normal: 1*4kB (M) 0*8kB 1*16kB (E) 0*32kB 11*64kB (M) 10*128kB (M) 4*256kB (ME) 0*512kB 2*1024kB (ME) 0*2048kB 0*4096kB = 5076kB
May 15 18:32:42 kernel: [ 1004.727897] 20241 total pagecache pages
May 15 18:32:42 kernel: [ 1004.727911] 0 pages in swap cache
May 15 18:32:42 kernel: [ 1004.727926] Swap cache stats: add 0, delete 0, find 0/0
May 15 18:32:42 kernel: [ 1004.727936] Free swap  = 0kB
May 15 18:32:42 kernel: [ 1004.727946] Total swap = 0kB
May 15 18:32:42 kernel: [ 1004.727956] 32768 pages RAM
May 15 18:32:42 kernel: [ 1004.727965] 0 pages HighMem/MovableOnly
May 15 18:32:42 kernel: [ 1004.727974] 1867 pages reserved
May 15 18:32:42 kernel: [ 1004.727984] Tasks state (memory values in pages):
May 15 18:32:42 kernel: [ 1004.727995] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
May 15 18:32:42 kernel: [ 1004.728035] [     60]     0    60      855      583    10240        0         -1000 systemd-udevd
May 15 18:32:42 kernel: [ 1004.728065] [    120]     0   120      537      351    10240        0             0 syslogd
May 15 18:32:42 kernel: [ 1004.728094] [    122]     0   122      537      341    10240        0             0 klogd
May 15 18:32:42 kernel: [ 1004.728122] [    820]     0   820     1918     1010    14336        0             0 haveged
May 15 18:32:42 kernel: [ 1004.728151] [    833]     0   833      537      350    10240        0             0 debian-installe
May 15 18:32:42 kernel: [ 1004.728179] [    840]     0   840      720      474    10240        0             0 screen
May 15 18:32:42 kernel: [ 1004.728207] [    841]     0   841      892      680    12288        0             0 screen
May 15 18:32:42 kernel: [ 1004.728234] [    843]     0   843      537      344    10240        0             0 sh
May 15 18:32:42 kernel: [ 1004.728262] [    844]     0   844      537      365     8192        0             0 sh
May 15 18:32:42 kernel: [ 1004.728290] [    845]     0   845      537      268    10240        0             0 tail
May 15 18:32:42 kernel: [ 1004.728318] [    846]     0   846     2098     1372    18432        0             0 debconf
May 15 18:32:42 kernel: [ 1004.728347] [    847]     0   847      495      353    10240        0             0 main-menu
May 15 18:32:42 kernel: [ 1004.728374] [   1165]     0  1165      478      333     8192        0             0 udpkg
May 15 18:32:42 kernel: [ 1004.728402] [   1166]     0  1166      537      396     8192        0             0 network-console
May 15 18:32:42 kernel: [ 1004.728431] [   1179]     0  1179     1383      774    14336        0         -1000 sshd
May 15 18:32:42 kernel: [ 1004.728459] [   1195]     0  1195     1383     1095    12288        0             0 sshd
May 15 18:32:42 kernel: [ 1004.728487] [   1198]     0  1198      537      363    10240        0             0 debian-installe
May 15 18:32:42 kernel: [ 1004.728515] [   1204]     0  1204      759      508    10240        0             0 screen
May 15 18:32:42 kernel: [ 1004.728543] [   1205]     0  1205     1192      948    12288        0             0 screen
May 15 18:32:42 kernel: [ 1004.728571] [   1207]     0  1207      537      363     8192        0             0 sh
May 15 18:32:42 kernel: [ 1004.728599] [   1208]     0  1208      537      371     8192        0             0 sh
May 15 18:32:42 kernel: [ 1004.728626] [   1209]     0  1209      537      306     8192        0             0 tail
May 15 18:32:42 kernel: [ 1004.728654] [   1210]     0  1210     4802     4091    26624        0             0 debconf
May 15 18:32:42 kernel: [ 1004.728682] [   1211]     0  1211      495      368    10240        0             0 main-menu
May 15 18:32:42 kernel: [ 1004.728711] [   4917]     0  4917      478      332    10240        0             0 udpkg
May 15 18:32:42 kernel: [ 1004.728739] [   4918]     0  4918      537      343    10240        0             0 partman-base.po
May 15 18:32:42 kernel: [ 1004.728767] [   4919]     0  4919      549      407    10240        0             0 partman
May 15 18:32:42 kernel: [ 1004.728795] [   4931]     0  4931      562      410    10240        0             0 anna
May 15 18:32:42 kernel: [ 1004.728824] [   5054]     0  5054      478      351     8192        0             0 udpkg
May 15 18:32:42 kernel: [ 1004.728853] [   5067]     0  5067      586      343    10240        0             0 debconf-loadtem
May 15 18:32:42 kernel: [ 1004.728867] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),task=debconf,pid=1210,uid=0
May 15 18:32:42 kernel: [ 1004.728927] Out of memory: Killed process 1210 (debconf) total-vm:19208kB, anon-rss:13844kB, file-rss:2520kB, shmem-rss:0kB, UID:0 pgtables:26kB oom_score_adj:0
May 15 18:32:42 kernel: [ 1004.772801] oom_reaper: reaped process 1210 (debconf), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 725
  • There's no problem so bad you cannot make it worse
I understand your issue now, I keep seeing LS441D in the thread title and get confused how you could be out of memory.

the LS-XL, LS-CHLv2 and LS-WTGL all have only 64MB where all the other devices have 128M+. I have just finished creating a "low memory" version of the installer which side steps the issue you're running into by detecting and activating swap earlier in the install process. I'm going to test it on the LS-CHLv2 shortly, assuming it works I publish it and post a link so you can test it on the LS-WTGL.

laksjan

  • Calf
  • *
  • Posts: 19
Great and thank you for your time on this... Can't wait to try it out...

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 725
  • There's no problem so bad you cannot make it worse
I'm still waiting for a Stretch test to finish before trying a Buster build but am hoping you can give it a try on your device as a test.

The files are posted here.
https://github.com/1000001101000/Debian_on_Buffalo/tree/master/Stretch/installer_images/armel_devices/lowmem

There has to be an existing swap device before starting the installer for it to work (it needs swap to even get to the partitioner as you've noticed). Starting with the stock firmware partitions is one way to accomplish this.

This takes longer than a typical install because of the heavy swap usage the whole time.

laksjan

  • Calf
  • *
  • Posts: 19
Hello,
Copied the images to the LS. But unable to ssh into the device as installer/install
The authenticity of host '192.168.1.32 (192.168.1.32)' can't be established.
RSA key fingerprint is SHA256:UKl4ykH/waQtt9/5hQXC+spoKn7mu7G2KdxTDs+XPBE.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added '192.168.1.32' (RSA) to the list of known hosts.
installer@192.168.1.32's password:
Permission denied, please try again.
installer@192.168.1.32's password:

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 725
  • There's no problem so bad you cannot make it worse
That usually means itís still in the stock firmware. Does it show up in nasnavigator/etc?

laksjan

  • Calf
  • *
  • Posts: 19
Yes, It does show up in the NAS Navigator... Let me try another reboot..

laksjan

  • Calf
  • *
  • Posts: 19
Hello,
I rebooted the NAS again and it failed to load (6 RED blinks). Need to revert back to the stock firmware. Any ideas?
FYI, I just copied only the following files to the NAS:
  • initrd.buffalo.armel-lowmem
  • uImage.buffalo.lswtgl
  • vmlinuz-armel

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 725
  • There's no problem so bad you cannot make it worse
vmlinuz-armel is not needed

initrd.buffalo.armel-lowmem should be renamed initrd.buffalo
uImage.buffalo.lswtgl should be renamed uImage.buffalo

laksjan

  • Calf
  • *
  • Posts: 19
Yes, did the same and got the 6 "RED" blinks at start-up... Restored the stock firmware back and now back online. Please let me know the next steps we can try... Also, just a note, these 2 custom files are only 88kb in size as opposed to the other images being 6MB & 2MB.
Is that wierd?