search for: hdd0

Hello everyone! I have to implement the functionality of mounting all VM disks/partitions. E.g. if a VM has 2 disks of 2 partitions each (I get it from virt-filesystems), I want to get the following structure on host node after mount: mnt/ ------hdd0/ -------------volume1/ -------------volume2/ ------hdd1/ -------------volume1/ -------------volume2/ I'd like to use guestmount due to syntax simplicity, but I found out that it's impossible to call e.g. guestmount -a disk.qcow2 -m /dev/sda1:/hdd0/volume1 -m /dev/sda2:/hdd0/volume2 mnt/...

...wrote: > Hello everyone! > > I have to implement the functionality of mounting all VM disks/partitions. > > E.g. if a VM has 2 disks of 2 partitions each (I get it from > virt-filesystems), I want to get the following structure on host > node after mount: > mnt/ > ------hdd0/ > -------------volume1/ > -------------volume2/ > ------hdd1/ > -------------volume1/ > -------------volume2/ > > I'd like to use guestmount due to syntax simplicity, but I found out > that it's impossible to call e.g. > guestmount -a disk.qcow2 -m /dev/sda1:/hd...

...t;> >> I have to implement the functionality of mounting all VM disks/partitions. >> >> E.g. if a VM has 2 disks of 2 partitions each (I get it from >> virt-filesystems), I want to get the following structure on host >> node after mount: >> mnt/ >> ------hdd0/ >> -------------volume1/ >> -------------volume2/ >> ------hdd1/ >> -------------volume1/ >> -------------volume2/ >> >> I'd like to use guestmount due to syntax simplicity, but I found out >> that it's impossible to call e.g. >> guestm...

...ink points to a file that is on a CIFS mount. So say I have computer B (running Mac OS X) that shares something using Samba. I mount such share on computer A, in /mnt/hdd-air. Then, on a share of computer A, I create a symlink to a file in /mnt/hdd-air: ln -s /mnt/hdd-air/gh/TimeMachine/file2 /mnt/hdd0/shares/TimeMachine/file2 If I mount my TimeMachine share (on computer A or any other computer), file2 is listed, but I can't access it. That is, it can't be accessed UNLESS the file was accessed successfully in the last second! Here's a test case I created on computer A: # This is m...

...d hard disk to the pool to increase my storage capacity without a raid controller? >From what I''ve found, the command should be "zpool add rpool <device>". Is that right? If so, how do I track down the device name? "zpool status" tells me my current device (hdd0) is named "c3d0s0". Where do I find the other device name? Thanks! -- This message posted from opensolaris.org

...boot was a com32 module rather than a configuration directive so that one can use it on the boot prompt, rather than require a menu entry/alias at all times. A more userfriendly localboot.c32 could do this and allow eg for friendly device-names. localboot next localboot floppy0 localboot hdd0 or something that makes more sense technically. And give a list of possibilities when invoked without options ? (Just freewheeling) We did notice on an HP Proliant ML 350 G6 that after booting syslinux from a USB stick: - localboot -1 booted caused to reload from the USB stick again - a co...

Greetings: I'm upgrading a fileserver running 3.4 (upgrade to a larger disk). I backed up the data from the "old" disk and slapped in a newer, larger disk and installed Centos-3.4. No problems. Now, there are some files on the "old" disk that I forgot to move to the back-up disk, so I'd like to mount the "old" disk as /dev/hdd and reboot the system and

...aster using PIO4 Oh, and I found that this server has a HighPoint RAID controller which can do RAID 0, 1, 0+1, and JBOD. Looking in my array configuration I see that we have: Channel Mode Status Primary Master: Mirror (RAID 1) for array #0 UDMA 5 HDD0 Secondary Master: Mirror ... UDMA 5 Hidden I initially said that this was a Promise controller. Here is my /etc/fstab for /: /dev/ad4s1a / ufs rw 1 1 Following is /var/run/dmesg.log after booting from kernel.good: Copyright (c) 1992-2001 The FreeBSD Project. Copyrig...

Hello, I am curious to know if there is an easy way to guess or identify the device names of disks. Previously the /dev/dsk/c0t0d0s0 system made sense to me... I had a SATA controller card with 8 ports, and they showed up with the numbers 1-8 in the "t" position of the device name. But I just built a new system with two LSI SAS HBAs in it, and my device names are along the lines of: