Sponsored Content
Full Discussion: Hard Drives and MBR
Special Forums Hardware Hard Drives and MBR Post 302816863 by hicksd8 on Tuesday 4th of June 2013 05:28:02 PM
Old 06-04-2013
The MBR (Master Boot Record) resides on the first sector of the disk and is where control is passed to by the machine BIOS.

The MBR will be different from operating system to operating system, and each operating system will have a way of writing its own MBR.

For example, in Windows

Code:
 
fdisk /mbr

(google that for syntax) will write an MBR and on Solaris the

Code:
 
installboot

command will write an MBR.

If an MBR exists at all when the disk comes from the factory, that will just be from the manufacturing test process and probably won't be what you need for your O/S. When the O/S install routine runs it will install its MBR.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hard drives

Will some one tell me what this means. "warning: ida 0 <slot 6> : command timed out on dev 1/42 blk 4824290 logical unit=0 blocks=5512102, size 2, cmd=0x20." I'm running SCO 505 on a proliant 1600r. Thnank you in advance. (3 Replies)
Discussion started by: franruiz
3 Replies

2. Filesystems, Disks and Memory

automatic copying files from external hard drives

I need to make it possible to automatically copy files from an external usb hard drive to a directory when i plug it in....if you can point me in the right direction, i would be very grateful....thanks a lot. :confused: (0 Replies)
Discussion started by: backman4sakn
0 Replies

3. Linux

No Hard Drives Have Been Found

I am using an Acer Aspire 4720Z with two partitions C and D. Windows is installed on C and I decided to install Red Hat Linux 9 in partition D. The two partitions are in NTFS file system. During my installation of the the Linux, a prompt was displayed on screen with the message: "No hard drives... (2 Replies)
Discussion started by: tamcomng
2 Replies

4. Solaris

formating and repartitioning an external hard drives

Version: solaris 10 x86 I just got a western digital external harddrive formated with fat 32. this drive came with some setup files which is meant for windows or mac. I want to reformat and partition this drive into two ( for solaris and windows) such that the setup files will still be there... (2 Replies)
Discussion started by: seyiisq
2 Replies

5. Filesystems, Disks and Memory

Help adding new hard drives

Folks; I just added 2 physical new hard drives to my SUSE server. My server is already running SUSE 10.3 version. Is there a command i can use to add the new space or even see if the system can sees them? (3 Replies)
Discussion started by: Katkota
3 Replies

6. UNIX for Dummies Questions & Answers

Set internal hard drives unaccessible to imager

Looking for some clues on how to set my internal hard drives inaccessible/busy to clonezilla. Noprobe doesn't work in startup and the drive is still found. I know I can find all hard drives using the following: sudo fdisk -l | grep GB | awk '{print $2}' | grep -Po "^+(?=:?)" I tried... (9 Replies)
Discussion started by: traustic
9 Replies

7. Solaris

Reinstall old hard drives

I have a T2000 Sun-Fire server. I have 2 sets of drives in a raid 1. Lets call them Set A and Set B. I had Set A installed and working. I needed a new install so I so build up Set B. After some time I wanted to put Set A back in the server. Now the system will not boot off of Set A. I tried to boot... (7 Replies)
Discussion started by: stu1811
7 Replies

8. Solaris

Trying to boot Solaris without hard drives in T5220

I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode. I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management. Tinkering around I... (4 Replies)
Discussion started by: nerdboy
4 Replies

9. Solaris

Solaris 8 - Accessing Hard Drives

Hi, I have two SCSI Hard Drives in a Sun Solaris 8 server as shown below. I would like to access Disk1 and look at its contents, directory structure and files. How do I change my default directory from Disk 0 to Disk 1 and vice versa? Thank you. (5 Replies)
Discussion started by: ssabet
5 Replies

10. UNIX for Beginners Questions & Answers

Understanding volumes and hard drives

Ok so i thought i was smart but i can tell I need some help. I am playing around with understanding lvm and adding disks to a linux box. I added a disk and then ran what i thought were commands to add this disk to the box but I think I messed up and would like some help. My question is did i... (5 Replies)
Discussion started by: cptkirkh
5 Replies
Makebootfat Bootable FAT Disk Creation(1)		      General Commands Manual			 Makebootfat Bootable FAT Disk Creation(1)

