FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 09-24-2011, 10:26 AM
martin f krafft
 
Default degraded RAID array on squeeze

also sprach Milos Negovanovic <milos.negovanovic@gmail.com> [2011.09.24.1134 +0200]:
> For details see host's SYSLOG (default: /var/log/syslog).

And?

Please try to provide all relevant information up front. It takes
a lot of effort of others if we have to pull all information out of
your nose.

--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems

"it is dangerous to be right when the government is wrong."
-- voltaire
 
Old 09-24-2011, 10:28 AM
martin f krafft
 
Default degraded RAID array on squeeze

also sprach Milos Negovanovic <milos.negovanovic@gmail.com> [2011.09.24.1143 +0200]:
> Hmmm this line looks suspicious:
> /dev/sdb3: LABEL="home" UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"
>
> Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID
> partition.

From the partition. Is the partition mounted by any chance?

Also, it is a common misunderstanding that fdisk knows anything
about RAID. What you are talking about is the partition type setting
0xfd, which has not been a requirement for years (only needed for
kernel-level auto-assembly, which is deprecated, not if md is loaded
by module).

--
martin | http://madduck.net/ | http://two.sentenc.es/

"the question of whether computers can think
is like the question of whether submarines can swim."
-- edsgar w. dijkstra

spamtraps: madduck.bogus@madduck.net
 
Old 09-24-2011, 10:30 AM
Andrew McGlashan
 
Default degraded RAID array on squeeze

Hi Milos,

Milos Negovanovic wrote:
root@micro ~ # blkid


Edited the following....

/dev/sda3: UUID="9bca8a2b-2283-9bed-c8fe-9f89b0860cb2" LABEL="micro:2" TYPE="linux_raid_member"
/dev/sdb3: LABEL="home" UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"


root@micro ~ # mdadm --detail --scan
ARRAY /dev/md/2 metadata=1.2 name=micro:2
UUID=9bca8a2b:22839bed:c8fe9f89:b0860cb2



Hmmm this line looks suspicious:
/dev/sdb3: LABEL="home" UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"


Yes, very suspicious.

How about the output of:

df -Tah


Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID
partition.


I expect blkid gets its details from /dev file system area and partprobe
will update entries there for new or changed disks / partitions.


If /dev/sdb3 is not actually your /home file system [or used otherwise],
then I would be deleting the partition, re-adding it as expected, then
do partprobe and blkid again to check it looks happy. Then hopefully
you can add /dev/sdb3 back into the md2 RAID1 device successfully.


If the disk is failing as it appears from the smartctl message ... then
I also concur that you should look at replacing the disk ASAP.


--
Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4E7DB12E.2030904@affinityvision.com.au">http://lists.debian.org/4E7DB12E.2030904@affinityvision.com.au
 
Old 09-24-2011, 11:05 AM
Milos Negovanovic
 
Default degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 08:30:06PM +1000, Andrew McGlashan wrote:
> Hi Milos,
>
> Milos Negovanovic wrote:
> >root@micro ~ # blkid
>
> Edited the following....
>
> >/dev/sda3: UUID="9bca8a2b-2283-9bed-c8fe-9f89b0860cb2"
> >LABEL="micro:2" TYPE="linux_raid_member" /dev/sdb3: LABEL="home"
> >UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"
> >
> >root@micro ~ # mdadm --detail --scan
> >ARRAY /dev/md/2 metadata=1.2 name=micro:2
> >UUID=9bca8a2b:22839bed:c8fe9f89:b0860cb2
>
> >Hmmm this line looks suspicious:
> >/dev/sdb3: LABEL="home" UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"
>
> Yes, very suspicious.
>
> How about the output of:
>
> df -Tah

