|
|
Sponsored Content
Operating Systems
Solaris
EFI disk labeling / understand the parition table / sectors not continue
Post 303028887 by javanoob on Thursday 17th of January 2019 11:59:59 AM
01-17-2019
|
|
8 More Discussions You Might Find Interesting
1. Solaris
First post :) ...
Here is a script for automatic labeling of previously unlabeled disks.
Other methods exist (format -f cmd_file), but I like this because it's all in one place.
#!/bin/ksh
#----------------------
# format_label
# Automatic labeling of previously unlabeled disks
#... (1 Reply)
Discussion started by: kwachtler
1 Replies
2. Filesystems, Disks and Memory
Is there a way to determine the number of available spare sectors on a disk ? as it may be useful for notifying a user to take a backup of the disk before it runs into a medium error. (6 Replies)
Discussion started by: rednex
6 Replies
3. Shell Programming and Scripting
Hello, I need advice on how to check if started processes are finished in perl, here's explanation :
OS is RHEL 4, perl -v = "This is perl, v5.8.0 built for i386-linux-thread-multi"
The logic of the script :
#!/usr/bin/perl
use warnings;
$param1 = $ARGV;
$param2 = $ARGV;
$param3 =... (2 Replies)
Discussion started by: sysgate
2 Replies
4. Filesystems, Disks and Memory
I found a document: Bad block HOWTO for smartmontools
My hard drive is Maxtor:
root]# fdisk -lu /dev/hda
Disk /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders, total 160086528 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x3f4e3f4d
... (0 Replies)
Discussion started by: justinian
0 Replies
5. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
6. Boot Loaders
i'm writing some code to simulate the boot progress after power on
but when i try to read the 2nd sector from a floppy disk, this operation always fail with ah=0x80h which means timeout, how can i get over this problem?
my code would be like this:
$ cat boot.S
.code16
#define SETUPLEN 4... (0 Replies)
Discussion started by: wljackhero
0 Replies
7. Linux
i'm writing some code to simulate the boot progress after power on
but when i try to read the 2nd sector from a floppy disk, this operation always fail with ah=0x80h which means timeout, how can i get over this problem?
my code would be like this:
$ cat boot.S
.code16
#define SETUPLEN 4... (0 Replies)
Discussion started by: wljackhero
0 Replies
8. UNIX for Advanced & Expert Users
i'm writing some code to simulate the boot progress after power on
but when i try to read the 2nd sector from a floppy disk, this operation always fail with ah=0x80h which means timeout, how can i get over this problem?
my code would be like this:
$ cat boot.S
.code16
#define SETUPLEN 4... (0 Replies)
Discussion started by: wljackhero
0 Replies
LEARN ABOUT FREEBSD
uefi
UEFI(8) BSD System Manager's Manual UEFI(8) NAME
UEFI -- Unified Extensible Firmware Interface bootstrapping procedures DESCRIPTION
The UEFI Unified Extensible Firmware Interface provides boot- and run-time services to operating systems. UEFI is a replacement for the legacy BIOS on the i386 and amd64 CPU architectures, and is also used on arm64 and ia64. The UEFI boot process loads system bootstrap code located in an EFI System Partition (ESP). The ESP is a GPT or MBR partition with a spe- cific identifier that contains an msdosfs(5) FAT file system with a specified file hierarchy. Partition Scheme ESP Identifier GPT C12A7328-F81F-11D2-BA4B-00A0C93EC93B MBR 0xEF The UEFI boot process proceeds as follows: 1. UEFI firmware runs at power up and searches for an OS loader in the EFI system partition. The path to the loader may be set by an EFI environment variable. If not set, the default is /EFI/BOOT/BOOTX64.EFI. The default UEFI boot configuration for FreeBSD installs boot1.efi as /EFI/BOOT/BOOTX64.EFI. 2. boot1.efi locates the first partition with the type freebsd-ufs, and from it loads loader.efi. 3. loader.efi loads and boots the kernel, as described in loader(8). The vt(4) system console is automatically selected when booting via UEFI. FILES
/boot/boot1.efi First stage UEFI bootstrap /boot/boot1.efifat msdosfs(5) FAT file system image containing boot1.efi for use by bsdinstall(8) and the bootcode argument to gpart(8). /boot/loader.efi Final stage bootstrap /boot/kernel/kernel default kernel /boot/kernel.old/kernel typical non-default kernel (optional) SEE ALSO
vt(4), msdosfs(5), boot(8), gpart(8) HISTORY
UEFI boot support first appeared in FreeBSD 10.1. AUTHORS
UEFI boot support was developed by Benno Rice <benno@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, and Nathan Whitehorn <nwhitehorn@FreeBSD.org>. The FreeBSD Foundation sponsored portions of the work. CAVEATS
EFI environment variables are not supported by loader(8) or the kernel. boot1.efi loads loader.efi from the first FreeBSD-UFS file system it locates, even if it is on a different disk. boot1.efi cannot load loader.efi from a ZFS(8) file system. As a result, UEFI does not support a typical root file system on ZFS configura- tion. BSD
October 17, 2014 BSD