This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
boot failed
#1
Hello,

I recently reflashed my TinkerBoard S from Android to Debian and am now not able to boot anymore.

When I try to boot the system fails and writes:
Code:
EXT4-fs error (device mmcblk1p2): ext4_lookup:1605: inode #7617: comm sudo: deleted inode referenced: 142365

From what I've read this could be a filesystem corruption.
I deleted everything on the board with gparted and made a new partion table (msdos)
Reinstalled TinkerOS Debian 2.0.8
But I get the same error

A common answer to this problem, is a too weak power supply. But mine had worked under Android.

I've spend some days googling the problem, but I do not find a solution. I'm afraid I maybe fried my board..... 

Can anybody help me?  Sad 


Here is the transcription of the error I get. I hope without typos.....
Code:
L2C: failed to init:  -19
rockchip_clk_register_branches: unkown clock type 9
vcc_sd: regulator get failed, ret=-517
vcc_flash: regulator get failed, ret=-517
rk-vcodec ff9a0000.vpn.service: could not find power_model mode
rk-vcodec ff9c0000.hevc-service: could not find power_model mode
mail ffa30000.gpu: Failed to get regulator
mail ffa30000.gpu: Power control initialization failed
rk_gmac-dumac ff290000.ehernet: phy regulator is not available yet, deferred probing
tinker-mcu: send_cmds: send command failed, ret: -6
tinker-mcu: tinker_mcu_probe: init_cmd_check failed: -6
im219 2-0010: Error -5 setting default controls
rockchip-sy-mipi-dphy ff770000.syscon:mipi-phy-rx0: invalid resource
rockchip-vpu ff9a0000.video-codec: can't request region for resource (mem 0xff9a0000-0xff9a07ff)
rockchip-vpu ff9a0000.video-codec: rockchip_vpu_hw_probe failed
rknandbase v1.2 2018-05-08
rockchip-vcp ff940000.vcp: invalid resource
rockchip-vcp ff980000.vcp: invalid resource
i2c i2c-6: of_12c: modalias failure on /hdmi@ff980000/ports
[drm:hdmi_config_hdr_infoframe] *ERROR* Not support DRM Infoframe
mail ffa30000.gpu: Failed to get leakage
mail ffa30000.gpu: Failed to get pvtm
rk_gmac-dumac ff290000.ethernet: cannot get clock clk_mac_speed
devfreq ffa30000.gpu: Couldn't update frequency transition information.
asoc-simple-card sound-simple-card: call_usermodulehelper fail, ret=-2, stauts =C
asoc-simple-card sound-simple-card: fSoC: DAFM unkown pin Headphones
/testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
/testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
/testcase-data/phandle-tests/consumer-a: could not find phandle
/testcase-data/phandle-tests/consumer-a: could not find phandle
/testcase-data/phandle-tests/consumer-a: arguments longer than property
/testcase-data/phandle-tests/consumer-a: arguments longer than property
overlay_is_topmost: #5 clashes #6 /testcase-data/overlay-node/test-bus/test-unittest8
overlay_removal_is_ok: Overlay #5 is not topmist
of_overlay_destroy: removal check failed for overlay #5
EXT4-fs (mmcblk1p2): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (mmcblk1p2): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mkdir: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm kbd_mode: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm kbd_mode: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm kbd_mode: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm touch: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
asoc-simple-card sound-simple-card: fSoC: DAFM unkown pin Headphones
rc.local[565]: ssh-keygen: generating new host keys: XXXXX XXXXXXX (removed from transcript)

Debian GNU/Linux 9 tinkerboard :ty1
tinkerboard login: [         16.042516]  EXT4-fs error (device mmcblk1p2): ext4_lookup: 1605: inode #7617: comm bash: deleted inode referenced: 142365
[        16.050621]  EXT4-fs error (device mmcblk1p2): ext4_lookup:1605: inode #7617: comm sudo: deleted inode referenced: 142365
Reply
#2
Using a linux box, try to check the memory integrity, eMMC ?
Otherwise try to re-flash it, but make sure the image is not corrupted.

