Re: degraded array - former device is unavailable

[Philip Ross]

Philip Ross wrote:
I'm getting exactly the same problem after upgrading a test system from 
Woody to Sarge. Every time I reboot the md raid1 root device is failing 
to come up with both mirrors (see dmesg output below). When I add the 
missing mirror manually using mdadm everything works fine up until the 
next reboot.


I've fixed the issue now. The problem was that I had removed (with mdadm 
--fail) one of the mirrors prior to doing the upgrade.


When mkinitrd ran as part of installing the new kernel, it didn't detect 
both raid devices and only set up an initial ram disk capable of 
detecting one of the mirrors.


To fix, I added the missing mirror (with mdadm --add), waited for the 
raid device to sync up and then re-ran mkinitrd and lilo.


Phil


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: No security updates for sarge ?

[Philip Ross]

Hannes Mayer wrote:

I've been wondering the past few days why there are no updates via
apt-get update/upgrade (I have the correct entries in
sources.list!). A few days ago I was reading at heise.de
(http://www.heise.de/newsticker/meldung/61076) that the security team
seems to have disappeared. In a previous thread I was reading that
some updates are in the queue, but have not been released yet.
I've seen some debian core team members posting on this list, so maybe
someone can clarify what's happening.


There's been some discussion about this subject on the Debian Security 
mailing list:


http://lists.debian.org/debian-security/2005/06/threads.html#00142


Phil


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: degraded array - former device is unavailable

[Philip Ross]

David Svejda wrote:
I've problem with software RAID 1. I've installed Debian 3.1 and 
everything went ok.The machine was running for few days, then it was 
halted due to power supply failure.


Then, after reboot, there is an error on md0 device as seen in 
/var/log/dmesg:


md0: former device ide/host0/bus0/target1/lun0/part1 is unavailable, 
removing from array!


Have you managed to resolve this issue?

I'm getting exactly the same problem after upgrading a test system from 
Woody to Sarge. Every time I reboot the md raid1 root device is failing 
to come up with both mirrors (see dmesg output below). When I add the 
missing mirror manually using mdadm everything works fine up until the 
next reboot.


Both partitions are set as Linux raid autodetect.

Other raid1 md devices on the machine (mounted on /home and /boot) start 
up without any problems.


I've created a new /etc/mdadm/mdadm.conf file as per the instructions in 
the Sarge release notes 
(http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-mdadm)


I'm only seeing the problems with the 2.4.27-2-686 kernel from Sarge. If 
I drop back to Woody's 2.4.18-1-686 kernel, everything works fine.


Does anyone have any ideas as to what is going on here?

Please CC me on any replies as I'm not currently subscribed to the list.

Thanks,

Phil


PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1410-0x1417, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x1418-0x141f, BIOS settings: hdc:DMA, hdd:DMA
hda: VMware Virtual IDE Hard Drive, ATA DISK drive
blk: queue c883ecc0, I/O limit 4095Mb (mask 0x)
hdc: VMware Virtual IDE Hard Drive, ATA DISK drive
hdd: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
blk: queue c883f114, I/O limit 4095Mb (mask 0x)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: 8388608 sectors (4295 MB) w/32KiB Cache, CHS=8322/16/63, UDMA(33)
hdc: attached ide-disk driver.
hdc: 13631488 sectors (6979 MB) w/32KiB Cache, CHS=13523/16/63, UDMA(33)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1 p2  p5 p6 p7 
 /dev/ide/host0/bus1/target0/lun0: p1 p2  p5 p6 p7 p8 
 [events: 0045]
md: bindide/host0/bus0/target0/lun0/part5,1
md: ide/host0/bus0/target0/lun0/part5's event counter: 0045
md5: former device ide/host0/bus1/target0/lun0/part5 is unavailable, 
removing from array!

md: RAID level 1 does not need chunksize! Continuing anyway.
md5: max total readahead window set to 124k
md5: 1 data-disks, max readahead per data-disk: 124k
raid1: device ide/host0/bus0/target0/lun0/part5 operational as mirror 0
raid1: md5, not all disks are operational -- trying to recover array
raid1: raid set md5 active with 1 out of 2 mirrors
md: updating md5 RAID superblock on device
md: ide/host0/bus0/target0/lun0/part5 [events: 0046]6(write) 
ide/host0/bus0/target0/lun0/part5's sb offset: 2929600

md: recovery thread got woken up ...
md5: no spare disk to reconstruct array! -- continuing in degraded mode
md: recovery thread finished ...
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 97736k swap-space (priority -1)
Adding Swap: 97740k swap-space (priority -2)
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,5), internal journal
Real Time Clock Driver v1.10f
pcnet32.c:v1.30c 05.25.2004 [EMAIL PROTECTED]
pcnet32: PCnet/PCI II 79C970A at 0x1080, 00 0c 29 69 18 b2 assigned IRQ 18.
eth0: registered as PCnet/PCI II 79C970A
pcnet32: 1 cards_found.
device-mapper: 4.1.1-ioctl (2004-04-07) initialised: [EMAIL PROTECTED]
 [events: 0039]
md: bindide/host0/bus1/target0/lun0/part1,1
 [events: 0039]
md: bindide/host0/bus0/target0/lun0/part1,2
md: ide/host0/bus0/target0/lun0/part1's event counter: 0039
md: ide/host0/bus1/target0/lun0/part1's event counter: 0039
md: RAID level 1 does not need chunksize! Continuing anyway.
md1: max total readahead window set to 124k
md1: 1 data-disks, max readahead per data-disk: 124k
raid1: device ide/host0/bus0/target0/lun0/part1 operational as mirror 0
raid1: device ide/host0/bus1/target0/lun0/part1 operational as mirror 1
raid1: raid set md1 active with 2 out of 2 mirrors
md: updating md1 RAID superblock on device
md: ide/host0/bus0/target0/lun0/part1 [events: 003a]6(write) 
ide/host0/bus0/target0/lun0/part1's sb offset: 97664
md: ide/host0/bus1/target0/lun0/part1 [events: 003a]6(write) 
ide/host0/bus1/target0/lun0/part1's sb offset: 97664

 [events: 0039]
md: bindide/host0/bus1/target0/lun0/part7,1
 [events: 0039]
md: bindide/host0/bus0/target0/lun0/part7,2
md: ide/host0/bus0/target0/lun0/part7's event counter: 0039
md: ide/host0/bus1/target0/lun0/part7's event counter: 0039
md: RAID level 1 does not need chunksize! Continuing anyway.
md7: max total readahead window set to 124k
md7: 1 

Woody Kernel Security Updates

[Philip Ross]

The recent 2.4.27 kernel fixed a few security issues 
(http://www.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.27). Does 
anyone know if these affect the current Woody kernel packages and if so 
when security updates are likely to be released?

Thanks,
Phil
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Debian woody or sarge?

[Philip Ross]

I am looking to migrate a few Red Hat boxes to Debian in the next month or
two and am currently wondering whether to install woody or sarge.

I've seen posts that suggest sarge will become the stable distribution soon
(http://lists.debian.org/debian-devel-announce/2003/debian-devel-announce-20
0308/msg00010.html).  Can anyone point me to an up to date estimation of the
release date?

Given Red Hat updates will end at the end of the year, I want to get up and
running with Debian before that.  If sarge doesn't become stable until next
year, would it be better to install woody now and upgrade to sarge in a few
months, or install sarge now? How long will woody remain supported with
security updates?

Thanks,

Phil




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]