Bodhi Quote That's abnormal. I don't recall anybody has reported this. How old is the 2.5" HDD in the 2nd slot? have you tried swaping these two 1<-->2? I have swapped in between 2.5inch disks as first happened. I completly agree there should be no clicks... It may be something particular with this NAS and more looking into this I start to believe this. I may restore stby enki - uBoot
Bodhi, It happened before all of latest DTS/init_sata also with the 2.5'' disk on slot 2 indeed. It clicks when BUS1 activates and then after whenever it writes on the disk. Would it may be a diffrent bit from “Functional Specifications for Kirkwood's GPIO Data Out Register” to activate BUS1 in a mode which is appropiate and silent? I know it is not quite good to hearby enki - uBoot
Bodhi, QuoteTest 2. Insert the 2x 2.5" HDD in the both slots. Boot and see if both SATA are spun up during kernel booting. result Test 2: Both 2.5'' HDDs spin after kernel boots; all OK. same 'click sounds' when you write on disk on slot no.2 Please note: with 3.5'' disk on slot 2 wihtout init_sata at u-boot to innitialize Bus 1... disk slot 2 doesnby enki - uBoot
Bodhi, QuoteTest 1. Insert the 3.5" HDD in the 1st slot, 2.5" HDD in the second slot. Boot and see if both SATA are spun up during kernel booting. result Test 1: Both 3.5'' (1st) and 2.5'' (2nd) HDDs spin after kernel boots; all OK. There is another small things I've noticed: regardless is 2.5'' or 3.5'' the disk on slot 2 when you wby enki - uBoot
Hi Bodhi, Yes please. There is a small thing, on how we include these instructions onto u-boot env. Let me explain and ask for a robust solution. The instructions to include init_sata into u-boot envs must be constructed in the way users don't need to stop uboot and execute them manually. I am not expert in u-boot instructions so asking the community to construct the u-boot env commanby enki - uBoot
Bodhi, Almost gave up on this one, however we have good news as below! The second SATA is UP and SPINNING. [ 8.841425] libata version 3.00 loaded. [ 12.078680] sata_mv f1080000.sata: version 1.28 [ 12.078963] sata_mv f1080000.sata: slots 32 ports 2 [ 12.087715] scsi host0: sata_mv [ 12.092177] scsi host1: sata_mv [ 12.096388] ata1: SATA max UDMA/133 irq 32 [ 12.10by enki - uBoot
Hi Bodhi, Ofcourse please take your time as it needs a bit of attention. I wonder if we can have a look at how was original uboot/kernel from Zyxel to recognize two 3.5 disks. Any ideas please give a shout and I shall try (as much as I can) to look into it as well. This guy on madadmin.com initiates sata disks with ' setenv init_sata 'mw.l f1010104 c70e0ffd;ide reset' which Iby enki - uBoot
Bodhi In previous log attached there is 'ata2: SATA link down (SStatus 0 SControl F300)' ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 12.353512][ T134] ata1.00: ATA-9: WDC WD20EFRX-68AX9N0, 80.00A80, max UDMA/133 [ 12.361003][ T134] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 12.386790][ T134] ata1.00: configured for UDMA/133 [ 12by enki - uBoot
Hi Bodhi Here they are fw_printenv variables and the serial console of u-boot (screen.log) snapshots into files attached. Enkiby enki - uBoot
Bodhi, It does load the new DTB as prints when booting from usb Found bootable drive on usb 0 loading uImage ... 5409256 bytes read in 763 ms (6.8 MiB/s) loading uInitrd ... 9963913 bytes read in 1137 ms (8.4 MiB/s) loading DTB /boot/dts/kirkwood-nsa320s.dtb ... 13021 bytes read in 1646 ms (6.8 KiB/s) ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-5.6.by enki - uBoot
Bodhi If I leave the boot sequence unintrerupted I have errors and it breaks... EHCI timed out on TD - token=0x80008d80 now I need to break the autoboot sequence and do setenv devices usb boot to skip check on sata disks and boot using the rootfs usb in debian. Question: how I make sure the DTB I've just update its loading because I am not sure the boot is taking the new DTBby enki - uBoot
Bodhi, I have tried the updated dtb on the nas with both sata disks in and it is the same behaviour as in only the first sata disk is recognized. Maybe I am missing something ...by enki - uBoot
Bodhi Thank you. I shall try it in couple of hiurs and shall get back to you... Eby enki - uBoot
Bodhi, Each of the boxes they have their own quirks. A solution for this NSA320s 3.5inch two disks would be great. Looking forward.by enki - uBoot
Hi Bodhi, This is what you have noted in here (https://forum.doozan.com/read.php?3,12381) ----------------------------------- Updated 30 Aug 2015 I've uploaded the Zyxel NSA310S/320S u-boot-2014.07-tld-4 image. The installation instruction is the same for the NSA310S/320S as for other boxes that have a different stock env location: iConnect, Pogo V4/Mobile, and Netgear Stora.by enki - uBoot
Hi Bodhi, I have already did that and both WD reds are technically ok. Booted exactly what you have suggested and it seems that it always recognize the disk placed on '1st hdd' slot on the nas but not both. When I had 2x 2.5inch wd reds they were both recognized but they were only 1TB. I cannot imagine is a power problem as 5A is the standard psu for this NSA320s. I have fby enki - uBoot
Hi I have sourced another 2x 3.5inch wd reds and I am trying to get them working with this NSA320s and something interesting happens: u-boot sees 3 USB devices (1x USB disk with rootfs + 2xWD reds) arting 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)by enki - uBoot
Bodhi, It works indeed to skip sata disks verification. Steam ahead to upgrade and get raid running. Many Thanks.by enki - uBoot
Bodhi, Yes, I have Debian and flashed mtd0 and envs. Now when I want to bring two sata hdds in and plug them into nas and boot the nas with them in I get the same error message 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 Reset Iby enki - uBoot
Hi Bodhi Now all sorted as I managed to boot the kernel. The problem was that the two sata disks were on and when I took them out usb disk has been recognized and was used to boot ... no need to make new uImage and uInitrd as the kwb contains everything to boot from the kernel as it is. BR. Eby enki - uBoot
After I stop autoboot and do boot .... got this Partition Map for USB device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80a88 ... EHCI timed out on TD - token=0x80a88 EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80a88 ** Can't read partitionby enki - uBoot
Bodhi, printenv results 99 % [....................................] 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 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHby enki - uBoot
Bodhi, When I do rootfs disk do I need to do this step? 4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Do not do this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time). Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for tby enki - uBoot
Bodhi, I sent kwb again. boot but I realised the envs are the ones which are looking for rootfs usb disk ...by enki - uBoot
bodhi Wrote: ------------------------------------------------------- > enki, > > Congrats! > > Now you can boot with the internal envs. Check > they are OK, > > > printenv > Oooops I haven't realised that I need to continue with booting and reset it again. I am trying again to send kwb to mtd0 ...by enki - uBoot
It works. tried again with full root rather sudo ... got 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 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egigby enki - uBoot
I followed: 1. run 'kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa310s.mtd0.kwb -p' command from a Linux laptop. and then 2. turned on NSA320s by pressing button; still the same behaviour rolling nothing '/\' like I have seen from others with % sending the kwb ... I shall try again.by enki - uBoot
bodhi Wrote: ------------------------------------------------------- > enki, > > Quote0. connect usb cable to serial console of > the NSA320s; lsusb shows: > Bus 003 Device 010: ID 067b:2303 Prolific > Technology, Inc. PL2303 Serial Port > > Did you try running serial console before the mtd0 > was bricked? Yes, it was working (saw uboot messages and I couby enki - uBoot
Hi Bodhi, I shall post in this topic. First thank you for prompt reply. I have tried the followings: 0. connect usb cable to serial console of the NSA320s; lsusb shows: Bus 003 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port 1. turned on NSA320s by pressing button; 2. run 'kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa310s.mtd0.kwb -p'by enki - uBoot
Hi Bodhi, First thank you for prompt reply. I have tried the followings: 0. connect usb cable to serial console of the NSA320s; lsusb shows: Bus 003 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port 1. turned on NSA320s by pressing button; 2. run 'kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa310s.mtd0.kwb -p' command from a Linux laptop.by enki - uBoot