4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310 NAS

[arti74]

The simple solution is always the best. Good Idea - and if something - I can turn it on by this command I think.
$this->bbcode_second_pass_code('', 'fw_setenv netconsole on')

[arti74]

Something's wrong with my kernel update - should be a newer version than the uname shows:
$this->bbcode_second_pass_code('', 'yaourt -S linux-kirkwood-dt
warning: linux-kirkwood-dt-4.16.8-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-kirkwood-dt-4.16.8-1

Total Installed Size: 25.30 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) reinstalling linux-kirkwood-dt [######################] 100%
>>> Updating module dependencies. Please wait ...
:: Running post-transaction hooks...
(1/2) Updating linux-kirkwood-dt initcpios
==> Building image from preset: /etc/mkinitcpio.d/linux-kirkwood-dt.preset: 'default'
-> -k 4.16.8-1-ARCH -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.16.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
(2/2) Arming ConditionNeedsUpdate...
[rtorrent@alarm ~]$ uname -r
4.16.7-1-ARCH')

[summers]

Think the problem is with not being able to boot from ext4 you have been using my uImage, and hence the number.

Reinstalling should create /boot/zImage which you need. so check.

So I think you don't need to be worried, you'll move to the new kernel when uboot can access the ext4 partition ...

[arti74]

Ok then, I will try to make the copy to the big drive, then I report back with everything.
Thanks

EDIT. It takes a lot longer as I thought (it's 47,3GB), I couldn't somehow copy it "on fly" - instead I tar it to my computer and now I'm extracting it to the big drive.

I have yet a question regarding the new fan that you bought - how did you connected it to your device since the standard fan connector is much bigger than the original one? (at least on the NSA310)
I don't see anywhere any adapter which would suit.
Actually I found one.. https://www.moddiy.com/products/Standar ... apter.html

EDIT... I made a huge mistake - forgot to take off the 'features' from the smaller disk before copy, now its the same problem which was before:
$this->bbcode_second_pass_code('', 'Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: WDC WD40PURX-64GVNY0 Firm: 80.00A80 Ser#: WD-WCC4E0SERLJD
Type: Hard Disk
Supports 48-bit addressing
Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)

USB device 0: unknown device

Device 0: Model: WDC WD40PURX-64GVNY0 Firm: 80.00A80 Ser#: WD-WCC4E0SERLJD
Type: Hard Disk
Supports 48-bit addressing
Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
... is now current device
ide found on device 0
Checking for: /uEnv.txt ...
** File not found /zImage **
** File not found /uImage **
No kernel found

Device 1: not available
Trying to boot from NAND ...
ubi0: attaching mtd1
ubi0: scanning is finished
UBI init error 22
Error reading superblock on volume 'ubi0:rootfs' errno=-19!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume')
I guess I repeat the same process one more time

Ummm not so fast maybe - I still cant update this linux kernel. I put the old disk after those modifications again to the device, yaourt -Sy linux-kirkwood-dt, but still the older 4.16.7-1-ARCH kernel...

[arti74]

So I'm stuck again...
$this->bbcode_second_pass_code('', 'NSA310> printenv
bootcmd=run startboot;run bootubi
bootfilem=uImage
bootfilez=zImage
bootpart=0:1
bootubi=echo Trying to boot from NAND ...;if run mountubi; then ubifsload ${loadaddr} /boot/zImage;ubifsload ${fdtaddr} /boot/dtbs/${fdtfile};ubifsumount; setenv bootargs console=${console} ubi.mtd=1 root=ubi0:rootfs ro rootfstype=ubifs rootwait ${mtdparts};bootz ${loadaddr} - ${fdtaddr};fi
console=ttyS0,115200
devnum=1
ethact=egiga0
ethaddr=CC:5D:4E:C9:F5:4A
fdtaddr=0x800000
fdtdir=/boot/dtbs
fdtfile=kirkwood-nsa310.dtb
if_netconsole=ping $serverip
ipaddr=192.168.1.5
loadaddr=0x810000
loadfdt=echo loading ${fdtdir}/${fdtfile} ...; load ${devtype} ${bootpart} ${fdtaddr} ${fdtdir}/${fdtfile}
loadimage=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfilez} || load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfilem}
loadrd=load ${devtype} ${bootpart} ${rdaddr} ${bootdir}/${rdfile}
mainargs=setenv bootargs console=${console} ${mtdparts} root=${root} rw rootwait ${optargs} ${ncargs}
mountubi=ubi part rootfs; ubifsmount ubi0:rootfs
mtddevname=u-boot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
ncip=192.168.1.5
ncipk=192.168.1.77
netconsole=off
partition=nand0,0
preboot=if env exists netconsole && test ${netconsole} = on; then if ping ${ncip}; then setenv stdin nc; setenv stdout nc; setenv stderr nc; version; if env exists ncargsusr; then echo ncargs has been defined by user; setenv ncargs ${ncargsusr}; else setenv ncargs ignore_loglevel netconsole=6665@${ipaddr}/eth0,6666@${ncipk}/; fi; fi; else echo Netconsole has been turned off.; echo To turn it on, set netconsole variable to on.; setenv stdin; setenv stdout; setenv stderr; setenv ncargs; fi
rdaddr=0x1100000
rdfile=initramfs-linux.img
serverip=192.168.1.74
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
startboot=usb start; ide reset; for devtype in usb ide; do setenv devnum 0; while ${devtype} dev ${devnum}; do echo ${devtype} found on device ${devnum}; setenv bootpart ${devnum}:1; echo Checking for: ${bootdir}/uEnv.txt ...; if test -e ${devtype} ${bootpart} ${bootdir}/uEnv.txt; then load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/uEnv.txt; env import -t ${loadaddr} ${filesize}; echo Loaded environment from ${bootdir}/uEnv.txt; echo Checking if uenvcmd is set ...; if test -n ${uenvcmd}; then echo Running uenvcmd ...; run uenvcmd; fi; fi; if run loadimage; then if env exists root; then echo root has been defined by user; else part uuid ${devtype} ${bootpart} uuid; setenv root PARTUUID=${uuid}; fi; run mainargs; if run loadfdt; then if run loadrd; then bootz ${loadaddr} ${rdaddr}:${filesize} ${fdtaddr}; else bootz ${loadaddr} - ${fdtaddr}; fi; else if run loadrd; then echo Booting uImage with initrd; bootm ${loadaddr} ${rdaddr}:${filesize}; else bootm ${loadaddr}; fi; fi; else echo No kernel found; fi; setexpr devnum ${devnum} + 1; done; done;

Environment size: 3039/131068 bytes')
I suspect bootpart 0:1 value since I have only one big /dev/sda1 partition, there's also this: $this->bbcode_second_pass_code('', 'setenv bootpart ${devnum}:1')
However when I have changed it:
$this->bbcode_second_pass_code('', 'NSA310> setenv bootpart ${devnum}:0
NSA310> setenv bootpart=0:0')
$this->bbcode_second_pass_code('', 'NSA310> setenv bootdir
NSA310> run startboot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: WDC WD40PURX-64GVNY0 Firm: 80.00A80 Ser#: WD-WCC4E0SERLJD
Type: Hard Disk
Supports 48-bit addressing
Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)

USB device 0: unknown device

Device 0: Model: WDC WD40PURX-64GVNY0 Firm: 80.00A80 Ser#: WD-WCC4E0SERLJD
Type: Hard Disk
Supports 48-bit addressing
Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
... is now current device
ide found on device 0
Checking for: /uEnv.txt ...
** File not found /zImage **
** File not found /uImage **
No kernel found

Device 1: not available')
Still 'Device 1: not available'

EDIT: Solved by Bodhi with this:
$this->bbcode_second_pass_code('', 'setenv bootdir /boot
boot')
$this->bbcode_second_pass_code('', 'uname -r
4.16.8-1-ARCH')

[summers]

good spot on the $this->bbcode_second_pass_code('', 'setenv bootpart ${devnum}:1;'), its a long time since I updated to a dt kernel, I know when I did it there were many things that hassled me. I forgot that it just look at the first partition in all usb and ide devices. It would be easy enough to change the script to scan all partitions - but that isn't want it does. So yes without changing the startboot script, easiest is to make the first partition of a disk the boot partition, but it can also be the root partition. SO thats what I have, the first partition as the root partition, and it contains /boot.

Now this you should be able to do when you make your big disk, make sure you copy the disk into the first partition.

On copying,have to say thats why I use tar via a pipe e.g. "tar cf - . | ( cd destination ; tar xf -)". Tar does it best to keep the files the same, so even thing like device files, and links, should go across. But going via a pipe, and nothing gets written to an intermediate location. Its whats is great with the unix pipe, in a case like this you are feeling GB->TB over a pipe, but the unix pipe will take all you throw at it.

On the ext flags to set, think we only need to worry about them on the new big disk, on the old small disk we will only ever boot from sda1, so on the small disk, I'd mount that at /boot on the root partition.

If booting a new disk and have access to uboot, I always think its worth while to do and "ext4ls ide 0:1 /" or equivalent, just to check you can access it.

For my case (not yet build up again, I don't have time in the week - I'll do it later this weekend). the fan uses a standard 3 pin header, e.g. two power, and sense wire. More modern fans are 4 pin (and you can change the speed), but still easy to get 3 pin fans. Only difference with the new fan, is that the lead is far longer. I should be able to hide this in the area below the riser for the ide disks, that board is at 90 deg to the main board, and across the back. It doesn't let air through so doesn't have the fan on it, but is empty behind.

Ah good that bodhi solved it. Guess you must have saveenv, when you cleared bootdir, as /boot is the default value. So hopefully now you are on you new big hard disk, and it auto boots, and you are on 2016 uboot and latest kernel? Have you decided if you'll install the rescue partition? I didn't bother as I have serial cables, so can always debug the hardware, as long as I don't trash uboot ...

[arti74]

Thank you for comment. My nsa310 is happily running Arch Linux with the newest dt kernel.
The only thing I miss are sensors which are still not recognized... I tred the i2cget command, but get:
$this->bbcode_second_pass_code('', 'i2cget -y 0x0 0x0a 0x07
Error: Read failed')
I have a small 40mm fan with a micro (mini?) 3 pin plug - so I need something to connect a new fan with the small fan input.

[summers]

Oh yes, found this page: https://www.quietpc.com/40mmfans

which says that the Scythe Mini Kaze, 40mm x 10mm Quiet Cooling Fan is a 40x10 fan, so should fit, and is cheaper than the noctua - but I'd guess noctua to be better ...

[arti74]

Possible, but the scythe is also quiet. However as I mentioned, the plug in both cases is too big for my board.

[summers]

$this->bbcode_second_pass_code('', 'sudo i2cget -y 0x0 0x0a 0x07
0x22
sudo i2cget -y 0x0 0x0a 0x08
0x7b') so on my nsa325 seems to work, 34 deg C (case open!) and fan at a somewhat strange 487rpm!.

does $this->bbcode_second_pass_code('', 'i2cdetect -l
i2cdetect 0') show anything?

And good that we finally finished the kernel and uboot upgrade, think its the hardest I heard of!