root@micro ~ # df -Tah
Filesystem Type Size Used Avail Use% Mounted on
/dev/md1 ext4 28G 587M 26G 3% /
tmpfs tmpfs 12G 8.0K 12G 1% /lib/init/rw
proc proc 0 0 0 - /proc
sysfs sysfs 0 0 0 - /sys
udev tmpfs 12G 180K 12G 1% /dev
tmpfs tmpfs 12G 0 12G 0% /dev/shm
devpts devpts 0 0 0 - /dev/pts
/dev/md2 ext4 1.4T 2.0G 1.3T 1% /var
none cgroup 0 0 0 - /cgroup

>
> >Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID
> >partition.
>
> I expect blkid gets its details from /dev file system area and
> partprobe will update entries there for new or changed disks /
> partitions.
>
> If /dev/sdb3 is not actually your /home file system [or used
> otherwise], then I would be deleting the partition, re-adding it as
> expected, then do partprobe and blkid again to check it looks happy.
> Then hopefully you can add /dev/sdb3 back into the md2 RAID1 device
> successfully.

Its not used as /home at all ... Ive tried deleting partition with
parted and re-creating it, setting the raid flag on it ... after
running partprobe and blkid, output is the same, also error when adding
it into RAID array is the same? Anyone know how to change the TYPE of
the partition as seen by the blkid? This is something installer has done
so there must be a way!

>
> If the disk is failing as it appears from the smartctl message ...
> then I also concur that you should look at replacing the disk ASAP.

Ill try to fix the RAID first, Ive seen crappy drives going into
temporary spasm and everything being OK after . I think my problem is
due to mdadm not seeing /dev/sdb3 as valid RAID partition, so Ill try to
fix that first.

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924110513.GG2602@googlemail.com">http://lists.debian.org/20110924110513.GG2602@googlemail.com
 
Old 09-24-2011, 11:46 AM
martin f krafft
 
Default degraded RAID array on squeeze

also sprach Milos Negovanovic <milos.negovanovic@gmail.com> [2011.09.24.1305 +0200]:
> > If the disk is failing as it appears from the smartctl message ...
> > then I also concur that you should look at replacing the disk ASAP.
>
> Ill try to fix the RAID first, Ive seen crappy drives going into
> temporary spasm and everything being OK after . I think my problem is
> due to mdadm not seeing /dev/sdb3 as valid RAID partition, so Ill try to
> fix that first.

You could try to /dev/zero it with dd and then to re-add it, BUT
FIRST MAKE SURE THERE ARE NO DATA ON THERE.

Can you mount /dev/sdb3 ?

--
martin | http://madduck.net/ | http://two.sentenc.es/

"wovon man nicht sprechen kann, darüber muß man schweigen."
-- wittgenstein

spamtraps: madduck.bogus@madduck.net
 
Old 09-24-2011, 11:54 AM
Tom H
 
Default degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 7:05 AM, Milos Negovanovic
<milos.negovanovic@gmail.com> wrote:
> On Sat, Sep 24, 2011 at 08:30:06PM +1000, Andrew McGlashan wrote:
>> Milos Negovanovic wrote:
>>>
>>> Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID
>>> partition.
>>
>> I expect blkid gets its details from /dev file system area and
>> partprobe will update entries there for new or changed disks /
>> partitions.
>>
>> If /dev/sdb3 is not actually your /home file system [or used
>> otherwise], then I would be deleting the partition, re-adding it as
>> expected, then do partprobe and blkid again to check it looks happy.
>> Then hopefully you can add /dev/sdb3 back into the md2 RAID1 device
>> successfully.
>
> Its not used as /home at all ... Ive tried deleting partition with
> parted and re-creating it, setting the raid flag on it ... after
> running partprobe and blkid, output is the same, also error when adding
> it into RAID array is the same? Anyone know how to change the TYPE of
> the partition as seen by the blkid?

If you don't pass "-c /dev/null" to blkid, it uses its cached data.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAOdo=SwLbu7-P=cwS2AVb_EnnCW4V6p7KWaRVzGnGLym8D1_XQ@mail.gmail. com">http://lists.debian.org/CAOdo=SwLbu7-P=cwS2AVb_EnnCW4V6p7KWaRVzGnGLym8D1_XQ@mail.gmail. com
 
Old 09-24-2011, 02:20 PM
Milos Negovanovic
 
Default degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 01:46:21PM +0200, martin f krafft wrote:
> also sprach Milos Negovanovic <milos.negovanovic@gmail.com> [2011.09.24.1305 +0200]:
> > > If the disk is failing as it appears from the smartctl message ...
> > > then I also concur that you should look at replacing the disk ASAP.
> >
> > Ill try to fix the RAID first, Ive seen crappy drives going into
> > temporary spasm and everything being OK after . I think my problem is
> > due to mdadm not seeing /dev/sdb3 as valid RAID partition, so Ill try to
> > fix that first.
>
> You could try to /dev/zero it with dd and then to re-add it, BUT
> FIRST MAKE SURE THERE ARE NO DATA ON THERE.
>
> Can you mount /dev/sdb3 ?
>

Ive dd-ed /dev/sdb3 and that did the trick! I was able to re-add the
partition to RAID array.

root@micro ~ # blkid -c /dev/null
/dev/sda1: UUID="ea2de79b-ee83-1c72-35ee-44eb048206bc" LABEL="micro:0" TYPE="linux_raid_member"
/dev/sda2: UUID="de73322a-76df-fa34-7b38-44b155266292" LABEL="micro:1" TYPE="linux_raid_member"
/dev/sda3: UUID="9bca8a2b-2283-9bed-c8fe-9f89b0860cb2" LABEL="micro:2" TYPE="linux_raid_member"
/dev/sdb1: UUID="ea2de79b-ee83-1c72-35ee-44eb048206bc" LABEL="micro:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="de73322a-76df-fa34-7b38-44b155266292" LABEL="micro:1" TYPE="linux_raid_member"
/dev/sdb3: UUID="9bca8a2b-2283-9bed-c8fe-9f89b0860cb2" LABEL="micro:2" TYPE="linux_raid_member"
/dev/md0: UUID="16453ab8-e70a-48f3-a435-649505897d2f" TYPE="swap"
/dev/md1: UUID="3810bb4b-12be-4e7a-9818-8503f90aa96f" TYPE="ext4"
/dev/md2: UUID="3c69773f-5595-4e29-9c8e-66bfbdfd4422" TYPE="ext4"

root@micro ~ # cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sdb3[2] sda3[0]
1424121720 blocks super 1.2 [2/1] [U_]
[>....................] recovery = 0.9%
(13493312/1424121720) finish=307.6min speed=76413K/sec

md1 : active raid1 sda2[0] sdb2[1]
29295544 blocks super 1.2 [2/2] [UU]

md0 : active (auto-read-only) raid1
sda1[0] sdb1[1]
11716536 blocks super 1.2 [2/2] [UU]

unused devices: <none>

Thanks to everyone for useful suggestions!

Ill let it rebuild parity and then Ill reboot the server just to make
sure everything is OK.

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924142031.GA2593@googlemail.com">http://lists.debian.org/20110924142031.GA2593@googlemail.com
 
Old 09-24-2011, 02:31 PM
Andrew McGlashan
 
Default degraded RAID array on squeeze

Milos Negovanovic wrote:

Ive dd-ed /dev/sdb3 and that did the trick! I was able to re-add the
partition to RAID array.


Great, but keep an eye on that disk. I would definitely be wanting to
ensure it's integrity ... at the very least make sure you have good
backups. I'm sure you know that simply using RAID is not a substitute
for having suitable backups.


Cheers
--
Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4E7DE9D1.1060801@affinityvision.com.au">http://lists.debian.org/4E7DE9D1.1060801@affinityvision.com.au
 

Thread Tools




All times are GMT. The time now is 10:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org