Last, try to boot from a SDcard and check the eMMC for file system consistency. Anyway to use it on eMMC, it will take a low lever writing, which is beyond the file system.

Very last options use badblocks to verify whether the eMMC has blocks damaged.
Light blue words might be a link. Have you try to click on them? Big Grin
Reply
#3
(01-19-2019, 08:20 PM)DuroHeci Wrote: Hello,

I recently reflashed my TinkerBoard S from Android to Debian and am now not able to boot anymore.

When I try to boot the system fails and writes:
Code:
EXT4-fs error (device mmcblk1p2): ext4_lookup:1605: inode #7617: comm sudo: deleted inode referenced: 142365

From what I've read this could be a filesystem corruption.
I deleted everything on the board with gparted and made a new partion table (msdos)
Reinstalled TinkerOS Debian 2.0.8
But I get the same error

A common answer to this problem, is a too weak power supply. But mine had worked under Android.

I've spend some days googling the problem, but I do not find a solution. I'm afraid I maybe fried my board..... 

Can anybody help me?  Sad 


Here is the transcription of the error I get. I hope without typos.....
Code:
L2C: failed to init:  -19
rockchip_clk_register_branches: unkown clock type 9
vcc_sd: regulator get failed, ret=-517
vcc_flash: regulator get failed, ret=-517
rk-vcodec ff9a0000.vpn.service: could not find power_model mode
rk-vcodec ff9c0000.hevc-service: could not find power_model mode
mail ffa30000.gpu: Failed to get regulator
mail ffa30000.gpu: Power control initialization failed
rk_gmac-dumac ff290000.ehernet: phy regulator is not available yet, deferred probing
tinker-mcu: send_cmds: send command failed, ret: -6
tinker-mcu: tinker_mcu_probe: init_cmd_check failed: -6
im219 2-0010: Error -5 setting default controls
rockchip-sy-mipi-dphy ff770000.syscon:mipi-phy-rx0: invalid resource
rockchip-vpu ff9a0000.video-codec: can't request region for resource (mem 0xff9a0000-0xff9a07ff)
rockchip-vpu ff9a0000.video-codec: rockchip_vpu_hw_probe failed
rknandbase v1.2 2018-05-08
rockchip-vcp ff940000.vcp: invalid resource
rockchip-vcp ff980000.vcp: invalid resource
i2c i2c-6: of_12c: modalias failure on /hdmi@ff980000/ports
[drm:hdmi_config_hdr_infoframe] *ERROR* Not support DRM Infoframe
mail ffa30000.gpu: Failed to get leakage
mail ffa30000.gpu: Failed to get pvtm
rk_gmac-dumac ff290000.ethernet: cannot get clock clk_mac_speed
devfreq ffa30000.gpu: Couldn't update frequency transition information.
asoc-simple-card sound-simple-card: call_usermodulehelper fail, ret=-2, stauts =C
asoc-simple-card sound-simple-card: fSoC: DAFM unkown pin Headphones
/testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
/testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
/testcase-data/phandle-tests/consumer-a: could not find phandle
/testcase-data/phandle-tests/consumer-a: could not find phandle
/testcase-data/phandle-tests/consumer-a: arguments longer than property
/testcase-data/phandle-tests/consumer-a: arguments longer than property
overlay_is_topmost: #5 clashes #6 /testcase-data/overlay-node/test-bus/test-unittest8
overlay_removal_is_ok: Overlay #5 is not topmist
of_overlay_destroy: removal check failed for overlay #5
EXT4-fs (mmcblk1p2): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (mmcblk1p2): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mkdir: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm kbd_mode: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm kbd_mode: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm kbd_mode: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm touch: deleted inode referenced: 142365
EXT4-fs error (mmcblk1p2): ext4_lookup:1605:  inode #7617: comm mount: deleted inode referenced: 142365
asoc-simple-card sound-simple-card: fSoC: DAFM unkown pin Headphones
rc.local[565]: ssh-keygen: generating new host keys: XXXXX XXXXXXX (removed from transcript)

