*** This bug is a duplicate of bug 154591 ***
https://bugs.launchpad.net/bugs/154591
The Problem seems to be in a list of Seagate harddrives which require
special treatments. Here is the source code that causes problems:
static const struct drive_list_entry hpa_list[] = {
{ "ST340823A
*** This bug is a duplicate of bug 154591 ***
https://bugs.launchpad.net/bugs/154591
I confirm this bug and just added an Open Question #16234. My details:
I upgraded Feisty to Gutsy but found Gutsy reboot hung with the message:
udevd-event[2118]: run_program : '/sbin/modprobe' abnormal exi
*** This bug is a duplicate of bug 154591 ***
https://bugs.launchpad.net/bugs/154591
It seems to be a problem with Seagate hard drives and the Gutsy kernel.
** This bug has been marked a duplicate of bug 154591
7.10 live cd does not boot, the error: udevd-event[2292]: modprobe abnormal
ex
Silly me, I thought I was answering to an LP question instead. :-)
--
hard drive not detected since gutsy update
https://bugs.launchpad.net/bugs/156428
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
I have no idea but I *know* that one of my machines dies right after
finishing booting here with Gutsy. The stopgap measure was to just boot
with the older, feisty kernel (letting grub know that the default boot
entry was the feisty one because that machine is headless and I don't
have time to lug
Thanks for your answer Rudd-O.
But why Feisty have no problem to mount that drive ? And why I can boot on this
partition ?
Because, if I understand your answer, it's a problem, maybe material, of my
hard drive.
I think, if you're right, that I'll try to resolve the problem with the
manufacturer
NB: this is a internal hard drive.
** Attachment added: "uname -a & lspci -v"
http://launchpadlibrarian.net/10142851/uname%20-a%20%26%20lspci%20-v
--
hard drive not detected since gutsy update
https://bugs.launchpad.net/bugs/156428
You received this bug notification because you are a member
It seems it's dying on first platter access to read the partition
tables, *or* it is chewing some corrupt partition information and
barfing after that. The backtrace seems to point to my first hunch. I
wish I could do more :-(.
--
hard drive not detected since gutsy update
https://bugs.launchpa
