Works find with Ubuntu 16.04 + 4.10.1-041001-generic
The kernel is downloaded from Ubuntu website
motherboard ASUS PRIME B350-PLUS.
** Attachment added: "Screenshot from 2017-03-13 16-53-20.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4836844/+files/Screensh
CPU is Ryzen 1700x
However lm-sensor is not working properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360
Title:
System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recogniz
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Titl
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 Ubuntu
Bu
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ub
Tried kernel v4.6-yakkety. Not working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
To manage notifications about this
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
To manage notifications about this bug go to:
https://bugs.launchpa
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
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 +
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
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
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
sdd is a usable external hard drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
To manage notifications about this bug
Ubuntu 14.04.4
lsblk
NAME MAJ:MIN RM
SIZE RO TYPE MOUNTPOINT
sda 8:00
931.5G 0 disk
├─sda1 8:1
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 Ubuntu
Bugs
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel Shipp
/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 Ubuntu
Bugs,
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
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
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717395/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717388/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Titl
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717401/+files/WifiSyslog.txt
** 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 the
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717396/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/161
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717393/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kern
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717390/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717391/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717398/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717397/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717392/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kern
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717400/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717389/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Kernel
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717399/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Title:
Ke
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717394/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611277
Public bug reported:
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 kernel to linux-images-4.4.0-34-generic only
The result is that the mapper was
Are we able to change the kernel of 14.04 to support docker images?
Cause upgrading to 16.04.1 ruins my fakeRaid with devicemapper set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557776
Title:
C
42 matches
Mail list logo
