Not personally having followed recent development cycles - would this be informative.?
The five biggest changes in Ubuntu 15.04, Vivid Vervet
from:
Type: Posts; User: ronparent; Keyword(s):
Not personally having followed recent development cycles - would this be informative.?
The five biggest changes in Ubuntu 15.04, Vivid Vervet
from:
You have failed to state what type of raid - ie software raid or fakeraid. Each can have their own problems.
My own experience of the boot dropping to an initramfs prompt was when the dmraid...
You are right, the raid 5 partition would not likely survive the MB swap. The 12.04 should see the raid 5? Try querying it from a live cd terminal with the command - sudo dmraid -ay. The response...
dyno:
This is probably your problem. Once written to a disk by the MB raid bios the raid designation persistently remains in as metadata on the drive until explicitly erased. To erase it, boot...
the /dev/dm-0 is generally your first raid array - it wouldn't have a file structure - so the statement is correct. But why is the system trying to mount it?
What is the output of 'sudo blkid'....
+1
I browse the forum from time to time and jump in whenever I can help. In the last several months Darko is there first with the right answers. What more can you ask? I definitely and...
The way a raid0 works is by having a raid bios on the MB use two disks as one by writing alternate sectors on each of the drive. This speeds up data reads and writes but distributed data between the...
I've been running the same MB both with the built in APU as well with a separate Radeon card with no problems for several months, and with the default drivers. My initial problems were with...
From the server forum:
You may get a better answer from the Servers forum. Although unfamiliar with the specific hardware, it appears to emulate a Windows 'fakeRAID' protocol. If the case the raid...
I have experience the same problem since early in the testing cycle. I searched through a bug report for this problem and found a suggested work-around from one of the recent posts that suggested...
There are other issues, but, the primary one is that if you want to 'un-raid' the drives you have to erase the raid meta data on them. Otherwise they continue to be seen as raid. I would wait for...
For a raid0 especially, it is recommended that both dives be identical!
Congratulations. It is not necessary to run a dmraid command on boot since the raid is made active with the boot.
There is apparently an issue with raid 1 in that apparently data corruption one...
Try installing dmraid. Its installation should permit the raid partitions to be seen and be mountable. The dmraid program is not installed by default by Ubuntu if Ubuntu is installed to any partition...
Lots of luck. I did get 12.10 working on a raid0 - in a round-about way. The 12.10 release note allude to problems with raid installations in that an alternate cd installation is not available! I did...
So far, so good! Everything look intact.
Here is where it gets tacky. With my system, in my attempts to install 12.10, the install process died at a point that I didn't have an operable system. We...
I can't tell from your narrative what you have left after trying your install.
Just to put things in perspective, you have what the Linux community calls a fakeRAID. It is a software raid setup...
A true fakeRAID array is usually accessed in a Linux system with dmraid rather than a driver per se. If dmraid is not already installed you can install it and in a terminal enter the command:
Note...
It is. Just remember that the metadata is persistent and must be erased to completely clear the raid. That would be done prior to uninstalling dmraid.
In a live cd session, open a terminal and...
Yes - I have actually done it!
You should be able to at least get the raid activated after boot by typing -
In any case you are probably operating in a situation beyond the scope of the...
Your install is on /dev/mapper/isw_bhiddahgdf_ARRAY6? This being the case, it appears the boot loader should be on /dev/mapper/isw_bhiddahgdf_ARRAY. And that is where the Windows boot loader is (ie ...
brucecode - the commands oldfred gives above are correct - my memory was faulty. The raid bios doesn't have to be turned on for drives to be recognized as raid, simply the presence of the metadata...
You apparently got your hands on a disk with raid metadata. If so, it is persistent and has to be erased to be able to use the drive normally. Open a terminal and write: assuming sdb is the new...
1st try a 'sudo grub-uodate' in a terminal. If it finds your new install, fine. Otherwise we go from there.
If a bios based RAID, what is the status of the RAID set in the RAID bios on boot? Are the /dev/mapper symbolic links present after boot? If the RAID at least appears functional in the RAID bios look...