cAosThis forum is for the discussion of cAos 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.
I downloaded this iso from the distrowatch link a while back and gave it a spin last night. The boot from cd went just well, very well. I liked that sidekick. So I installed. Used the auto partition for workstations. After I restarted,,, well it would not boot. Just stop at the bios splash and that was the end of my HD. Removed HD and pc booted. So me thinking, I did something wrong, stuck a different HD and preceded to install. Auto partition for workstation. Well,,, that was the end of that HD. Just thought I would pass that a long. You guys need a couple of hard drives?
Do you have any more info on what is going on? I can't believe that an OS install would destroy your HD. It might erase everything on it or cause it to not boot, but I don't believe it would totally destroy it (i.e. cause some sort of hardware failure). I'm guessing by what you are describing that the install created the system and installed everything, but the master boot record is now corrupt. If you leave those HD's in your system and boot from the sidekick, can you see any data on the drives? (There should be some way to mount and view the HD's in the system).
It may have been the auto partitioner. But the drives are not usable. DragonFly BSD Killed two drive also about six months ago. They had a new auto installer, samething I thought I did something wrong and put a second drive in, and killed that. I still have all four drives, If I plug them in a IDE the motherboard locks up at the bios.
It sounds as though the partition type has been changed to a type your BIOS is not expecting. See if you can find the partition type option(s) in your BIOS and try changing the types supported. (I seem to recall that there is at least one type that is a proprietary Windows one that most Linux system will, unless coerced, not use.)
It sounds as though the partition type has been changed to a type your BIOS is not expecting. See if you can find the partition type option(s) in your BIOS and try changing the types supported. (I seem to recall that there is at least one type that is a proprietary Windows one that most Linux system will, unless coerced, not use.)
this would be good. I'll look, wonder if it is that os/2 deal. that would be great if I could get my HD's back. I think cAos and dragonfly lean toward server hardware.
It sounds as though the partition type has been changed to a type your BIOS is not expecting. See if you can find the partition type option(s) in your BIOS and try changing the types supported. (I seem to recall that there is at least one type that is a proprietary Windows one that most Linux system will, unless coerced, not use.)
Well I feel dumn! The large disk [DOS][OTHER]. Now the drives boot. Thank you, PTrenholme. I can play with DragonFly. Got all 4 Drives back.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.