bodhi Wrote: ------------------------------------------------------- > mervin, > > > as you. Is your nas running fine with 2 HDDs? > my > > tread with detail of problem is here > > > > > I've looked at the NSA320S DTS. I think I need to > modify it for you (2 HDDs) and Marek (USB) to > try. > > Unfortunately, I'm aboutby mervin - Debian
Hi Marek I would like to ask you for help, I have same NAS as you. Is your nas running fine with 2 HDDs? my tread with detail of problem is here https://forum.doozan.com/read.php?3,51739by mervin - Debian
bodhi, > Remind me again, how many USB ports this NSA320S > box has and are they a mix of USB 2.0 and 3.0? There are 3 USB 2.0, one in front and two at back.by mervin - uBoot
bodhi Wrote: ------------------------------------------------------- > Nice! are they both 3.5" HDD? Yes, both are 3.5" HDD > Somehow I think we are missing something here! my > NSA310S is running with USB rootfs. The USB thumb > drive is Sandisk Ultra Fit 16GB USB 3.0, but it is > attached to USB 2.0 port. I tried couple USB with samo output. I was thinkby mervin - uBoot
Hi I tryed something different. I install debian on HDD and try booted up with both of HDDs inserted. booted up fully without errors, both hdds are fully accesible. the reason for installing debian on USB was to get hdds spindown to save energy U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:50:06 -0700) ZyXEL NSA310S/320S 1/2-Bay Power Media Server SoC: Kirkwood 88F6702_A1 DRAM: 256 MiBby mervin - uBoot
bodhi I mean debian cannot access hdds when 1st SATA is plugged. Any suggestions what can be wrong? root@debian:~# fdisk -l Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 sectors Unitby mervin - uBoot
Bodhi init_sata_power is the smallest issue here, I would say to get 1st sata running without issues its the main thing. Take your time, no hurry Thanks Quote bodhi Wrote: ------------------------------------------------------- > Hi mervin, > > I think I need to modify the DTS to fix this problem once for all. > > However, as I recall the init_sata_power must be uby mervin - uBoot
Hi Bodhi I play around with setup and get couple bootlogs. I upgraded to newest kernel and get debian boot with 2 hdds, but fdisk -l get debian in bits. So far I could say 1st sata slot is giving trouble. 2nd slot no problem but your fix from kernel 5.8.3 in DTS file is not working, I need to use init sata power.by mervin - uBoot
bodhi was a bit different result but debian did not boot fully. so far I can remember on I try to install debian on HDD and then I was booting from usb, thats was only time I got debian running with both HDDs, but was total mess was reading bit from usb and otber bit from hdd. Now I got same feeling as hdd get initialized in debian then linux start looking for rootfs on hdd instead of usb Uby mervin - uBoot
Hi Bodhi I was busy for while and dont have time to play with nas. I did check USB drive and I make fresh install on 2nd USB, I was reading forum and find to set only usb in devices but didnt fix it. with usb only I get working debian. With HDDs I get to initramfs U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:50:06 -0700) ZyXEL NSA310S/320S 1/2-Bay Power Media Server SoC: Kirkwood 88F6702_by mervin - uBoot
Hi Im start thinking this box is good for skip. I got no futher as U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:50:06 -0700) ZyXEL NSA310S/320S 1/2-Bay Power Media Server SoC: Kirkwood 88F6702_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot: 0 NSA3by mervin - uBoot
Hi I'll tried all 3 usb ports but I got same error no rootfs. In case it need to be inserted into first usb port. NSA3x0S> usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... Use USB retry period from the environment: 15 second(s) 1 Storage Device(s) found NSA3x0S> usb tree USB deviby mervin - uBoot
Hi I get error in step 1. here is full bootlog U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:50:06 -0700) ZyXEL NSA310S/320S 1/2-Bay Power Media Server SoC: Kirkwood 88F6702_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot: 0 NSA3x0S> printenvby mervin - uBoot
bodhi Wrote: ------------------------------------------------------- > mervin, > > I am a little bit busy, but your issue is on my > browser tabs! will take a look when I have some > time. Yes sure, take your time. You going great job. Thanksby mervin - uBoot
Hi I was trying my best do get NAS up and running, but no luck. I made fresh usb with ext3 partition. instaled 5.2.9 then upgraded to 5.8.3 here are bootlog in different situations. I will say best run what i get was with USB + HDD in 2nd slot + init sata power, the rest of runs was without init sata power. what I think I must reset enviroment to default with your script from 2016, Im lost dby mervin - uBoot
Hi. I managed to solve the problem with netconsole, was bit tuff because I was not geting output, but input was working, I was typing on blind but I get it running. but I came across another problem, secon HDD making a clicking noise(initialising or something similar) every minute or so, when i dissable this then debian dont see it init_sata_power 'mw.l f1010104 c70e0ffd' its noby mervin - uBoot
serial console with disconnected nc U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:50:06 -0700) ZyXEL NSA310S/320S 1/2-Bay Power Media Server SoC: Kirkwood 88F6702_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 Using egiga0 device ARP Retry count exceeded; starting again ping faby mervin - uBoot
I was changing values in envs an I got to this asus@asus-X51L:~/Plocha/nsa32s$ sudo kwboot -t -B 115200 /dev/ttyUSB0 heslo pre používateľa asus: � U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:50:06 -0700) ZyXEL NSA310S/320S 1/2-Bay Power Media Server SoC: Kirkwood 88F6702_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serby mervin - uBoot
When I put in Hdds in debian didn't boot up. But when I deleted apparitions of Hdds I got debian running. I'm starting thinking if its not easier to get debian running from hdd as from USB stick.by mervin - uBoot
mervin Wrote: ------------------------------------------------------- > hi > when I plug usb with EXT3 I got same results. but > when I pulled out both HDDs, than debian booted > without errors. today I will try to plug in EXT4 > usb and see what it will hapen. > should I now upgrade debian to newest or just > leave? > What is best app to get it running as NAS agby mervin - uBoot
hi when I plug usb with EXT3 I got same results. but when I pulled out both HDDs, than debian booted without errors. today I will try to plug in EXT4 usb and see what it will hapen. should I now upgrade debian to newest or just leave? What is best app to get it running as NAS again? omv?by mervin - uBoot
Tomorrow I will create new debian usb and make it to ext3. Anyway what I have spotted that the network and front leds are not working and HDD is making clicking sound repeatedly Thanksby mervin - uBoot
USB drive is Kingston DataTraveler 2.0 (PMAP) with MBR boot with uImage worked well, I got another error [ 14.270690][ T1] Run /init as init process Loading, please wait... Starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Runningby mervin - uBoot
I have make a changes to load both HDDs SA3x0S> setenv init_sata_power 'mw.l f1010104 c70e0ffd' NSA3x0S> setenv bootcmd 'run init_sata_power; run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset' NSA3x0S> setenv devices usb NSA3x0S> boot I have attached terminal with debian boot, im getting error [ 13.798119][ T1] Kernel panicby mervin - uBoot
here are envs before save NSA3x0S> printenv arcNumber=4931 baudrate=115200 bootcmd=run init_sata_power; run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb;by mervin - uBoot
enki Hi can you send me your env and uEnvs Thanksby mervin - uBoot
Thats worked well. its booting now. I flashed uboot.2017.07-tld-1.nsa310s.mtd0.kwb now I will need to flash uboot.2016.05-tld-1.environment.img the right way it will be this ext2load usb 0:1 0x800000 uboot.img nand erase 0x00000 0x1000000 nand write 0x800000 0xc00000x100000 or this ext2load usb 0:1 0x800000 uboot.img nand erase 0x0 0x1000000 nand write 0x800000 0xc0000 0x20000by mervin - uBoot
bodhi Wrote: ------------------------------------------------------- > mervin, > > So you want to flash u-boot in serial console? is > that correct? if it is, use an Ext3 USB. > > Remove all USB drives except one with u-boot.kwb > on it > > > usb start > ext2load usb 0:1 0x800000 uboot.kwb > Yes, I need to flash uboot and flash new enviromentsby mervin - uBoot