system does not boot due to device-mapper error
Bug #398059 reported by
Roman Shtylman
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.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
tags: | added: regression-potential |
Changed in linux: | |
status: | Confirmed → Fix Released |
Changed in linux (Ubuntu): | |
assignee: | nobody → Andy Whitcroft (apw) |
status: | Triaged → In Progress |
Changed in linux: | |
importance: | Unknown → High |
To post a comment you must log in.
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".