crying hard disk on reboot

Thank you for taking the time to report this bug and helping to make Ubuntu better. You inidcate that you are running Gutsy yet this bug report is filed against the 2.6.22 kernel and the 2.6.24 kernel. Have you test this with Hardy? Thanks in advance.

I 've tested this problem with Gutsy 2.6.22 from repos, 2.6.24-rc4 (kernel.org, hardy config) and Hardy 2.6.22, but I will test it with Hardy 2.6.24 soon.

Thanks

So tested it with Hardy alpha 2+updates from today:

Kernel 2.6.24-2-generic and bug is still not fixed.

I have the same laptop, with the same kernel and with the same problem. The second hard disk makes a terrible noise while rebooting, but this also affects vista. Only while rebooting. If I shut down usually, there is nothing unnormal to hear.

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

I'v already tested this issue with Hardy Alpha 2 relase as you can read 3 posts above. Thanks

Perhaps this might be helpfull:

Output of lspci -vv:
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3) (prog-if 85 [Master SecO PriO])
        Subsystem: Hewlett-Packard Company Unknown device 30cf
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0 (750ns min, 250ns max)
        Interrupt: pin A routed to IRQ 23
        Region 0: I/O ports at 30f8 [size=8]
        Region 1: I/O ports at 30ec [size=4]
        Region 2: I/O ports at 30f0 [size=8]
        Region 3: I/O ports at 30e8 [size=4]
        Region 4: I/O ports at 30d0 [size=16]
        Region 5: Memory at b0004000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Output of cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA Model: TOSHIBA MK1637GS Rev: DL03
  Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA Model: TOSHIBA MK1637GS Rev: DL03
  Type: Direct-Access ANSI SCSI revision: 05

Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks!

I've opened a new task against the actively developed kernel and am closing the task against linux-source-2.6.22. Thanks!

Hi Tobias,

Can you actually attach your logs files for the newer Hardy release. It should be for the 2.6.24 kernel. Also, Hardy Alpha3 will be out in a day or two. You might want to wait and retest and then get the log files. Thanks.

Latest Hardy kernel updates didn't fix the problem. Thanks.

Tested with a fresh alpha 4 amd64 and i386 - still not fixed. Thanks.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

The error still occurs with latest Intrepid kernel 2.6.27-1.2

But I now figured out, that it does not, if the hard drive is unmounted before reboot (tested with sdb as non root fs).

Perhaps someone can work around this, writing a smoothy init script, unfortunately I'm not skilled enough to do it on my own.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]