Debian GNU/Linux 9 tinkerboard :ty1
tinkerboard login: [         16.042516]  EXT4-fs error (device mmcblk1p2): ext4_lookup: 1605: inode #7617: comm bash: deleted inode referenced: 142365
[        16.050621]  EXT4-fs error (device mmcblk1p2): ext4_lookup:1605: inode #7617: comm sudo: deleted inode referenced: 142365




Looks like a power failure.

vcc_sd: regulator get failed, ret=-517
vcc_flash: regulator get failed, ret=-517
rk-vcodec ff9a0000.vpn.service: could not find power_model mode
rk-vcodec ff9c0000.hevc-service: could not find power_model mode
mail ffa30000.gpu: Failed to get regulator
mail ffa30000.gpu: Power control initialization failed
rk_gmac-dumac ff290000.ehernet: phy regulator is not available yet, deferred probing

Important:
Use a 3.0A power adapter.
Use a short thick usb to microSD.

I had a problem with always getting the Low Power message flashing.
I found a very thick 3 foot cable like the one below. And with no switch.
The low power message is gone.
So all this time it was a cable.
I used cables that the Tinkerboard would not even boot.
I bought a 3.0A and a 4.9A USB adapter and both I could not use.
It could fix your power problem.

So, yes there is two major issues with the adapter and cable.
Android maybe able to handle the adapter and cable but not the TinkerboardOS.

https://www.ebay.com/itm/High-Speed-USB-...rk:16:pf:0
Reply
#4
@Im4Tinker
Quote:Using a linux box, try to check the memory integrity, eMMC ?

Otherwise try to re-flash it, but make sure the image is not corrupted.

I reflashed with a freshly downloaded image, now it works  Smile Smile Smile   Thank you so much. The old image must have get damaged at some point.
Reply
#5
(01-20-2019, 12:38 PM)DuroHeci Wrote: @Im4Tinker
Quote:Using a linux box, try to check the memory integrity, eMMC ?

Otherwise try to re-flash it, but make sure the image is not corrupted.

I reflashed with a freshly downloaded image, now it works  Smile Smile Smile   Thank you so much. The old image must have get damaged at some point.



Can you let me know if you get the low power message?
Reply
#6
@Jay Smith

I use a 3000 mA 5V power supply with a short (~ 50 cm) thick usb cable. Having no troubles at the moment.

Quote:vcc_sd: regulator get failed, ret=-517
vcc_flash: regulator get failed, ret=-517
rk-vcodec ff9a0000.vpn.service: could not find power_model mode
rk-vcodec ff9c0000.hevc-service: could not find power_model mode
mail ffa30000.gpu: Failed to get regulator
mail ffa30000.gpu: Power control initialization failed
rk_gmac-dumac ff290000.ehernet: phy regulator is not available yet, deferred probing

All lines above are still present in the dmesg output, except for 

Quote:mail ffa30000.gpu: Failed to get regulator

mail ffa30000.gpu: Power control initialization failed

I put the output of dmesg here for you if you are interested.


Attached Files
.txt   dmesg.txt (Size: 60.55 KB / Downloads: 1)
Reply
#7
(01-20-2019, 04:02 PM)DuroHeci Wrote: @Jay Smith

I use a 3000 mA 5V power supply with a short (~ 50 cm) thick usb cable. Having no troubles at the moment.

Quote:vcc_sd: regulator get failed, ret=-517
vcc_flash: regulator get failed, ret=-517
rk-vcodec ff9a0000.vpn.service: could not find power_model mode
rk-vcodec ff9c0000.hevc-service: could not find power_model mode
mail ffa30000.gpu: Failed to get regulator
mail ffa30000.gpu: Power control initialization failed
rk_gmac-dumac ff290000.ehernet: phy regulator is not available yet, deferred probing

All lines above are still present in the dmesg output, except for 

Quote:mail ffa30000.gpu: Failed to get regulator

mail ffa30000.gpu: Power control initialization failed

I put the output of dmesg here for you if you are interested.


I get the same.  Must be common and causes no problems.
Reply
#8
During startup there might be such messages. There are patches in /etc which may improve something after a completed boot.
Light blue words might be a link. Have you try to click on them? Big Grin
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)