* blkid and partition problem
@ 2010-05-22 0:28 Tim Bostrom
2010-05-22 2:31 ` Tim Bostrom
2010-05-26 15:16 ` Bill Davidsen
0 siblings, 2 replies; 4+ messages in thread
From: Tim Bostrom @ 2010-05-22 0:28 UTC (permalink / raw)
To: linux-raid
Looking for some help. I'm trying to start my array but just noticed
that somehow my the UUID got assigned to my physical drive and not the
partition. The partition doesn't show up in /dev/. Drive sdm has a
valid partition, but blkid is set on the physical disk.
/dev/sdm is the drive causing issue. The partition is there (see
fdisk output below). It contains data so I'd like to not have to
completely wipe the drive. Is there any option to fix this?
blkid output (see /dev/sdm):
----------------------
/dev/sda1: UUID="dd8018e3-2939-4236-9a63-c36d6df9cf80" TYPE="ext3"
/dev/sda2: UUID="287f5ab6-d463-43a2-a3b2-7bf789dd8744" TYPE="ext3"
/dev/sda3: UUID="336a1681-af86-401d-946e-201ae37780fe" TYPE="swap"
/dev/sdb1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sdc1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sdd1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sde1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sdf1: UUID="649526d8-828a-57b4-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sdg1: UUID="649526d8-828a-57b4-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sdh: UUID="7ea182f5-0c31-3e24-adba-30185bcf511e" LABEL="1"
TYPE="linux_raid_member"
/dev/sdi: UUID="7ea182f5-0c31-3e24-adba-30185bcf511e" LABEL="1"
TYPE="linux_raid_member"
/dev/sdj1: UUID="f911d5fb-8cf2-0015-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/sdk1: UUID="f911d5fb-8cf2-0015-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
/dev/md0: LABEL="teradata" UUID="2e7624ad-f059-4e35-a18a-eb8ffa645d54"
TYPE="ext3"
/dev/sdm: UUID="db34c204-6c5a-7156-28d0-d68913f396a5" LABEL="0"
TYPE="linux_raid_member"
/dev/md1: UUID="eea5390f-8f24-4a82-b899-7924fb126a5b" TYPE="ext3"
fdisk -l /dev/sdm output:
------------------
Disk /dev/sdm: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000f2387
Device Boot Start End Blocks Id System
/dev/sdm1 1 121601 976760001 fd Linux raid autodetect
ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 2010-05-21 16:32 /dev/sda
brw-rw---- 1 root disk 8, 1 2010-05-21 16:32 /dev/sda1
brw-rw---- 1 root disk 8, 2 2010-05-21 16:32 /dev/sda2
brw-rw---- 1 root disk 8, 3 2010-05-21 16:32 /dev/sda3
brw-rw---- 1 root disk 8, 16 2010-05-21 16:32 /dev/sdb
brw-rw---- 1 root disk 8, 17 2010-05-21 16:32 /dev/sdb1
brw-rw---- 1 root disk 8, 32 2010-05-21 16:32 /dev/sdc
brw-rw---- 1 root disk 8, 33 2010-05-21 16:32 /dev/sdc1
brw-rw---- 1 root disk 8, 48 2010-05-21 16:32 /dev/sdd
brw-rw---- 1 root disk 8, 49 2010-05-21 16:32 /dev/sdd1
brw-rw---- 1 root disk 8, 64 2010-05-21 16:32 /dev/sde
brw-rw---- 1 root disk 8, 65 2010-05-21 16:32 /dev/sde1
brw-rw---- 1 root disk 8, 80 2010-05-21 16:32 /dev/sdf
brw-rw---- 1 root disk 8, 81 2010-05-21 16:32 /dev/sdf1
brw-rw---- 1 root disk 8, 96 2010-05-21 16:32 /dev/sdg
brw-rw---- 1 root disk 8, 97 2010-05-21 16:32 /dev/sdg1
brw-rw---- 1 root disk 8, 112 2010-05-21 16:32 /dev/sdh
brw-rw---- 1 root disk 8, 128 2010-05-21 16:32 /dev/sdi
brw-rw---- 1 root disk 8, 144 2010-05-21 16:32 /dev/sdj
brw-rw---- 1 root disk 8, 145 2010-05-21 16:32 /dev/sdj1
brw-rw---- 1 root disk 8, 160 2010-05-21 16:32 /dev/sdk
brw-rw---- 1 root disk 8, 161 2010-05-21 16:32 /dev/sdk1
brw-rw---- 1 root disk 8, 176 2010-05-21 16:32 /dev/sdl
brw-rw---- 1 root disk 8, 192 2010-05-21 16:32 /dev/sdm
Any help is greatly appreciated.
-Tim
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: blkid and partition problem
2010-05-22 0:28 blkid and partition problem Tim Bostrom
@ 2010-05-22 2:31 ` Tim Bostrom
2010-05-22 6:15 ` Luca Berra
2010-05-26 15:16 ` Bill Davidsen
1 sibling, 1 reply; 4+ messages in thread
From: Tim Bostrom @ 2010-05-22 2:31 UTC (permalink / raw)
To: linux-raid
Some more RAID specific info:
/dev/md2:
Version : 0.90
Creation Time : Thu Apr 22 09:46:10 2010
Raid Level : raid5
Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
Raid Devices : 4
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Mon May 17 03:03:01 2010
State : active, degraded, Not Started
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : f911d5fb:8cf20015:ab2fedca:3ef56cfb (local to host
teraserver.teambostrom.com)
Events : 0.7473
Number Major Minor RaidDevice State
0 8 161 0 active sync /dev/sdk1
1 0 0 1 removed
2 0 0 2 removed
3 8 145 3 active sync /dev/sdj1
[Fri May 21-19:31:10] [root@teraserver tbostrom]# mdadm -E /dev/sdm
/dev/sdm:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : db34c204:6c5a7156:28d0d689:13f396a5
Name : 0
Creation Time : Mon Feb 16 17:06:30 2009
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953525032 (931.51 GiB 1000.20 GB)
Array Size : 5860574592 (2794.54 GiB 3000.61 GB)
Used Dev Size : 1953524864 (931.51 GiB 1000.20 GB)
Data Offset : 136 sectors
Super Offset : 8 sectors
State : active
Device UUID : f7446973:f8b8f899:45e53330:004e0ca7
Update Time : Sat Feb 28 14:42:38 2009
Checksum : e23f94ed - correct
Events : 7
Layout : left-symmetric
Chunk Size : 32K
Device Role : Active device 1
Array State : AAAA ('A' == active, '.' == missing)
[Fri May 21-19:31:37] [root@teraserver tbostrom]# mdadm -E /dev/sdj1
/dev/sdj1:
Magic : a92b4efc
Version : 0.90.00
UUID : f911d5fb:8cf20015:ab2fedca:3ef56cfb (local to host
teraserver.teambostrom.com)
Creation Time : Thu Apr 22 09:46:10 2010
Raid Level : raid5
Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
Array Size : 2930279808 (2794.53 GiB 3000.61 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 2
Update Time : Mon May 17 03:03:01 2010
State : clean
Active Devices : 2
Working Devices : 3
Failed Devices : 2
Spare Devices : 1
Checksum : eb4f7c77 - correct
Events : 7473
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 145 3 active sync /dev/sdj1
0 0 8 161 0 active sync /dev/sdk1
1 1 0 0 1 faulty removed
2 2 0 0 2 faulty removed
3 3 8 145 3 active sync /dev/sdj1
4 4 8 193 4 spare
-tim
On Fri, May 21, 2010 at 5:28 PM, Tim Bostrom <tbostrom@gmail.com> wrote:
> Looking for some help. I'm trying to start my array but just noticed
> that somehow my the UUID got assigned to my physical drive and not the
> partition. The partition doesn't show up in /dev/. Drive sdm has a
> valid partition, but blkid is set on the physical disk.
>
> /dev/sdm is the drive causing issue. The partition is there (see
> fdisk output below). It contains data so I'd like to not have to
> completely wipe the drive. Is there any option to fix this?
>
> blkid output (see /dev/sdm):
> ----------------------
> /dev/sda1: UUID="dd8018e3-2939-4236-9a63-c36d6df9cf80" TYPE="ext3"
> /dev/sda2: UUID="287f5ab6-d463-43a2-a3b2-7bf789dd8744" TYPE="ext3"
> /dev/sda3: UUID="336a1681-af86-401d-946e-201ae37780fe" TYPE="swap"
> /dev/sdb1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdc1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdd1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sde1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdf1: UUID="649526d8-828a-57b4-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdg1: UUID="649526d8-828a-57b4-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdh: UUID="7ea182f5-0c31-3e24-adba-30185bcf511e" LABEL="1"
> TYPE="linux_raid_member"
> /dev/sdi: UUID="7ea182f5-0c31-3e24-adba-30185bcf511e" LABEL="1"
> TYPE="linux_raid_member"
> /dev/sdj1: UUID="f911d5fb-8cf2-0015-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdk1: UUID="f911d5fb-8cf2-0015-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/md0: LABEL="teradata" UUID="2e7624ad-f059-4e35-a18a-eb8ffa645d54"
> TYPE="ext3"
> /dev/sdm: UUID="db34c204-6c5a-7156-28d0-d68913f396a5" LABEL="0"
> TYPE="linux_raid_member"
> /dev/md1: UUID="eea5390f-8f24-4a82-b899-7924fb126a5b" TYPE="ext3"
>
>
> fdisk -l /dev/sdm output:
> ------------------
> Disk /dev/sdm: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x000f2387
>
> Device Boot Start End Blocks Id System
> /dev/sdm1 1 121601 976760001 fd Linux raid autodetect
>
>
> ls -l /dev/sd*
> brw-rw---- 1 root disk 8, 0 2010-05-21 16:32 /dev/sda
> brw-rw---- 1 root disk 8, 1 2010-05-21 16:32 /dev/sda1
> brw-rw---- 1 root disk 8, 2 2010-05-21 16:32 /dev/sda2
> brw-rw---- 1 root disk 8, 3 2010-05-21 16:32 /dev/sda3
> brw-rw---- 1 root disk 8, 16 2010-05-21 16:32 /dev/sdb
> brw-rw---- 1 root disk 8, 17 2010-05-21 16:32 /dev/sdb1
> brw-rw---- 1 root disk 8, 32 2010-05-21 16:32 /dev/sdc
> brw-rw---- 1 root disk 8, 33 2010-05-21 16:32 /dev/sdc1
> brw-rw---- 1 root disk 8, 48 2010-05-21 16:32 /dev/sdd
> brw-rw---- 1 root disk 8, 49 2010-05-21 16:32 /dev/sdd1
> brw-rw---- 1 root disk 8, 64 2010-05-21 16:32 /dev/sde
> brw-rw---- 1 root disk 8, 65 2010-05-21 16:32 /dev/sde1
> brw-rw---- 1 root disk 8, 80 2010-05-21 16:32 /dev/sdf
> brw-rw---- 1 root disk 8, 81 2010-05-21 16:32 /dev/sdf1
> brw-rw---- 1 root disk 8, 96 2010-05-21 16:32 /dev/sdg
> brw-rw---- 1 root disk 8, 97 2010-05-21 16:32 /dev/sdg1
> brw-rw---- 1 root disk 8, 112 2010-05-21 16:32 /dev/sdh
> brw-rw---- 1 root disk 8, 128 2010-05-21 16:32 /dev/sdi
> brw-rw---- 1 root disk 8, 144 2010-05-21 16:32 /dev/sdj
> brw-rw---- 1 root disk 8, 145 2010-05-21 16:32 /dev/sdj1
> brw-rw---- 1 root disk 8, 160 2010-05-21 16:32 /dev/sdk
> brw-rw---- 1 root disk 8, 161 2010-05-21 16:32 /dev/sdk1
> brw-rw---- 1 root disk 8, 176 2010-05-21 16:32 /dev/sdl
> brw-rw---- 1 root disk 8, 192 2010-05-21 16:32 /dev/sdm
>
>
>
> Any help is greatly appreciated.
>
> -Tim
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: blkid and partition problem
2010-05-22 2:31 ` Tim Bostrom
@ 2010-05-22 6:15 ` Luca Berra
0 siblings, 0 replies; 4+ messages in thread
From: Luca Berra @ 2010-05-22 6:15 UTC (permalink / raw)
To: linux-raid
On Fri, May 21, 2010 at 07:31:50PM -0700, Tim Bostrom wrote:
>/dev/sdm:
> Magic : a92b4efc
> Version : 1.2
....
>/dev/sdj1:
> Magic : a92b4efc
> Version : 0.90.00
probably you have two superblocks on /dev/sdm
one at the beginning of sdm version 1.2, and one at the end of sdm1
(version 0.90) and md finds the first one.
you should be able to fix that by issuing
mdadm --zero-superblock /dev/sdm
partx -a /dev/sdm
mdadm /dev/md2 -a /dev/sdm1
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: blkid and partition problem
2010-05-22 0:28 blkid and partition problem Tim Bostrom
2010-05-22 2:31 ` Tim Bostrom
@ 2010-05-26 15:16 ` Bill Davidsen
1 sibling, 0 replies; 4+ messages in thread
From: Bill Davidsen @ 2010-05-26 15:16 UTC (permalink / raw)
To: Tim Bostrom; +Cc: linux-raid, Neil Brown
Tim Bostrom wrote:
> Looking for some help. I'm trying to start my array but just noticed
> that somehow my the UUID got assigned to my physical drive and not the
> partition. The partition doesn't show up in /dev/. Drive sdm has a
> valid partition, but blkid is set on the physical disk.
>
> /dev/sdm is the drive causing issue. The partition is there (see
> fdisk output below). It contains data so I'd like to not have to
> completely wipe the drive. Is there any option to fix this?
>
> blkid output (see /dev/sdm):
> ----------------------
> /dev/sda1: UUID="dd8018e3-2939-4236-9a63-c36d6df9cf80" TYPE="ext3"
> /dev/sda2: UUID="287f5ab6-d463-43a2-a3b2-7bf789dd8744" TYPE="ext3"
> /dev/sda3: UUID="336a1681-af86-401d-946e-201ae37780fe" TYPE="swap"
> /dev/sdb1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdc1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdd1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sde1: UUID="cdaba8bd-8094-3c6a-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdf1: UUID="649526d8-828a-57b4-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdg1: UUID="649526d8-828a-57b4-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdh: UUID="7ea182f5-0c31-3e24-adba-30185bcf511e" LABEL="1"
> TYPE="linux_raid_member"
> /dev/sdi: UUID="7ea182f5-0c31-3e24-adba-30185bcf511e" LABEL="1"
> TYPE="linux_raid_member"
> /dev/sdj1: UUID="f911d5fb-8cf2-0015-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/sdk1: UUID="f911d5fb-8cf2-0015-ab2f-edca3ef56cfb" TYPE="linux_raid_member"
> /dev/md0: LABEL="teradata" UUID="2e7624ad-f059-4e35-a18a-eb8ffa645d54"
> TYPE="ext3"
> /dev/sdm: UUID="db34c204-6c5a-7156-28d0-d68913f396a5" LABEL="0"
> TYPE="linux_raid_member"
> /dev/md1: UUID="eea5390f-8f24-4a82-b899-7924fb126a5b" TYPE="ext3"
>
>
> fdisk -l /dev/sdm output:
> ------------------
> Disk /dev/sdm: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x000f2387
>
> Device Boot Start End Blocks Id System
> /dev/sdm1 1 121601 976760001 fd Linux raid autodetect
>
>
> ls -l /dev/sd*
> brw-rw---- 1 root disk 8, 0 2010-05-21 16:32 /dev/sda
> brw-rw---- 1 root disk 8, 1 2010-05-21 16:32 /dev/sda1
> brw-rw---- 1 root disk 8, 2 2010-05-21 16:32 /dev/sda2
> brw-rw---- 1 root disk 8, 3 2010-05-21 16:32 /dev/sda3
> brw-rw---- 1 root disk 8, 16 2010-05-21 16:32 /dev/sdb
> brw-rw---- 1 root disk 8, 17 2010-05-21 16:32 /dev/sdb1
> brw-rw---- 1 root disk 8, 32 2010-05-21 16:32 /dev/sdc
> brw-rw---- 1 root disk 8, 33 2010-05-21 16:32 /dev/sdc1
> brw-rw---- 1 root disk 8, 48 2010-05-21 16:32 /dev/sdd
> brw-rw---- 1 root disk 8, 49 2010-05-21 16:32 /dev/sdd1
> brw-rw---- 1 root disk 8, 64 2010-05-21 16:32 /dev/sde
> brw-rw---- 1 root disk 8, 65 2010-05-21 16:32 /dev/sde1
> brw-rw---- 1 root disk 8, 80 2010-05-21 16:32 /dev/sdf
> brw-rw---- 1 root disk 8, 81 2010-05-21 16:32 /dev/sdf1
> brw-rw---- 1 root disk 8, 96 2010-05-21 16:32 /dev/sdg
> brw-rw---- 1 root disk 8, 97 2010-05-21 16:32 /dev/sdg1
> brw-rw---- 1 root disk 8, 112 2010-05-21 16:32 /dev/sdh
> brw-rw---- 1 root disk 8, 128 2010-05-21 16:32 /dev/sdi
> brw-rw---- 1 root disk 8, 144 2010-05-21 16:32 /dev/sdj
> brw-rw---- 1 root disk 8, 145 2010-05-21 16:32 /dev/sdj1
> brw-rw---- 1 root disk 8, 160 2010-05-21 16:32 /dev/sdk
> brw-rw---- 1 root disk 8, 161 2010-05-21 16:32 /dev/sdk1
> brw-rw---- 1 root disk 8, 176 2010-05-21 16:32 /dev/sdl
> brw-rw---- 1 root disk 8, 192 2010-05-21 16:32 /dev/sdm
>
>
>
> Any help is greatly appreciated.
>
Let me propose a cause for this. Assume that after partitioning sdm you
created an array, and when giving the members you typed /dev/sdm rather
than /dev/sdm1. Sound possible? You might try assembling an array with
the members and give /dev/sdm instead of /dev/sdm1, specifying read-only
to prevent issues.
My reasoning is that using the whole disk you would write over the UUID
on the partition, but the partition table might be safe.
Corrections welcome.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-05-26 15:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-22 0:28 blkid and partition problem Tim Bostrom
2010-05-22 2:31 ` Tim Bostrom
2010-05-22 6:15 ` Luca Berra
2010-05-26 15:16 ` Bill Davidsen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).