SuSE 9.1. system doesn't boot after kernel update
Hello list, I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with "ReiserFS: hda2: checking transactions log (hda2)" as the last message. There the system stands forever. Booting with "Failsafe" doesn't works either, the system than hangs while initializing the PCI bus. I have then reinstalled the system without the adaptec and installed the kernel-update. Without the adaptec, the systems boots without any problems thereafter. Is this a known bug? Any hints how can to get the Adaptec to work with the updated kernel ? regards, martin -- Martin Markgraf Markgraf Network & Security Consulting mm@secprofs.de SecProfs - Your security professionals fon: +49 203 3469667 Prinz-Albrecht-Strasse 68 fax: +49 203 3469668 47058 Duisburg
--- Martin Markgraf <mm@secprofs.de> schrieb: > Hello list,
I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with
"ReiserFS: hda2: checking transactions log (hda2)"
as the last message. There the system stands forever.
Hi, this seems to be a very common problem with SATA and also with some systems without SATA but more than one harddisks - i'm sorry but i don't really know any details except that a lot of people are having this problem :-( you may want to look at this german discussion about this issue: http://linuxforen.de/forums/showthread.php?t=140825&page=1&pp=15 best regards Franz ___________________________________________________________ Bestellen Sie Y! DSL und erhalten Sie die AVM "FritzBox SL" für 0. Sie sparen 119 und bekommen 2 Monate Grundgebührbefreiung. http://de.adsl.yahoo.com
Franz Mach wrote:
--- Martin Markgraf <mm@secprofs.de> schrieb: > Hello list,
I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with
"ReiserFS: hda2: checking transactions log (hda2)"
as the last message. There the system stands forever.
Hi,
this seems to be a very common problem with SATA and also with some systems without SATA but more than one harddisks - i'm sorry but i don't really know any details except that a lot of people are having this problem :-(
you may want to look at this german discussion about this issue: http://linuxforen.de/forums/showthread.php?t=140825&page=1&pp=15
Thank you for your reply. Unfortunaly the guys there have also no solution so far. regards, martin -- Martin Markgraf Markgraf Network & Security Consulting mm@secprofs.de SecProfs - Your security professionals fon: +49 203 3469667 Prinz-Albrecht-Strasse 68 fax: +49 203 3469668 47058 Duisburg
On Mon, Jun 21, 2004 at 02:50:48PM +0200, Martin Markgraf wrote:
Hello list,
I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with
"ReiserFS: hda2: checking transactions log (hda2)"
hda2 is your root ?
as the last message. There the system stands forever.
Did you try pci=noacpi ? If that doesn't help please boot into single user mode with the adaptec by specifying single on the boot loader prompt, then do echo 1 > /proc/sys/kernel/sysrq echo 9 > /proc/sys/sysrq-trigger klogconsole -r0 mount -n -o remount,rw / (if hda2 wasn't your root do mount /path/to/hda2mountpoint ) Does it already hang? Are there are any messages on the screen? If it hangs do alt-sysrq-t and check for the backtrace of the mount process and report that. Best would be if you could connect a serial console before this to catch all messages. -Andi
Hi, Andi Kleen wrote:
On Mon, Jun 21, 2004 at 02:50:48PM +0200, Martin Markgraf wrote:
Hello list,
I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with
"ReiserFS: hda2: checking transactions log (hda2)"
hda2 is your root ?
Yes, it is.
as the last message. There the system stands forever.
Did you try pci=noacpi ?
So far, I have only try the "failsafe" settings together (ide=nodma apm=off acpi=off )which make things even worse. The system than hang trying to initialize the pci bus.
If that doesn't help please boot into single user mode with the adaptec by specifying single on the boot loader prompt, then do
echo 1 > /proc/sys/kernel/sysrq echo 9 > /proc/sys/sysrq-trigger klogconsole -r0 mount -n -o remount,rw / (if hda2 wasn't your root do mount /path/to/hda2mountpoint )
Does it already hang? Are there are any messages on the screen?
Hmm to try this, I have to reinstall the the update which I wouldn't like at this time, because the system is in use at the moment. Perhaps I have time to try this at the weekend.
If it hangs do alt-sysrq-t and check for the backtrace of the mount process and report that.
Best would be if you could connect a serial console before this to catch all messages.
Thank you for your suggestions, I hope I find time to try them out at the weekend. regards, martin -- Martin Markgraf Markgraf Network & Security Consulting mm@secprofs.de SecProfs - Your security professionals fon: +49 203 3469667 Prinz-Albrecht-Strasse 68 fax: +49 203 3469668 47058 Duisburg
On Monday 21 June 2004 16:08, Andi Kleen wrote:
On Mon, Jun 21, 2004 at 02:50:48PM +0200, Martin Markgraf wrote:
Hello list,
I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with
"ReiserFS: hda2: checking transactions log (hda2)"
hda2 is your root ?
as the last message. There the system stands forever.
Did you try pci=noacpi ?
If that doesn't help please boot into single user mode with the adaptec by specifying single on the boot loader prompt, then do
echo 1 > /proc/sys/kernel/sysrq echo 9 > /proc/sys/sysrq-trigger klogconsole -r0 mount -n -o remount,rw / (if hda2 wasn't your root do mount /path/to/hda2mountpoint )
Does it already hang? Are there are any messages on the screen?
If it hangs do alt-sysrq-t and check for the backtrace of the mount process and report that.
Best would be if you could connect a serial console before this to catch all messages.
-Andi
I've got the same problem as Martin Markgraf mentions above with kernel-default-2.6.5-7.75 . With me some other people do have this problem (according to the list Franz Mach pointed me to). Recovering is easy, just restore the original kernel or one of the earlier update kernels. My system has a MSI K8T Neo mainboard, AMD Athlon 64, one sata disk and a pata disk with Suse 9.1 on the sata disk and WinXP on the pata disk. For testing purposes I've got an installation of Suse 9.1 as well on the /hda3 as /hda2. The installation on /hda2 uses a LVM system on my extended partition, the installation on /hda3 has nothing special. Installed kernel-default-2.6.5-7.75 on /hda3. After that the system hangs during boot with the message: ReiserFS: hda3: checking transaction log (hda3) Tried the options mentioned by Andi Kleen above with my installation on /hda3. 1] pci=noacpi --> made it worse (even ctrl-alt-del or alt-sysrq-t didn't work anymore) I had to power off the system to reboot 2] specified 'single' on the boot prompt -->did'nt make difference, the system still hangs, so I don't reach the echo part 3] I did alt-sysrq-t after [2] but the output is too much to write down manually, can you specify more exact what to look for? Sorry, but I don't have a nullmodem cable for creating a serial console Roel Vestjens
On Tuesday 22 June 2004 I mentioned a problem with kernel-default-2.6.5-7.75. The system kept hanging during boot with the message: "ReiserFS: hda3: checking transaction log (hda3)" Reinstalling the original default kernel from dvd solved my booting problem. After fixing the system I tried to find out what went wrong and if it's something to do with my system (MSI K8T Neo mainboard, AMD Athlon 64 3000, one s-ata disk and a p-ata disk with Suse 9.1 on the sata disk and WinXP on the pata disk) or the installation. A lot of people (not only with the 64 bit kernel version) had the same problem with this particular kernel update. Reading many messages I discovered that the latest patch of mkinitrd and the new kernel patch kernel-default-2.6.5-7.95 seemed to solve this problem. So did I, but kept the same booting problem. Even after a complete clean install from DVD, followed with an update of just the mkinitrd patch and after a reboot updating the kernel to kernel-default-2.6.5-7.95. An update to the latest kernel from ftp.suse.com/pub/projects/kernel/kotd/x86_64 doesn't solve my problem either. Everything I tried, different booting parameters, skipping my second disk and usb in fstab, it didn't make any difference. The system still stops with the annoying line: "ReiserFS: hda3: checking transaction log (hda3)" I expect it has really something to do with SuSE specific modifications of the kernel because a clean install of the 2.6.7 kernel (compilation from source) results in a working system. Can anyone give me a clue what causes this problem? Roel Vestjens
After reading another fifty messages in the German SuSE mailing list someone mentioned a solution SuSE mailed to him:
boot with 'barrier=off', some IDE disks need it.
I tried it and ... my system boots again!!! Roel. On Sunday 25 July 2004 22:28, Roel Vestjens wrote:
On Tuesday 22 June 2004 I mentioned a problem with kernel-default-2.6.5-7.75. The system kept hanging during boot with the message: "ReiserFS: hda3: checking transaction log (hda3)" Reinstalling the original default kernel from dvd solved my booting problem.
After fixing the system I tried to find out what went wrong and if it's something to do with my system (MSI K8T Neo mainboard, AMD Athlon 64 3000, one s-ata disk and a p-ata disk with Suse 9.1 on the sata disk and WinXP on the pata disk) or the installation. A lot of people (not only with the 64 bit kernel version) had the same problem with this particular kernel update. Reading many messages I discovered that the latest patch of mkinitrd and the new kernel patch kernel-default-2.6.5-7.95 seemed to solve this problem.
So did I, but kept the same booting problem. Even after a complete clean install from DVD, followed with an update of just the mkinitrd patch and after a reboot updating the kernel to kernel-default-2.6.5-7.95. An update to the latest kernel from ftp.suse.com/pub/projects/kernel/kotd/x86_64 doesn't solve my problem either. Everything I tried, different booting parameters, skipping my second disk and usb in fstab, it didn't make any difference. The system still stops with the annoying line: "ReiserFS: hda3: checking transaction log (hda3)"
I expect it has really something to do with SuSE specific modifications of the kernel because a clean install of the 2.6.7 kernel (compilation from source) results in a working system.
Can anyone give me a clue what causes this problem?
Roel Vestjens
participants (4)
-
Andi Kleen -
Franz Mach -
Martin Markgraf -
Roel Vestjens