Nice, Ubuntu just wiped out my RAID array...

Different hardware = different issues.

Agreed to a certain extent but the principal is the same.
Did you read any documentation as to how ubuntu would behave when you tried to install it on your particular hardware? Does ubuntu fully support your hardware? Have the vendor indicated it should be ok or supplied drivers for your hardware?

Who's moaning?

You are! You haven't asked for help you just made a statement on your bad experience.

Doesn't matter wether it's RAID 0, 1, 5 or JBOD, backups are essential period.

RAID 1 is a back up
 
Agreed to a certain extent but the principal is the same.
Did you read any documentation as to how ubuntu would behave when you tried to install it on your particular hardware? Does ubuntu fully support your hardware? Have the vendor indicated it should be ok or supplied drivers for your hardware?

I didn't read enough apparently.

You are! You haven't asked for help you just made a statement on your bad experience.

No, I'm not, starting the discussion is effectively asking for help if anybody had seen the issue before. Other than that it was a warning as backed up by my last line in the initial post.



RAID 1 is a back up

No, it's redundancy, a backup is a very different thing, maybe you need to do some reading too?
 
The latest Ubuntu also buggered up my HDD when I installed it a few months ago. Bear in mind I am not a complete novice at installing Linux distros, and I had installed all of the previous Ubuntu versions before, and am well familiar with its disk partitioner. I don't have RAID but it still corrupted one of my partitions - a partition I had not told it to touch, and it wasn't even on the same part of the disk where I had told it to make changes.
 
literally, back up is having a plan in place in case things don't go as expected.

Your're reading too much into it.
 
literally, back up is having a plan in place in case things don't go as expected.

Your're reading too much into it.

"Having a plan" has got bugger all to do with redundancy. All redundancy gives you is sustained uptime in the event of a single failure.

To the OP, it seems as if you've found a fairly serious bug in the Ubuntu installer / your hardware combo. Should be fairly easy to report - you've got a good demonstration of the steps required to reproduce and it really should be looked at by some devs. Unfortunately, the devs can't test on every hardware combination and rely on people to report bugs so that they can fix them.
 
Redundancy - having a back up in case the primary fails.

Which part of a RAID1 array is the primary? Both drives are equal partners and as such your comment is invalid.

Any network admin using your idea of a backup would be fired I hope.
 
Try just re-adding the two disks to the RAID array, without attempting to re-format or anything else, looks to me like the array & its data should still be there :)

I'd also avoid the JMicron controller like the plauge, its not a proper hardware solution, and there are plenty of forum posts about odd issues with it when trying to install. You might also try reading Bugzilla, massive post on issues with its drivers here https://launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/57502
For that matter, I don't know why you chose to use it for your RAID array as opposed to the Intel ports (I wouldn't- The Intel drivers are more mature and much better supported both under Linux & Windows), but more importantly I'd try with the CD drive on one of the Intel ports, as I suspect that this is probably somewhere at the root of your issue.

Cheers

-Leezer-
 
That is NOT a hardware RAID array, its a FAKERAID controller, requiring drivers to be installed in Windows for it to work.

YES the Ubuntu installer shouldn't have touched your partitions until you committed to the changes, but it seeing two individual disks has nothing to do with it. No matter what, none of those fakeraid controllers show up under Linux as one drive because all they do is present a drive controller with a funky bios to the driver in Windows - Linux just sees that as a plain old HDD controller.
 
Try just re-adding the two disks to the RAID array, without attempting to re-format or anything else, looks to me like the array & its data should still be there :)

It is, which is why I re-did the process and took photos.

I'd also avoid the JMicron controller like the plauge, its not a proper hardware solution, and there are plenty of forum posts about odd issues with it when trying to install. You might also try reading Bugzilla, massive post on issues with its drivers here https://launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/57502
For that matter, I don't know why you chose to use it for your RAID array as opposed to the Intel ports (I wouldn't- The Intel drivers are more mature and much better supported both under Linux & Windows), but more importantly I'd try with the CD drive on one of the Intel ports, as I suspect that this is probably somewhere at the root of your issue


Cheers

-Leezer-

The DS3 Intel ports don't support RAID as far as I am aware. My optical drives are both IDE.

That is NOT a hardware RAID array, its a FAKERAID controller, requiring drivers to be installed in Windows for it to work.

YES the Ubuntu installer shouldn't have touched your partitions until you committed to the changes, but it seeing two individual disks has nothing to do with it. No matter what, none of those fakeraid controllers show up under Linux as one drive because all they do is present a drive controller with a funky bios to the driver in Windows - Linux just sees that as a plain old HDD controller.

Does not change the fact that it did and continues to change something.
 
no, RAID 1 arent true "backup" what if controller died, then u got no backup :)

true backup method would be OFF site backup like usb external hard drive or NAS device :)

yes i've had RAID 1 failed on me completely twice, lost all data so i dumped raid 1 as i realised it was wrong way for true backup :)
 
RAID 1 is not designed as a backup. it's designed to give resiliency through redundancy. simple as that.

Saying that RAID 1 is a backup is like saying that an Active/Active/Passive (or even an Active/Active) Exchange cluster is backed up because there is redundancy.
 
no, RAID 1 arent true "backup" what if controller died, then u got no backup :)

true backup method would be OFF site backup like usb external hard drive or NAS device :)

yes i've had RAID 1 failed on me completely twice, lost all data so i dumped raid 1 as i realised it was wrong way for true backup :)

Well i can unplug any of my drives from my RAID controller and stick it in the onboard controller and it works fine. Admittedly i have to reset the drive for that controller if i want RAID1 again but i still have access to all the data. Dunno what you did wrong but it wasnt the RAID's fault.
 
Well i can unplug any of my drives from my RAID controller and stick it in the onboard controller and it works fine. Admittedly i have to reset the drive for that controller if i want RAID1 again but i still have access to all the data. Dunno what you did wrong but it wasnt the RAID's fault.

I have a hardware raid card with 2 RAID1 arrays hanging off it. If that card dies, I lose everything, unless I can get exactly the same (not cheap) card to plug everything into. I can't just "stick it in the onboard controller" and have it all work ok.

As has been said before, RAID 1 is not a backup.
 
I have a hardware raid card with 2 RAID1 arrays hanging off it. If that card dies, I lose everything, unless I can get exactly the same (not cheap) card to plug everything into. I can't just "stick it in the onboard controller" and have it all work ok.

As has been said before, RAID 1 is not a backup.

Nice one. I have a hardware RAID card with 2 RAID1 arrays. I can take anyone of OS disks and stick it in the onboard RAID controller and boot from it. When i stick it back in the proper controller it auto rebuilds its self. Give it a go. Thing you may be doing wrong is not having the drivers for the software raid already in the OS.
 
Back
Top Bottom