This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notifications about
This bug was fixed in the package curtin - 0.1.0~bzr351-0ubuntu1
---
curtin (0.1.0~bzr351-0ubuntu1) xenial; urgency=medium
* New upstream snapshot.
* partitioning: limited support for odd ordering of partition
numbers (LP: #1543263). Specifically targetted at MAAS and
** Changed in: curtin
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notifications about th
** Branch linked: lp:~smoser/curtin/trunk.lp1532062
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notifications about this bug go to
more info here, and I'm going to merge Robert's change.
On a system the kernel team has, the value of 'removable' changed even from
one version of a kernel to another.
$ uname -r
4.2.0-27-generic
$ cat /sys/class/block/sda/removable
0
But on 4.4.0-2-generic that same sysatem shows that drive as
** Branch linked: lp:~returntoreptar/curtin/removable-drive-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notifications about
I'm guessing that this particular scsi controller supports hot plug and
so identifies the drives as removable since technically you can yank out
the raid bays and replace them while the system is on. The whole
concept of whether a drive is "removable" or not is a hand waving best
guess that really
** Changed in: curtin
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistak
Sure no problem! I have attached the output of sudo lshw as a file,
since it was a bit long.
** Attachment added: "Output of lshw on system with "removable" drives."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1532062/+attachment/4548195/+files/lshw-output-anakin
--
You received th
Robert,
I took a quick gander at util-linux source, and it is just reading
/sys/class/block//removable
There isnt' any util-linux specific knowledge that says "this is
removable", but rather its just telling you what the kernel is telling
it.
Would you mind posting/attaching:
sudo lshw
?
I r
shoot. you're right. i was just reading columns wrong. I was reading the 'RO'
as 'RM'.
thanks for your patience. At least lsblk is providing consitent information,
so that is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Sounds good, here is the output from: lsblk --pairs "--output=$full" /dev/sda
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0B" DISC-MAX="0B" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sda" LABEL="" LOG-SEC="512" MAJ:MIN="8:0" MIN-IO="512"
MODE="brw-rw" MODEL="main" MOUNTPOINT="" NAME="s
Sorry I should've known that wouldn't format correctly once I posted, I
have tried to structure the lsblk -l output here:
http://pastebin.com/hQktMbXg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/153
ok, so this is wierd, lets focus on 'sda' and see if we can't prune this down.
>From your statements in the bug opening:
$ lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 100G 0 disk
sda1 8:1 1 100G 0 part /
but then, when we do the longer 'lsblk --bytes --pairs --output=...' command in
Sure, output is below (sorry its a bit hard to structure it in an easy
to read manner here):
lsblk --bytes --pairs --output=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX
,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-
IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-
SIZE,SIZE,STA
hm... actually, reading your 'lsblk' output above, those devices do
*not* show as removable.
could you collect output of this:
lsblk --bytes --pairs
--output=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY
Just a note, 'RM' is what curtin is reading as 'removable'.
Not that this is definitive, but
http://linoxide.com/linux-command/linux-lsblk-command/ indicates that RM means
removable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
18 matches
Mail list logo
