Your message dated Sun, 08 Dec 2013 04:38:15 +0000
with message-id <[email protected]>
and subject line Re: Bug#731660: linux image 486: The system is looking for
/dev/hdaX while only /dev/sdaX are available
has caused the Debian Bug report #731660,
regarding linux image 486: The system is looking for /dev/hdaX while only
/dev/sdaX are available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
731660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731660
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-3.2.0-4-486
Objet : linux image 486: The system is looking for /dev/hdaX while only
/dev/sdaX are available
Date : dimanche 8 décembre 2013, 02:17:01
De : Yohann Ferreira <[email protected]>
À : [email protected]
Hi there,
I've been updating an Toshiba Tecra today (2005-2006 laptop), and I noticed
that since that between the kernel version 2.6.32 and the kernel versions
3.2.0 and 3.11 there is a quite meaningful difference;
When using the linux kernel (linux-image-486) 3.2.0 or 3.11 version, the
system doesn't start and complains about not finding the /dev/hda2 (which is my
root system partition). The fact is that there is no hda2, but only sda[1-5]
there.
The system then prompts me to give a location, and starts when I give
'/dev/sda2' but only to fail later on as many other scripts complain about not
finding hda2 as well.
This is currently functionning correctly when using the kernel 2.6.32 as there
are hdaX nodes there.
Is this a bug? And if it isn't, how can I translate those nodes correctly when
booting the new kernels?
Best regards,
-----------------------------------------
--- End Message ---
--- Begin Message ---
On Sun, 2013-12-08 at 02:23 +0100, Yohann Ferreira wrote:
> Package: linux-image-3.2.0-4-486
>
>
> Objet : linux image 486: The system is looking for /dev/hdaX while only
> /dev/sdaX are available
> Date : dimanche 8 décembre 2013, 02:17:01
> De : Yohann Ferreira <[email protected]>
> À : [email protected]
>
> Hi there,
>
> I've been updating an Toshiba Tecra today (2005-2006 laptop), and I noticed
> that since that between the kernel version 2.6.32 and the kernel versions
> 3.2.0 and 3.11 there is a quite meaningful difference;
>
> When using the linux kernel (linux-image-486) 3.2.0 or 3.11 version, the
> system doesn't start and complains about not finding the /dev/hda2 (which is
> my
> root system partition). The fact is that there is no hda2, but only sda[1-5]
> there.
> The system then prompts me to give a location, and starts when I give
> '/dev/sda2' but only to fail later on as many other scripts complain about
> not
> finding hda2 as well.
>
> This is currently functionning correctly when using the kernel 2.6.32 as
> there
> are hdaX nodes there.
> Is this a bug? And if it isn't, how can I translate those nodes correctly
> when
> booting the new kernels?
This is not a kernel bug. You should not refer to /dev/hda in any
configuration files. You should be able to fix most of these
configuration files automatically by booting into the old kernel,
running 'dpkg-reconfigure linux-base' and answering 'yes' twice.
Ben.
--
Ben Hutchings
Knowledge is power. France is bacon.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
