|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells
|Recommended Links||Installation of Red Hat from a USB drive||Setting up the Installation Server||autoyast|
For a successful install, you should have:
You can also use
and look for a device that matches your USB drive. Then check the partition as root type via:
or, if you know the disk
fdisk -l /dev/<disk>
The output should have line like
/dev/sdb1 * 1 3924 1004528 c W95 FAT32 (LBA)
Here "FAT32" indicates the filesystem. If you see a star (as in the example above), then this means that the bootable flag is set.
(<disk> is the disk name, e.g. "sdb". It's not the partion name as "sdb1"). Then press "a", and enter the partition number (e.g. 1, if the partition is sdb1). Save the changes with "w". If the automount prevents the changes from being saved, you can temporarily disable automount using "rcdbus stop" as root.
Then press "t" (to change the partition type) and "c" (for FAT32). Save the changes with "w".
umount /dev/<partition> mkfs.vfat -F 32 /dev/<partition>
(Here <partition> is the partition, for example "sdb1").
If this fails, fix the filesystem with
fsck.vfat -a /dev/<partition>
mkdir /mnt/dvd mkdir /mnt/usb
mount dvd.iso /mnt/dvd -o loop
Also mount the USB drive:
mount /dev/sdb1 /mnt/usb
cp -R -L /mnt/dvd/* /mnt/usb/
Make sure the script is executable:
chmod +x mksusebootdisk
syslinux if it isn't already:
zypper install syslinux
Run the script with arch set to 32 for i386, or 64 for x86_64. This should work for any architecture e.g. ppc, IA64.
./mksusebootdisk --arch --partition /dev/<partition> /mnt/dvd
This command works reasonably fast. It will fail if you forgot to unmount (using umount) the USB disk. It will also fail (and give a "not a FAT file system" error if you press crtl-c) if the drive has errors. To fix the errors, use
fsck.vfat -w -r /dev/<partition>
During setup, the install media will not be automatically found. The setup will fall back to text-mode setup where you can choose the install media location.
Your media should be in Local hard drive and USB drive should be /dev/sda1 or similar. The setup will ask for the ISO file location on the selected drive. Type in the file path and name. Initial / is required, so if your image is at the root of the drive and has name of dvd.iso, you need to type: /dvd.iso
Why cannot I just use the mkbootdisk shipped with SuSE Linux
The PC won't boot from USB drive
If no matter what you try, the machine does not boot from the USB drive:
Support How to create a bootable USB drive to install SLESSuSE Linux Enterprise Server 10 (SLES 10)
SituationThis explains how to create a bootable USB stick to install SLES 10 from for situations where a CD-ROM drive may not be available in the server. It assumes the machine BIOS allows booting from a USB device.
ResolutionIt is first necessary to download CD1 or a mini.iso of SLES 10. The proceedure can then be completed in either Windows or Linux.
Creating a bootable USB device from Windows
- Extract the contents of the .iso file to a temporary directory like C:\isotemp (A utility such as WinRAR can be used for this)
- Assuming the USB device is E: copy the contents of C:\isotemp\boot\i386\loader\* to E:\
Note: replace i386 with x86_64 if it is 64 bit
- Delete E:\isolinux.bin
- Rename E:\isolinux.cfg to E:\syslinux.cfg
- Download syslinux and extract it to C:\syslinux (Note: this must be downloaded separately from the Internet)
- Open a command prompt and change to C:\syslinux\syslinux
- Run syslinux E:
Creating a bootable USB device from Linux
This example will use /dev/sdb as the USB device.
Create a FAT16 partition on the USB device:
(/dev/sdb1 must be a primary partition no more than 4GB in size)
mkfs.vfat -F 16 /dev/sdb1
mount -o loop SLES-10-i386-GM-CD1.iso /mnt
/mnt/boot/i386/mkbootdisk --32 --partition /dev/sdb1 /mnt
mount -o loop SLES-10-x86_64-GM-CD1.iso /mnt
/mnt/boot/x86_64/mkbootdisk --64 --partition /dev/sdb1 /mnt
The USB device can then be booted from. For a network installation, select the default 'linux' option and enter options for a custom installation server:
Additional InformationQuite often it is required to set the boot device order each time the USB device is connected. It must be placed before the hard drives in the system.
This application can also be used for SuSE Linux Enterprise Server 9 (SLES 9), however, SLES 9 does not include the mkbootdisk utility so it must be downloaded separately or taken from SLES 10.
Must be 16 bit FAT
If the mkbootdisk script fails with the error: "must be 16 bit FAT", the cause is that the FAT partition is not using a 16-bit file allocation type. You can confirm this using the command:
fsck.vfat -v /dev/sdb1
and looking for the line:
2 FATs, 32 bit entries
This must read "16 bit entries" for the script to succeed. You must recreate the filesystem using mkfs.vfat to modify this.
WARNING: Not enough clusters for a 16 bit FAT!
When attempting to execute the mkfs.vfat command it may fail with the following error:
WARNING: Not enough clusters for a 16 bit FAT!The filesystem will be misinterpreted as having a 12 bit FAT without mount option "fat=16".
mkfs.vfat: Attempting to create a too large file system
This is caused by attempting to create a 16-bit file allocation table size on a partition larger than 4GB. Verify a partition smaller than 4G has been created on the USB device.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3499891
- Creation Date:03-14-2007
- Modified Date:07-26-2012
- SUSESUSE Linux Enterprise Server
The C:\ drive on my laptop is reserved entirely for XP. I made three partitions on my USB External Drive. I want to put SUSE into the first partition. I plan to follow the advice of an excellent tutorial by Simon Parsons
"Understanding the Boot Process and NTLDR" 03/04/2002 on devhood.com/tutorials. Now I have several questions about the SUSE install process:
First, I do not want to put a new bootloader into the mbr. Instead, I want to tell SUSE to put the initial GRUB bootloader at the beginning of the first sector of the partition that I allocate for SUSE. How do I tell the SUSE install process to do that? Second, I want to understand why the SUSE install process is in two steps. Why does a reboot take place between steps 1 and 2? Is the part after the second reboot just doing additional package installation? I need to know this because BEFORE a reboot I need to set up the Windows Bootloader(NTLDR) to access the SUSE partition.
Thanks for taking the time to read this, whether or not you can contribute to an answer. And check out the referenced tutorial. It is a short, easy read and very clear in its approach.
Hi. I have a Suse 11.0 64 BITS installed on a USB connected IDE drive. (I have a Compaq V2321US Turion machine), as you, I have the internal drive with the WXP that came with it for support issues. It doesn't have USB boot, but I can boot it up with the installation DVD (yes it's boring to put it on the tray everytime I boot Linux) but I haven't found any suitable solution. I installed grub on the boot sector of the USB drive (/dev/sda) so, when it is not plugged in, the laptop goes directly to the wxp boot), when it is plugged in, the dvd finds the usb drive and I can boot. Regards.
Howard3005, if you have the dvd in the drive while the install is going, it will go back to the install after the reboot. Now for putting the bootloader to the 1st sector rather than MBR, when the SUSE install loads up (and assuming the install for 10 is similar to 9.3) there is a heading called bootloader, under here you can choose where the bootloader is installed.
tutankamon, if you use ntldr as your bootloader, you can have it boot into SUSE without the use of the SUSE install media. It will act the same as grub/lilo, and when you want to boot SUSE, just select it from the ntldr list. The tutorial that Howard3005 is using, talks about setting this up link
Life is complex, it has a real part and an imaginary part.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: October, 03, 2017