Update to 2.6.34.3-1 & LTS 2.6.32.18-1 killed dmraid box??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Guys,

This one caught me by surprise. I have my test server that I update before updating my regular server. It is based on a MSI K9N2 board (MS-7374) with a Phenom 9850 proc & 8G of ram. The box has 2 dmraid arrays:

[22:00 ecstasy:/mnt/arch] # dmraid -r
/dev/sdd: nvidia, "nvidia_baaccaja", mirror, ok, 1465149166 sectors, data@ 0
/dev/sdc: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0
/dev/sdb: nvidia, "nvidia_baaccaja", mirror, ok, 1465149166 sectors, data@ 0
/dev/sda: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0

[22:00 ecstasy:/mnt/arch] # dmraid -s
*** Active Set
name   : nvidia_baaccaja
size   : 1465149056
stride : 128
type   : mirror
status : ok
subsets: 0
devs   : 2
spares : 0
*** Active Set
name   : nvidia_fdaacfde
size   : 976773120
stride : 128
type   : mirror
status : ok
subsets: 0
devs   : 2
spares : 0

	The kernel updates applied tonight were:

[2010-08-16 20:13] upgraded kernel26 (2.6.34.2-2 -> 2.6.34.3-1)
[2010-08-16 20:13] upgraded kernel26-headers (2.6.34.2-2 -> 2.6.34.3-1)
[2010-08-16 20:14] upgraded kernel26-lts (2.6.32.17-2 -> 2.6.32.18-1)

	Both completed successfully. The pacman.log info is here:

http://www.3111skyline.com/dl/Archlinux/bugs/pm-updt-8-16.txt

After boot to the normal 2.6.34 kernel, the box kept automatically rebooting itself - WTF? So I booted to the LTS kernel, which booted this time and rebuilt the initramfs file with:

/sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img

It completed successfully. Rebooting resulted in an error that the the partitions were corrupt. So I attempted to boot back into the LTS kernel. It failed as well?? So I rebooted into suse 11.0 which is on the other array. The box booted into suse without any problems. I then mouted the Arch array and the partitions are fine. (that's where the raid info above came from).

I don't know what is going on here. Kernel updates on this box have always been uneventful. Tonight all hell broke loose. What could have caused Arch to report the partitions were bad? More important, what do I do to get Arch back? I believe I have the correct modules in mkinitcpio.conf (they are the same ones I have had in the conf file since I first loaded Arch with the 200902 install media in March '09). Here is the lspci info (running suse):

	The raid controller is the standard nvraid soft raid controller:

00:09.0 RAID bus controller: nVidia Corporation Device 0ad8 (rev a2)
        Subsystem: Micro-Star International Co., Ltd. Device 7374
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 4347
        I/O ports at b080 [size=8]
        I/O ports at b000 [size=4]
        I/O ports at ac00 [size=8]
        I/O ports at a880 [size=4]
        I/O ports at a800 [size=16]
        Memory at f9e76000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [44] Power Management version 2
        Capabilities: [8c] SATA HBA <?>
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable+
        Capabilities: [ec] HyperTransport: MSI Mapping Enable+ Fixed+
        Kernel driver in use: ahci
        Kernel modules: ahci

What say the gurus? (Tobias what could have changed here?) Any help would be greatly appreciated. I'll keep dorking with it, but I'm at a loss here...


Additional Info:

	The partitions on the box are:

[22:02 ecstasy:/mnt/arch] # cat /proc/partitions
major minor  #blocks  name

   8     0  488386584 sda
   8     1          1 sda1
   8     5      72229 sda5
   8     6    2104483 sda6
   8     7   20972826 sda7
   8     8  465234336 sda8
   8    16  732574584 sdb
   8    17          1 sdb1
   8    21   19534977 sdb5
   8    22     120456 sdb6
   8    23   39062016 sdb7
   8    24    1951866 sdb8
   8    25   15358108 sdb9
   8    26   30716248 sdb10
   8    27    7510356 sdb11
   8    28  618317721 sdb12
   8    32  488386584 sdc
   8    33          1 sdc1
   8    37      72229 sdc5
   8    38    2104483 sdc6
   8    39   20972826 sdc7
   8    40  465234336 sdc8
   8    48  732574584 sdd
   8    49          1 sdd1
   8    53   19534977 sdd5
   8    54     120456 sdd6
   8    55   39062016 sdd7
   8    56    1951866 sdd8
   8    57   15358108 sdd9
   8    58   30716248 sdd10
   8    59    7510356 sdd11
   8    60  618317721 sdd12
 253     0  732574583 dm-0
 253     1  488386583 dm-1
 253     2  732572001 dm-2
 253     3   19534977 dm-3
 253     4     120456 dm-4
 253     5   39062016 dm-5
 253     6    1951866 dm-6
 253     7   15358108 dm-7
 253     8   30716248 dm-8
 253     9    7510356 dm-9
 253    10  618317721 dm-10
 253    11  488384001 dm-11
 253    12      72229 dm-12
 253    13    2104483 dm-13
 253    14   20972826 dm-14
 253    15  465234336 dm-15


--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux