You are not logged in.
Posting blkid from present boot into linux 3.0 showing a different uuid for the /dev/md0 than those for the raid devices. It is also different from what was given to it in the .iso install, therein it was the same as the two raid devices (non-sub uuid).
I was under the impression uuid was permanent for a given device........
sh-4.2# blkid
/dev/sdd2: UUID="4a16e80d-1cdf-4461-aed4-689350c2c0b4" TYPE="swap"
/dev/sdc2: UUID="a8c739b8-af37-b8fb-9c51-c5618c4d2545" UUID_SUB="27af2a91-1121-dcc9-1c9b-add0fc16678c" LABEL="archiso:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="a8c739b8-af37-b8fb-9c51-c5618c4d2545" UUID_SUB="ad29fc37-8741-3258-a383-1b336dcd3b03" LABEL="archiso:0" TYPE="linux_raid_member"
/dev/sda1: LABEL="ARCH_201108" TYPE="udf"
/dev/sdc1: UUID="b1a189f4-6708-437d-a335-d4fd9cc6ee55" TYPE="swap"
/dev/sdb1: UUID="06652432-dc62-4e88-86c3-9b301a1ddf74" TYPE="ext2"
/dev/sdd1: UUID="909993fb-bc95-4b3b-999e-15e6953a564a" TYPE="ext2"
/dev/sdd3: UUID="0e55cd32-ad2e-44a9-92d2-6f089176bf1a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdd4: UUID="5b9804e6-0076-47d4-abd4-dfd300907013" SEC_TYPE="ext2" TYPE="ext3"
/dev/sde1: UUID="909993fb-bc95-4b3b-999e-15e6953a564a" TYPE="ext2"
/dev/sde2: UUID="4a16e80d-1cdf-4461-aed4-689350c2c0b4" TYPE="swap"
/dev/sde3: UUID="d4df3e26-4890-4cbc-ac71-4919c9e54dfc" TYPE="ext3"
/dev/sde4: UUID="5b9804e6-0076-47d4-abd4-dfd300907013" TYPE="ext3"
/dev/md0: UUID="21051486-3736-4e32-ad55-7fd2fbbb7fe2" TYPE="ext3"
sh-4.2#
EDIT: In ramfs prompt during boot attempt of the new install blkid shows no /dev/md0 listing which suggests that mdadm has been ignored for raid but the two raid devices are correctly set up with uuid and raid nomenclature. Only /dev/md0 is missing and its uuid. How can this be?
Last edited by lilsirecho (2011-10-25 15:56:21)
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
Opened /etc/mdadm.conf in this hdd boot-up and it shows the uuid of the two raid devices but the name of the /dev/md0 has been corrupted by the .iso:
ARRAY /dev/md/archiso:0 metadata=1.2 name=archiso:0 UUID=a8c739b8:af37b8fb:9c51c561:8c4d2545How does this happen?
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
Further info on the raid0 components:
sh-4.2# mdadm -E /dev/md0
mdadm: No md superblock detected on /dev/md0.
sh-4.2# mdadm -D /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sun Oct 23 03:44:15 2011
Raid Level : raid0
Array Size : 31032320 (29.59 GiB 31.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun Oct 23 03:44:15 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 512K
Name : archiso:0
UUID : a8c739b8:af37b8fb:9c51c561:8c4d2545
Events : 0
Number Major Minor RaidDevice State
0 8 18 0 active sync /dev/sdb2
1 8 34 1 active sync /dev/sdc2
sh-4.2# cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 sdb2[0] sdc2[1]
31032320 blocks super 1.2 512k chunks
unused devices: <none>
sh-4.2# mdadm -E /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : a8c739b8:af37b8fb:9c51c561:8c4d2545
Name : archiso:0
Creation Time : Sun Oct 23 03:44:15 2011
Raid Level : raid0
Raid Devices : 2
Avail Dev Size : 31033012 (14.80 GiB 15.89 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : ad29fc37:87413258:a3831b33:6dcd3b03
Update Time : Sun Oct 23 03:44:15 2011
Checksum : c8303fb - correct
Events : 0
Chunk Size : 512K
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)
sh-4.2# mdadm -E /dev/sdc2
/dev/sdc2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : a8c739b8:af37b8fb:9c51c561:8c4d2545
Name : archiso:0
Creation Time : Sun Oct 23 03:44:15 2011
Raid Level : raid0
Raid Devices : 2
Avail Dev Size : 31033012 (14.80 GiB 15.89 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 27af2a91:1121dcc9:1c9badd0:fc16678c
Update Time : Sun Oct 23 03:44:15 2011
Checksum : fe18ca09 - correct
Events : 0
Chunk Size : 512K
Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing)
sh-4.2# This data obtained in HDD boot-up. Interesting that /devmd0 has differing superblock reports.
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
Performed the dd command on two 16gb cf drives having raid0 Archlinux bootable to a pair of new 16GB drives successfully. These then contained raid0 bootable kernel26v39.
Upon booting up, performed ....pacman -Syu..... and downloaded 316 packages including the latest Linux. This took around 2 1/2 hours. These were installed to /dev/md0 in the raid0 array. The conflicts were resolved before install ran.
After install completed, rebooted. The arch prompt appeared and loading began but /dev/md0 required fsck.
Rebooted to another arch system and performed a long e2fsck which resulted in a clean /dev/md0.
Rebooted into the raid0 pair and was successful in reaching xfce4 Desktop.
The procedure was performed weeks ago with a fauilure so I can only assume that the latest Linux-3.0.7-1 corrected the difficulty or corrupted downloads introduced the failed attempt.
The combo in raid0 boots in ten seconds as does the original raid0 using kernel26.
Hdparm with these 16gb devices reports a more sedate 122 MB/s for /dev/md0.
Thus, the upgrade is now history!
x86_64
Last edited by lilsirecho (2011-10-29 04:30:47)
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