From: Harald W. <hwe...@gm...> - 2008-05-17 23:46:47
|
Hello, How can logical hard disk partitions be accessed within a colinux environment? The hard disk partition is like: Disk /dev/hda: 400.0 GB, 400088457216 bytes 255 heads, 63 sectors/track, 48641 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 5099 40957686 7 HPFS/NTFS /dev/hda2 5100 20397 122881185 7 HPFS/NTFS /dev/hda3 20398 21856 11719417+ 83 Linux /dev/hda4 21857 48641 215150512+ 5 Extended /dev/hda5 21857 28543 53713296 8e Linux LVM /dev/hda6 28544 35230 53713296 8e Linux LVM /dev/hda7 35231 41917 53713296 8e Linux LVM /dev/hda8 41918 48641 54010498+ 8e Linux LVM hda1 and hda2 are Windows XP Home C: and D: . hda3 is the root partition of a Linux installation (Debian 4.0). hda5 contains an LV group with LVs for swap and /home. I use the coLinux Snapshot 20080425 with the kernel and modules version 2.6.22.18-co-0.8.0 as provided by Henry Nestler. The basic configuration is not special: mem=256 kernel=vmlinux root=/dev/cobd0 ro cobd0=d:\coLinux\system.img eth0=pcap-bridge,"LAN-Verbindung" system.img contains a minimal Debian 4.0 installation. When trying to access the linux partitions under colinux like: cobd1=\Device\Harddisk0\Partition3 cobd2=\Device\Harddisk0\Partition4 cobd3=\Device\Harddisk0\Partition5 cobd4=\Device\Harddisk0\Partition6 cobd5=\Device\Harddisk0\Partition7 only the primary partition 3 (cobd1) is effectively visible under coLinux. The logical partitions cannot be accessed: colinux:~# cat /dev/cobd2 cat: /dev/cobd2: No such device colinux:~# ls -l /dev/cobd2 brw-rw---- 1 root disk 117, 2 May 18 01:13 /dev/cobd2 According to the output of "dd --list" under Windows, [see http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm ] the partitions should well exist: [...] \\?\Device\Harddisk0\Partition0 link to \\?\Device\Harddisk0\DR0 Fixed hard disk media. Block size = 512 size is 400088457216 bytes \\?\Device\Harddisk0\Partition1 link to \\?\Device\HarddiskVolume1 \\?\Device\Harddisk0\Partition2 link to \\?\Device\HarddiskVolume2 \\?\Device\Harddisk0\Partition3 link to \\?\Device\HarddiskVolume3 Fixed hard disk media. Block size = 512 size is 12000683520 bytes \\?\Device\Harddisk0\Partition4 link to \\?\Device\HarddiskVolume4 size is 55002415104 bytes \\?\Device\Harddisk0\Partition5 link to \\?\Device\HarddiskVolume5 size is 55002415104 bytes \\?\Device\Harddisk0\Partition6 link to \\?\Device\HarddiskVolume6 size is 55002415104 bytes \\?\Device\Harddisk0\Partition7 link to \\?\Device\HarddiskVolume7 size is 55306750464 bytes [...] Is there a way to access the partitions under coLinux? I also tried to access the whole hard disk under coLinux: cobd1=\Device\Harddisk0\Partition0 alias hda=:cobd1 The entire hard disk seems to be visible under coLinux now. fdisk -l , or partprobe -d -s work fine: colinux:~# partprobe -d -s /dev/hda: msdos partitions 1 2 3 4 <5 6 7 8> /dev/cobd1: msdos partitions 1 2 3 4 <5 6 7 8> However, the partitions themselves are not present. Even partprobe is not able to communicate the partitions to the kernel: debian:~# partprobe -s Error: Error informing the kernel about modifications to partition /dev/hda1 -- Invalid argument. This means Linux won't know about any changes you made to /dev/hda1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. Error: Error informing the kernel about modifications to partition /dev/hda2 -- Invalid argument. This means Linux won't know about any changes you made to /dev/hda2 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. [...] Finally, I'd like to try to access the locical partitions via the losetup command with --offset option. But the loop module is not present within the kernel/modules provided by Henry. Is there a reason why loop is ommitted? Would it be possible to access the locical partitions using loop with offset? Regards, Harald |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-05-18 21:24:29
|
Hello Harald, Harald Weidner wrote: > How can logical hard disk partitions be accessed within a colinux > environment? Logical disk can access. But I have never used LVM there. > The hard disk partition is like: > > Disk /dev/hda: 400.0 GB, 400088457216 bytes > 255 heads, 63 sectors/track, 48641 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/hda1 * 1 5099 40957686 7 HPFS/NTFS > /dev/hda2 5100 20397 122881185 7 HPFS/NTFS > /dev/hda3 20398 21856 11719417+ 83 Linux > /dev/hda4 21857 48641 215150512+ 5 Extended > /dev/hda5 21857 28543 53713296 8e Linux LVM > /dev/hda6 28544 35230 53713296 8e Linux LVM > /dev/hda7 35231 41917 53713296 8e Linux LVM > /dev/hda8 41918 48641 54010498+ 8e Linux LVM > > hda1 and hda2 are Windows XP Home C: and D: . > hda3 is the root partition of a Linux installation (Debian 4.0). > hda5 contains an LV group with LVs for swap and /home. > > I use the coLinux Snapshot 20080425 with the kernel and modules > version 2.6.22.18-co-0.8.0 as provided by Henry Nestler. The basic > configuration is not special: > > mem=256 > kernel=vmlinux > root=/dev/cobd0 ro > cobd0=d:\coLinux\system.img > eth0=pcap-bridge,"LAN-Verbindung" > > system.img contains a minimal Debian 4.0 installation. > > When trying to access the linux partitions under colinux like: > > cobd1=\Device\Harddisk0\Partition3 > cobd2=\Device\Harddisk0\Partition4 > cobd3=\Device\Harddisk0\Partition5 > cobd4=\Device\Harddisk0\Partition6 > cobd5=\Device\Harddisk0\Partition7 > > only the primary partition 3 (cobd1) is effectively visible under coLinux. > The logical partitions cannot be accessed: > > colinux:~# cat /dev/cobd2 > cat: /dev/cobd2: No such device > colinux:~# ls -l /dev/cobd2 > brw-rw---- 1 root disk 117, 2 May 18 01:13 /dev/cobd2 cat on a partition is not good idea. Perhaps you can access this by reading block size only with "dd if=/dev/cobd2 bs=512 count=1" ? If not, run the coLinux debugger to see more about problems an the windows detailed error message. Run the debugger: colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml Than try to read one block. Stop the debugger. Open the file debug.xml with IE or notepad. Typicaly at the end you should see the error from block device read and the Windows internal error code. > According to the output of "dd --list" under Windows, > [see http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm ] > the partitions should well exist: > > [...] > \\?\Device\Harddisk0\Partition0 > link to \\?\Device\Harddisk0\DR0 > Fixed hard disk media. Block size = 512 > size is 400088457216 bytes > \\?\Device\Harddisk0\Partition1 > link to \\?\Device\HarddiskVolume1 > \\?\Device\Harddisk0\Partition2 > link to \\?\Device\HarddiskVolume2 > \\?\Device\Harddisk0\Partition3 > link to \\?\Device\HarddiskVolume3 > Fixed hard disk media. Block size = 512 > size is 12000683520 bytes > \\?\Device\Harddisk0\Partition4 > link to \\?\Device\HarddiskVolume4 > size is 55002415104 bytes > \\?\Device\Harddisk0\Partition5 > link to \\?\Device\HarddiskVolume5 > size is 55002415104 bytes > \\?\Device\Harddisk0\Partition6 > link to \\?\Device\HarddiskVolume6 > size is 55002415104 bytes > \\?\Device\Harddisk0\Partition7 > link to \\?\Device\HarddiskVolume7 > size is 55306750464 bytes > [...] That's a strong result. In normal case, all Linux Partition have a line "Fixed hard disk media. Block size = 512" Is that normal for LVM, that they don't have? I don't know. >From the "size is" I would say from \Device\HarddiskVolume4 to \Device\HarddiskVolume7 is your LVM array for hda5 to hda8. Your config was ok. YOu can writ also the short form: hda3=\Device\Harddisk0\Partition3 hda5=\Device\Harddisk0\Partition4 hda6=\Device\Harddisk0\Partition5 hda7=\Device\Harddisk0\Partition6 hda8=\Device\Harddisk0\Partition7 Remember: The Extended Partition /dev/hda4 you can never see under Windows and is not countered. > Is there a way to access the partitions under coLinux? > > > I also tried to access the whole hard disk under coLinux: > > cobd1=\Device\Harddisk0\Partition0 > alias hda=:cobd1 > > The entire hard disk seems to be visible under coLinux now. > fdisk -l , or partprobe -d -s work fine: > > colinux:~# partprobe -d -s > /dev/hda: msdos partitions 1 2 3 4 <5 6 7 8> > /dev/cobd1: msdos partitions 1 2 3 4 <5 6 7 8> > > However, the partitions themselves are not present. Even partprobe is not > able to communicate the partitions to the kernel: > > debian:~# partprobe -s > Error: Error informing the kernel about modifications to partition /dev/hda1 -- Invalid argument. This means Linux won't know about any changes you made to /dev/hda1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. > Error: Error informing the kernel about modifications to partition /dev/hda2 -- Invalid argument. This means Linux won't know about any changes you made to /dev/hda2 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. > [...] cobd and the alias hdaX has no partitions support. "partprobe" is not usable on cobd and not usable on the alias hdaX. You can configure to use the whole disks as scsi. This driver has partition support and is available in the coLinux 0.8.0 snapshots. scsi0=disk,\Device\Harddisk0\Partition0 Than you have all your partitions from /dev/sda1 to /dev/sda8. "partprobe" should work with this device. Be carefully with accessing the windows partition from that driver. You should never mount the windows partitions (sda1, sda2)! Please also don't mount Windows aktive partitions as readonly, you risk to read wrong datas. > Finally, I'd like to try to access the locical partitions via the > losetup command with --offset option. But the loop module is not present > within the kernel/modules provided by Henry. > > Is there a reason why loop is ommitted? Would it be possible to access > the locical partitions using loop with offset? Loop is not a module. Loop is compiled in: $ zgrep LOOP < /proc/config.gz CONFIG_BLK_DEV_LOOP=y I'm afraid you need modules to use the LVM. All drivers after CONFIG_MD are only in the modules (CONFIG_BLK_DEV_DM=m). After you have installed modules under /lib/modules, you can use the LVM modules. I don't know what modules you need to load. Please check the files in lib/modules/2.6.25/kernel/drivers/md/ they begining with "dm-". Please also read Linux kernel source under Documentation/device-mapper. -- Henry N. |
From: Harald W. <hwe...@gm...> - 2008-05-18 22:32:04
|
Hallo Henry, Thank you for your quick response. Henry Nestler <Henry.Ne@Arcor.de>: >> colinux:~# cat /dev/cobd2 >> cat: /dev/cobd2: No such device >cat on a partition is not good idea. Perhaps you can access this by >reading block size only with "dd if=/dev/cobd2 bs=512 count=1" ? The cat command was only used to show that the error message. The dd command gives the same error: dd: opening `/dev/cobd2': No such device >If not, run the coLinux debugger to see more about problems an the >windows detailed error message. Run the debugger: > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml >Than try to read one block. >Stop the debugger. Open the file debug.xml with IE or notepad. Typicaly >at the end you should see the error from block device read and the >Windows internal error code. The according messages are: - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" timestamp="00000016.3900969652" local_index="668" facility="0" function="co_os_file_block_get_size" line="212" level="10" driver_index="802"> <string>device \Device\Harddisk0\Partition4</string> </log> - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" timestamp="00000016.3900971984" local_index="669" facility="0" function="co_os_file_block_detect_size_harddisk" line="154" level="10" driver_index="803"> <string>fail status C000000E</string> </log> - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" timestamp="00000016.3900972192" local_index="670" facility="0" function="co_os_file_block_detect_size_binary_search" line="99" level="3" driver_index="804"> <string>size is zero</string> </log> Regards, Harald |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-05-19 23:44:02
|
Harald Weidner wrote: >>> colinux:~# cat /dev/cobd2 >>> cat: /dev/cobd2: No such device > > [...] > >> If not, run the coLinux debugger to see more about problems an the >> windows detailed error message. Run the debugger: >> colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml >> Than try to read one block. >> Stop the debugger. Open the file debug.xml with IE or notepad. Typicaly >> at the end you should see the error from block device read and the >> Windows internal error code. > > The according messages are: > > - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" > timestamp="00000016.3900969652" local_index="668" facility="0" > function="co_os_file_block_get_size" line="212" level="10" > driver_index="802"> > <string>device \Device\Harddisk0\Partition4</string> > </log> > - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" > timestamp="00000016.3900971984" local_index="669" facility="0" > function="co_os_file_block_detect_size_harddisk" line="154" level="10" > driver_index="803"> > <string>fail status C000000E</string> > </log> The translated error message from include/ddk/ntstatus.h: STATUS_NO_SUCH_DEVICE ((NTSTATUS)0xC000000EL) That means the ZwDeviceIoControlFile(..., IOCTL_DISK_GET_LENGTH_INFO, ...) does not work. That's harmless. > - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" > timestamp="00000016.3900972192" local_index="670" facility="0" > function="co_os_file_block_detect_size_binary_search" line="99" level="3" > driver_index="804"> > <string>size is zero</string> > </log> coLinux can copen the devie but can't ead any? Is the device locked? Is the device opened by Windows perhaps? Please try to read a block with the windows variant of dd: dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1 Try the official names "\\?\Device\Harddisk0\Partition4" or "\\?\Device\HarddiskVolume4", as you have seen from dd --list. -- Henry N. |
From: Harald W. <hwe...@gm...> - 2008-05-21 18:20:26
|
Hello, Henry Nestler <Henry.Ne@Arcor.de>: >coLinux can copen the devie but can't ead any? >Is the device locked? Is the device opened by Windows perhaps? I don't think so. >Please try to read a block with the windows variant of dd: > dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1 > >Try the official names "\\?\Device\Harddisk0\Partition4" or >"\\?\Device\HarddiskVolume4", as you have seen from dd --list. The result is: D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1 rawwrite dd for windows version 0.5. Written by John Newbigin <jn...@it...> This program is covered by the GPL. See copying.txt for details Error reading file: 2 Das System kann die angegebene Datei nicht finden 0+0 records in 0+0 records out Same for the HarddiskVolume4 partition, and also for the Partition 6. On the other two partitions, it works fine: D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition5 of=foo bs=512 count=1 rawwrite dd for windows version 0.5. Written by John Newbigin <jn...@it...> This program is covered by the GPL. See copying.txt for details 1+0 records in 1+0 records out This means that Windows can access the two partitions of type 0x83 (Linux), but refuses access to type 0x8e (Linux LVM). While coLinux is running, none of the partitions can be accessed, but the error messages are different: (Type 0x8e Linux LVM) D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1 rawwrite dd for windows version 0.5. Written by John Newbigin <jn...@it...> This program is covered by the GPL. See copying.txt for details Error reading file: 2 Das System kann die angegebene Datei nicht finden 0+0 records in 0+0 records out (Type 0x83 Linux) D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition5 of=foo bs=512 count=1 rawwrite dd for windows version 0.5. Written by John Newbigin <jn...@it...> This program is covered by the GPL. See copying.txt for details Error native opening input file: 0 Der Vorgang wurde erfolgreich beendet Regards, Harald |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-05-21 19:37:49
|
Harald Weidner wrote: > Henry Nestler: > >> coLinux can copen the devie but can't ead any? >> Is the device locked? Is the device opened by Windows perhaps? > > I don't think so. > >> Please try to read a block with the windows variant of dd: >> dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1 >> >> Try the official names "\\?\Device\Harddisk0\Partition4" or >> "\\?\Device\HarddiskVolume4", as you have seen from dd --list. > > The result is: > > D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1 > rawwrite dd for windows version 0.5. > Written by John Newbigin <jn...@it...> > This program is covered by the GPL. See copying.txt for details > Error reading file: 2 Das System kann die angegebene Datei nicht finden > 0+0 records in > 0+0 records out > > Same for the HarddiskVolume4 partition, and also for the Partition 6. > [...] > > This means that Windows can access the two partitions of type 0x83 (Linux), > but refuses access to type 0x8e (Linux LVM). Interesting. Now, we know, that coLinux and dd.exe can't read this partition type 0x8e. But why? Exist any other "read" for such type of drive? Any tool for "raw read" any partition type? Is Windows handling such devices and trying to made a disk array? The other of interesting is, that dd.exe does not show the blocksize. > While coLinux is running, none of the partitions can be accessed, but the > error messages are different: > > (Type 0x8e Linux LVM) > D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1 > rawwrite dd for windows version 0.5. > Written by John Newbigin <jn...@it...> > This program is covered by the GPL. See copying.txt for details > Error reading file: 2 Das System kann die angegebene Datei nicht finden > 0+0 records in > 0+0 records out > > (Type 0x83 Linux) > D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition5 of=foo bs=512 count=1 > rawwrite dd for windows version 0.5. > Written by John Newbigin <jn...@it...> > This program is covered by the GPL. See copying.txt for details > Error native opening input file: 0 Der Vorgang wurde erfolgreich beendet That is ok. coLinux has open the partition exclusivly. New idea: Use coLinux 0.8.0 and the "whole disk" as scsi0=disk,\\?\Device\Harddisk0\Partition0 This is an other driver inside Linux kernel. You should see partitions sda3, sda5 and so, directly after boot in the kernel messages. -- Henry N. |
From: Harald W. <hwe...@gm...> - 2008-05-22 05:58:50
|
Hello, >Interesting. Now, we know, that coLinux and dd.exe can't read this >partition type 0x8e. But why? Exist any other "read" for such type of >drive? I don't know of such processes. It's an almoust freshly setup Windows XP Home SP2 without special processes or hacks. When Windows was installed, only hda1 and hda2 were partitioned, the remaining hard disk was unpartitioned space. Later, the space was partitioned using the Debian installer. >New idea: >Use coLinux 0.8.0 and the "whole disk" as > > scsi0=disk,\\?\Device\Harddisk0\Partition0 > >This is an other driver inside Linux kernel. You should see partitions >sda3, sda5 and so, directly after boot in the kernel messages. It does not work directly this way... scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 coscsi0: unable to open device! rc: 1 coscsi0: unable to open device! rc: 1 coscsi0: unable to open device! rc: 1 coscsi0: unable to open device! rc: 1 sd 0:0:0:0: [sda] READ CAPACITY failed sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x00 sd 0:0:0:0: [sda] Sense not available. sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] Attached SCSI disk colinux:/tmp# dd if=/dev/sda of=test.img bs=512 count=1 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0 seconds, Infinity B/s colinux:/tmp# dd if=/dev/sda3 of=test.img bs=512 count=1 dd: opening `/dev/sda3': No such file or directory But with a slight modification, it works really fine: scsi0=disk,\Device\Harddisk0\Partition0 scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 > sd 0:0:0:0: [sda] Attached SCSI disk ...and all partitions are visible and can be used inside coLinux, even LVM works! Thanks a lot! Regards, Harald |
From: Harald W. <hwe...@gm...> - 2008-05-18 23:30:42
|
Hello again, Henry Nestler <Henry.Ne@Arcor.de>: >Logical disk can access. But I have never used LVM there. I have no made some further experiments and set hda5 type "Linux LVM" and an LVM physical volume hda6 type "Linux", but contains also an LVM PV hda7 type "Linux LVM" but contains an ext3 partition hda8 type "Linux" and contains an ext3 partition The results: Only the devices of type "Linux" are recognized by coLinux. The partitions of type "Linux LVM" are ignored and yield to the error message "No such device" when being accessed with cat or dd. The ext3 partition hda8 can be mounted without further problems into colinux. The LVM partition hda6 is not recognized by LVM inside coLinux, unless the following parameter is set in /etc/lvm/lvm.conf: # List of pairs of additional acceptable block device types found # in /proc/devices with maximum (non-zero) number of partitions. types = [ "cobd", 32 ] All in all, this is not nice but solves my problems accessing a logical partition containing LVM. >That's a strong result. In normal case, all Linux Partition have a line > "Fixed hard disk media. Block size = 512" >Is that normal for LVM, that they don't have? I don't know. With the above configuration, it looks like: [...] \\?\Device\Harddisk0\Partition4 link to \\?\Device\HarddiskVolume4 size is 55002415104 bytes \\?\Device\Harddisk0\Partition5 link to \\?\Device\HarddiskVolume5 Fixed hard disk media. Block size = 512 size is 55002415104 bytes \\?\Device\Harddisk0\Partition6 link to \\?\Device\HarddiskVolume6 size is 55002415104 bytes \\?\Device\Harddisk0\Partition7 link to \\?\Device\HarddiskVolume7 Fixed hard disk media. Block size = 512 size is 55306750464 bytes [...] E.g. all partitions of type "Linux" are displayed with the "Fixed hard disk media. Block size = 512" line, but not the "Linux LVM" partitions. It does not matter wether the partitions actually contain LVM or ext3. Regards, Harald |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-05-19 23:50:34
|
Harald Weidner wrote: > hda5 type "Linux LVM" and an LVM physical volume > hda6 type "Linux", but contains also an LVM PV > hda7 type "Linux LVM" but contains an ext3 partition > hda8 type "Linux" and contains an ext3 partition > > The results: > > Only the devices of type "Linux" are recognized by coLinux. > The partitions of type "Linux LVM" are ignored and yield to the > error message "No such device" when being accessed with cat or dd. > > The ext3 partition hda8 can be mounted without further problems into > colinux. > > The LVM partition hda6 is not recognized by LVM inside coLinux, unless > the following parameter is set in /etc/lvm/lvm.conf: > > # List of pairs of additional acceptable block device types found > # in /proc/devices with maximum (non-zero) number of partitions. > types = [ "cobd", 32 ] > > > All in all, this is not nice but solves my problems accessing a logical > partition containing LVM. > > >> That's a strong result. In normal case, all Linux Partition have a line >> "Fixed hard disk media. Block size = 512" >> Is that normal for LVM, that they don't have? I don't know. > > With the above configuration, it looks like: > > [...] > \\?\Device\Harddisk0\Partition4 > link to \\?\Device\HarddiskVolume4 > size is 55002415104 bytes > \\?\Device\Harddisk0\Partition5 > link to \\?\Device\HarddiskVolume5 > Fixed hard disk media. Block size = 512 > size is 55002415104 bytes > \\?\Device\Harddisk0\Partition6 > link to \\?\Device\HarddiskVolume6 > size is 55002415104 bytes > \\?\Device\Harddisk0\Partition7 > link to \\?\Device\HarddiskVolume7 > Fixed hard disk media. Block size = 512 > size is 55306750464 bytes > [...] > > E.g. all partitions of type "Linux" are displayed with the "Fixed hard > disk media. Block size = 512" line, but not the "Linux LVM" partitions. > It does not matter wether the partitions actually contain LVM or ext3. I have one free partition. How can I setup it as "Linux LVM"? Short steps or a link to any simple help side would help me, please. -- Henry N. |
From: Robert B. <ro...@ro...> - 2008-05-20 00:02:51
|
On Tue, 20 May 2008 01:51:14 +0200 Henry Nestler <Henry.Ne@Arcor.de> wrote: > I have one free partition. How can I setup it as "Linux LVM"? > Short steps or a link to any simple help side would help me, please. http://www.gentoo.org/doc/en/lvm2.xml is what I follow. I know it's Gentoo specific, but the LVM parts are pretty much distro agnostic... Unless your / is on the LVM, it's pretty straight forward to use... Rob. |
From: Harald W. <hwe...@gm...> - 2008-05-20 06:47:18
|
Hello Henry, Henry Nestler <Henry.Ne@Arcor.de>: >I have one free partition. How can I setup it as "Linux LVM"? >Short steps or a link to any simple help side would help me, please. The only thing you need to do to reproduce the behavior is to set the partition type to 8e ("Linux LVM / Solaris") with fdisk. If you want to make further experiments with LVM, you should boot a diskless Linux (e.g. Knoppix) and set the partition type to 8e. Then: create a LVM physical volume on the partition: pvcreate /dev/hda8 create a volume group: vgcreate test /dev/hda8 create a logical volume within the volume group lvcreate -n vol1 -L 1G test The volume group's device is now visible under /dev/test/vol1 , which is a symbolic link to /dev/mapper/test-vol1 . You can handle it like an ordinary partition, e.g. mkfs.ext3 /dev/test/vol1 mount -t ext3 /dev/test/vol1 /mnt/volume1 Use the commands pvs, vgs, and lvs to list the physical volumes, volume groups, and logical volumes on your system. Use pvscan, vgscan, and lvscan to rescan the LVM configuration after attaching a device or making externally changes. Thank you for your support! Regards, Harald |