How To Start Legacy-OS-2 From USB? Which Boot Codes In Syslinux?

Ubuntu 12.04

I installed updates, which included a new kernel. I went to remove one of the older kernels and got:

Code:

jnojr@DEV:~$ sudo apt-get purge linux-image-3.13.0-46-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-46-generic gir1.2-ubuntuoneui-3.0 wireless-regdb iw
  linux-headers-3.13.0-46 crda linux-headers-3.5.0-23-generic lesstif2
  linux-headers-3.5.0-23 libubuntuoneui-3.0-1 thunderbird-globalmenu
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  linux-image-3.13.0-46-generic*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 197 MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 340656 files and directories currently installed.)
Removing linux-image-3.13.0-46-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
update-initramfs: Deleting /boot/initrd.img-3.13.0-46-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found Windows Vista (loader) on /dev/sda1
Found CentOS release 6.6 (Final) on /dev/sdb1
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found Windows Vista (loader) on /dev/sda1
Found CentOS release 6.6 (Final) on /dev/sdb1
Found memtest86+ image: /boot/memtest86+.bin
error: syntax error.
error: Incorrect command.
error: syntax error.
error: Incorrect command.
error: syntax error.
error: line no: 146
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
done
Purging configuration files for linux-image-3.13.0-46-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic

I have no idea how I'd "ensure there are no errors" in the /etc/grub related files... I have no idea what's supposed to be there. Looking at the line it's complaining about in /boot/grub/grub.cfg.new doesn't tell me anything. How do i find out what it's unhappy about?

Hello

I have installed a CentOS 6.4 on VmWare.

Now, after several days of using it, it suddenly does not boots. There is a problem with its initialization, here is the error:

Kernel Panic : Unalble to init. Try passing init= option to the kernel.
Pid 1 : Swapper not tainted.

I have used CentOS.iso to rescue it, but it still does not solve it.

My grub.conf contains:

PHP Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/sda2
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-358.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=UUID=6082bcf5-00ba-4bf8-86ea-9821d774cb6f rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
 initrd /initramfs-2.6.32-358.el6.x86_64.img 



How should I solve it then? Thanks in advance

Hello,

for the reason my PC hangs a long time at the boot line
initrd /boot/initrd.img-3.7.10-antix.7-486-smp
I decided to uopdate it with
update-initramfs -u
but the error
"cryptsetup: WARNING: failed to detect canonical device of /dev/sda2" appear.

I have few questions now:
- how to create a quick initrd
- how to avoid that error?

Your help will be much appreciated.

On my Antix13 (similar Debian Wheezy), I have installed bootchart2 and pybootchartgui.
I have created entries in /boot/grub/menu.lst (see below),
but there are no /var/log/bootchart.tgz as per https://www.debian-administration.or...with_bootchart or http://forums.debian.net/viewtopic.php?f=16&t=38869
What should I do? I made perhaps something wrong.



Code:

timeout 5
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title  antiX at sda2, kernel 3.7.10-antix.7-486-smp
root   (hd0,1)
kernel /boot/vmlinuz-3.7.10-antix.7-486-smp root=/dev/sda2 quiet nomodeset radeon.modeset=0
initrd /boot/initrd.img-3.7.10-antix.7-486-smp

# added
title  antiX at sda2, kernel 3.7.10-antix.7-486-smp bootchart
root   (hd0,1)
kernel /boot/vmlinuz-3.7.10-antix.7-486-smp root=/dev/sda2 ro init=/sbin/bootchartd radeon.modeset=0
#

boot
...

Hi, I'm pretty new to Linux.

I'm currently working on a project in my Linux Administration class, but have run into a bit of a bump.

I'm tasked with booting Linux (currently using CentOS 7) through the GRUB prompt. I've loaded the kernel, but I'm having an issue with the initrd.

I've tried both of these commands:
"linux /boot/initrd-plymouth.img"
"linux /boot/initramfs-3.10.0-123.el7.x86_64.img"

Neither of these commands have worked. It only returns the message "invalid magic number" for both of the commands. Any ideas on how I can fix this?

Thanks for any help in advance. It should help me understand Linux better!

When working with a virtual terminal, I find it often easier to edit a file to execute than to construct a regular-expression etc. to inject the right UUID etc. into the command. I have run into an error while doing this. I suspect it is stems from quote mishandling, or improper escape sequences. (I ran directly from the command line earlier, forgot a quotation mark, and it gave a similar bad result.)
The program in question was efibootmgr. I had a file vaguely similar to this one, named efiboot.Hz:
Code:

efibootmgr -c -g -L "Debian (EFI stub)" -l '\EFI\debian\vmlinuz' -u 'root=UUID=$UUID ro quiet rootfstype=ext4 add_efi_memmap initrd=\\EFI\\debian\\initrd.img'
efibootmgr -c -d /dev/sdb -L "Debian Linux" -l '\EFI\debian\vmlinuz' -u 'root=UUID=1234-ffff-789 ro quiet rootfstype=ext4 add_efi_memmap initrd=\\EFI\\debian\\initrd.img'

Then I executed:
Code:

`tail -n 1 efiboot.Hz`

efibootmgr -v revealed the previous command produced a garbled name and boot options, and most importantly it didn't boot. Manually writing the last line on the terminal did produce the desired effect. I thought I checked the output from tail before putting the back-ticks.
What did I do wrong?

Hello,

I am new to Linux images (pxe, livecd). I would like to add files to a linux image, like something under etc or var, and have the files be available on the client.
The server I am working on was already configured with a pxe image, and only 2 files are present under the pxe client folder: initrd and vmlinuz. So I am wondering if either of these files contain the dirs /etc, /var, etc..., and how I could add files to them.

To give some background, I have done the same thing in Windows. An image in Windows is typically either boot.img or install.img. You can mount either of these to a folder using the Windows SDK tool imagex.exe /mountrw <img file> 1 <mount point>. From here you can add/remove/modify any files you want. Then commit the changes with imagex.exe /unmount <mountpoint> /commit.

Can someone provide insight to the linux image creation process, which of the files (initrd, vmlinuz/vmlinux, etc...) contain what for the client boot, or something similar to the Windows Image editing process?

I know I'm asking for a range of info, but pointers to any material to help my understanding will be greatly appreciated.

Thanks,
Jon

Hello all,
I'm having an issue booting my linux installation after installing refind. I googled the issue but nothing seems relevant to fixing it.
Refind starts up fine and I can see linux (vmlinuz...) but when I select it to boot it says

Failed to open file: install\initrd.gz
Trying to load files to higher address
Failed to open file: install\initrd.gz

It is a dual boot system with Win8. It is an encrypted installation if that makes any difference. Both systems are efi.
How might i go about fixing this? Any pointers and/or relevant threads appreciated

Hi guys,

I'm new to this forum and linux too.
I thought of installing a lightweight distro of linux and did some research on the net where I found people recommending Puppy Linux. Plus it is (theoretically speaking) possible to run it from a USB (flash) drive which I decided to try out but it seems like it's not that simple a task as a lot of people (all over the internet) say it is.

What I tried so far is this: installing it into a thumb drive using unetbootin follwing a youtube tutorial (which basically showed how to download an iso of puppy, use unetbootin to make the thumbdrive bootable and install puppy on it). It didn't work. The USB wasn't recognized as a bootable device. I know for sure it can be booted from it since I tried ubuntu from the same USB and the same Laptop (which is able to boot from USB).

I thought that something with the Flash Drive not OK so I tried to use a windows installer to install puppy like other windows programms but this didn't work either. This time Puppy was recognized because there was an option to boot either Puppy or Windows 7 but when I chose to boot from Puppy nothing happens just a screen flash, some letters in the top left corner saying something like NTSC or NTSF (I can't read it properly because it goes away too fast) then after the screen flash the whole thing again (boot from win 7 or Puppy I choose Puppy again the flash... basically a loop).

Any ideas what I'm doing wron or what the problem is?

Thank You for any replies.

Hi,

Just downloaded the "systemrescuecd-x86-4.5.2". I then mounted it, created a bootable USB stick. I then copied the source to it. I also copied the source to my PXE server. However, all though the program works brilliantly when booting it from USB, I cannot get it to load completely via the PXE method - basically via PXE boot, I do not see the selection menu.

I hope somebody with more experience can shed some light on this matter, as Linux is not one of my strong points.

The following is my PXE servers config:
LABEL rescue32_3
MENU LABEL ^System Rescue CD 32 bit
KERNEL sysresccd/isolinux/rescue32
APPEND initrd=/sysresccd/isolinux/initram.igz,/sysresccd/sysrcd.dat


Using the above config, PXE Linux appears to find and load the following on the client:
Loading sysresccd/isolinux/rescue32... ok
Loading sysresccd/isolinux/initram.igz... ok
Loading sysresccd/sysrcd.dat... ok

The first sign of the issue during PXE boot is when the program starts to load from RAM on the client:
Reading all physical volumes. This may take a while...
Searching for /sysrcd.dat on devices...
Attempting to mount device: /dev/sda...

Various other attempts to mount volumes and then:
!Cannot find device with /sysrcd.dat. Retrying...

This issue then propagates for other volumes and then displays:
!Cannot find device with /sysrcd.dat on devices.
Running a mini shell (cannot complete the boot process)
bin/sh: can't access tty: job control turned off


Any help would be very much appreciated, as it would be a shame not to be able to use this fantastic resource via PXE.


Kind regards,
proliant800