OscarCK Posted March 27, 2018 Share Posted March 27, 2018 Hi, I was using my M2 Plus yesterday getting the 3rd USB to work, everything went well with that got it working, and if I remember correctly I also ran the Update & Upgrade through the armbian-config utility before shutting everything down, today when I got back from class with a custom PCB adapter for the 3rd USB, I connect it with the USB device, I connect the power to the board and wait for the VirtualHere server to start up and show up at my computer, when I noticed it wasn't showing up I did a ip scan and couldn't see the ip, connected a screen to the HDMI and got this on the boot up, it just cycles through the same screen. When I installed the image about 2 weeks ago and also ran the script to install it to the emmc, so it is not running from an SD card. I hope its just some kind of boot script that is missing a letter or something and don't have to reinstall the image, I just got the board running just fine for my project. The video is a little bit blurry but should be readable at full screen. Thanks Oscar Link to comment Share on other sites More sharing options...
Igor Posted March 27, 2018 Share Posted March 27, 2018 28 minutes ago, OscarCK said: The video is a little bit blurry but should be readable at full screen. That looks fine, but why a screen goes off its hard to say without more detailed inspection - serial console logs. Have you tried booting board only? If there is a power restraint, HDMI is shut off. Link to comment Share on other sites More sharing options...
OscarCK Posted March 27, 2018 Author Share Posted March 27, 2018 I checked for yesterdays logs but hadn't turned on logging on putty, there shouldn't be any problem with the power since I had exactly the same things connected, the only thing drawing current through the M2+ is an Arduino Mega2560 which doesn't have any load its just running logic level stuff, I also tried booting without it connected but the same thing happens, it is running from a Meanwell 5V 3A industrial DIN power supply, I checked the power and it is stable at 5.05V the whole time, I connected an SD card with the image (5.38 mainline) I had downloaded 2 weeks ago and it boots just fine. Oh and the No Signal on the monitor stays for about a minute or two before the next boot up shows up. Link to comment Share on other sites More sharing options...
Igor Posted March 27, 2018 Share Posted March 27, 2018 26 minutes ago, OscarCK said: Oh and the No Signal on the monitor stays for about a minute or two before the next boot up shows up. So you mean you have a boot cycle ... than kernel must crash for some reason. This mainline is not bulletproof yet Try to get some more info why it crashes. Worse case you will need to go back to older version of the kernel. Link to comment Share on other sites More sharing options...
OscarCK Posted March 27, 2018 Author Share Posted March 27, 2018 Well going to an older kernel isn't really the problem, it's getting the setup working again, the server has a paid license that shouldn't need to changed since it is hardware based but I have already asked the guy for a new code because I did a no no with the previous installation and feel like he thinks I'm robbing him if I ask it again, even though he said no problem if I'm having problems with my board and I need a new code :-P I ran an fdisk while booted with the SD card and got the following, so it seems the mmc superblock is corrupt, unless I'm reading it wrong. login as: admin admin@192.168.1.50's password: ____ ____ _ __ __ ____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | \/ |___ \ _ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |\/| | __) || |_ | |_) | (_| | | | | (_| | | | | (_| | | __/| | | | | |/ __/_ _| |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| |_| |_|_____||_| Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.14-sunxi System load: 0.40 0.30 0.12 Up time: 2 min Memory usage: 5 % of 1000MB IP: 192.168.1.50 CPU temp: 41°C Usage of /: 8% of 15G [ 0 security updates available, 32 updates total: apt upgrade ] Last check: 2018-03-27 17:05 Last login: Tue Mar 27 17:16:13 2018 admin@bananapim2plus:~$ sudo fdisk -l Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 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 Disklabel type: dos Disk identifier: 0x0e1c69a6 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 30805119 30796928 14.7G 83 Linux Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 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 Disklabel type: dos Disk identifier: 0x07dfd210 Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 8192 15117183 15108992 7.2G 83 Linux Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 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/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 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 admin@bananapim2plus:~$ sudo fsck /dev/mmcb1k1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) fsck.ext2: No such file or directory while trying to open /dev/mmcb1k1 Possibly non-existent device? admin@bananapim2plus:~$ sudo fsck /dev/mmcblk1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> Found a dos partition table in /dev/mmcblk1 Link to comment Share on other sites More sharing options...
OscarCK Posted March 27, 2018 Author Share Posted March 27, 2018 Well it was the wrong partition I was scanning first, run a superblock backup check and couldn't find anything, and then run the same on the next one, and found something run the fsck on the correct one and it got fixed. admin@bananapim2plus:~$ sudo fsck /dev/mmcblk1p1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) /dev/mmcblk1p1: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (1464622, counted=1464617). Fix<y>? yes Free inodes count wrong (380735, counted=380731). Fix<y>? yes /dev/mmcblk1p1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mmcblk1p1: 91621/472352 files (0.2% non-contiguous), 424007/1888624 blocks admin@bananapim2plus:~$ sudo fsck /dev/mmcblk1p1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/mmcblk1p1: 91621/472352 files (0.2% non-contiguous), 424007/1888624 blocks It now boots just just fine, should I try a new update/upgrade or should I wait for more from you, of course there isn't actually any need to update yet but all fixes are good fixes. Oscar Link to comment Share on other sites More sharing options...
Igor Posted March 27, 2018 Share Posted March 27, 2018 4 minutes ago, OscarCK said: It now boots just just fine, should I try a new update/upgrade or should I wait for more from you, of course there isn't actually any need to update yet but all fixes are good fixes. It is labeled testing for this reason ... no warranty for this kernel - if you have some production stuff, rather freeze kernel update (armbian-config -> system), update other userspace packages normally with apt update and upgrade, and wait for a stable version. IMO this is ATM the best way to go. Link to comment Share on other sites More sharing options...
OscarCK Posted March 27, 2018 Author Share Posted March 27, 2018 Oh I though it would only update to stable kernels since I was running mainline and hadn't enabled the "nightly builds" option. Thanks for the great work so far btw! Oscar Link to comment Share on other sites More sharing options...
Igor Posted March 27, 2018 Share Posted March 27, 2018 10 minutes ago, OscarCK said: Oh I though it would only update to stable kernels Mainline kernel for H3, H5, and A64 hasn't reached stable yet. They are in experimental/testing phase. 4.14.y will hopefully be the first one. For some people, some cases, they are fine for some time ... Link to comment Share on other sites More sharing options...
Recommended Posts