[Tails-testers] Tails won't load past boot loader screen

Delete this message

Reply to this message
Autor: h.velveteen7three
Data:  
Dla: tails-testers@boum.org
Temat: [Tails-testers] Tails won't load past boot loader screen
Hello,
I've only been able to successfully start Tails (v. 3.15) once. This is the first ticket I've ever sent, so I apologize in advance if I don't have all of the requisite information or I've included nonessential information.

Issue: Tails fails to start a second time

Computer information

Computer: MacBook Pro 13" (Late 2011)

OS: macOS High Sierra 10.13.6

CPU: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz

RAM: 16 GB 1333 MHz DDR3

Graphics: Intel HD 3000 512 MB

Tails Ver: 3.15 on SanDisk Cruzer Glide USB (32 GB)

I've previously been able to run Tails on the same computer, from the same USB stick back from Tails Version 3.13 up to 3.14.

Last successful version to run was 3.14. Logged on and attempted to auto update to 3.14.2 but after about 20 mins, the status bar for zenity hadn't moved.
-Rebooted computer.
-Manually downloaded 3.15 .img file and flashed to same USB with Etcher.

Initially it started up fine, re-established persistent folder. Restarted Tails, boot loader displayed fine, but when I pressed 'enter' to start Tails, got black screen with following:

BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) aufs not available.

I then typed 'exit' and got:

mount: mounting aufs on /root/ failed: no such device
mount: mounting /dev on /root/dev failed: No such file or firectory
mount: mounting /dev on /root/dev failed: No such file or firectory
mount: mounting /run on /root/run failed: No such file or firectory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
/init: line 272: 6: Bad file descriptor
[ 53.543755] Kernal panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 53.543755]
[ 53.543788] CPU: 1 PID: 1 Comm: init Tainted: G OE 4.19.0-5-amd64 #1 Debian 4.19.37-5
[ 53.543817] Hardware name: Apple Inc. MacBookPro8,1/Mac-94245B3640C91CB1, BIOS 83.0.0.0.0 12/19/2018
[ 53.543847] Call trace:
[ 53.543863] dump_stack+0x5c/0x80
[ 53.543878] panic+0xe7/0x24a
[ 53.543891] do_exit.cold.22+0x26/0x7f
[ 53.543907] ? handle_mm_fault+0xda/0x200
[ 53.543922] do_group_exit+0x3a/0xa0
[ 53.543936] __x64_sys_exit_group+0x14/0x110
[ 53.543953] do_syscall_64+0x53/0x100
[ 53.543969] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 53.543987] RIP: 0033:0x7fe60a0b6618
[ 53.544003] Code: Bad RIP value.
[ 53.544015] RSP: 002b:00007ffc0d73dcd8 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
[ 53.544041] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe60a0b6618
[ 53.544064] RDX: 0000000000000002 RSI: 000000000000003c RDI: 0000000000000002
[ 53.544088] RBP: 0000000000000004 R08: 00000000000000e7 R09: ffffffffffffff98
[ 53.544111] R10: 0000000000000208 R11: 0000000000000206 R12: 000000000000008f
[ 53.544134] R13: 0000000000000007 R14: 00007ffc0d73e1c8 R15: 0000000000000000
[ 53.544186] Kernel Offset: 0x37400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffff
[ 53.544229]---[end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 53.544229] ]---

Subsequent attempts to load Tails have been hit or miss, but mostly misses. If I'm able to successfully boot up and start tails, I'll attempt the root terminal solution:

sgdisk --recompute-chs /dev/bilibop

Aside from that, I don't know what else to try. Any help would be greatly appreciated.

R,
-H

Sent with [ProtonMail](https://protonmail.com) Secure Email.