Ubuntu
update-manager package

Feisty>Gutsy upgrade bricked my hard drives

Bug #156366 reported by dsiddens on 2007-10-23

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	Invalid	Undecided	Michael Vogt

Bug Description

I used the update notification at Synaptic Package Manager on my Feisty laptop to begin the Gutsy upgrade. After the files were obtained it began replacing Feisty to Gutsy versions. As the files were being written, I noticed quite a few dependencies errors with their messages that a given file (program) would not be installed or might not work properly. This message suggested that I file a bug report. A bit further on into this upgrade process I noticed that there were messages giving me the option to "compare the differences" between the file I had and the new file. So on one of these messages, I don't know which one, I selected "D" and was given a command line screen that described stuff I did not know about and then sat there saying "end".

I figured that hitting enter would return me to the install process. Not so. The machine was sitting at the command prompt waiting for, I don't know what. Eventually I thought if I did a power down/up that the install process would pick up from where it left off. Again, not so. I tried booting from the regular kernal choice and from the recovery mode, neither of which yeilded a working computer.

From the screens that stopped on the boot attempts I wrote down the last screen of each attempt. The significant lines are:

For the kernel 2.6.22-14 (recovery mode)
[10.960197]/build/buildd/linux-source-2.6.22-2.6.22/drivers/ftc/hc.tosys.c: unable to open rtc device(rtc0)
[10.973499] input: AT Translated Set 2 keyboard as /class/input/input1
[11.063970] VFS: Cannot open root device "UUID =adc16267-58e2-4882-9850-9da2e35d482" or unknown-block (0,0)
[11.064022] Please append a correct "root=" boot option; here are the available partitions:
[11.064075] Kernel panic - not sysncing: VFS: Unable to mount root fs on unknown-block (0,0)

For the kernel 2.6.22.14-generic
[16.798468] PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
[17.014051] Kernal panic-not syncing: VFS: Unable to mount root fs on unknown-block (0,0)

At the bottom of the screen:
Kernel alive
kernel direct mapping tables up to 100000000@8000-d000

I had other boot choices which I went through and tried them all with the result that I was brought to a light blue screen with a cursor that I could move around but no text or sign-in boxes.

The machine in question is an HP dv8000 AMD64 laptop with two internal hard drives. It was running fine with the Feisty software.
I've used our second laptop to download the Gutsy AMD64 .iso and burn a CD. I am at the "bricked" laptop as I write this, but only on the CD. I want help with finding, identifying and recovering important files, if not the entire hard disks. Such files include e-mail, boat information, passwords, bookmarks, etc. This is the second time in an upgrade process that this level of screw-up has happened. Last time was Dapper to Edgy and I lost all information. Help, please! Doug

Thank you, Doug

Revision history for this message

Michael Vogt (mvo) wrote on 2007-10-24:

Thanks for taking the time to report this bug and helping to make Ubuntu better.

A big sorry that you experienced a problem like this. Have you tried booting with the 2.6.20 kernel that should be still instaleld on your system?

If you still have access to the harddrive, could you please add the log files from '/var/log/dist-upgrade/' to this bugreport as attachments to your bug report?

Thanks in advance,
Michael

Changed in update-manager:
assignee:	nobody → mvo
status:	New → Incomplete

Revision history for this message

dsiddens (angel03) wrote on 2007-10-25: Re: [Bug 156366] Re: Feisty>Gutsy upgrade bricked my hard drives

Thank you Michael for your reply. Where the situtation is: I went to town and bought a new WD120 2" drive and have a successful install from the Gutsy CD that I made from the .iso download. As for access to the hd, yes it's sitting on my brief case! This HP dv8000 laptop (amd64) has space for two hd's. I had two inside, they are both out now, only the new 120G is in. Tomorrow I'll put back in the drive that was the primary and see what I can see using the new Gutsy install. I must tell you that I'm ignorant of the command line. So I'll be looking for GUI apps that will let me poke at the bricked drive(s).

Thank you again for your response and if you know of a GUI way to look at the drives I'd appreciate learning about it.

Thanks, Doug Siddens aboard SV Drakus in Oriental NC

