On 10/01/2013 03:08 PM, Matthew Miller wrote:
On Tue, Oct 01, 2013 at 01:56:01PM -0400, Sean Darcy wrote:
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?
So, here's what to do in ten actually-pretty-easy steps:
- Stop (but do not terminate) the broken instance,
- Launch a new temporary instance in the same zone. (Or use an existing one that's working.)
- Detach the root volume from the broken instance
- Attach it to the working instance as /dev/sdf (or whatever)
- In the working instance, mount the filesystem
- Find and fix the problem (possibly edit the /boot/grub/menu.lst?)
- Unmount the filesystem
- Detach from the working instance
- Reattach to the hopefully-fixed original instance
- Boot
As step four and a half, you may actually want to run fsck on the volume.
In general, you should store your data on a separate volume so that if this happens you just replace the machine and go on without worrying about it.
Finally got around to try to fix this. Did steps 1-4, using an F19 cloud image. But then:
fdisk -l /dev/xvdf
Disk /dev/xvdf: 2147 MB, 2147483648 bytes, 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x20ac7dda
This doesn't look like a partition table Probably you selected the wrong device.
Device Boot Start End Blocks Id System /dev/xvdf1 ? 3224498923 3657370039 216435558+ 7 HPFS/NTFS/exFAT /dev/xvdf2 ? 3272020941 5225480974 976730017 16 Hidden FAT16 /dev/xvdf3 ? 0 0 0 6f Unknown /dev/xvdf4 50200576 974536369 462167897 0 Empty
Partition table entries are not in disk order
fsck /dev/xvdf1 fsck from util-linux 2.23.2 e2fsck 1.42.7 (21-Jan-2013) fsck.ext2: No such file or directory while trying to open /dev/xvdf1 Possibly non-existent device?
mount /dev/xvdf1 /mnt/xvdf1 mount: special device /dev/xvdf1 does not exist
Really odd.
sean
fdisk /dev/xvdf Welcome to fdisk (util-linux 2.23.1).
Changes will remain in memory only, until you decide to write them. Be careful before using the write command.
Command (m for help): p
Disk /dev/xvdf: 2147 MB, 2147483648 bytes, 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x20ac7dda
This doesn't look like a partition table Probably you selected the wrong device.
Device Boot Start End Blocks Id System /dev/xvdf1 ? 3224498923 3657370039 216435558+ 7 HPFS/NTFS/exFAT /dev/xvdf2 ? 3272020941 5225480974 976730017 16 Hidden FAT16 /dev/xvdf3 ? 0 0 0 6f Unknown /dev/xvdf4 50200576 974536369 462167897 0 Empty
fsck /dev/xvdf1 fsck from util-linux 2.23.1 e2fsck 1.42.7 (21-Jan-2013) fsck.ext2: No such file or directory while trying to open /dev/xvdf1 Possibly non-existent device?
mount /dev/xvdf1 xvdf1 mount: special device /dev/xvdf1 does not exist