Bug 309040

Summary: Unable to update install onto MD raid from prev beta installs
Product: [openSUSE] openSUSE 10.3 Reporter: Richard Creighton <rccj>
Component: InstallationAssignee: Cyril Hrubis <chrubis>
Status: RESOLVED DUPLICATE QA Contact: Stanislav Visnovsky <visnov>
Severity: Major    
Priority: P0 - Crit Sit CC: art.fore, locilka
Version: Beta 3   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 10.3   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Docs supporting installation problems into MD raid
Additional Beta 3 documentation of this problem
Upgrade from functioning 10.2 to Beta 3 to MD raid
Log files from Art Fore 10.3 beta report
Partitioning scheme of MD Raid

Description Richard Creighton 2007-09-09 08:38:09 UTC 
Previously using http://en.opensuse.org/How_to_install_SUSE_Linux_on_software_RAID  several versions of 10.3 Alpha and beta have been installed on MD raid filesystem.  Using 10.3 Beta 3 DVD install, install fails just after all files have been installed and it attempts to install bootloader.   It wants to format sda (low-level) which would destroy the MD raid filesystem.  I stopped it from doing so and it would not boot, of course.   I booted from the DVD and booted the installed system from the DVD and installed GRUB from within the updated system.   The normal install never completed, ie, it didn't go through the normal setting up of the network or other things after the install update on the installation.  I did those things manually from within Yast, ie, set up repos and updates schedules etc.   Attached is the /boot/grub directory (unmodified by the install  program), a screenshot of my partition table and the complete YAST2 log directory produced during the install attempt.  I tried this twice.   The first time I had an IDE drive online with 10.2 installed but it wanted to ruin that installation for which bug 304657 is still open, so I physically removed it for this trial to isolate the IDE-SATA bug from the MDraid issue outlined here.  Now that it is manually updated, it boots and runs quite normally in all respects, it is just that the install program is unable to install GRUB.  Running from a booted system, GRUB can be installed.
Comment 1 Richard Creighton 2007-09-09 08:43:28 UTC 
Created attachment 162886 [details]
Docs supporting installation problems into MD raid

Contains 2 directories and a screenshot.   YAST2 logs directory, GRUB directory and partition table screenshot showing disk layout of system.
Comment 2 Richard Creighton 2007-09-10 22:49:44 UTC 
I was able finally to get a complete installation of Beta 3 from the DVD.  In order to do this, I had to physically remove the IDE drive containing the 10.2 installation of SuSE which I was NOT trying to upgrade anyway and was being corrupted at every turn.   I gave up trying to do an update installation which was originally a 10.2 clone that I had updated with previous 10.3 betas (with limited success due to the IDE-SATA bug) but previously I had always been able to get GRUB to install and the system to boot until now.  This time, I was stopped cold so I decided to see if a clean install would work and once the IDE drive was off-line, it worked without trouble including GRUB installation.   It apparantly is the UPGRADE of GRUB that failed in the previous attempt in case that clue is of any help.
Comment 3 Thomas Fehr 2007-09-11 08:27:08 UTC 
Lukas, could you check if mounting of system to update is ok.
If yes this is probably an issue with yast2-bootloader.
Comment 4 Lukas Ocilka 2007-09-11 09:21:05 UTC 
clients/switch_scr_finish.ycp:90 Can't create component 'chroot=/mnt:scr'
SCROpen 'chroot=/mnt:scr' failed: -1
clients/switch_scr_finish.ycp:36 Cannot switch to SCR '/mnt'
clients/switch_scr_finish.ycp:47 User decided to debug the current problem

* ---------- Debugger Start ---------- *
=== System Checking ===
Checking for /usr/bin/chroot binary... true
Checking for chroot directory /mnt... true
Checking for binary /mnt/bin/ls... true
Trying to chroot... true
Debug: exit>0<
stdout>
bin
boot
Data
dev
etc
HDA1
HDA2
home
lib
local
lost+found
media
mnt
opt
proc
root
sbin
srv
success
sys
tmp
usr
var
<
stderr><
-- I.C. Winner --
Checking for /usr/lib/YaST2/bin/y2base in /mnt... false
* ---------- Debugger Finish ---------- *

So, it seems y2base is missing on the just installed system...

Could you, please, check whether the file /usr/lib/YaST2/bin/y2base exists in the system?
Comment 5 Richard Creighton 2007-09-11 11:43:30 UTC 
As you will observe in comment 2 above, I did a complete CLEAN install which wiped the MD1 and MD2 file systems clean via formatting.  I did not repartition or recreate the raid arrays from scratch.  As a result, no traces of previous attempts remain.   That is why I  provided complete directories of the previous attempts.   I have observed many requests for information and I tried to anticipate what might be needed by including the entire Yast2 log directory.   If the data isn't in there, it wasn't created.   As to anything in /usr/lib/*, that was in the partition/file system that was reformatted during the successful clean install.   

I might note that This partition was previously created as a 10.2 system IAW the instructions in the web site HOWTO and it worked famously and previous alpha and betas always balked during the updates (wanting to write GRUB to my USB) but even though I wouldn't let it, the installation would continue and the system would boot and I cleaned up the GRUB by booting from the CD to the installed - updated system.   This time, it could not boot to the installed/updated system nor would the installation program continue with the normal post install stuff like network, user or other cleanup functions.   Thus, the MBR appeared to have been damaged or I could have fixed things after a reboot but that didn't happen this time.   This prompted the clean install attempt prior to an anticipated reinstall of 10.2.   Pleasently, I had no problems.

So, it appears that the UPDATE installation (which I would suggest will be the most common mode of installing 10.3) failed to update and damaged the existing installation to the point of preventing any repair or booting.   I might point out that there is already a bug opened against the REPAIR function which when run against a system with a MD raid fails miserably, so my options were limited to a clean install of 10.3 B3 or a clean install of an earlier version.  

Now that I have a functioning system again, I am willing to risk it once more if you wish me to attempt something, I will document anything I can if you will tell me what you think you will need and from what directory and at what stage.  Short of that, there is nothing remaining from the failed update installation.
Comment 6 Lukas Ocilka 2007-09-11 14:31:12 UTC 
Well, it seems that zypp had problem "before" the known issue appeared:

2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/VLC_10.2'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/20070820-152606'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/10.2_0'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Installation_DVD_image'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Guru_10.2'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/RPMS'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/http:/download.opensuse.org/repositories/KDE:/Community/openSUSE_Factory'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/VLC_10.3'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Packman_10.1'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Factory_SL-OSS-factory-debug/inst-source'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/http:/download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-extra'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/openSUSE-10.3-Updates'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/http:/software.opensuse.org/download/mozilla/SUSE_Factory'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/suse'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Guru_10.3'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/10.3_-_Main_Repositoy_NON_STANDARD'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Packman_10.2'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/DVD'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/10.3_0'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Packman_10.3'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/10.3_1'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/http:/download.opensuse.org/repositories/openSUSE:10.3/standard'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/Factory_distribution_SL-OSS-factory_inst-source'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/10.3'. Not a direcotry.
2007-09-08 19:49:49 <3> linux(3632) [zypp] Fetcher.cc(addCachePath):124 Not adding cache: '/var/cache/zypp/raw/http:/download.opensuse.org/update/10.3'. Not a direcotry.

After the unsuccessful installation/upgrade, /usr/lib/YaST2/bin/y2base didn't appear to be on the system and SCR Switch (chroot) failed. Please, check zypp.

Mounting:
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:470 FS type sysfs is not modular, skipping modprobe...
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:954 mounting LABEL=boot to /boot
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4839 DetectFs:LABEL=boot
2007-09-08 19:48:39 <1> linux(3632) [libstorage] Storage.cc(findVolume):5192 label:boot uuid:
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4852 DetectFs ret `ext3
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4839 DetectFs:LABEL=boot
2007-09-08 19:48:39 <1> linux(3632) [libstorage] Storage.cc(findVolume):5192 label:boot uuid:
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4852 DetectFs ret `ext3
2007-09-08 19:48:39 <1> linux(3632) [YCP] FileSystems.ycp:1092 used_fs:`ext3 ret:ext3
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:467 Calling 'modprobe ext3'
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:510 mounting (/mnt/boot, LABEL=boot, ) yield nil
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:876 Scriptout: ["/dev/md1", "101018", "16351", "79451", "18%", "/mnt/boot\n"]
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:885 Boot size is: 101018 recommended min.: 65536
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:954 mounting LABEL=data to /home
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4839 DetectFs:LABEL=data
2007-09-08 19:48:39 <1> linux(3632) [libstorage] Storage.cc(findVolume):5192 label:data uuid:
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4852 DetectFs ret `ext3
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4839 DetectFs:LABEL=data
2007-09-08 19:48:39 <1> linux(3632) [libstorage] Storage.cc(findVolume):5192 label:data uuid:
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4852 DetectFs ret `ext3
2007-09-08 19:48:39 <1> linux(3632) [YCP] FileSystems.ycp:1092 used_fs:`ext3 ret:ext3
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:467 Calling 'modprobe ext3'
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:510 mounting (/mnt/home, LABEL=data, ) yield nil
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:1054 mounting /dev/disk/by-id/scsi-SATA_WDC_WD1200BB-00WD-WMACM1130623-part3 to swap
2007-09-08 19:48:39 <3> linux(3632) [bash] ShellCommand.cc(shellcommand):78 swapon: cannot stat /dev/disk/by-id/scsi-SATA_WDC_WD1200BB-00WD-WMACM1130623-part3: No such file or directory
2007-09-08 19:48:39 <3> linux(3632) [YCP] RootPart.ycp:1068 swapon failed: /sbin/swapon /dev/disk/by-id/scsi-SATA_WDC_WD1200BB-00WD-WMACM1130623-part3
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:1054 mounting LABEL=swap to swap
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:954 mounting proc to /proc
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4839 DetectFs:proc
2007-09-08 19:48:39 <3> linux(3632) [YCP] Storage.ycp:4844 DetectFs device:proc not found (ret:-2001)
2007-09-08 19:48:39 <1> linux(3632) [YCP] Storage.ycp:4852 DetectFs ret `unknown
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:470 FS type proc is not modular, skipping modprobe...
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:510 mounting (/mnt/proc, proc, proc) yield nil
2007-09-08 19:48:39 <1> linux(3632) [YCP] RootPart.ycp:1241 MountPartition (/dev/md2) = true

It's not easy to reproduce the bug, I guess...
Mounting went OK, solver did the job well too...
Comment 7 Richard Creighton 2007-09-11 15:01:33 UTC 
Take note that without physically removing the IDE drive containing the functioning 10.2 installation that I do NOT want upgraded (it contains my hardware 1.5 TB raid that has no driver in 10.3 yet) I cannot install 10.3 Beta 3 at all.  With the 10.2 IDE drive in place, All alpha and beta versions are affected by the change in HDx to SDx naming (ATA to SATA) and GRUB gets written to the IDE drive and not the SATA drive containing the MD raid.  The first time that happened, I was truly alarmed because it was unexpected and I thought I had lost my 1.5TB hardware raid, but my 10.2 repair disk saved the day.   Now, if 10.3 repair would do the same :)   But for now, the root cause is the IDE/SATA issue followed by the upgrade bootloader failure which is the subject of this bug.  Is the install upgrade bootloader different than the install new bootloader?   It would seem so.
Comment 8 Richard Creighton 2007-09-13 09:32:10 UTC 
Created attachment 163800 [details]
Additional Beta 3 documentation of this problem 

I reinstalled 10.2 onto the system and was able to boot either installation, ie, from the IDE drive or from the MD raid installation.   I took a log and GRUB snapshot (the before files) as a reference.   I then upgraded the MD system using the most recent Beta 10.3 B3 available which had the effect of making the MD system unbootable at the point where the system first updates GRUB.  I took another snapshot by booting from the IDE system and saving the MD logs and GRUB files as they existed at that time.  Then, I used the CD to boot the installed 10.3 whereupon the installation continued as if it had been successful with thee initial reboot that had just failed.   I conitinued the install up to the point where I could log in as root.   At that point, I captured the additional Logs which are included as separate entries so you can see the break more easily.  I modified the 10.2 IDE drive GRUB to boot either installation but the new 10.3 install will not boot from BIOS, only from chainloading from the IDE drive.  That means the MBR on the SATA drive was also damaged in addition to the GRUB entries included in the enclosed attachment files.   I hope some of this helps...I did a complete wipe of the previous 10.3 installation to put  10.2 back on for this test and 10.2 installed and booted without complaint...again.  This IDE-SATA renaming thing IMO was an ill conceived 'upgrade' by someone.  I see so many buglist entries that are a direct or indirect result of that decision.  Opinion mode off;  I know it wasn't your decision. Anyhow, I hope this additional fresh documentation may help.  One thing fixed of note is that the IDE drive wasn't affected until I tried to update the MBR on the MD SATA drive under 10.3, but that is another issue.   Related, but not directly part of the install.
Comment 9 Richard Creighton 2007-09-17 09:24:07 UTC 
Created attachment 172743 [details]
Upgrade from functioning 10.2 to Beta 3 to MD raid

These are logs and other support documents taking a functioning MD raid system from 10.2 to 10.3 B3 with a stop at mid installation to fix an error at the point where the system tries to boot the updated system and continue with network and cleanup configuration.   This interrupt was caused by 2 things,  First, a driver for an installed disk controller is not properly upgraded/compatable between 10.2 and 10.3 so the reboot drops to repair mode.  Second, the GRUB file produced includes kernels that do not exist anymore and the ones that do are pointed to on (hd1,0) rather than (hd0,0) which I edited manually so the boot could continue and the install complete.   The documentation is divided into 4 sections, each with its own directory.   Much progress toward fixing this bug is evident since it was first reported.  It almost worked.   The first directory is Not a malfunction, it is a functioning 10.2 system,  The last directory is a functioning 10.3 system after manual editing.   The other two do reflect errors.   The IDE drive remains physically removed from the system and when reinserted, the installation still fails disastrously as before.
Comment 10 Art Fore 2007-09-17 14:55:04 UTC 
With the help of Richard, I have gotten to this point. I will make is short.

complete install or upgrade to Suse 10.2 results in same thing. During install reboot, grub comes up, select sus 10.3, then it goes to command prompt with error 15 for initrd and kernel files.

Boot from DVD, either 10.2 or 10.3, select install, then select other, boot installed system. Installation completes and I can reboot the same way again. Tried all of the hd2,0, hd0.1, with no success when booting with dvd and editing the grub boot screen. This system worked fine with Suse 10.2! There are 5 sata disks and DVD drive only. Motherboard is Gigabyte GA-M57SLI-S4 with 4 GB ram.

I will not be able to do any more until I get back from Germany next week, assuming the typhoon does not delay the airplane.

Attached is the file with grub config files, fstab, and log messages.

Well, couldn't find how to attach file, so here is copy/paste of the file.

device.map

(hd3)	/dev/sdd
(hd4)	/dev/sde
(fd0)	/dev/fd0
(hd0)	/dev/sda
(hd2)	/dev/sdc
(hd1)	/dev/sdb

menu.lst

# Modified by YaST2. Last modification on Mon Sep 17 21:15:30 CST 2007
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.3
    root (hd0,0)
    kernel /vmlinuz-2.6.22.3-7-default root=/dev/md2 vga=0x317 resume=/dev/md1 splash=silent showopts
    initrd /initrd-2.6.22.3-7-default

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
    rootnoverify (hd0,0)
    chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.3
    root (hd0,0)
    kernel /vmlinuz-2.6.22.3-7-default root=/dev/md2 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3
    initrd /initrd-2.6.22.3-7-default

fstab

/dev/md2             /                    ext3       acl,user_xattr        1 1
/dev/md0             /boot                ext3       acl,user_xattr       1 2
/dev/md4             /backup              ext3       defaults              1 2
/dev/md3             /home                ext3       acl,user_xattr        1 2
/dev/disk/by-id/scsi-SATA_Maxtor_6B200M0_B41KXB6H-part1 /old_files           ext3       defaults              1 2
/dev/md1             swap                 swap       defaults              0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/fd0             /media/floppy        auto       noauto,user,sync      0 0

boot.msg booting with 10.2 dvd

Cannot find map file.
No module symbols loaded - kernel modules not enabled.

Cannot build symbol table - disabling symbol lookups
klogd 1.4.1, log source = ksyslog started.
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>Adding 2056184k swap on /dev/md1.  Priority:-2 extents:1 across:2056184k
<6>EXT3 FS on md2, internal journal
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3 FS on md0, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3 FS on md4, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3 FS on md3, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3 FS on sde1, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>bootsplash: status on console 0 changed to off
Kernel logging (ksyslog) stopped.
Kernel log daemon terminating.

Boot logging started on /dev/tty1(/dev/console) at Mon Sep 17 21:56:30 2007

done
Starting udevd done
Loading required kernel modules
doneActivating swap-devices in /etc/fstab...
done/bin/mknod -m600 /dev/shm/root b 9 2
Checking root file system...
fsck 1.40.2 (12-Jul-2007)
/dev/md2: clean, 203329/2675808 files, 1197449/5341184 blocks
donemount: according to mtab, /dev/md2 is already mounted on /

Activating device mapper...
done
Checking file systems...
fsck 1.40.2 (12-Jul-2007)
/dev/md0: clean, 42/26104 files, 14756/104320 blocks
/dev/md4: clean, 984542/39075840 files, 24596648/78142144 blocks
/dev/md3: clean, 642/36274176 files, 1187942/72517392 blocks
Backup (/dev/disk/by-id/scsi-SATA_Maxtor_6B200M0_B41KXB6H-part1): clean, 715104/24903680 files, 22779188/49785427 blocks
donedone
Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/md0 on /boot type ext3 (rw,acl,user_xattr)
/dev/md4 on /backup type ext3 (rw)
/dev/md3 on /home type ext3 (rw,acl,user_xattr)
/dev/sde1 on /old_files type ext3 (rw)
donemodprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory


Configuring serial ports...
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
Configured serial ports
doneMounting securityfs on /sys/kernel/security done
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Loading AppArmor module failed
Setting current sysctl status from /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
fs.inotify.max_user_watches = 65536
done
Enabling syn flood protectiondone
Disabling IP forwardingdone
done
<notice>killproc: kill(3869,29)
Creating /var/log/boot.msg
doneActivating remaining swap-devices in /etc/fstab...
doneSetting up hostname 'linux-sporthorse'done
Setting up loopback interface Setting up the hardware clockdone
    lo        
    lo        IP address: 127.0.0.1/8   
done
System Boot Control: The system has been set up
Failed features: boot.apparmor
Skipped features: boot.cycle
System Boot Control: Running /etc/init.d/boot.local
done<notice>killproc: kill(3869,3)

INIT: 
Boot logging started on /dev/tty1(/dev/console) at Mon Sep 17 21:56:35 2007

Master Resource Control: previous runlevel: N, switching to runlevel: 5
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Loading AppArmor module failed
<notice>startproc: execve (/bin/dbus-daemon) [ /bin/dbus-daemon --system ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/bin/dbus-daemon ]
<notice>startproc: execve (/sbin/resmgrd) [ /sbin/resmgrd ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/sbin/resmgrd ]
Entering runlevel: 5


Starting resource managerdone
Starting D-Bus daemonacpid: no ACPI support in kernelskipped
done
<notice>startproc: execve (/usr/sbin/console-kit-daemon) [ /usr/sbin/console-kit-daemon ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/console-kit-daemon ]
<notice>startproc: execve (/sbin/syslog-ng) [ /sbin/syslog-ng ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh ESCDELAY=10 LC_ALL=POSIX INSTSYS=/mounts/instsys INIT_VERSION=sysvinit-2.86 initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 SPLASHCFG= PWD=/ lang=en_US YAST_DEBUG=/debug/yast.debug PREVLEVEL=N LINES=44 acpi=off HOME=/ SHLVL=2 BOOT_IMAGE=linux SPLASH=no splash=silent _=/sbin/startproc DAEMON=/sbin/syslog-ng ]
Starting ConsoleKitdone
<notice>startproc: execve (/sbin/klogd) [ /sbin/klogd -c 1 -x -x ], [ CONSOLE=/dev/console TERM=linuxInitializing random number generatordone
 SHELL=/bin/sh ESCDELAY=10 LC_ALL=POSIX INSTSYS=/mounts/instsys INIT_VERSION=sysvinit-2.86 initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 SPLASHCFG= PWD=/ lang=en_US YAST_DEBUG=/debug/yast.debug PREVLEVEL=N LINES=44 acpi=off HOME=/ SHLVL=2 BOOT_IMAGE=linux SPLASH=no splash=silent _=/sbin/startproc DAEMON=/sbin/klogd ]
Starting syslog services.done
Starting HAL daemon<notice>startproc: execve (/usr/sbin/hald) [ /usr/sbin/hald --daemon=yes ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/hald ]
done
Loading CPUFreq modules (CPUFreq not supported)
Starting Firewall Initialization (phase 1 of 2) SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
SuSEfirewall2: Warning: Kernel lacks support for IPv6 REJECT target! Using DROP for IPv6 instead.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables-batch v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
SuSEfirewall2: Error: iptables-batch failed, re-running using iptables
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
done
Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8   
done    eth0      device: nVidia Corporation MCP55 Ethernet (rev a2)
              No configuration found for eth0
unusedSetting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .done
<notice>startproc: execve (/sbin/portmap) [ /sbin/portmap ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/sbin/portmap ]
Starting RPC portmap daemondone
Mount CIFS File Systems unused
Loading keymap i386/qwerty/us.map.gz
doneLoading compose table latin1.adddone
Start Unicode mode
doneLoading console font lat9w-16.psfu  -m trivial G0:loadable
doneStarting service kdm<notice>startproc: execve (/opt/kde3/bin/kdm) [ /opt/kde3/bin/kdm ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh ESCDELAY=10 INSTSYS=/mounts/instsys INIT_VERSION=sysvinit-2.86 initrd=initrd,10240768.spl KDEROOTHOME=/root/.kdm REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 SPLASHCFG= PWD=/ LANG=en_US.UTF-8 lang=en_US YAST_DEBUG=/debug/yast.debug PREVLEVEL=N LINES=44 acpi=off QT_SYSTEM_DIR=/usr/share/desktop-data HOME=/ SHLVL=2 BOOT_IMAGE=linux XCURSOR_THEME=crystalwhite WINDOWMANAGER=/usr/bin/kde SPLASH=no splash=silent _=/sbin/startproc DAEMON=/opt/kde3/bin/kdm ]
done
<notice>checkproc: /opt/kde3/bin/kdm 5529
<notice>startproc: execve (/sbin/auditd) [ /sbin/auditd ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/sbin/auditd ]
Starting auditd done
<notice>startproc: execve (/usr/sbin/cupsd) [ /usr/sbin/cupsd ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/cupsd ]
Starting cupsddone
<notice>startproc: execve (/usr/sbin/irqbalance) [ /usr/sbin/irqbalance ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/irqbalance ]
Starting irqbalance done
<notice>startproc: execve (/usr/sbin/nscd) [ /usr/sbin/nscd ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/nscd ]
Starting Name Service Cache Daemondone
Starting mail service (Postfix)done
<notice>checkproc: /opt/kde3/bin/kdm 5529
<notice>startproc: execve (/usr/sbin/cron) [ /usr/sbin/cron ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/cron ]
Starting CRON daemondone
Starting powersaved: <notice>startproc: execve (/usr/sbin/powersaved) [ /usr/sbin/powersaved -d -v 3 ], [ HOME=/ PATH=/bin:/sbin:/usr/bin:/usr/sbin SHELL=/bin/sh RUNLEVEL=5 PREVLEVEL=N DAEMON=/usr/sbin/powersaved ]
done
<notice>startproc: execve (/usr/sbin/smartd) [ /usr/sbin/smartd ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/smartd ]
Starting smartd done
<notice>startproc: execve (/usr/sbin/sshd) [ /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=linux ESCDELAY=10 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 INSTSYS=/mounts/instsys initrd=initrd,10240768.spl REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG= lang=en_US PREVLEVEL=N YAST_DEBUG=/debug/yast.debug acpi=off LINES=44 SHLVL=2 HOME=/ BOOT_IMAGE=linux splash=silent SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/sshd ]
Starting SSH daemondone
<notice>killproc: kill(5521,15)
Starting Firewall Initialization (phase 2 of 2) SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
SuSEfirewall2: Warning: Kernel lacks support for IPv6 REJECT target! Using DROP for IPv6 instead.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables-batch v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
SuSEfirewall2: Error: iptables-batch failed, re-running using iptables
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
iptables v1.3.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
done
done
Master Resource Control: runlevel 5 has been reached
Failed services in runlevel 5: boot.apparmor
Skipped services in runlevel 5: acpid smbfs
<notice>killproc: kill(4719,3)

/var/log/messages booting with 10.2 DVD

Sep 17 21:56:36 linux-sporthorse syslog-ng[4803]: syslog-ng version 1.6.12 starting
Sep 17 21:56:36 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:36 linux-sporthorse SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Sep 17 21:56:36 linux-sporthorse SuSEfirewall2: Warning: Kernel lacks support for IPv6 REJECT target! Using DROP for IPv6 instead.
Sep 17 21:56:36 linux-sporthorse rchal: CPU frequency scaling is not supported by your processor.
Sep 17 21:56:36 linux-sporthorse rchal: boot with 'CPUFREQ=no' in to avoid this warning.
Sep 17 21:56:36 linux-sporthorse rchal: Cannot load cpufreq governors - No cpufreq driver available
Sep 17 21:56:36 linux-sporthorse SuSEfirewall2: batch committing...
Sep 17 21:56:36 linux-sporthorse SuSEfirewall2: Error: iptables-batch failed, re-running using iptables
Sep 17 21:56:37 linux-sporthorse SuSEfirewall2: Firewall rules set to CLOSE.
Sep 17 21:56:37 linux-sporthorse ifup:     lo        
Sep 17 21:56:37 linux-sporthorse ifup:     lo        
Sep 17 21:56:37 linux-sporthorse ifup: IP address: 127.0.0.1/8  
Sep 17 21:56:37 linux-sporthorse ifup:  
Sep 17 21:56:37 linux-sporthorse ifup:     eth0      device: nVidia Corporation MCP55 Ethernet (rev a2)
Sep 17 21:56:37 linux-sporthorse ifup:               No configuration found for eth0
Sep 17 21:56:38 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:38 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:41 linux-sporthorse kernel: klogd 1.4.1, log source = /proc/kmsg started.
Sep 17 21:56:42 linux-sporthorse auditd[5561]: Started dispatcher: /sbin/audispd pid: 5563
Sep 17 21:56:42 linux-sporthorse kernel: audit(1190037402.092:2): audit_pid=5561 old=0 by auid=4294967295
Sep 17 21:56:42 linux-sporthorse audispd[5563]: listening on /var/run/audit_events
Sep 17 21:56:42 linux-sporthorse auditd[5561]: Init complete, auditd 1.5.5 listening for events
Sep 17 21:56:43 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:44 linux-sporthorse syslog-ng[4803]: last message repeated 8 times
Sep 17 21:56:44 linux-sporthorse /usr/sbin/cron[5708]: (CRON) STARTUP (V5.0)
Sep 17 21:56:44 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:44 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:44 linux-sporthorse powersaved[5725]: WARNING (CpufreqManagement:51) No capability cpufreq_control
Sep 17 21:56:44 linux-sporthorse powersaved[5725]: WARNING (CpufreqManagement:51) No capability cpufreq_control
Sep 17 21:56:44 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:44 linux-sporthorse powersaved[5725]: ERROR (run:85) Cannot access acpi/apm event file
Sep 17 21:56:44 linux-sporthorse smartd[5733]: smartd version 5.37 [x86_64-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Home page is http://smartmontools.sourceforge.net/ 
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Opened configuration file /etc/smartd.conf
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Drive: DEVICESCAN, implied '-a' Directive on line 27 of file /etc/smartd.conf
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Device: /dev/hda, opened
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Device: /dev/hda, packet devices [this device CD/DVD] not SMART capable
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Device: /dev/sda, opened
Sep 17 21:56:44 linux-sporthorse smartd[5733]: Device /dev/sda: ATA disk detected behind SAT layer
Sep 17 21:56:45 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   For example: '/dev/sda -a -d sat'
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device: /dev/sdb, opened
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device /dev/sdb: ATA disk detected behind SAT layer
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   For example: '/dev/sdb -a -d sat'
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device: /dev/sdc, opened
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device /dev/sdc: ATA disk detected behind SAT layer
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:56:45 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   For example: '/dev/sdc -a -d sat'
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device: /dev/sdd, opened
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device /dev/sdd: ATA disk detected behind SAT layer
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   For example: '/dev/sdd -a -d sat'
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device: /dev/sde, opened
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device /dev/sde: ATA disk detected behind SAT layer
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:56:45 linux-sporthorse smartd[5733]:   For example: '/dev/sde -a -d sat'
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device: /dev/sda, opened
Sep 17 21:56:45 linux-sporthorse smartd[5733]: Device: /dev/sda, not found in smartd database.
Sep 17 21:56:45 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:45 linux-sporthorse SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Sep 17 21:56:45 linux-sporthorse SuSEfirewall2: Warning: Kernel lacks support for IPv6 REJECT target! Using DROP for IPv6 instead.
Sep 17 21:56:45 linux-sporthorse SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Sep 17 21:56:45 linux-sporthorse SuSEfirewall2: using default zone 'ext' for interface eth0
Sep 17 21:56:45 linux-sporthorse SuSEfirewall2: batch committing...
Sep 17 21:56:45 linux-sporthorse SuSEfirewall2: Error: iptables-batch failed, re-running using iptables
Sep 17 21:56:45 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:45 linux-sporthorse sshd[5887]: Server listening on 0.0.0.0 port 22.
Sep 17 21:56:45 linux-sporthorse modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-default/modules.dep: No such file or directory
Sep 17 21:56:46 linux-sporthorse SuSEfirewall2: Firewall rules successfully set
Sep 17 21:56:46 linux-sporthorse smartd[5733]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
Sep 17 21:56:46 linux-sporthorse smartd[5733]: Device: /dev/sdb, opened
Sep 17 21:56:46 linux-sporthorse smartd[5733]: Device: /dev/sdb, not found in smartd database.
Sep 17 21:56:47 linux-sporthorse smartd[5733]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list.
Sep 17 21:56:47 linux-sporthorse smartd[5733]: Device: /dev/sdc, opened
Sep 17 21:56:47 linux-sporthorse smartd[5733]: Device: /dev/sdc, not found in smartd database.
Sep 17 21:56:47 linux-sporthorse smartd[5733]: Device: /dev/sdc, is SMART capable. Adding to "monitor" list.
Sep 17 21:56:47 linux-sporthorse smartd[5733]: Device: /dev/sdd, opened
Sep 17 21:56:47 linux-sporthorse smartd[5733]: Device: /dev/sdd, not found in smartd database.
Sep 17 21:56:48 linux-sporthorse smartd[5733]: Device: /dev/sdd, is SMART capable. Adding to "monitor" list.
Sep 17 21:56:48 linux-sporthorse smartd[5733]: Device: /dev/sde, opened
Sep 17 21:56:48 linux-sporthorse smartd[5733]: Device: /dev/sde, found in smartd database.
Sep 17 21:56:48 linux-sporthorse smartd[5733]: Device: /dev/sde, is SMART capable. Adding to "monitor" list.
Sep 17 21:56:48 linux-sporthorse smartd[5733]: Monitoring 5 ATA and 0 SCSI devices
Sep 17 21:56:51 linux-sporthorse smartd[6084]: smartd has fork()ed into background mode. New PID=6084.
Sep 17 21:56:52 linux-sporthorse kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Sep 17 21:56:52 linux-sporthorse kernel: ISO 9660 Extensions: RRIP_1991A
Sep 17 21:56:52 linux-sporthorse hald: mounted /dev/hda on behalf of uid 1000
Sep 17 21:57:58 linux-sporthorse gconfd (afore-6207): starting (version 2.19.1), pid 6207 user 'afore'
Sep 17 21:57:58 linux-sporthorse gconfd (afore-6207): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep 17 21:57:58 linux-sporthorse gconfd (afore-6207): Resolved address "xml:readwrite:/home/afore/.gconf" to a writable configuration source at position 1
Sep 17 21:57:58 linux-sporthorse gconfd (afore-6207): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Sep 17 21:57:58 linux-sporthorse gconfd (afore-6207): Resolved address "xml:readonly:/etc/gconf/gconf.xml.schemas" to a read-only configuration source at position 3
Sep 17 21:58:06 linux-sporthorse kernel: usb 1-1: new high speed USB device using ehci_hcd and address 4
Sep 17 21:58:07 linux-sporthorse kernel: usb 1-1: new device found, idVendor=058f, idProduct=6387
Sep 17 21:58:07 linux-sporthorse kernel: usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=3
Sep 17 21:58:07 linux-sporthorse kernel: usb 1-1: Product: Mass Storage Device
Sep 17 21:58:07 linux-sporthorse kernel: usb 1-1: Manufacturer: JetFlash
Sep 17 21:58:07 linux-sporthorse kernel: usb 1-1: SerialNumber: GLQP6SI0
Sep 17 21:58:07 linux-sporthorse kernel: usb 1-1: configuration #1 chosen from 1 choice
Sep 17 21:58:07 linux-sporthorse kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Sep 17 21:58:07 linux-sporthorse kernel: usb-storage: device found at 4
Sep 17 21:58:07 linux-sporthorse kernel: usb-storage: waiting for device to settle before scanning
Sep 17 21:58:08 linux-sporthorse kernel:   Vendor: JetFlash  Model: TS8GJF168         Rev: 8.07
Sep 17 21:58:08 linux-sporthorse kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Sep 17 21:58:08 linux-sporthorse kernel: SCSI device sdf: 16023550 512-byte hdwr sectors (8204 MB)
Sep 17 21:58:08 linux-sporthorse kernel: sdf: Write Protect is off
Sep 17 21:58:08 linux-sporthorse kernel: sdf: Mode Sense: 03 00 00 00
Sep 17 21:58:08 linux-sporthorse kernel: sdf: assuming drive cache: write through
Sep 17 21:58:08 linux-sporthorse kernel: SCSI device sdf: 16023550 512-byte hdwr sectors (8204 MB)
Sep 17 21:58:08 linux-sporthorse kernel: sdf: Write Protect is off
Sep 17 21:58:08 linux-sporthorse kernel: sdf: Mode Sense: 03 00 00 00
Sep 17 21:58:08 linux-sporthorse kernel: sdf: assuming drive cache: write through
Sep 17 21:58:08 linux-sporthorse kernel:  sdf: sdf1
Sep 17 21:58:08 linux-sporthorse kernel: sd 6:0:0:0: Attached scsi removable disk sdf
Sep 17 21:58:08 linux-sporthorse kernel: sd 6:0:0:0: Attached scsi generic sg5 type 0
Sep 17 21:58:08 linux-sporthorse kernel: usb-storage: device scan complete
Sep 17 21:58:08 linux-sporthorse hald: mounted /dev/sdf1 on behalf of uid 1000
Sep 17 21:59:31 linux-sporthorse sudo:    afore : 1 incorrect password attempt ; TTY=pts/2 ; PWD=/home/afore ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
Sep 17 21:59:38 linux-sporthorse sudo:    afore : TTY=pts/2 ; PWD=/home/afore ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
Sep 17 21:59:38 linux-sporthorse sudo:    afore : TTY=pts/2 ; PWD=/home/afore ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
Sep 17 22:05:38 linux-sporthorse gconfd (root-6336): starting (version 2.19.1), pid 6336 user 'root'

/var/log/messages booting with 10.3 DVD

Sep 17 21:35:02 linux-sporthorse syslog-ng[5637]: syslog-ng version 1.6.12 starting
Sep 17 21:35:03 linux-sporthorse SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Sep 17 21:35:03 linux-sporthorse SuSEfirewall2: batch committing...
Sep 17 21:35:03 linux-sporthorse SuSEfirewall2: Firewall rules set to CLOSE.
Sep 17 21:35:04 linux-sporthorse ifup:     lo        
Sep 17 21:35:04 linux-sporthorse ifup:     lo        
Sep 17 21:35:04 linux-sporthorse ifup: IP address: 127.0.0.1/8  
Sep 17 21:35:04 linux-sporthorse ifup:  
Sep 17 21:35:04 linux-sporthorse ifup:     eth0      device: nVidia Corporation MCP55 Ethernet (rev a2)
Sep 17 21:35:04 linux-sporthorse ifup:               No configuration found for eth0
Sep 17 21:35:07 linux-sporthorse kernel: klogd 1.4.1, log source = /proc/kmsg started.
Sep 17 21:35:07 linux-sporthorse kernel: NET: Registered protocol family 10
Sep 17 21:35:07 linux-sporthorse kernel: lo: Disabled Privacy Extensions
Sep 17 21:35:07 linux-sporthorse kernel: Mobile IPv6
Sep 17 21:35:07 linux-sporthorse kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Sep 17 21:35:07 linux-sporthorse kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 17 21:35:07 linux-sporthorse kernel: Netfilter messages via NETLINK v0.30.
Sep 17 21:35:07 linux-sporthorse kernel: nf_conntrack version 0.5.0 (8192 buckets, 65536 max)
Sep 17 21:35:09 linux-sporthorse auditd[6457]: Started dispatcher: /sbin/audispd pid: 6459
Sep 17 21:35:09 linux-sporthorse kernel: audit(1190036109.575:3): audit_pid=6457 old=0 by auid=4294967295
Sep 17 21:35:09 linux-sporthorse audispd[6459]: listening on /var/run/audit_events
Sep 17 21:35:09 linux-sporthorse auditd[6457]: Init complete, auditd 1.5.5 listening for events
Sep 17 21:35:11 linux-sporthorse /usr/sbin/cron[6583]: (CRON) STARTUP (V5.0)
Sep 17 21:35:12 linux-sporthorse smartd[6611]: smartd version 5.37 [x86_64-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Home page is http://smartmontools.sourceforge.net/ 
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Opened configuration file /etc/smartd.conf
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Drive: DEVICESCAN, implied '-a' Directive on line 27 of file /etc/smartd.conf
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Problem creating device name scan list
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sda, opened
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device /dev/sda: ATA disk detected behind SAT layer
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   For example: '/dev/sda -a -d sat'
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sdb, opened
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device /dev/sdb: ATA disk detected behind SAT layer
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   For example: '/dev/sdb -a -d sat'
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sdc, opened
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device /dev/sdc: ATA disk detected behind SAT layer
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   For example: '/dev/sdc -a -d sat'
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sdd, opened
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device /dev/sdd: ATA disk detected behind SAT layer
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   For example: '/dev/sdd -a -d sat'
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sde, opened
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device /dev/sde: ATA disk detected behind SAT layer
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   Try adding '-d sat' to the device line in the smartd.conf file.
Sep 17 21:35:12 linux-sporthorse smartd[6611]:   For example: '/dev/sde -a -d sat'
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sda, opened
Sep 17 21:35:12 linux-sporthorse smartd[6611]: Device: /dev/sda, not found in smartd database.
Sep 17 21:35:13 linux-sporthorse SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Sep 17 21:35:13 linux-sporthorse SuSEfirewall2: using default zone 'ext' for interface eth0
Sep 17 21:35:13 linux-sporthorse smartd[6611]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
Sep 17 21:35:13 linux-sporthorse smartd[6611]: Device: /dev/sdb, opened
Sep 17 21:35:14 linux-sporthorse smartd[6611]: Device: /dev/sdb, not found in smartd database.
Sep 17 21:35:14 linux-sporthorse sshd[6727]: Server listening on :: port 22.
Sep 17 21:35:14 linux-sporthorse SuSEfirewall2: batch committing...
Sep 17 21:35:14 linux-sporthorse SuSEfirewall2: Firewall rules successfully set
Sep 17 21:35:14 linux-sporthorse smartd[6611]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list.
Sep 17 21:35:14 linux-sporthorse smartd[6611]: Device: /dev/sdc, opened
Sep 17 21:35:14 linux-sporthorse smartd[6611]: Device: /dev/sdc, not found in smartd database.
Sep 17 21:35:15 linux-sporthorse smartd[6611]: Device: /dev/sdc, is SMART capable. Adding to "monitor" list.
Sep 17 21:35:15 linux-sporthorse smartd[6611]: Device: /dev/sdd, opened
Sep 17 21:35:15 linux-sporthorse smartd[6611]: Device: /dev/sdd, not found in smartd database.
Sep 17 21:35:16 linux-sporthorse smartd[6611]: Device: /dev/sdd, is SMART capable. Adding to "monitor" list.
Sep 17 21:35:16 linux-sporthorse smartd[6611]: Device: /dev/sde, opened
Sep 17 21:35:16 linux-sporthorse smartd[6611]: Device: /dev/sde, found in smartd database.
Sep 17 21:35:16 linux-sporthorse smartd[6611]: Device: /dev/sde, is SMART capable. Adding to "monitor" list.
Sep 17 21:35:16 linux-sporthorse smartd[6611]: Monitoring 5 ATA and 0 SCSI devices
Sep 17 21:35:19 linux-sporthorse smartd[6861]: smartd has fork()ed into background mode. New PID=6861.
Sep 17 21:35:20 linux-sporthorse kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Sep 17 21:35:20 linux-sporthorse kernel: ISO 9660 Extensions: RRIP_1991A
Sep 17 21:35:20 linux-sporthorse hald: mounted /dev/sr0 on behalf of uid 1000
Sep 17 21:36:01 linux-sporthorse sudo:    afore : TTY=pts/2 ; PWD=/home/afore ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
Sep 17 21:36:01 linux-sporthorse sudo:    afore : TTY=pts/2 ; PWD=/home/afore ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
Sep 17 21:36:27 linux-sporthorse gconfd (afore-7223): starting (version 2.19.1), pid 7223 user 'afore'
Sep 17 21:36:27 linux-sporthorse gconfd (afore-7223): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep 17 21:36:27 linux-sporthorse gconfd (afore-7223): Resolved address "xml:readwrite:/home/afore/.gconf" to a writable configuration source at position 1
Sep 17 21:36:27 linux-sporthorse gconfd (afore-7223): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Sep 17 21:36:27 linux-sporthorse gconfd (afore-7223): Resolved address "xml:readonly:/etc/gconf/gconf.xml.schemas" to a read-only configuration source at position 3
Comment 11 Richard Creighton 2007-09-17 15:14:17 UTC 
Created attachment 172807 [details]
Log files from Art Fore 10.3 beta report

Art E=mailed his log files  -indicated difficulty attaching to original report - enclosed here for him.
Comment 13 Lukas Ocilka 2007-10-04 06:59:10 UTC 
See comment #7:

--- cut ---
But for now, the root cause is the
IDE/SATA issue followed by the upgrade bootloader failure which is the subject
of this bug.  Is the install upgrade bootloader different than the install new
bootloader?   It would seem so.
--- cut ---

I have to admit that I'm totally lost in this bug...
Comment 14 Richard Creighton 2007-10-04 07:32:54 UTC 
(In reply to comment #13 from Lukas Ocilka)
> See comment #7:
> 
> --- cut ---
> But for now, the root cause is the
> IDE/SATA issue followed by the upgrade bootloader failure which is the subject
> of this bug.  Is the install upgrade bootloader different than the install new
> bootloader?   It would seem so.
> --- cut ---
> 
> I have to admit that I'm totally lost in this bug...
> 
Good morning Lukas.  This bug started out because 10.3 could not update my 10.2 MD Raid installation.   It evolved into something having little to do with MD Raid and something to do with the IDE/SATA renaming decision and implementation.  This has generated, and is continuing to generate bug reports even in the GM from what I am seeing, and there are three main issues that have surfaced while debuging this original issue.  First, The installer has problems determining that a current MD Raid partition exists for upgrading and using that structure the same as it would as if it were a  physical structure.   10.2 did this properly.   Secondly, Because the IDE drive gets renamed from HDxx to SDAx during the upgrade but after the files are installed onto the SATA drives, when the MBR is updated and the /boot and GRUB files are updated, the installer expects to put them on what was SDAx (the SATA drive that has the new installation) but due to the renaming, SDAx is now the IDE drive which is the drive that gets the new MBR and /boot information by error.    Third, The repair program absolutely knows nothing about MD Raid and insists on 'repairing' the raw SATA partitions and not the MD raid file system contained on them.   As the repair program is running fsck which checks file systems, it should check file systems, not physical devices those file systems reside on., eg, it should check fsck /dev/md1 not fsck /dev/sdb1 when sdb1 is part of a MD array.   Thus, this bug really should be divided into 3 bugs for admin purposes, but that isn't my perogative as a user.  I reported the base problem and am hoping to amplify my findings as to the cause based upon months of research and experimentation.   I am not a systems programmer but I am willing to try to solve the problem.   It appears this problem is going to bite SuSE hard in several areas in GM when people with IDE equipment start trying to upgrade vs new installs.   I hope this helps.
Comment 15 Lukas Ocilka 2007-10-04 10:53:11 UTC 
Hmm, I've installed openSUSE 10.2 with this configuration:

/dev/hda6 -------------------------> /boot
/dev/hda7 --+
/dev/hdb6 --+
/dev/sda7 --+--> RAID5 /dev/md0 ---> /

Installation/Upgrade to openSUSE 10.3 GM detected the system well.
I haven't touched anything in the update proposal but the [Update] button ;)

Everything went OK, system boots OK.
Please give it a try with 10.3 GM.
Comment 16 Thomas Fehr 2007-10-04 10:58:46 UTC 
I assume the problem only happens if /boot is also on a MD raid (necessarily 
a raid1).
Comment 17 Richard Creighton 2007-10-04 13:14:26 UTC 
(In reply to comment #16 from Thomas Fehr)
> I assume the problem only happens if /boot is also on a MD raid (necessarily 
> a raid1).
> 

Yes, I supplied a partitioning info but basically the IDE drive was self contained and had 10.2 on it and was supposed to be exempt.  I set up the raid(s) plural IAW the HOWTO on the openSuSE website except for the one for the /home where I used a raid 5 and the example was a raid 1.   Swap was a raid 0, Boot was a raid 1, Root was a raid 1 and home was raid 5 (raid 1 in the howto).  Under 10.2, this worked perfectly and I could boot either installation, The one from the IDE drive OR the one contained on the RAID 1 MD installation /boot which had its own MBR which I could test by going to bios and selecting which device to boot from.   It would boot properly even if I electrically removed the IDE drive and left only the MD Raid installations.   There was NO stub drive anywhere.   This is the way it is now with 10.3 once I got it to work by removing the IDE and manually fudging around with GRUB and eventually getting it to write a MBR in the /boot raid and by editing boot.lst manually I coulld boot properly (and still do).   The problem only shows its head when the IDE drive is legacy equipment originaly HDxx and you are updating an installation on the SATA contained RAID.

A gentleman who also posted to this bug had a different configuration that I could not help him solve completely but he added his logs but it is obvious it is based upon a very similar scenerio and his is also a pure MD Raid installation whereas mine had the complication of the other install.   I also had a query from someone that had Windows that refused to boot after the install due to rewriting the MBR on the Windows drive destroying the Windows boot, but that I wasn't sure was related to MD Raid so I didn't mention it here before but it did relate to the renaming in the middle of an install problem that still seems to exist.   

The RC2 install went much nicer once I took out the IDE drive and even recognized there was a MD raid install to upgrade, it just didn't want to write back to the MD raid to update the grub/mbr even though the IDE drive wasn't there so it had nothing to do with the rename bug, Strictly the install to MD Raid.   When I debugged it, It had swapped the MD0 and MD1 array (swap and boot) which I had put in a different order.   I had to reinstall from scratch because there was too much damage when it wrote swap stuff in the boot partition before I could stop it.   Like I said, close but no cigar.  But the match stayed lit :)
Comment 18 Richard Creighton 2007-10-04 13:44:15 UTC 
(In reply to comment #15 from Lukas Ocilka)
> Hmm, I've installed openSUSE 10.2 with this configuration:
> 
> /dev/hda6 -------------------------> /boot
> /dev/hda7 --+
> /dev/hdb6 --+
> /dev/sda7 --+--> RAID5 /dev/md0 ---> /
> 
> Installation/Upgrade to openSUSE 10.3 GM detected the system well.
> I haven't touched anything in the update proposal but the [Update] button ;)
> 
> Everything went OK, system boots OK.
> Please give it a try with 10.3 GM.
> 

I am about 5 hours away from the completion of the GM download (torrent is slow) but your installation does not have /boot or the MBR (I suppose) ON THE RAID it appears which is different from the HOWTO and from the installations that have failed.   I will certainly try the GM when it finishes downloading though but for a proper test, the MBR and /boot need to be IN the MD raid structure as per the howto.   The setup I am running now has no external boot device of any kind, eg, everything is part of the MD raid structure (also supplied in one of the partition screenprints supplied as attachments) which I will resend showing how it is configured now.  This uses 8 drives, Four are used in MD raid and 4 are  attached to a hardware raid controller called /raidbox on the partitioning scheme.   It is when *everything* is as the Howto suggests and there is no external boot partition that things get messed up most.
Comment 19 Richard Creighton 2007-10-04 13:49:48 UTC 
Created attachment 176337 [details]
Partitioning scheme of MD Raid

Please note there is no device used to boot the system OTHER than the /boot contained completely within the MD raid structure.   Even the MBR is written on the /boot 'partition' contained therein.  This works flawlessly....until one tries to update it.   With 10.2, there was not a problem doing so, therefore it must be possible with 10.3 once things stabilize.
Comment 20 Richard Creighton 2007-10-06 14:53:58 UTC 
> 
> Everything went OK, system boots OK.
> Please give it a try with 10.3 GM.
> 

Update with IDE drive OUT of the equation went OK. Communicated with Art from above comment, he had success also.   Repair function still hosed (different bug), discovered a couple new ones I'll post shortly.   Given this bug relates only to ability to update a pure MD raid array installation, it appears to have been corrected provided there is NO IDE involved.   The IDE bug remains and the MBR is written to the IDE device even if the RAID device is entirely on the SATA devices but that was / is a separate issue.   Therefore, I am recommending that this bug be closed if the IDE/SATA aspects and the REPAIR aspects of the MD raid are being addressed.   If a new bug needs to be opened, I will be happy to do so but if it is already being handled, no sense adding noise to the equation.
Comment 21 Richard Creighton 2007-10-06 23:30:08 UTC 
Addendum:  Bug 331604 was opened for the IDE/SATA bug by someone else so the bug lives and hopefully will be addressed independently of this bug.
Comment 22 Cyril Hrubis 2007-10-17 17:57:39 UTC 
The IDE/SATA bug is living separately so that I'm reassigning this to fix repair functionality.
Comment 23 Jiří Suchomel 2007-10-17 19:35:16 UTC 
There is already a separate bug for MD RAID support in yast2-repair (bug 304657   
). Cyril, please close this as a duplicate of that IDE/SATA bug.
Comment 24 Cyril Hrubis 2007-10-18 11:38:24 UTC 

*** This bug has been marked as a duplicate of bug 331604 ***