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 05-02-2008, 12:45 PM
Dexter Filmore
 
Default software raid5 array degrades from initrd

So here's the story:

Software raid5 on debian etch with 2.6.22 kernel from backports.

Hardware: Asus K8N-E Deluxe, nForce3/250Gb chipset.
Has:
2 sATA ports from the nF3 (sata_nv)
4 sATA ports from an onboard Silicon Image 3114 (sata_sil)
4 sATA ports from an PCI controller, Silicon Image 3114, too.

I used to run this setup:
4x Samsung Spinpoint 250GB on the onboard 3114, started by initrd. All fine.

Now I upgraded to 5x500GB. Built the array degraded on the 4 PCI controller
ports, transferred all the data, then moved the 4x500 to the onboard 3114.

Now I added the fifth disk and --add'ed it to the array and it synced.

I thought all was fine. Wrong.

Upon reboot, the 5th disk that now sat on the PCI controller alone was kicked
from the array for being non fresh. I suspected a shutdown problem, found one
with 2.6.22 and the shutdown utility, fixed that and resynced.
Next reboot: same story.
So I synced, booted a live CD (knoppix) and checked out mdadm -E in regard of
the event count. All ok. So no shutdown problem.
I even moved the fifth disk from the PCI controller to the NV controller on
the board.

Two resyncs later I decided to reconf mdadm to *not* start from the initrd and
not auto-assemble at boot time.
I then assembled the array manually and tadaa, all fine, array works and is
synced.

Now: what's going on here? both onboard 3114 and pci 3114 controllers are
handled by the same kernel module, so either initrd sees all or none.
Why would it not wanna see the 5th disk from initrd, but when I manually
assemble, it's fine?

Dex


--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-02-2008, 01:19 PM
martin f krafft
 
Default software raid5 array degrades from initrd

also sprach Dexter Filmore <Dexter.Filmore@gmx.de> [2008.05.02.1345 +0100]:
> Two resyncs later I decided to reconf mdadm to *not* start from
> the initrd and not auto-assemble at boot time. I then assembled
> the array manually and tadaa, all fine, array works and is synced.
>
> Now: what's going on here? both onboard 3114 and pci 3114
> controllers are handled by the same kernel module, so either
> initrd sees all or none. Why would it not wanna see the 5th disk
> from initrd, but when I manually assemble, it's fine?

Please provide full logs of what happens when the initrd script
runs.

Also, please provide the output of

/usr/share/bug/mdadm/script 3>&1

run as root.

--
.'`. martin f. krafft <madduck@debian.org>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems

half a bee, philosophically, must ipso facto half not be.
but half the bee has got to be, vis-a-vis its entity. you see?
but can a bee be said to be or not to be an entire bee,
when half the bee is not a bee, due to some ancient injury?
-- monty python
 
Old 05-02-2008, 08:47 PM
Alex Samad
 
Default software raid5 array degrades from initrd

On Fri, May 02, 2008 at 02:45:04PM +0200, Dexter Filmore wrote:
> So here's the story:
[snip]
> Now: what's going on here? both onboard 3114 and pci 3114 controllers are
> handled by the same kernel module, so either initrd sees all or none.
> Why would it not wanna see the 5th disk from initrd, but when I manually
> assemble, it's fine?
>
> Dex
Used to have a similar problem.

look in /etc/mdadm/mdadm.conf make sure the arrays is defined properly
in there also make sure you have
DEVICE partitions

or at least have it pointing to all the right devices/partitions

then update your initramfs

from memory the problem i had was I had not fully specified my array in
/etc/mdadm/mdadm.conf. Another way to put it they array information in
the initram fs was from an old array specification and only part of the
array would get started.

another thing you can try is entering busybox during the initrd process
just before it starts/load /

alex

>
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
> w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
> b++(+++) DI+++ D- G++ e* h>++ r* y?
> ------END GEEK CODE BLOCK------
>
> http://www.vorratsdatenspeicherung.de
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

--
"Just remember it's the birds that's supposed to suffer, not the hunter."

- George W. Bush
01/22/2004
Roswell, NM
advising quail hunter and New Mexico Sen. Pete Domenici
 
Old 05-03-2008, 04:23 PM
Dexter Filmore
 
Default software raid5 array degrades from initrd

Am Freitag, 2. Mai 2008 15:19:02 schrieb martin f krafft:
> also sprach Dexter Filmore <Dexter.Filmore@gmx.de> [2008.05.02.1345 +0100]:
> > Two resyncs later I decided to reconf mdadm to *not* start from
> > the initrd and not auto-assemble at boot time. I then assembled
> > the array manually and tadaa, all fine, array works and is synced.
> >
> > Now: what's going on here? both onboard 3114 and pci 3114
> > controllers are handled by the same kernel module, so either
> > initrd sees all or none. Why would it not wanna see the 5th disk
> > from initrd, but when I manually assemble, it's fine?
>
> Please provide full logs of what happens when the initrd script
> runs.

initrd has its own log...?
(Been running Slackware witrh custom kernels for years, initrd = mystery to
me)
If you mean the dmesg part, here it comes:

sd 6:0:0:0: [sdb] Synchronizing SCSI cache
sd 6:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
sd 6:0:0:0: [sdb] Stopping disk
sd 6:0:0:0: [sdb] START_STOP FAILED
sd 6:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
ata8.00: disabled
sd 7:0:0:0: [sdc] Synchronizing SCSI cache
sd 7:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
sd 7:0:0:0: [sdc] Stopping disk
sd 7:0:0:0: [sdc] START_STOP FAILED
sd 7:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
ata9.00: disabled
sd 8:0:0:0: [sdd] Synchronizing SCSI cache
sd 8:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
sd 8:0:0:0: [sdd] Stopping disk
sd 8:0:0:0: [sdd] START_STOP FAILED
sd 8:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
ata10.00: disabled
sd 9:0:0:0: [sde] Synchronizing SCSI cache
sd 9:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
sd 9:0:0:0: [sde] Stopping disk
sd 9:0:0:0: [sde] START_STOP FAILED
sd 9:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
ACPI: PCI interrupt for device 0000:02:0c.0 disabled
ata3.00: disabled
sd 2:0:0:0: [sda] Synchronizing SCSI cache
sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
sd 2:0:0:0: [sda] Stopping disk
sd 2:0:0:0: [sda] START_STOP FAILED
sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
ACPI: PCI interrupt for device 0000:02:09.0 disabled
sata_sil 0000:02:09.0: version 2.2
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKD] -> GSI 18 (level, low) ->
IRQ 20
scsi10 : sata_sil
scsi11 : sata_sil
scsi12 : sata_sil
scsi13 : sata_sil
ata11: SATA max UDMA/100 cmd 0xf88fa880 ctl 0xf88fa88a bmdma 0xf88fa800 irq 20
ata12: SATA max UDMA/100 cmd 0xf88fa8c0 ctl 0xf88fa8ca bmdma 0xf88fa808 irq 20
ata13: SATA max UDMA/100 cmd 0xf88faa80 ctl 0xf88faa8a bmdma 0xf88faa00 irq 20
ata14: SATA max UDMA/100 cmd 0xf88faac0 ctl 0xf88faaca bmdma 0xf88faa08 irq 20
ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata11.00: ATA-8: SAMSUNG HD501LJ, CR100-13, max UDMA7
ata11.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata11.00: configured for UDMA/100
ata12: SATA link down (SStatus 0 SControl 310)
ata13: SATA link down (SStatus 0 SControl 310)
ata14: SATA link down (SStatus 0 SControl 310)
scsi 10:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 10:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 10:0:0:0: [sda] Write Protect is off
sd 10:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 10:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 10:0:0:0: [sda] Write Protect is off
sd 10:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sda: sda1
sd 10:0:0:0: [sda] Attached SCSI disk
ACPI: PCI Interrupt 0000:02:0c.0[A] -> Link [LNKC] -> GSI 17 (level, low) ->
IRQ 21
scsi14 : sata_sil
scsi15 : sata_sil
scsi16 : sata_sil
scsi17 : sata_sil
ata15: SATA max UDMA/100 cmd 0xf8a08c80 ctl 0xf8a08c8a bmdma 0xf8a08c00 irq 21
ata16: SATA max UDMA/100 cmd 0xf8a08cc0 ctl 0xf8a08cca bmdma 0xf8a08c08 irq 21
ata17: SATA max UDMA/100 cmd 0xf8a08e80 ctl 0xf8a08e8a bmdma 0xf8a08e00 irq 21
ata18: SATA max UDMA/100 cmd 0xf8a08ec0 ctl 0xf8a08eca bmdma 0xf8a08e08 irq 21
ata15: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata15.00: ATA-8: SAMSUNG HD501LJ, CR100-13, max UDMA7
ata15.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata15.00: configured for UDMA/100
ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata16.00: ATA-8: SAMSUNG HD501LJ, CR100-13, max UDMA7
ata16.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata16.00: configured for UDMA/100
ata17: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata17.00: ATA-8: SAMSUNG HD501LJ, CR100-13, max UDMA7
ata17.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata17.00: configured for UDMA/100
ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata18.00: ATA-8: SAMSUNG HD501LJ, CR100-13, max UDMA7
ata18.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata18.00: configured for UDMA/100
scsi 14:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 14:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 14:0:0:0: [sdb] Write Protect is off
sd 14:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 14:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 14:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 14:0:0:0: [sdb] Write Protect is off
sd 14:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 14:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sdb: sdb1
sd 14:0:0:0: [sdb] Attached SCSI disk
scsi 15:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 15:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 15:0:0:0: [sdc] Write Protect is off
sd 15:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 15:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 15:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 15:0:0:0: [sdc] Write Protect is off
sd 15:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 15:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sdc: sdc1
sd 15:0:0:0: [sdc] Attached SCSI disk
scsi 16:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 16:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 16:0:0:0: [sdd] Write Protect is off
sd 16:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 16:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 16:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 16:0:0:0: [sdd] Write Protect is off
sd 16:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 16:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sdd: sdd1
sd 16:0:0:0: [sdd] Attached SCSI disk
scsi 17:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 17:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 17:0:0:0: [sde] Write Protect is off
sd 17:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 17:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 17:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 17:0:0:0: [sde] Write Protect is off
sd 17:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 17:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sde: sde1
sd 17:0:0:0: [sde] Attached SCSI disk
md: md0 stopped.
md: md0 stopped.
md: bind<sdc1>
md: bind<sda1>
md: bind<sdd1>
md: bind<sdb1>
md: bind<sde1>
md: kicking non-fresh sdb1 from array!
md: unbind<sdb1>
md: export_rdev(sdb1)
raid5: device sde1 operational as raid disk 0
raid5: device sdd1 operational as raid disk 3
raid5: device sda1 operational as raid disk 2
raid5: device sdc1 operational as raid disk 1
raid5: allocated 5245kB for md0
raid5: raid level 5 set md0 active with 4 out of 5 devices, algorithm 2
RAID5 conf printout:
--- rd:5 wd:4
disk 0, o:1, dev:sde1
disk 1, o:1, dev:sdc1
disk 2, o:1, dev:sda1
disk 3, o:1, dev:sdd1


>
> Also, please provide the output of
>
> /usr/share/bug/mdadm/script 3>&1
>
> run as root.

Output attached.



--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de
 
Old 05-04-2008, 12:49 PM
martin f krafft
 
Default software raid5 array degrades from initrd

also sprach Dexter Filmore <Dexter.Filmore@gmx.de> [2008.05.03.1723 +0100]:
> initrd has its own log...?

No, it just prints to the console.

I suggest you add break=bottom to the kernel command line (and
remove the raid=noautodetect, which you don't need) and then reboot,
inspect the console output and tell us what it says.

You can exit the shell to continue the boot.

--
.'`. martin f. krafft <madduck@debian.org>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems

microsoft: for when quality, reliability, and security
just aren't that important!
 
Old 05-04-2008, 10:56 PM
Dexter Filmore
 
Default software raid5 array degrades from initrd

Am Sonntag, 4. Mai 2008 14:49:19 schrieb martin f krafft:
> also sprach Dexter Filmore <Dexter.Filmore@gmx.de> [2008.05.03.1723 +0100]:
> > initrd has its own log...?
>
> No, it just prints to the console.
>
> I suggest you add break=bottom to the kernel command line (and
> remove the raid=noautodetect, which you don't need) and then reboot,
> inspect the console output and tell us what it says.
>
> You can exit the shell to continue the boot.

Well, it works now that I switched to assembling from rcS.d and I really don't
wanna degrade the array on purpose again. The error message loosk like in the
dmesg output I posted in reply to your first answer.

Dex


--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-04-2008, 10:59 PM
Dexter Filmore
 
Default software raid5 array degrades from initrd

Am Freitag, 2. Mai 2008 22:47:07 schrieb Alex Samad:
> On Fri, May 02, 2008 at 02:45:04PM +0200, Dexter Filmore wrote:
> > So here's the story:
>
> [snip]
>
> > Now: what's going on here? both onboard 3114 and pci 3114 controllers are
> > handled by the same kernel module, so either initrd sees all or none.
> > Why would it not wanna see the 5th disk from initrd, but when I manually
> > assemble, it's fine?
> >
> > Dex
>
> Used to have a similar problem.
>
> look in /etc/mdadm/mdadm.conf make sure the arrays is defined properly
> in there also make sure you have
> DEVICE partitions
>
> or at least have it pointing to all the right devices/partitions
>
> then update your initramfs
>
> from memory the problem i had was I had not fully specified my array in
> /etc/mdadm/mdadm.conf. Another way to put it they array information in
> the initram fs was from an old array specification and only part of the
> array would get started.

Array info was all fine.
I had an issue with 2.6.18 that it wouldn't see all partitions, I fixed that
by going 2.6.22 (and yes, I fixed the shutdown issue with hddown).

>
> another thing you can try is entering busybox during the initrd process
> just before it starts/load /
>

How exactly do I enter Busybox?


--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-05-2008, 05:46 AM
Alex Samad
 
Default software raid5 array degrades from initrd

On Mon, May 05, 2008 at 12:59:52AM +0200, Dexter Filmore wrote:
> Am Freitag, 2. Mai 2008 22:47:07 schrieb Alex Samad:
> > On Fri, May 02, 2008 at 02:45:04PM +0200, Dexter Filmore wrote:
> > > So here's the story:
> >
> > [snip]
>
> >
> > another thing you can try is entering busybox during the initrd process
> > just before it starts/load /
> >
>
> How exactly do I enter Busybox?

been a while, but I think it is an option on the console as it comes up

>
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
> w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
> b++(+++) DI+++ D- G++ e* h>++ r* y?
> ------END GEEK CODE BLOCK------
>
> http://www.vorratsdatenspeicherung.de
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

--
"But all in all, it's been a fabulous year for Laura and me."

- George W. Bush
12/20/2001
Washington, DC
summing up his first year in office, three months after the 9/11 attacks
 

Thread Tools




All times are GMT. The time now is 05:27 AM.

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