One day while booted into ChromeOS while AFK the OS seems to have gotten messed up. When I got back the screen stated that ChromeOS was damaged or missing. I tried to boot into linux but that failed as well (sadly I cannot remember how exacly). Since then I foolishly disabled developer mode and that also disabled USB booting. Recovery repeatedly fails.
The mainboard is Atlas
I have the recovery logs here - dmesg · GitHub
I tried to look thhrough them and find any good reason but I cannot find why recovery fails. I assumed that the SSD/MMC failed but would be keen to get confirmation if it is a hardware fault and not simply software.
what’s the recovery reason? dmesg doesn’t help, need recovery.log
I thought that recovery would bring back ChromeOS etc, that’s why I decided to do it. I probably should have tried to flash Linux again instead… But since disabling and re-enabling developer mode, that stopped being an option… So I am happy with alternatives to recovery if preferred, but no idea what other options there are to putting a working OS back on the laptop.
The first file in the link is the dmesg but the other logs are down lower in the same link. If you scroll past the dmesg you’ll see more
Edit: I had done a surface scan for a failed SSD and I did not find any at the time but if recovery.log is meant to provide the most useful info, would these messages suggest it has to do with the SSD not being found aka. it is dead?
get_fixed_dst_drive
+ local dev rootdev
+ '[' -n '/sys/devices/pci0000:00/0000:00:1e.4/mmc_host/mmc*/mmc*:*/block/mmcblk* /sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/nvme/nvme*/nvme*n1' ]
+ '[' -d '/sys/devices/pci0000:00/0000:00:1e.4/mmc_host/mmc*/mmc*:*/block/mmcblk*' ]
+ continue
+ '[' -d '/sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/nvme/nvme*/nvme*n1' ]
+ continue
+ echo
+ DST=
+ '[' -z ]
+ dlog 'SSD for installation not specified'
+ echo 'SSD for installation not specified'
+ return 1
+ on_error
+ '[' -n ]
+ message on_error
+ '[' -z 1 ]
+ message_on_error
+ instructions error
+ showbox -115 error
+ local 'offset=0,-115'
+ shift
+ local 'message_token=error'
+ shift
+ local 'message_file=/etc/screens/en-US/error.png'
+ '[' '!' -f /etc/screens/en-US/error.png ]
+ showimage /etc/screens/en-US/error.png 0,-115
+ local 'image=/etc/screens/en-US/error.png'
+ local 'offset=0,-115'
+ shift
+ shift
+ printf '\033]image:file=%s;offset=%s;scale=%d\033\' /etc/screens/en-US/error.png 0,-115 0
+ showicon -115 /etc/screens/icon_warning.png
+ local 'icon_left=-471'
+ local 'icon_top=-162'
+ shift
+ showimage /etc/screens/icon_warning.png -471,-162
+ local 'image=/etc/screens/icon_warning.png'
+ local 'offset=-471,-162'
+ shift
+ shift
+ printf '\033]image:file=%s;offset=%s;scale=%d\033\' /etc/screens/icon_warning.png -471,-162 0
+ progress empty
+ showbox 0 empty
+ local 'offset=0,0'
+ shift
+ local 'message_token=empty'
+ shift
+ local 'message_file=/etc/screens/en-US/empty.png'
+ '[' '!' -f /etc/screens/en-US/empty.png ]
+ showimage /etc/screens/en-US/empty.png 0,0
+ local 'image=/etc/screens/en-US/empty.png'
+ local 'offset=0,0'
+ shift
+ shift
+ printf '\033]image:file=%s;offset=%s;scale=%d\033\' /etc/screens/en-US/empty.png 0,0 0
+ dev_notice empty
+ showbox 115 empty
+ local 'offset=0,115'
+ shift
+ local 'message_token=empty'
+ shift
+ local 'message_file=/etc/screens/en-US/empty.png'
+ '[' '!' -f /etc/screens/en-US/empty.png ]
+ showimage /etc/screens/en-US/empty.png 0,115
+ local 'image=/etc/screens/en-US/empty.png'
+ local 'offset=0,115'
+ shift
+ shift
+ printf '\033]image:file=%s;offset=%s;scale=%d\033\' /etc/screens/en-US/empty.png 0,115 0
+ signal_fatal_error
sure looks like your eMMC is dead
Thanks, good to have that verified by someone with experience in reading these logs. I will look into getting a replacement
unless you are skilled in such repairs, the eMMC is not going to be easily replaced unfortunately
1 Like