You are not logged in.
Pages: 1
Gparted lists the active devices when opened in arch.
This is always true in HDD boot of the system which lista all sd, hdd, and raid items.
However, when booted into raid0 dev md0, gparted does not list md0 as a device but does list the component devices of the raid array.
The md0 array can be mounted in /mnt with the normal command...mount /dev/md0 /mnt/md...
The array is assembled from two separate CF to Sata adapters using either two 8GB or two 16GB CF cards.
Either of the arrays when booted display the same gparted anomaly, showing up in HDD when queried and not being discovered when booted in raid0.
Other than this strange behavior, the raid arrays perform as expected.
As outlined above, this occurs in both raid0 arrays.
Gparted reports that the array is identified as .../dev/md/0....no such device. Addressing the array as md0 (not md/0) permits the array to be mounted in /mnt/md when the array is the OS device as described previously
Thus gparted identifies the array correctly from HDD boots but not from raid0 array boots.
No further clues.............EDIT: x86_64 Latest kernel
Last edited by lilsirecho (2011-07-13 16:09:03)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Pages: 1