system does not boot due to device-mapper error

Bug #398059 reported by Roman Shtylman
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
High
linux (Ubuntu)
Fix Released
High
Andy Whitcroft

Bug Description

When trying to boot into the 2.6.31-2-generic kernel (or any .31 kernel for that matter) My system hangs with the error:

"device-mapper: table: 252:0: sda too small for target"

The above error just keeps getting echoed out to the screen. This did not happen prior to the .31 kernel(s)

/ is on two disks in raid 0. Each disk is 32GB making a total of 64GB for root. There is 37GB of free space on root.

I use dmraid for my multidisk setup and up until this kernel line have never experience such an error in booting.

Revision history for this message
Gerhard Bogner (bogi788) wrote :

I can reproduce this on 9.04 with the 2.6.31-rc2 kernel from the ubuntu kernel PPA:

When booting dmraid fails to set up the raid devices and dmesg shows "device-mapper: table: 252:0: sda too small for target" and "device-mapper: table: 252:0: sdb too small for target".

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Stagger (stagger-jmk) wrote :

I am also affected by this. I have a two disc raid 0 (ICH9R fakeraid, Abit IP35 Pro).

Revision history for this message
Stagger (stagger-jmk) wrote :

Also happens with the 2.6.31-rc3 kernel from the repositories.

Revision history for this message
Jacques L. (asdfgerv) wrote :

I can confirm this with all 2.6.31 kernels in karmic to date, *and* with the latest kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/. The 2.6.30 kernel that used to be in the repositories works fine though (using it at the moment).

My system is on two disc on raid0 with intel software raid.

When I try to activate the raid set manually from the busybox shell prompt, after the boot sequence times out, (by typing dmraid -ay), I get the message 'The set isw_ezfgzegerh_zef could not be activated' (or similar).

Revision history for this message
EagleDM (eagle-maximopc) wrote :

I can confirm this also, with ICH10R, I filed a bug and I am experiencing the same problem, cannot get activated and cannot boot with dmraid with the same message.

Revision history for this message
Roman Shtylman (shtylman) wrote :

Has anyone filed a bug against the kernel on the kernel bug tracker? If so, can we get the link here?

Revision history for this message
EagleDM (eagle-maximopc) wrote :

DMRAID is so bugged that now I'm afraid of just using it and wasting my entire array, someone should definetly post on the kernel bug tracker, we don't need more bugs, with dmraid alone is enough.

Changed in linux:
status: Unknown → Confirmed
Revision history for this message
Kano (master-kanotix) wrote :

For Kanotix I patch my kernels using this patch since I found it, works fine. Ubuntu seems to ignore my hints in the IRC, so here you have it again in your beloved LP:

http://patchwork.kernel.org/patch/33534/

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
tags: added: regression-potential
Revision history for this message
Roman Shtylman (shtylman) wrote :

I have tested a kernel with the patch (.31-4) and it worked for me. I was able to boot my system just fine.

Revision history for this message
Daniel T Chen (crimsun) wrote :
Changed in linux:
status: Confirmed → Fix Released
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
status: Triaged → In Progress
Revision history for this message
Andy Whitcroft (apw) wrote :

It seems that a version of this patch has been mainlined since 2.6.31-rc4 and will be in the next rebase of the Karmic kernel which should occur this week:

  commit 5dea271b6d87bd1d79a59c1d5baac2596a841c37
  Author: Mike Snitzer <email address hidden>
  Date: Thu Jul 23 20:30:42 2009 +0100

    dm table: pass correct dev area size to device_area_is_valid

    Incorrect device area lengths are being passed to device_area_is_valid().

    The regression appeared in 2.6.31-rc1 through commit
    754c5fc7ebb417b23601a6222a6005cc2e7f2913.

    With the dm-stripe target, the size of the target (ti->len) was used
    instead of the stripe_width (ti->len/#stripes). An example of a
    consequent incorrect error message is:

      device-mapper: table: 254:0: sdb too small for target

    Signed-off-by: Mike Snitzer <email address hidden>
    Signed-off-by: Alasdair G Kergon <email address hidden>

Revision history for this message
Daniel T Chen (crimsun) wrote :

Fixed in the -5.24 upload.

Changed in linux (Ubuntu):
status: In Progress → Fix Released
Changed in linux:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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