Hi antiXers!!!
Afirmative,"That´s correct" and Absolutely (my answer to: New to Linux? New to antiX? New to fluxbox?)
My sad story:
I want my old p2p PC to dualboot: antiX/WinXP(already installed)
To be on the safe side, I recreated the box on a vmware (workstation 9) machine and I´m testing it before getting my hands dirty
(the size of disks are pretty smaller on en VM than on the hard one...)
Everything OK so far but the windowsXPsp3-created dynamic disk. It won´t get mounted.
I have already tried ldmtool...
Not only it is not working, but the installation has also corrupted some stuff on the OS: Control Center won´t open, Quit button not working any more...
By the way, Synaptic told me that"locale" and"system-antiX" should be uninstalled to get ldmtool installed. Is this right?
(not a problem, have a snapshot)
Any clue will be appreciated.
Thank you in advance!
panchuz
--------------------- JUST DATA ----------------------------
fdisk -l output:
---------------
[...]
Disk /dev/sdb: 3 GB, 3216084480 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 391 3140676 42 SFS
Disk /dev/sdc: 2 GB, 2146798080 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 261 2096451 42 SFS
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
fstab content:
-------------
# Pluggable devices are handled by uDev, they are not in fstab
UUID=c16fd45e-e7d9-4311-b299-b5e9ffd733c4 / auto defaults,noatime 1 1
UUID=b783778b-17b7-4b74-a575-516f7ead22ad swap swap sw,pri=1 0 0
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0622 0 0
/dev/sr0 /media/sr0 iso9660 noauto,users,exec,relatime 0 0
UUID=A6902D29902D0203 /media/sda1 ntfs-3g noauto,users,noexec,uid=1000,gid=users,dmask=002,fmask=113,relatime 0 0
UUID=C688777B88776937 /media/sdc1 ntfs-3g noauto,users,noexec,uid=1000,gid=users,dmask=002,fmask=113,relatime 0 0
/dev/cdrom /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/sr0 /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
ldmtool output:
--------------
root@fantiX:/home/panchuz# ldmtool scan
[
"4b1fb013-f809-4887-af99-5cd620ee2108"
]
root@fantiX:/home/panchuz# ldmtool show diskgroup 4b1fb013-f809-4887-af99-5cd620ee2108
{
"name" :"Equipo1Dg0",
"guid" :"4b1fb013-f809-4887-af99-5cd620ee2108",
"volumes" : [
"Volume1"
],
"disks" : [
"Disk1",
"Disk2"
]
}
root@fantiX:/home/panchuz# ldmtool show volume 4b1fb013-f809-4887-af99-5cd620ee2108 Volume1
{
"name" :"Volume1",
"type" :"spanned",
"size" : 10473393,
"chunk-size" : 0,
"hint" :"F:",
"partitions" : [
"Disk1-01",
"Disk2-01"
]
}
root@fantiX:/home/panchuz# ldmtool show partition 4b1fb013-f809-4887-af99-5cd620ee2108 Disk1-01
{
"name" :"Disk1-01",
"start" : 0,
"size" : 6281216,
"disk" :"Disk1"
}
root@fantiX:/home/panchuz# ldmtool show disk 4b1fb013-f809-4887-af99-5cd620ee2108 Disk1
Segmentation fault
root@fantiX:/home/panchuz# ldmtool show disk 4b1fb013-f809-4887-af99-5cd620ee2108 Disk2
Segmentation fault
root@fantiX:/home/panchuz# ldmtool create volume 4b1fb013-f809-4887-af99-5cd620ee2108 Volume1
Unable to create volume Volume1 in disk group 4b1fb013-f809-4887-af99-5cd620ee2108: Disk Disk1 required by spanned volume Volume1 is missing
topic title: Mount LDM volume on antiX
5 posts
• Page 1 of 1
-
Posts: 2
- Joined: 19 Feb 2015
-
Posts: 604
- Joined: 27 Feb 2009
#2
Seems like more of an ldmtool/vmware/windows question than an antiX question?
Why not just cleanup, defragment and reduce the size of the XP drive on XP, and once that's done, install antiX in the unused area?
Or if thats not safe enough, take the drive out and use a different drive to test with first. You could load XP on it and then downsize it and install antiX, etc to duplicate what you'd need to do to the main one.
I guess what I'm really saying is that I don't think your test is a good reflection of the scenario you are trying to test because you are injecting a bunch of unnecessary permutations more than exist in your live scenario. I have made a few machines dual boot xp and antiX without trouble.
And then again, you might get lucky and find someone that uses a similar setup.
Why not just cleanup, defragment and reduce the size of the XP drive on XP, and once that's done, install antiX in the unused area?
Or if thats not safe enough, take the drive out and use a different drive to test with first. You could load XP on it and then downsize it and install antiX, etc to duplicate what you'd need to do to the main one.
I guess what I'm really saying is that I don't think your test is a good reflection of the scenario you are trying to test because you are injecting a bunch of unnecessary permutations more than exist in your live scenario. I have made a few machines dual boot xp and antiX without trouble.
And then again, you might get lucky and find someone that uses a similar setup.
-
Posts: 604
- Joined: 27 Feb 2009
#3
You must have meant"locales" not"locale". It is required by"system-antix".
I don't see an"ldmtool" in the default repositories, so I'm guessing you are trying to install it from someplace else. You didn't say what version of antiX you have, but if its 13.2, you should try to find a"wheezy" compatible version to have the highest likelihood of success, since antiX 13.2 is based on Debian Wheezy.
I am also assuming you have noticed that your ldmtool program was crashing? If you didn't that's what that segmentation fault thing is, IMO...
Looks like its only in Jessie and Sid as far as Debian is concerned. You probably need to tell people your system setup. At this point you are beyond my ability. My guess is you are going to have a mess on your hand if you remove system-antix and locales.
I don't see an"ldmtool" in the default repositories, so I'm guessing you are trying to install it from someplace else. You didn't say what version of antiX you have, but if its 13.2, you should try to find a"wheezy" compatible version to have the highest likelihood of success, since antiX 13.2 is based on Debian Wheezy.
I am also assuming you have noticed that your ldmtool program was crashing? If you didn't that's what that segmentation fault thing is, IMO...
Looks like its only in Jessie and Sid as far as Debian is concerned. You probably need to tell people your system setup. At this point you are beyond my ability. My guess is you are going to have a mess on your hand if you remove system-antix and locales.
-
Posts: 2
- Joined: 19 Feb 2015
#4
Thank thriftee for both replays!!!!
I can see now that I didn´t explain myself very good....
AntiX is installed and dualboot is working fine... on a single non-dynamic disk (3 partitions in it: ntfs, ext2, swap) Absolutely no problems there.
Now this box has two more disks. They work as a software-made LDM (single) volume, created in XP.
I just want to access THAT LDM volume from antiX the same way I do from XP. This LDM volume is just used for data storage (p2p)...no SO and no software on it
I installed ldmtools only after antiX was installed and fully functional...and after that, antiX started to malfunction...
Hope this clears stuff a bit.
I can see now that I didn´t explain myself very good....
Yes! I have already done that.Why not just cleanup, defragment and reduce the size of the XP drive on XP, and once that's done, install antiX in the unused area?
Or if thats not safe enough, take the drive out and use a different drive to test with first. You could load XP on it and then downsize it and install antiX, etc to duplicate what you'd need to do to the main one.
AntiX is installed and dualboot is working fine... on a single non-dynamic disk (3 partitions in it: ntfs, ext2, swap) Absolutely no problems there.
Now this box has two more disks. They work as a software-made LDM (single) volume, created in XP.
I just want to access THAT LDM volume from antiX the same way I do from XP. This LDM volume is just used for data storage (p2p)...no SO and no software on it
I installed ldmtools only after antiX was installed and fully functional...and after that, antiX started to malfunction...
Hope this clears stuff a bit.
Yes, I had to enable the testing Debian repository.I don't see an"ldmtool" in the default repositories, so I'm guessing you are trying to install it from someplace else.
That´s right: my antiX version is 13.2, but I couldn´t find any package to manage LDM disks on the wheezy repositoryYou didn't say what version of antiX you have, but if its 13.2, you should try to find a"wheezy" compatible version to have the highest likelihood of success, since antiX 13.2 is based on Debian Wheezy.
Ok. Synaptic had to uninstall both (locales & system-antix) to install ldmtool... is this right?You must have meant"locales" not"locale". It is required by"system-antix".
-
Posts: 604
- Joined: 27 Feb 2009
#5
Oh my! LOL
Its not ready for prime time, but getting close, that being antiX14.4 which is in alpha, I think, which is based on Jessie, and Jessie has ldmtool in its repository.
You are above my pay grade for sure, but if you are just trying to get things usable, I'd keep it simple and get rid of the ldm over in XP, and then reinstall antiX. To be honest, a version of gparted I used the other day, for example, couldn't successfully downsize an xp ntfs partition, and it did trash it, so therefore I would ask as little weird stuff as possible from the linux working with the MS's drives and avoid trouble by keeping things simple. I only READ from my windows ntfs drives with linux in order to avoid trouble. Otherwise you might find yourself on the"bleeding edge" of technology.
Its not ready for prime time, but getting close, that being antiX14.4 which is in alpha, I think, which is based on Jessie, and Jessie has ldmtool in its repository.
You are above my pay grade for sure, but if you are just trying to get things usable, I'd keep it simple and get rid of the ldm over in XP, and then reinstall antiX. To be honest, a version of gparted I used the other day, for example, couldn't successfully downsize an xp ntfs partition, and it did trash it, so therefore I would ask as little weird stuff as possible from the linux working with the MS's drives and avoid trouble by keeping things simple. I only READ from my windows ntfs drives with linux in order to avoid trouble. Otherwise you might find yourself on the"bleeding edge" of technology.