Hi guys,
i have Rock64 4gb version and i can't boot new stretch 0.6.41 image (OMV). When i put SD card with flashed image (tried etcher and pine64 installer too ...), there are cycling errors like:
- Buffer I/O error on dev mmcblk1, logical block 0, async page read
- mmc1: tried to reset card
- mmcblk1: error -84 transfering data, sector ....... cmd response 0x900, card status 0x0
and more.
Around after minute device restart, and looping with errors again. I have three 16gb class 10 cards (all the same), but the same result with each. I don't think that it is a problem with cards, because I'm able to boot Jessie OMV image 0.5.15 without problems on any card. When i try to upgrade from 0.5.15, i end up like with flashed 0.6.41 image. I have read a few posts with similar problems, mostly on 4gb boards.
Someone here with 4gb board running new images? Please help and sorry for my english. TY.
(05-23-2018, 02:37 PM)Brendon Wrote: Hi guys,
i have Rock64 4gb version and i can't boot new stretch 0.6.41 image (OMV). When i put SD card with flashed image (tried etcher and pine64 installer too ...), there are cycling errors like:
- Buffer I/O error on dev mmcblk1, logical block 0, async page read
- mmc1: tried to reset card
- mmcblk1: error -84 transfering data, sector ....... cmd response 0x900, card status 0x0
and more.
Around after minute device restart, and looping with errors again. I have three 16gb class 10 cards (all the same), but the same result with each. I don't think that it is a problem with cards, because I'm able to boot Jessie OMV image 0.5.15 without problems on any card. When i try to upgrade from 0.5.15, i end up like with flashed 0.6.41 image. I have read a few posts with similar problems, mostly on 4gb boards.
Someone here with 4gb board running new images? Please help and sorry for my english. TY.
I'm running bionic-containers-0.6.41-arm64 on a 4GB (and 2GB) board without any issues at present. I'll download the stretch-omv image to see if I can reproduce your problems. I did have issues with a Samsung EVO+ card, but I don't know if it was rock64 or image-specific, or just an freak event...
I tried both the armhf and arm64 versions of stretch-openmediavault-rock64-0.6.41-227 but I can't reproduce your issues with that particular image.
My setup is rock64 v2.0, 4GB ram, 16GB Samsung EVO. SPI flash had the latest version of uboot (not that it matters if you have never flashed yours, as it would then be blank by default), the eMMC was disabled, serial console plugged in to the rpi header, and GbE networking connected.
armhf - https://pastebin.com/SNEp9GRL
arm64 - https://pastebin.com/JG2YZAbU
Seen similar reports but I too wasn't able to reproduce this issue on my boards.
Solved!!! I've bought a new 16GB Kingston SD, and everything works perfect now. Two times flash and few reboots without single issue. So conclusion - don't use shitty cards (3x Intenso in my case). It seems that Rock64 is a little bit card "sensitive".
TY for your help pfeerick, you guys are doing great job.
05-24-2018, 10:01 AM
(This post was last modified: 05-24-2018, 10:24 AM by edupv.)
I was using bionic-minimal-rock64-0.6.33-211-arm64.img.xz, I upgraded to the current stable release 0.6.41-227 by "apt upgrade" today, then my rock64 is unable to boot now. I don't have a working usb serial console adapter, so I don't know the boot message.
I am using an emmc module, I tried the "jumper pull" method (pull emmc jumper 2-3 seconds after applying power) many times to boot the sdcard, but have never succeed. I can boot the sdcard (armbian) only when the emmc module removed from the socket. I don't know how to make my rock64 working with the emmc module again.
(05-24-2018, 09:37 AM)Brendon Wrote: Solved!!! I've bought a new 16GB Kingston SD, and everything works perfect now. Two times flash and few reboots without single issue. So conclusion - don't use shitty cards (3x Intenso in my case). It seems that Rock64 is a little bit card "sensitive".
TY for your help pfeerick, you guys are doing great job.
There are so many fake cards out there - even from reputable retailers - its hardly your fault. I just had a sandisk from amazon give me 2MB/s speeds ... obviously fake.
(05-24-2018, 10:01 AM)edupv Wrote: I was using bionic-minimal-rock64-0.6.33-211-arm64.img.xz, I upgraded to the current stable release 0.6.41-227 by "apt upgrade" today, then my rock64 is unable to boot now. I don't have a working usb serial console adapter, so I don't know the boot message.
I am using an emmc module, I tried the "jumper pull" method (pull emmc jumper 2-3 seconds after applying power) many times to boot the sdcard, but have never succeed. I can boot the sdcard (armbian) only when the emmc module removed from the socket. I don't know how to make my rock64 working with the emmc module again.
Try pulling the jumper a little sooner, nearer to 1-2 seconds, and then try a bit longer 3-4 seconds... I suspect it will be the former that will fix it not the latter... uboot could be nearly finished booting from the microSD before the eMMC is enabled. Otherwise, if you write the 0.6.44 image from ayufan to to your microSD, and boot from it with the jumper left connected, I'm wondering if that is the purpose of the new rock64_reset_emmc.sh script, so that you can reset it and then access it?
If that doesn't work, your best/simplest option may be to get a usb-to-eMMC adapter... then you can always just unplug the eMMC and write to it on another computer...
|
