Sponsored Content
Operating Systems Solaris EFI disk labeling / understand the parition table / sectors not continue Post 303029046 by javanoob on Sunday 20th of January 2019 12:41:43 AM
Old 01-20-2019
Quote:
Originally Posted by jlliagre
As long as there are no overlapping areas, that doesn't matter.

If your SSD is a $500k house, these gaps sum up to less than two tenth of a cent...
Hahaha jlliagre, nice analogy..
Thank for your reply. I am just wondering why are these sectors distributed in such way and how they sums up.

Last question i hope you don't mind, since these are 4k disks, is there any reason why ZFS are aligning them with start sector 256 ? instead of the default 40 ?

Code:
40 = 40 * 512 = 20480bytes 
20480bytes/4096=5 x 4k sector  - which is in multiples of 4k and should be fine.

Regards,
Noob
 

8 More Discussions You Might Find Interesting

1. Solaris

Automatic disk labeling

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

SCSI disk spare sectors

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

perl - understand process status and continue the code execution

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

Smartmontools and fixing Unreadable Disk Sectors

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

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

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

read sectors from disk failed with timeout

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

read sectors from disk failed with timeout

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

read sectors from disk failed with timeout

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
efi(4)							     Kernel Interfaces Manual							    efi(4)

NAME
efi - Extensible Firmware Interface description DESCRIPTION
The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium-based platform firmware. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12 or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform. For a hard disk, the system partition is a contiguous grouping of sectors on the disk, where the starting sector and size are defined by the EFI partition table, which resides on the second logical block of the hard disk, and/or by the Master Boot Record (MBR), which resides on the first sector of the hard disk. For a floppy disk, a partition is defined to be the entire disk. The System Partition can contain directories, data files, and EFI Images. The EFI system firmware may search the directory of the EFI sys- tem partition, EFI volume, to find possible EFI Images that can be loaded. The HP-UX bootloader is one example of an EFI Image. HP-UX contains a set of EFI utilities: efi_fsinit(1M) Initialize an EFI volume; that is, create a header and an empty directory. efi_cp(1M) Copy files to and from an EFI volume. efi_mkdir(1M) Create directories in an EFI volume. efi_ls(1M) List the contents of an EFI volume. efi_rm(1M) Remove files from an EFI volume. efi_rmdir(1M) Remove directories from an EFI volume. The EFI utilities are the only utilities in HP-UX where the internal structure of an EFI volume is known. To the rest of HP-UX, an EFI system partition is simply a partition containing unspecified data. The EFI volume cannot be mounted to HP-UX currently. An EFI volume can be created on any HP-UX file (either regular disk file or device special file) that supports random access via lseek(2). Within an EFI volume, individual files and directories are identified by 1- to 255-character file names. File names can consist of any alphanumeric characters (A through Z, a through z, and 0 through 9) and the certain set of special characters (. $ % ' - _ @ ~ ` ! ( ) + , : ; = # & ? ^ [ ] { } space). The first character of an EFI file name can be any valid EFI characters, except the space. When comparing two EFI names, differences in the case of alphabetic characters are not significant. For example, the following file names are considered the same: If one exists, the user will not be able to create the other. The directory may be made up of multiple components, separated by slashes(/). The last directory component must be followed by a slash to separate it from the file name. There are two special directory components, (.) and (..). They represent the current directory and the parent directory as in other file systems. SEE ALSO
efi_cp(1M), efi_fsinit(1M), efi_ls(1M), efi_mkdir(1M), efi_rm(1M), efi_rmdir(1M). Itanium(R)-Based Processor Family Only efi(4)
All times are GMT -4. The time now is 09:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy