drives not mounting on startup

[C. Villforth]

Since I upgraded to Karmic Koala (Kubuntu), my drives do not mount at startup. At boot I see a very short message saying that drives could not be mounted. The system freezes right before it goes to the login screen. I am able to get around this by booting to recovery, then shutting down the system (I need to press the power button as "shutwdon now" wont shutdown but returns to recovery mode). After that the system boots in normal mode, but is broken again each time I shut it down. Older kernels are not working, they produce a corrupted screen after about 10 sec.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: carolin 1747 F.... pulseaudio
                      carolin 1750 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfebf4000 irq 16'
   Mixer name : 'Realtek ALC660-VD'
   Components : 'HDA:10ec0660,10430000,00100001 HDA:10573055,10431316,00100700'
   Controls : 23
   Simple ctrls : 15
Date: Sun Nov 1 19:19:17 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=4821d6b2-d6bf-4332-99ea-ce0c6bfea716
MachineType: ASUSTeK Computer Inc. F5R
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=2bf0348e-de02-47e9-aed7-bcd5168001f2 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel paging request at 4047077d
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:

dmi.bios.date: 01/16/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5RAS.3
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F5R
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5RAS.3:bd01/16/2007:svnASUSTeKComputerInc.:pnF5R:pvr1.0:rvnASUSTeKComputerInc.:rnF5R:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: F5R
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Jeremy Foshee (jeremyfoshee)]

Hi C.,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 470772

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[C. Villforth (carovi)]

Hi,

The problem never really went away, I was later on able to boot, but
there seems to have been problems with the mounting (for example when
doing the harddrive checks that run every 30th boot or so, the print
out did not show the mountpoint '\dev\sda2' or so but some incredible
long combination of numbers ). Some weeks ago, the whole file system
broke (I am not sure if it was in any way related), but I havent tried
to reinstall ubuntu on the laptop as I have bought a new one.

Greetings

Carolin

On Apr 22, 2010, at 12:53 PM, Jeremy Foshee wrote:

> Hi C.,
>
> This bug was reported a while ago and there hasn't been any activity
> in it recently. We were wondering if this is still an issue? Can you
> try with the latest development release of Ubuntu? ISO CD images
> are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a
> Terminal (Applications->Accessories->Terminal). It will
> automatically gather and attach updated debug information to this
> report.
>
> apport-collect -p linux 470772
>
> Also, if you could test the latest upstream kernel available that
> would be great. It will allow additional upstream developers to
> examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds
> . Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag. This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug
> description and deleting the 'needs-upstream-testing' text. Please
> let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> drives not mounting on startup
> https://bugs.launchpad.net/bugs/470772
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Since I upgraded to Karmic Koala (Kubuntu), my drives do not mount
> at startup. At boot I see a very short message saying that drives
> could not be mounted. The system freezes right before it goes to the
> login screen. I am able to get around this by booting to recovery,
> then shutting down the system (I need to press the power button as
> "shutwdon now" wont shutdown but returns to recovery mode). After
> that the system boots in normal mode, but is broken again each time
> I shut it down. Older kernels are not working, they produce a
> corrupted screen after about 10 sec.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to
> be restarted.
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: carolin 1747 F.... pulseaudio
> carolin 1750 F.... kmix
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0...

[Jeremy Foshee (jeremyfoshee)]

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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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.]