piter75 Posted January 6, 2020 Posted January 6, 2020 1 hour ago, Enrico said: i dont find it on armbian-config It's in System menu. You can also run: sudo nand-sata-install directly from the command line.
Enrico Posted January 7, 2020 Posted January 7, 2020 nand-sata-install as root Unsupported u-boot processing configuration! root@Iobroker:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1 179:0 0 30G 0 disk └─mmcblk1p1 179:1 0 29.4G 0 part / zram0 253:0 0 50M 0 disk /var/log zram1 253:1 0 1G 0 disk [SWAP] were i should found the Nvme SSD
Igor Posted January 7, 2020 Posted January 7, 2020 2 hours ago, Enrico said: were i should found the Nvme SSD It looks like it was not detected. Have you tried on both kernels? Do you have some other brand for testing?
piter75 Posted January 7, 2020 Posted January 7, 2020 3 hours ago, Enrico said: Unsupported u-boot processing configuration! Beside what Igor suggested this line tells me that you are using quite old image that had a bug in u-boot writing function. Can you try 19.11.7 from https://dl.armbian.com/nanopim4v2/archive?
reinisv Posted January 14, 2020 Posted January 14, 2020 I recently received NanoPi M4V2 and all of the current armbian NanoPi M4V2 images I tested did not boot fully- I got a blinking green LED, Ethernet link was up, but no IP address requested. Serial console output stopped with "Starting kernel...". Tested the FriendlyCore images- those did boot correctly.
martinayotte Posted January 14, 2020 Posted January 14, 2020 27 minutes ago, reinisv said: Serial console output stopped with "Starting kernel...". To get more verbose log details, you need to edit /boot/armbianEnv.txt and change "verbosity=7" as well as "console=serial" ... 1
reinisv Posted January 14, 2020 Posted January 14, 2020 9 minutes ago, martinayotte said: To get more verbose log details, you need to edit /boot/armbianEnv.txt and change "verbosity=7" as well as "console=serial" ... Now that is very strange... I re-flashed the same armbian image to SD card, changed the settings you suggested and see the serial console as expected, system even gets the IP address. Do the default armbian settings disable serial console? Maybe I messed up the DHCP configuration in NetworkManager on the host PC when I tried running it for the first time...
Igor Posted January 14, 2020 Posted January 14, 2020 4 hours ago, reinisv said: Do the default armbian settings disable serial console? Serial console is enabled, but boot log goes to the HDMI by default on boards that have HDMI. You have to tell to where this output goes. In both cases you can login via console, but you have to wait until boot finishes. First one takes longer since it expends SD card/boot media. This can take a while if your media is old, big or old and big.
denni_isl Posted January 15, 2020 Posted January 15, 2020 Did notice after last update yesterday that /etc/environment was empty (after replacing it wit its PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games") I got a wifi connection.
Igor Posted January 15, 2020 Posted January 15, 2020 3 minutes ago, denni_isl said: Did notice after last update yesterday that /etc/environment was empty Update from to where?
Igor Posted January 15, 2020 Posted January 15, 2020 Just now, denni_isl said: armbian-config Yes, but what have you done inside that tool. I have to know to understand to be able to recreate and fix.
Igor Posted January 15, 2020 Posted January 15, 2020 Have you switched to beta. What about perhaps providing logs? (armbianmonitor -u) I have no supernatural abilities.
TCB13 Posted January 16, 2020 Posted January 16, 2020 Hello guys, V2 buster image, kernel 5.4 from an NVMe drive. It works mostly fine but I've been having a consistent issue with copying directories with large files from a USB 3 drive to the internal NVMe. After `cp -r` the green LED of the board stops flashing and it reboots by itself. Unfortunately I can't get logs after the reboot so I don't know how to post more info about this. I never had this issue with the original board with the same USB3 ASM1051E SATA 6Gb/s bridge.
TCB13 Posted January 16, 2020 Posted January 16, 2020 Another thing I noticed: TCP offloading is still broken in all boards as discussed previously here: And here: https://github.com/MichaIng/DietPi/issues/2028 To make the network work properly under load and some protocols like HTTPS and NFS I have to run: ethtool -K eth0 rx off tx off after the network is up. This issue seems to affect both the original M4 and the v2 with all kernels.
TCB13 Posted January 16, 2020 Posted January 16, 2020 10 hours ago, TCB13 said: Hello guys, V2 buster image, kernel 5.4 from an NVMe drive. It works mostly fine but I've been having a consistent issue with copying directories with large files from a USB 3 drive to the internal NVMe. After `cp -r` the green LED of the board stops flashing and it reboots by itself. Unfortunately I can't get logs after the reboot so I don't know how to post more info about this. I never had this issue with the original board with the same hard drives. @Igor I just noticed that you had some info about this problem before here: Is there any fix for this? I never had with this issue with a original board, using the same USB3 ASM1051E SATA 6Gb/s bridge What about you @NicoD , since you're always running nice tests, have you experienced such issues?
piter75 Posted January 16, 2020 Posted January 16, 2020 46 minutes ago, TCB13 said: To make the network work properly under load and some protocols like HTTPS and NFS I have to run: ethtool -K eth0 rx off tx off after the network is up. This issue seems to affect both the original M4 and the v2 with all kernels. Did you build the kernel yourself? I have committed a fix (https://github.com/armbian/build/commit/8c93385a84e2c8847ad5cf03684bee9c58596bf7) to the build system a few days ago. It should fix issues with the most common MTU of 1500. It will be build into some future kernel / image build. 1
TCB13 Posted January 16, 2020 Posted January 16, 2020 3 minutes ago, piter75 said: Did you build the kernel yourself? No I didn't build it myself but thank you for the update.
TCB13 Posted January 16, 2020 Posted January 16, 2020 I've also notice some random reboots / maybe crashes without logs: Quote Jan 16 01:38:11 localhost kernel: [ 95.592186] Bluetooth: L2CAP socket layer initialized Jan 16 01:38:11 localhost kernel: [ 95.592200] Bluetooth: SCO socket layer initialized Jan 16 01:38:11 localhost kernel: [ 95.593656] Bluetooth: HCI UART driver ver 2.3 Jan 16 01:38:22 localhost kernel: [ 106.182318] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro,data=orderedJan 16 14:17:03 localhost kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] Jan 16 14:17:03 localhost kernel: [ 0.000000] Linux version 5.4.7-rockchip64 (root@builder) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-201 9.03 (arm-rel-8.36))) #19.11.5 SMP PREEMPT Wed Jan 1 09:39:17 CET 2020 Jan 16 14:17:03 localhost kernel: [ 0.000000] Machine model: FriendlyElec NanoPi M4 Ver2.0 As you can see it was running fine without any messages at 1:38 am and them it later rebooted by itself at 2:17 pm without logging anything.
NicoD Posted January 16, 2020 Author Posted January 16, 2020 6 hours ago, TCB13 said: What about you @NicoD , since you're always running nice tests, have you experienced such issues? I do not use ethernet since I do not have a connection in my work area. So I was not aware of this. Good to see there's already a fix for it. Please provide the output of : armbianmonitor -u for more info. 17 hours ago, TCB13 said: I've been having a consistent issue with copying directories with large files from a USB 3 drive to the internal NVMe. Could you be a bit more precise please. What file size is large? Is this with every USB3 device the same? How are both drives formatted? Is the USB3 drive powered by the M4?
TCB13 Posted January 16, 2020 Posted January 16, 2020 2 hours ago, NicoD said: I do not use ethernet since I do not have a connection in my work area. So I was not aware of this. Good to see there's already a fix for it. Please provide the output of : armbianmonitor -u for more info. Could you be a bit more precise please. What file size is large? Is this with every USB3 device the same? How are both drives formatted? Is the USB3 drive powered by the M4? Hi, About the Ethernet: as expected I was able to fix it by disabling tcp offload. Now about the hard drive: It's a SATA hard drive connected via a USB 3 ASM1051E SATA bridge. The disk has its own power supply and if I connect it to my old M4 (the original one) I'm able to copy GB of data without issues, however in the M4v2 the board restarts itself. I guess since it works fine on the old M4 it is safe to assume that the issue is on the new board and/or kernel. The only difference here is that the old board is runing a 4.X kernel while the new one is running 5.X.
piter75 Posted January 16, 2020 Posted January 16, 2020 3 minutes ago, TCB13 said: it is safe to assume that the issue is on the new board and/or kernel. The only difference here is that the old board is runing a 4.X kernel while the new one is running 5.X Could you possibly test it with 4.x on M4v2? 1
NicoD Posted January 16, 2020 Author Posted January 16, 2020 8 minutes ago, TCB13 said: Now about the hard drive: It's a SATA hard drive connected via a USB 3 ASM1051E SATA bridge. The disk has its own power supply and if I connect it to my old M4 (the original one) I'm able to copy GB of data without issues, however in the M4v2 the board restarts itself. I guess since it works fine on the old M4 it is safe to assume that the issue is on the new board and/or kernel. The only difference here is that the old board is runing a 4.X kernel while the new one is running 5.X. As @piter75 commented. Try the 4.x image. I'm using the M4V2 with 4.x for a while and haven't had any issues like that. I often copy big files of GB's to my externel USB HD. So I do not think the issue is with the M4V2, but might be with 5.x instead. Mainline kernel is still a work in progress.
TCB13 Posted January 17, 2020 Posted January 17, 2020 @piter75 and @NicoD as you guys suggested I decided to try the 4.x image and it works just fine! Look like there are bugs in the 5.x image. Thank you. PS: I tried to downgrade the kernel using armbian-config and my system never booted again had to do a fresh install. I've noticed that the CPU in the 5.x image was running up to 2.02Ghz on the big cores, with the 4.x image seems to be a cap at 1.80Ghz.
piter75 Posted January 17, 2020 Posted January 17, 2020 4 hours ago, TCB13 said: as you guys suggested I decided to try the 4.x image and it works just fine! Look like there are bugs in the 5.x image. Thank you. Thanks for verifying. Now we have one less variable in this equation. Would you be able to spare some more time and test the same scenario with 5.x on NanoPi M4?
Matthias Posted January 17, 2020 Posted January 17, 2020 7 hours ago, TCB13 said: @piter75 and @NicoD as you guys suggested I decided to try the 4.x image and it works just fine! Look like there are bugs in the 5.x image. Thank you. Interesting, I also had problems copying files using the 5.4 kernel on my NanoPi M4V2. I compiled it myself and copies files from the sd-card to and external hard drive connected via the SATA-hat. I used file systems on the hard drive that were able to detect corrupted data on the drive (ZFS and BTRFS) and every time I did a scrub after copying the files, failed CRC-checks within the data were reported, some of them even at the same position on two redundant drives (mirror). I'll try again with the legacy kernel (4.x). Would be greate if it works in this configuration. @piter75: Did you apply your fixes for ethernet also to the legacy kernel? Then it would be much easier to get the data onto the device in the first place. 1
piter75 Posted January 17, 2020 Posted January 17, 2020 11 minutes ago, Matthias said: @piter75: Did you apply your fixes for ethernet also to the legacy kernel? Then it would be much easier to get the data onto the device in the first place. Oh... I somehow fixed my mind on the fact that it was working properly with 4.4 and fixed it only in "current" and "dev". I will verify it with 4.4 and try to fix if needed.
TCB13 Posted January 17, 2020 Posted January 17, 2020 4 hours ago, piter75 said: Thanks for verifying. Now we have one less variable in this equation. Would you be able to spare some more time and test the same scenario with 5.x on NanoPi M4? Yes I will, but only in a few days. I'll report as soon as I have new information.
Matthias Posted January 17, 2020 Posted January 17, 2020 1 hour ago, piter75 said: Oh... I somehow fixed my mind on the fact that it was working properly with 4.4 and fixed it only in "current" and "dev". I will verify it with 4.4 and try to fix if needed. Don't worry. I remember darkly that when I tested it one month ago the legacy kernel was good at receiving and bad at sending while the current kernel was cood at sending and bad at receiving. See here:
Nobby42 Posted January 17, 2020 Posted January 17, 2020 On 1/16/2020 at 1:58 AM, TCB13 said: Hello guys, V2 buster image, kernel 5.4 from an NVMe drive. It works mostly fine but I've been having a consistent issue with copying directories with large files from a USB 3 drive to the internal NVMe. After `cp -r` the green LED of the board stops flashing and it reboots by itself. Unfortunately I can't get logs after the reboot so I don't know how to post more info about this. I never had this issue with the original board with the same USB3 ASM1051E SATA 6Gb/s bridge. Hi, I have had formative experience with the NanoPI M4v2.. First, you need a real power supply. The Rasbberry 4 power supply for example breaks down when using a NMVe and a SSD, at high load, to below 5V (approx. 4.8V - 4.7V). 2. the CPU frequency. I think the 1.5/2Ghz is too much. I have had several crashes. For example the NanoPi crashes when transferring large amounts of data, sometimes processes (kworker, sshd, ...) just crashed and sometimes the NanoPi just stopped. Since I use the frequency to 1.4/1.8Ghz and a similar power supply, it looks like the NanoPI runs stable with NMVe and USB SSD. Currently I am using the NanoPi as a file server, MQTT Broker and nextcloud server and haven't had any crashes for 4 days.
Recommended Posts