-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rescue USB/ISO doesn't boot. #261
Comments
I did a |
It looks like the kernel has problems while decompressing the initramfs on the USB. Could you try to unzip it manually and extract it with cpio? |
$ sudo zcat ~/Documents/ttemp/initrd.cgz | cpio -i |
I attempted this with 2048 MB of ram on a ubuntu VM |
The original ramdisk on your Ubuntu, what kind of compression/filesystem does it use ? (check with the Are there any kernel boot parameters set on the system that may be needed for booting this kernel/initrd ? |
nothing but the default ubuntu. no flags were added, |
@DrDrache I was expecting a CPIO archive or a filesystem...
|
@DrDrache does the same problem occur with rear-1.15? I'm not sure what we can do to help you with this? Or is it fine to close this issue? No response within 1 month means "yes" |
close the issue with "no feedback received" within 1 month - if needed you may re-open the call [ @DrDrache ] |
I'm looking into this more myself, but on 2 systems, both ubuntu 12.04.02 i686
One with the LTS enablement pack (fresh install) and one without
(so kernel 3.5.0-34 and kernel 3.2.0-xxx) when the Bootable image is made, then
attempted to boot from, on the same system, and other systems, you get attached screenshot (do not know how to log)
/etc/rear/local.conf are the same each time
USB :
OUTPUT=USB
BACKUP=NETFS
USB_DEVICE=/dev/sdb
BACKUP_URL=usb:///dev/disk/by-label/REAR-000
ISO:
OUTPUT=ISO
BACKUP=NETFS
BACKUP_URL=nfs:///Ip-addres/mnt/storage/rear/
BUT it works perfect with another system also 12.04.02 i686 with kernel 3.9.2, is there a workaround? (manually switch backup images?)
link to iso : http://www.sendspace.com/file/7fq4z1
The text was updated successfully, but these errors were encountered: