How do I setup Windows Spanned Dynamic Disks to be used in Linux?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How do I setup Windows Spanned Dynamic Disks to be used in Linux?
I setup two hard drives in Windows Vista to be spanned together. I want to be able to access them from my Linux, but I cannot figure out how. So far the first thing I have done is setup my kernel with the following options:
Code:
[*] Multiple devices driver support (RAID and LVM)
<*> Device mapper support
[*] Device mapper debugging support
...
...
[*] Advanced partition selection
[*] Windows Logical Disk Manager (Dynamic Disk) support
[*] Windowx LDM extra logging
I am using kernel 2.6.23.1
I have Device-Mapper 1.02.22 installed
The first volume in my span is /dev/sdb1
The second volume in my span is /dev/sdd1
This is the output from "$ dmesg | grep ldm" loading the disk /dev/sdb:
Code:
sdb:<7>ldm_validate_partition_table(): Found W2K dynamic disk partition type.
ldm_parse_privhead(): PRIVHEAD version 2.12 (Windows Vista).
ldm_parse_privhead(): Parsed PRIVHEAD successfully.
ldm_parse_privhead(): PRIVHEAD version 2.12 (Windows Vista).
ldm_parse_privhead(): Parsed PRIVHEAD successfully.
ldm_parse_privhead(): PRIVHEAD version 2.12 (Windows Vista).
ldm_parse_privhead(): Parsed PRIVHEAD successfully.
ldm_validate_privheads(): Validated PRIVHEADs successfully.
ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
ldm_parse_tocblock(): Parsed TOCBLOCK successfully.
ldm_parse_tocblock(): Parsed TOCBLOCK successfully.
ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
ldm_validate_tocblocks(): Validated 2 TOCBLOCKs successfully.
ldm_parse_vmdb(): Parsed VMDB successfully.
ldm_parse_vblk(): Parsed VBLK 0x1 (type: 0x35) ok.
ldm_parse_vblk(): Parsed VBLK 0x3 (type: 0x51) ok.
ldm_parse_vblk(): Parsed VBLK 0x2 (type: 0x34) ok.
ldm_parse_vblk(): Parsed VBLK 0x5 (type: 0x33) ok.
ldm_parse_vblk(): Parsed VBLK 0x6 (type: 0x34) ok.
ldm_parse_vblk(): Parsed VBLK 0x4 (type: 0x32) ok.
ldm_parse_vblk(): Parsed VBLK 0x7 (type: 0x33) ok.
ldm_partition(): Parsed LDM database successfully.
This is the output from "$ dmesg | grep ldm" loading the disk /dev/sdd:
Code:
sdd:<7>ldm_validate_partition_table(): Found W2K dynamic disk partition type.
ldm_parse_privhead(): PRIVHEAD version 2.12 (Windows Vista).
ldm_parse_privhead(): Parsed PRIVHEAD successfully.
ldm_parse_privhead(): PRIVHEAD version 2.12 (Windows Vista).
ldm_parse_privhead(): Parsed PRIVHEAD successfully.
ldm_parse_privhead(): PRIVHEAD version 2.12 (Windows Vista).
ldm_parse_privhead(): Parsed PRIVHEAD successfully.
ldm_validate_privheads(): Validated PRIVHEADs successfully.
ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
ldm_parse_tocblock(): Parsed TOCBLOCK successfully.
ldm_parse_tocblock(): Parsed TOCBLOCK successfully.
ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
ldm_validate_tocblocks(): Validated 2 TOCBLOCKs successfully.
ldm_parse_vmdb(): Parsed VMDB successfully.
ldm_parse_vblk(): Parsed VBLK 0x1 (type: 0x35) ok.
ldm_parse_vblk(): Parsed VBLK 0x3 (type: 0x51) ok.
ldm_parse_vblk(): Parsed VBLK 0x2 (type: 0x34) ok.
ldm_parse_vblk(): Parsed VBLK 0x5 (type: 0x33) ok.
ldm_parse_vblk(): Parsed VBLK 0x6 (type: 0x34) ok.
ldm_parse_vblk(): Parsed VBLK 0x4 (type: 0x32) ok.
ldm_parse_vblk(): Parsed VBLK 0x7 (type: 0x33) ok.
ldm_partition(): Parsed LDM database successfully.
This seems correct to me so I then try to setup Device-Mapper according to instruction in my kernel/Documentation/filesystems/ntfs.txt
I run "$ fdisk -lu /dev/sdb" which outputs:
Code:
Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 63 625140399 312570168+ 42 SFS
Then run "$ fdisk -lu /dev/sdd" which outputs:
Code:
Disk /dev/sdd: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 63 625140399 312570168+ 42 SFS
From this info I setup a table file for dmsetup, the table has the following,
Code:
# Offset into Size of this Raid type Device Start sector
# volume device of device
0 625140337 linear /dev/sdb1 0
625140337 625140337 linear /dev/sdd1 0
I then run "$ dmsetup create newdevice /etc/newdevice1" which gives the following error:
Here you go, just so you know, I used to have /dev/sdb1 as a basic disk, so the line I commented out is like that because of how it was previously setup
this may take me some time I need to refresh my knowledge of windows first. it may take me a day to get it to work.
once I have it working I will message you with how I did it.
It might take me a bit longer I have just got an assignment from college and I will be spending most of my time on this.
It should only take a few days but Don't be too surprised if it takes me a week.
I will keep you posted with an update on my progress each day.
If this is important I can make it a higher priority if you like but that will cause some strains on my time.
Is that ok?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.