search for: startsector

List, Happy NY. >From the bash command below, I'm trying to parse out the startsector value: $ sudo file mini_vusb.img mini_vusb.img: x86 boot sector, Microsoft Windows XP MBR, Serial 0x25d84; partition 1: ID=0xe, active, starthead 1, startsector 32, 390496 sectors First try was with grep/egrep but I wanted to capture 'startsector 32' as a group (). Nothing came close to wo...

...ile of 4GB. We want to use this image file as a template for creating Xen guests which their disk will be an LVM device. The disk image file is of type: file /var/lib/xen/images/rhel52.img /var/lib/xen/images/rhel52.img: x86 boot sector; partition 1: ID=0x83, active, starthead 1, startsector 63, 9221247 sectors; partition 2: ID=0x83, starthead 0, startsector 9221310, 19438650 sectors, code offset 0x48 By dd/cat this image file to an empty LVM device cat /var/lib/xen/images/rhel52.img > /dev/VolGroup00/rhel52 and by using this configuration file name = "r...

Hello , everyone I am a newcomer to xen , which i study in recent months . I have deploy the xen-4.1.2 on dell server , centos as dom0 , now , i use the vhd format to be the virtual hard disk , after i execute " xm new ***.cfg" , this vm generate the vm in "xm list" , but when i execute " xm start *** ", "Error: Boot loader didn''t return any data

...ub-install it outputs: "The file /boot/grub/stage1 not read correctly" (I've tried --recheck option, and depmod and update-grub commands with no success) Output of file command on virtual disk file is: /virtuales/videodisk.img: x86 boot sector; partition 1: ID=0x82, starthead 1, startsector 63, 4273227 sectors; partition 2: ID=0x83, active, starthead 0, startsector 4273290, 77626080 sectors The DomU file is: DomU (file): name = "video" uuid = "54d25d78-b9d0-0159-542c-bb601cc936bb" maxmem = 1024 memory = 512 vcpus = 1 builder = "hvm" kernel = "/usr...

...images. Type: 'help' for help on commands 'man' to read the manual 'quit' to quit the shell ><fs> run ><fs> list-filesystems ><fs> list-partitions /dev/sda1 ><fs> file /dev/sda1 ; partition 4: ID=0xa5, active, starthead 0, startsector 0, 50000 sectors ><fs> vfs-type /dev/sda1 zfs_member I tried opening it with virt-rescue, but for some reason the zfs-fuse daemon would not start, and hence other commands such as zpool didn't work. I opened a bug to look at enabling ZFS: https://bugzilla.redhat.com/show_bug.cgi?id...

I installed Centos 6.x 64 bit with the minimal ISO and used two disks in RAID 1 array. Filesystem Size Used Avail Use% Mounted on /dev/md2 97G 918M 91G 1% / tmpfs 16G 0 16G 0% /dev/shm /dev/md1 485M 54M 407M 12% /boot /dev/md3 3.4T 198M 3.2T 1% /vz Personalities : [raid1] md1 : active raid1 sda1[0] sdb1[1] 511936 blocks super 1.0

...stall it outputs: "The file /boot/grub/stage1 not read correctly" (I''ve tried --recheck option, and depmod and update-grub commands with no success) Output of file command on virtual disk file is: /virtuales/videodisk.img: x86 boot sector; partition 1: ID=0x82, starthead 1, startsector 63, 4273227 sectors; partition 2: ID=0x83, active, starthead 0, startsector 4273290, 77626080 sectors The DomU file is: DomU (file): name = "video" uuid = "54d25d78-b9d0-0159-542c-bb601cc936bb" maxmem = 1024 memory = 512 vcpus = 1 builder = "hvm" kernel = "/usr...

...er into the image of the guest OS, I use the following procedure (guest OS is not running): 1. losetup -f --show /tmp/guest_os.img #map guest OS image to, e.g., /dev/loop0. So, "file -s /dev/loop0" shows: "/dev/loop0: x86 boot sector; partition 1: ID=0x83, starthead 32, startsector 2048, 2095104 sectors, extended partition table (last)\011, code offset 0x0" 2. losetup -f --show -o 1048576 /dev/loop0 #map partition with ext4 to, e.g., /dev/loop1. So, "file -s /dev/loop1" shows: "/dev/loop1: Linux rev 1.0 ext4 filesystem data, UUID=11e3ba2e-63aa-47ac...

Hello, I was looking for a way to detect the installed boot loader of an image and I found this: https://github.com/arvidjaar/bootinfoscript This script will inspection a lot of things on a running system and will output a Report. The most interesting part is that it uses known Master and Volume Boot Record byte-patterns to determine the installed boot loader:

...d more general path here is to add the advanced detection signatures to 'file'. At the moment when you run 'file' on a hard drive it does some sort of detection like this: # file -bsL /dev/sdb DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x0,32,33), end-CHS (0xce,29,63), startsector 2048, 250067632 sectors, extended partition table (last) Adding it to file means it will be available in libguestfs automatically (via 'guestfs_file' API), and means it would be generally useful to other people as well. However I'm not opposed to adding it to libguestfs if for some re...

I've been able to successfully kickstart CentOS 3.9 from the base repo, but no such luck after merging os and updates. I think I did everything right - updated base/comps.xml and regenerated hdlist/hdlist2. Updated the yum repo as well although I'm pretty sure it's not used by anaconda. This is difficult to debug. The setup is running under kvm on a CentOS 6.4 host, and for some

...'man' to read the manual > 'quit' to quit the shell > > ><fs> run > ><fs> list-filesystems > ><fs> list-partitions > > /dev/sda1 > > ><fs> file /dev/sda1 > > ; partition 4: ID=0xa5, active, starthead 0, startsector 0, 50000 > sectors > ><fs> vfs-type /dev/sda1 > > zfs_member > > I tried opening it with virt-rescue, but for some reason the zfs-fuse > daemon would not start, and hence other commands such as zpool didn't > work. I've taken a quick look at this, and got...

On 02/03/2014 3:16 pm, Richard W.M. Jones wrote: > On Mon, Feb 03, 2014 at 03:12:28PM -0500, Andre Goree wrote: >> I'm wondering whether or not anyone has tried to use guestmount on >> an image with a ZFS partition (MBR partition table). I can't seem >> to find much on the internet regarding it, but I do see hints that >> may lead me to a solution. I'm

...ot code to 10MB disk image: root at debian64:~# dd if=/usr/lib/syslinux/mbr.bin of=10MB bs=1 count=440 conv=notrunc 440+0 records in 440+0 records out 440 bytes (440 B) copied, 0,000622907 s, 706 kB/s root at debian64:~# file -s 10MB 10MB: x86 boot sector; partition 1: ID=0x6, active, starthead 0, startsector 1, 1606499 sectors, code offset 0x31 root at debian64:~# 7) Installed syslinux to 10MB1 partition(that is the reason I used 32256 byte offset): root at debian64:~# syslinux --install --offset 32256 10MB root at debian64:~# 8) Mounted this 10MB1 partition: root at debian64:~# mount 10MB /media/...

Hi Konrad, Does this look at all familiar? There is some more info in the full bug log at http://bugs.debian.org/637234 . In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e