---- Michael Vogt <email address hidden> wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better.
>
> A big sorry that you experienced a problem like this. Have you tried
> booting with the 2.6.20 kernel that should be still instaleld on your
> system?
>
> If you still have access to the harddrive, could you please add the log
> files from '/var/log/dist-upgrade/' to this bugreport as attachments to
> your bug report?
>
> Thanks in advance,
> Michael
>
> ** Changed in: update-manager (Ubuntu)
> Assignee: (unassigned) => Michael Vogt (mvo)
> Status: New => Incomplete
>
> --
> Feisty>Gutsy upgrade bricked my hard drives
> https://bugs.launchpad.net/bugs/156366
> You received this bug notification because you are a direct subscriber
> of the bug.

Revision history for this message

dsiddens (angel03) wrote on 2007-10-26:

Michael, I put the previous primary hd into the #2 position of the
laptop drive bay. When I tried to boot I got a locked machine sitting
at a light blue screen. When I took the software damaged drive out and
booted from the new hd and Gutsy it came up fine. I did not change
anything about the Gusty hd.

Doug

dsiddens wrote:
> Thank you Michael for your reply. Where the situtation is: I went to
> town and bought a new WD120 2" drive and have a successful install from
> the Gutsy CD that I made from the .iso download. As for access to the
> hd, yes it's sitting on my brief case! This HP dv8000 laptop (amd64)
> has space for two hd's. I had two inside, they are both out now, only
> the new 120G is in. Tomorrow I'll put back in the drive that was the
> primary and see what I can see using the new Gutsy install. I must tell
> you that I'm ignorant of the command line. So I'll be looking for GUI
> apps that will let me poke at the bricked drive(s).
>
> Thank you again for your response and if you know of a GUI way to look
> at the drives I'd appreciate learning about it.
>
> Thanks, Doug Siddens aboard SV Drakus in Oriental NC
>
>

Revision history for this message

dsiddens (angel03) wrote on 2007-10-28:

Michael,
Thank you for your considerate reply. However, the drive in
question, when inserted into the laptop's #2 position somehow prevent
the new hd with a functioning install of Gutsy from booting. Can you
please recommend a GUI program that will allow me to manipulate the
bricked drives and pull off the files I need? If such a thing is not
possible can I send the drives to Ubuntu headquarters and have one of
the 'brains' make a recovery and examination for the purpose of
improving Ubuntu? I'll pay postage and insurance both ways.

Thank you Doug

Michael Vogt wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better.
>
> A big sorry that you experienced a problem like this. Have you tried
> booting with the 2.6.20 kernel that should be still instaleld on your
> system?
>
> If you still have access to the harddrive, could you please add the log
> files from '/var/log/dist-upgrade/' to this bugreport as attachments to
> your bug report?
>
> Thanks in advance,
> Michael
>
> ** Changed in: update-manager (Ubuntu)
> Assignee: (unassigned) => Michael Vogt (mvo)
> Status: New => Incomplete
>
>

Revision history for this message

dsiddens (angel03) wrote on 2007-11-02: Re: 3 minute boot time

Hello Michael,

I've not received any other communications from you, with the exception
of the tea and sympathy email, so thought I'd write to you again.

Issue #1: I still have two bricked hard drives with data on them. Can
you help me get my data?

Issue #2: I put in a _new hard drive_ and installed Gutsy 64 on the HP
dv8000, Turion64, 2G RAM laptop. Boot time to get to the user name and
password screens is 3:04 minutes!

Your assistance will be much appreciated.

Thank you, Doug Siddens aboard SV Drakus

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2007-12-13:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in update-manager:
status:	Incomplete → Invalid

Revision history for this message

dsiddens (angel03) wrote on 2007-12-14:

I did a hot insert of the bricked h.d. into the #2 h.d. bay of the HP dv8000. The system became unresponsive except for the cursor still being able to move. I removed the bricked h.d. and the system responds as expected. Would it make a difference if I put a jumper on the master/slave pins of the bricked h.d.? Right now there is no jumper on those pins.The drive is a Seagate Momentus 5400.2 120GB.

Changed in update-manager:
status:	Invalid → New

Revision history for this message

dsiddens (angel03) wrote on 2007-12-14:

I shut down the computer, removed the functioning Gutsy h.d., installed the bricked h.d. in the #1 postion and powered on. The machine stopped with the following on screen:
[13.443102] PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
[13.443146] PCI: Cannot allocate resource region 8 of bridge 0000:00:04.0
[13.658688] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

and at the bottom of the screen:
Kernel alive
kernel direct mapping tables up to 100000000@8000-d000

in addition to the above on-screen messages, the caps lock led was flashing

Doug

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-02-01:

not an update-manager issue.

Changed in update-manager:
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuupdate-manager package

Feisty>Gutsy upgrade bricked my hard drives

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
update-manager package