I know this is probably a separate issue, but this is the most recent
article I can find on dmraid. I can't get the dmraid to activate on
boot. I downloaded and installed the 16.04 packages that are listed in
this thread, but it isn't hooking into my boot sequence properly.
--
You received this b
On a Dell Dimension 5150:
Does not work with /boot/vmlinuz-4.4.0-34-generic
Works properly with /boot/vmlinuz-3.13.0-93-generic
Two disks / RAID1.
Boot very slow including grub.
syslog shows a deep slow down when activating UUID access.
-> First when activating swap.
-> When fstab is adapted to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dmraid (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
Thank you very much! Currently the system works normally with the raid
devices loaded.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Ca
About your question about maximum RAID size: I cannot answer that. There
possibly are different limits on what dmraid can construct via device-
mapper (those are likely higher than 4TB). But then there might be
limits that the meta-data which the BIOS uses impose. And I have no clue
there.
--
You
** Attachment added:
"libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723896/+files/libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb
--
You received this bug notification because you are a membe
Those packages are compiled against 14.04 user-space and should need no
update for libdevmapper.
** Attachment added: "dmraid_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723895/+files/dmraid_1.0.0.rc16-4.2ubuntu4~14.04.1_am
Oh, sorry, wait a second. I think I made a mistake and compiled the
package against 16.04 user-space.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ub
It says my libdevmapper (2:1.02.77) is too old, it needs (2:1.02.97)
instead. So I should install the patch after I switched the kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/16112
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status in dmraid package in Ubuntu:
Con
I'm only using Linux on this PC. But the migration process seems to
tired. Maybe I'll just stick to the dmraid if there's not major
problems.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
So now I'll just have to install these two packages and switch to a
newer kernel to see if the fix works? Another question is that does
dmraid have maximum size limit of the raid devices (something like raid
1 up to 4TB)?
--
You received this bug notification because you are a member of Kernel
Pa
** Attachment added: "libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723890/+files/libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packa
Sorry, I was distracted by other things. So I will be attaching a
proposed update to dmraid and some pre-built package to test. I just
cannot promise that change will be accepted.
About converting to mdadm: That would be an option that might be more
future proof but only if you do not want to use
** Attachment added: "dmraid_1.0.0.rc16-4.2ubuntu4_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723889/+files/dmraid_1.0.0.rc16-4.2ubuntu4_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Sorry to bother you, since dmraid as no update anymore, so is it
recommended to use mdadm instead? Is the transfer possible or I'll have
to wipe out the whole disk and rebuild it? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Sadly, Marvell SATA controller seems to have its own configuration (I'll
try to send a mail to GigaByte support). I've checked the hotplug
related options in the BIOS, they are all turned off.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
The commit is a legit stable fix and part of the Ubuntu 16.04 kernel since
version 4.4.0-18 (your dmesg shows you a re running 4.4.0-34). So unfortunately
not helping in your case. I extracted the relevant syslog data below. >From
that info, the two disks are connected to a Marvell controller in
Tried kernel v4.6-yakkety. Not working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status in dmraid packa
Hi, is the change log of kernel 4.4.5 a valid upstream commit?
commit a55479ab637cda5ebbfdb9eb7c062bd99c13d5d9
Author: Manuel Lauss
Date: Sat Feb 27 16:10:05 2016 +0100
ata: ahci: don't mark HotPlugCapable Ports as external/removable
commit dc8b4afc4a04fac8ee55a19b59f2356a25e7e778
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status in dmraid package in Ubuntu:
Confirmed
Status
Yes, it sounds like that is the initial trigger. So somewhere between
3.16 and 4.4 the kernel got better in declaring which disk drives could
be hot-plugged. And the AHCI and (likely) the fakeraid modes potentially
support to hot-plug disks (you could have externally accessible drive
bays). Sometim
I found someone has similar problem using 4.4.0 kernel in arch linux.
Are these events related?
dmraid thinks my array devices are removable (they aren't...)
https://bbs.archlinux.org/viewtopic.php?id=208580
[SOLVED] Hard disk partitions showing up as removable devices
https://bbs.archlinux.org/v
Ubuntu 14.04.4 + 4.4.0-34-generic
NOTICE: creating directory /var/lock/dmraid
WARN: locking /var/lock/dmraid/.lock
NOTICE: skipping removable device /dev/sdb
NOTICE: skipping removable device /dev/sdc
WARN: missing dm serial file for /dev/dm-0
WARN: missing dm serial file for /dev/dm-1
NOTICE: /de
Ubuntu 14.04.4 + 3.16.0-77-generic
NOTICE: creating directory /var/lock/dmraid
WARN: locking /var/lock/dmraid/.lock
WARN: missing dm serial file for /dev/dm-0
WARN: missing dm serial file for /dev/dm-1
WARN: missing dm serial file for /dev/dm-2
WARN: missing dm serial file for /dev/dm-3
NOTICE: /d
So it appears that "dmraid -r -d -d -v -v -v" would produce enough
output to at least see whether it is trying the disks which contain the
raid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
What you see (the multipath message) is from a kernel module that gets
loaded. That does not necessarily mean it is really used. That is the
way that dmraid, lvm, multipath and mdadm work. Only mdadm is different
in using different kernel driver modules than the rest.
But in general the commands a
I saw this line
Aug 10 11:26:09 bblabcloud kernel: [ 26.001170] device-mapper:
multipath: version 1.7.0 loaded
when the system startup.
But when I type multipath in terminal, I was told multipath is not
installed. Is the multipath in the terminal is a config tool to config
the device-mapper mult
The following commands are executed in Ubuntu 14.04.4 + 4.4.0-34-generic
1. dmraid -d -r
DEBUG: not isw at 17091787776
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 17090705920
DEBUG: not isw at 982805117952
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 982804036096
The following commands are executed in Ubuntu 14.04.4 +
3.16.0-77-generic
1. dmraid -d -r
DEBUG: not isw at 2000313908224
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 2000312826368
DEBUG: not isw at 2000315046912
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 2000313
I got some time and did a rebuild of dmraid in Xenial, which completed.
So I am not really understanding why running dmraid in 16.04 does claim
to find nothing while it does succeed in 14.04. I am attaching the two
debs here just in case an actual rebuild produces something different
than before.
** Attachment added: "libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu3_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4718232/+files/libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu3_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packa
That sounds more like, despite dmraid using ddf in the name, the BIOS
uses some different format which mdadm does not recognize. So that would
mean you cannot switch from dmraid to mdadm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
So am I able to switch from dmraid to mdadm to control the raid1 without
affecting the hard drive in Ubuntu 14.04.4?
Because when I do a fresh install of Ubuntu 16.04.1, which comes with
Kernel 4.4.0-34, mdadm (pre-installed in 16.04.1 already) says my raid
device does not have recognized superblo
The 14.01.x output is not that surprising, dmraid is setting up the
raid1 as device-mapper targets. The problem is that dmraid has been
abandoned upstream. So the package is unchanged since 14.04 (that could
mean it does not even compile anymore).
So there might be some options:
1. Sicne mdadm is
sdd is a usable external hard drive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status in linux package i
Ubuntu 14.04.4
lsblk
NAME MAJ:MIN RM
SIZE RO TYPE MOUNTPOINT
sda 8:00
931.5G 0 disk
├─sda1 8:1
Oh I think I meant ddf not dds in my previous post. So it could be that
this just moved from being handled by dmraid to mdadm. Could you add the
output of lsblk and "cat /proc/mdstat", please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Yes, I've already done that. I try to use dmraid with arg "-ay" to scan
any possible raid devices when I changed kernel in 14.04.4, and dmraid
returns no raid found. fdisk shows /dev/sdb and /dev/sdc as
ddf_raid_member.
--
You received this bug notification because you are a member of Kernel
Pack
Sure, those BIOS fakeraid boards are getting rare (meaning only you can
do tests and provide info). So you can (with the current 16.04.1 kernel)
check whether the dmraid package is still installed. If yes, try to run
it in various modes (there is one to only show things, but also one that
is suppos
Sure, I've rolled back to the working kernel after the boot failed.
Thank you!
Is there any thing I can do to fix this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
The user-space tool that is responsible to set up fakeraid (except for
Intel MSM and DDS style meta-data). Make sure that package is still
installed and the dmraid command is still usable.
A rc1 mainline kernel is probably a bit too recent since the first
release candidate can always be unstable.
/scripts/init-top/udev: line 14: can't create /sys/kernel/uevent-helper:
Permission denied.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check root delay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing m
Sorry, I'm not able to boot my PC with kernel
4.8.0-040800rc1_4.8.0-040800rc1.201608072231.
The error message is as follows:
/scripts/init-top/udev: line 14: can't create /sys/kernel/uevent_helper:
permissions failed
--
You received this bug notification because you are a member of Kernel
Packa
Yes, you can remove the mainline kernel with dpkg --purge
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Stat
Is testing the upstream kernel able to reverse back to the original
state just like I install the 4.4.0-34-generic on Ubuntu 14.04.4?
After the trial, am I able to remove the upstream kernel with apt-get
remove and purge? Thanks.
--
You received this bug notification because you are a member of
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
Comment #17 should have said the "latest v4.8 kernel"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status i
apport information
** Tags added: apport-collected trusty
** Description changed:
Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
from Ubuntu 14.04. I've tried three ways but none of them work.
1. Update 14.04.4 to 16.04.1
2. Fresh install 16.04.1
3. Update kern
49 matches
Mail list logo