NAME
makebootfat - Makebootfat Bootable FAT Disk Creation SYNOPSIS
makebootfat [options] IMAGE DESCRIPTION
This utility creates a bootable FAT filesystem and populates it with files and boot tools. It is mainly designed to create bootable USB and Fixed disk for the AdvanceCD project. The official site of AdvanceCD and makebootfat is: http://advancemame.sourceforge.net/ OPTIONS
-o, --output DEVICE Specify the output device. It must be the device where you want to setup the filesystem. You can use the special "usb" value to automatically select the USB Mass Storage device connected at the system. This option is always required. -b, --boot FILE -1, --boot-fat12 FILE -2, --boot-fat16 FILE -3, --boot-fat32 FILE Specify the FAT boot sector images to use. The -b option uses the same sector for all the FAT types. The other options can be used to specify a different sector for different FAT types. The FAT types for which a boot sector is not specified are not used. This option is always required. -m, --mbr FILE Specify the MBR sector image to use. If this option is specified a partition table is created on the disk. Otherwise the disk is filled without a partition table like a floppy disk. -F, --mbrfat Change the MBR image specified with the -m option to pretend to be a FAT filesystem starting from the first sector of the disk. This allows booting from USB-FDD (Floppy Disk Drive) also using a partition table generally required by USB-HDD (Hard Disk Drive). The MBR image specified with the -m option must have executable code positioned like a FAT boot sector. You can use the included 'mbr- fat.bin' file. -c, --copy FILE Copy the specified file in the root directory of the disk. The file is copied using the readonly attribute. -x, --exclude FILE Exclude the specified files and subdirectories in the IMAGE directory to copy. The path must be specified using the same format used in the IMAGE directory specification. -X, --syslinux2 Enforce the syslinux 2.xx FAT limitations. Syslinux 2.xx doesn't support FAT32 at all, and FAT16 with 64 and 128 sectors per cluster formats. This option excludes all the FAT formats not supported by syslinux. Please note that it limits the maximum size of filesystem to 1 GB. -Y, --syslinux3 Enforce the syslinux 3.xx FAT support. Syslinux 3.00 supports all the FAT types and sizes but it requires a special customisation of the boot sector and of the file 'ldlinux.sys'. This option does this customisation without the need to use the syslinux installer if the 'ldlinux.sys' file is copied on disk with the -c option. -Z, --zip If possible force the ZIP-Disk compatibility. It sets a geometry of 32 sectors and 64 heads. It also uses the 4'th partition entry in the partition table. It's required to boot also in USB-ZIP mode. -P, --partition Ensure to operate on a partition and not on a disk. -D, --disk Ensure to operate on a disk and not on a partition. -L, --label LABEL Set the FAT label. The label is a string of 11 chars. -O, --oem OEM Set the FAT OEM name. The OEM name is a string of 11 chars. -S, --serial SERIAL Set the FAT serial number. The serial number is a 32 bit unsigned integer. -E, --drive DRIVE Set the BIOS drive to setup in the FAT boot sector. Generally this value is ignored by boot sectors, with the exception of the FAT12 and FAT16 FreeDOS boot sectors that require the correct value or the value 255 to force auto detection. -v, --verbose Print some information on the device and on the filesystem created. -i, --interactive Show the errors in a message box. Only for Windows. -h, --help Print a short help. -V, --version Print the version number. IMAGE Directory image to copy on the disk. All the files and subdirectories present in this directory are copied on the disk. DISKS AND PARTITIONS NAMES
In Linux disk devices are named /dev/hdX or /dev/sdX where X is a letter. Partition devices are named /dev/hdXN or /dev/sdXN where X is a letter and N a digit. In Windows disk devices are named \.PhysicalDriveN where N is a digit. Partition devices are named \.X: where X is a letter, but some- times \.X: is a disk and not a partition, for example on floppies and on all the USB Mass Storage devices without a partition table. SYSLINUX
To make a bootable FAT using syslinux you must use the -X option for syslinux version 2.xx or the -Y option for syslinux version 3.xx. You must also copy in the root directory of the disk the files: ldlinux.sys The syslinux loader. syslinux.cfg The syslinux configuration file. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the 'ldlinux.bss' boot sector with the -b option and possibily the 'mbr.bin' MBR sector with the -m option. Both the sector images are present in the syslinux package. For example: makebootfat -o usb -Y -b ldlinux.bss -m mbr.bin -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image LOADLIN AND FREEDOS
To make a bootable FAT using loadlin and FreeDOS you must copy in the root directory of the disk the files: kernel.sys The FreeDOS kernel. Remember to use the "32" kernel version to support FAT32. command.com The FreeDOS shell. autoexec.bat Used to start loadlin. loadlin.exe The loadlin executable. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the FreeDOS boot sectors available on the FreeDOS 'sys' source package with the -1, -2, -3 option. For the MBR you can use the sectors image available on the FreeDOS 'fdisk' source package. For example: makebootfat -o /dev/hda1 -E 255 -1 fat12com.bin -2 fat16com.bin -3 fat32lba.bin -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image MULTI STANDARD USB BOOTING
The BIOS USB boot support is generally differentiated in three categories: USB-HDD, USB-FDD and USB-ZIP. The USB-HDD (Hard Disk Drive) standard is the preferred choice and it requires the presence of a partition table in the first sector of the disk. You can create this type of disk using the -m option. The USB-FDD (Floppy Disk Drive) standard requires the presence of a filesystem starting from the first sector of the disk without a parti- tion table. You can create this type of disk without using the -m option. The USB-ZIP (ZIP Drive) standard requires the presence of a device with a very specific geometry. Specifically, it requires a geometry with 32 sectors and 64 heads. It also requires the presence of a partition table with only a bootable partition in the fourth entry. You can create this type of disk using the -m and -Z option. Generally these standards are incompatible, but using the -m, -F and -Z options you can create a disk compatible with all of them. To use the -F option, the MBR image specified must follow the constrains: o It must start with a standard FAT 3 bytes jump instruction. o It must have the bytes from address 3 to 89 (included) unused. And example of such image is in the 'mbrfat.bin' file. For example to create a syslinux image: makebootfat -o usb -Y -Z -b ldlinux.bss -m mbrfat.bin -F -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image and for a FreeDOS and loadlin image: makebootfat -o usb -E 255 -Z -1 fat12com.bin -2 fat16com.bin -3 fat32chs.bin -m mbrfat.bin -F -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image Please note that FreeDos has some problems booting from USB. It works only on very few conditions. EXCLUSION
To exclude some files or directories in the image copy, you can use the -x option using the same path specification which are you using for the image directory. For example, if you need to exclude the 'isolinux' and 'syslinux' subdirectories from the 'image' directory you can use the command: makebootfat ... -x image/isolinux -x image/syslinux image COPYRIGHT
This file is Copyright (C) 2004, 2005 Andrea Mazzoleni SEE ALSO
syslinux(1), mkdosfs(1), dosfsck(1) Makebootfat Bootable FAT Disk Creation(1)
All times are GMT -4. The time now is 08:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy