I worked around this by removing the long name
/dev/isw_/p1 and replacing it with /dev/dm-1 in the
/etc/fstab
Interestingly, this is the 2nd raid in the system. The first one mounts
with no problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358491
Title:
Have anyone found a solution? I have the same problem here..
"conflicting device node '/dev/mapper/1sw_bchgjehgcf_biosraid6' found,
link to '/dev/dm-6' will not be created"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
TJ, I have the same problem on my home system, a HP Z600 with hardware
RAID.
Looking at the results from 4 different reboots today:
$ grep "conflicting device node" https://bugs.launchpad.net/bugs/1358491
Title:
[Trusty] fails to boot with kernels later than v3.11: systemd-
udevd[133]: confl
blausand, I'm afraid I've not spent much time on this issue since I
developed the work-around of moving the rootfs. As it only affected the
forensics server when hot-swap disks with dmraid metadata were attached
I've not re-visited this issue so far.
--
You received this bug notification because
I have the very same problem and it freaks me out because i cannot return to
the much older kernel that woud boot.
*I kindly request some guidance to a temporary manual fix.*
The mapper-ID (isw_) seems to change from time to time. I don't know if
that stems from the Ubuntu (Studio 14.04 LTS)
The 'fake' RAID controller has two disks attached. Each is configured as
separate RAID-0 stripe arrays - this is because the controller doesn't
support JBOD pass-through.
This issue is caused by the LVM volumes on a fake-RAID device failing to
be ready because the LVM VG_CADDY/rootfs is not create
Looking closer, the reason 3.11.x starts is that there are no dmraid
device-mapper nodes created at all. I'm modifying the /init script so I
can break in early, and re-run it to break-points of my choice, to do
more diagnosis.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (tj)
*
Due to bug 560246 "Launchpad requires the REFERER header on form
submission..." apport-collect cannot send the system diagnostic data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358491
Title:
[T
** Attachment added: "Successful boot with kernel 3.11.0-12-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358491/+attachment/4181112/+files/caddy-good.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
10 matches
Mail list logo
