Using Fedora-x86_64-19-20130627-sda (ami-10cce555) on us-west-1b, I updated to the recent kernel. Now it won't boot. It seems initrd is fried. Anyway to get in to make it to boot from a previous kernel?
Or is this another argument for making more frequent snapshots?
BTW, this kernel worked with another instance in asia. Perhaps it's an aws issue in us-west?
sean
syslog:
[J Booting 'Fedora (3.11.2-201.fc19.x86_64) 19 (Schrödinger’s Cat)'
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-3.11.2-201.fc19.x86_64 ro root=UUID=e3577648-5703-459d-b55
7-b3947684f8ab serial=tty0 console=ttyS0,115200n8 console=hvc0 console=tty1 LAN
G=en_US.UTF-8
initrd /boot/initramfs-3.11.2-201.fc19.x86_64.img
block error -1 for op 0
Error 3: Bad or corrupt data while decompressing file
Press any key to continue...Xen Minimal OS! start_info: 0xac4000(VA) nr_pages: 0x26700 shared_inf: 0x8c534000(MA) pt_base: 0xac7000(VA) nr_pt_frames: 0x9 mfn_list: 0x990000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: root=/dev/sda1 ro 4 stack: 0x94f860-0x96f860 MM: Init _text: 0x0(VA) _etext: 0x5ff6d(VA) _erodata: 0x78000(VA) _edata: 0x80b00(VA) stack start: 0x94f860(VA) _end: 0x98fe68(VA) start_pfn: ad3 max_pfn: 26700 Mapping memory range 0xc00000 - 0x26700000 setting 0x0-0x78000 readonly skipped 0x1000 MM: Initialise page allocator for c01000(c01000)-26700000(26700000) MM: done Demand map pfns at 26701000-2026701000. Heap resides at 2026702000-4026702000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x26701000. Initialising scheduler Thread "Idle": pointer: 0x2026702010, stack: 0x26640000 Initialising xenbus Thread "xenstore": pointer: 0x20267027c0, stack: 0x26650000 Dummy main: start_info=0x96f960 Thread "main": pointer: 0x2026702f70, stack: 0x26660000 "main" "root=/dev/sda1" "ro" "4" vbd 2049 is hd0 ******************* BLKFRONT for device/vbd/2049 **********
backend at /local/domain/0/backend/vbd/544/2049 Failed to read /local/domain/0/backend/vbd/544/2049/feature-barrier. Failed to read /local/domain/0/backend/vbd/544/2049/feature-flush-cache. 4194304 sectors of 512 bytes ************************** Thread "kbdfront": pointer: 0x2026830010, stack: 0x26680000 ******************* FBFRONT for device/vfb/0 **********
******************* KBDFRONT for device/vkbd/0 **********
Failed to read device/vfb/0/backend-id. Failed to read device/vkbd/0/backend-id. Error ENOENT when reading the backend path device/vkbd/0/backend Thread "kbdfront" exited. Error ENOENT when reading the backend path device/vfb/0/backend