dmraid thinks my array devices are removable (they aren't...)

schmidtbag · 2016-02-06 19:42:43

I have a RAID0 setup that I use to store game data on, and it is used by both Arch and Windows. To clarify - no OS boots off of it, and it is built by the motherboard. On Arch, I've been using dmraid to access the array and have been for well over a year. Earlier this week I ran an update, and I can no longer access the array anymore. I don't have a /dev/dm-1 anymore and the only file /dev/mapper/ is "control". Running "dmraid -ay" says "no raid disks". Windows can use the array no problem.

Running "dmesg | grep sdb" says:

[    3.367083] sd 12:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[    3.367151] sd 12:0:0:0: [sdb] Write Protect is off
[    3.367153] sd 12:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.367181] sd 12:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.395249]  sdb: sdb1
[    3.395252] sdb: p1 size 976744448 extends beyond EOD, enabling native capacity
[    3.396144]  sdb: sdb1
[    3.396148] sdb: p1 size 976744448 extends beyond EOD, truncated
[    3.396364] sd 12:0:0:0: [sdb] Attached SCSI removable disk
[  408.623426]  sdb: sdb1
[  408.623441] sdb: p1 size 976744448 extends beyond EOD, truncated
[  412.598527]  sdb: sdb1
[  412.598554] sdb: p1 size 976744448 extends beyond EOD, truncated
[  412.603175]  sdb: sdb1
[  412.603204] sdb: p1 size 976744448 extends beyond EOD, truncated
[  429.344016]  sdb: sdb1
[  429.344041] sdb: p1 size 976744448 extends beyond EOD, truncated

And for sdc:

[    3.380627] sd 13:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[    3.380679] sd 13:0:0:0: [sdc] Write Protect is off
[    3.380683] sd 13:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    3.380708] sd 13:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.409823] sd 13:0:0:0: [sdc] Attached SCSI removable disk

Last edited by schmidtbag (2016-02-12 01:48:49)

schmidtbag · 2016-02-10 03:17:51

I tried running "dmraid -ay -vvv -d" and it outputted the following:

WARN: locking /var/lock/dmraid/.lock
NOTICE: skipping removable device /dev/sdb
NOTICE: skipping removable device /dev/sdc
NOTICE: skipping removable device /dev/sdd
NOTICE: /dev/sda: asr     discovering
NOTICE: /dev/sda: ddf1    discovering
NOTICE: /dev/sda: hpt37x  discovering
NOTICE: /dev/sda: hpt45x  discovering
NOTICE: /dev/sda: isw     discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi     discovering
NOTICE: /dev/sda: nvidia  discovering
NOTICE: /dev/sda: pdc     discovering
NOTICE: /dev/sda: sil     discovering
NOTICE: /dev/sda: via     discovering
no raid disks
WARN: unlocking /var/lock/dmraid/.lock

This is weird, because sda has nothing to do with my array and both sdb and sdc are not removable devices (but, sdd is).

schmidtbag · 2016-02-12 01:27:15

I have confirmed that this is specifically an issue with Arch. I tried booting a separate disk based on Debian Jessie, and it was able to mount the array without a problem. Here is the output (for Debian, the disks are sdd and sde):

WARN: locking /var/lock/dmraid/.lock
NOTICE: skipping removable device /dev/sdf
NOTICE: /dev/sde: asr     discovering
NOTICE: /dev/sde: ddf1    discovering
NOTICE: /dev/sde: hpt37x  discovering
NOTICE: /dev/sde: hpt45x  discovering
NOTICE: /dev/sde: isw     discovering
DEBUG: not isw at 250059348992
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 250058267136
NOTICE: /dev/sde: jmicron discovering
NOTICE: /dev/sde: jmicron metadata discovered
NOTICE: /dev/sde: lsi     discovering
NOTICE: /dev/sde: nvidia  discovering
NOTICE: /dev/sde: pdc     discovering
NOTICE: /dev/sde: sil     discovering
NOTICE: /dev/sde: via     discovering
NOTICE: /dev/sdd: asr     discovering
NOTICE: /dev/sdd: ddf1    discovering
NOTICE: /dev/sdd: hpt37x  discovering
NOTICE: /dev/sdd: hpt45x  discovering
NOTICE: /dev/sdd: isw     discovering
DEBUG: not isw at 250059348992
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 250058267136
NOTICE: /dev/sdd: jmicron discovering
NOTICE: /dev/sdd: jmicron metadata discovered
NOTICE: /dev/sdd: lsi     discovering
NOTICE: /dev/sdd: nvidia  discovering
NOTICE: /dev/sdd: pdc     discovering
NOTICE: /dev/sdd: sil     discovering
NOTICE: /dev/sdd: via     discovering
NOTICE: /dev/sdc: asr     discovering
NOTICE: /dev/sdc: ddf1    discovering
NOTICE: /dev/sdc: hpt37x  discovering
NOTICE: /dev/sdc: hpt45x  discovering
NOTICE: /dev/sdc: isw     discovering
DEBUG: not isw at 160041884672
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 160040802816
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi     discovering
NOTICE: /dev/sdc: nvidia  discovering
NOTICE: /dev/sdc: pdc     discovering
NOTICE: /dev/sdc: sil     discovering
NOTICE: /dev/sdc: via     discovering
NOTICE: /dev/sdb: asr     discovering
NOTICE: /dev/sdb: ddf1    discovering
NOTICE: /dev/sdb: hpt37x  discovering
NOTICE: /dev/sdb: hpt45x  discovering
NOTICE: /dev/sdb: isw     discovering
DEBUG: not isw at 500107860992
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 500106779136
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi     discovering
NOTICE: /dev/sdb: nvidia  discovering
NOTICE: /dev/sdb: pdc     discovering
NOTICE: /dev/sdb: sil     discovering
NOTICE: /dev/sdb: via     discovering
NOTICE: /dev/sda: asr     discovering
NOTICE: /dev/sda: ddf1    discovering
NOTICE: /dev/sda: hpt37x  discovering
NOTICE: /dev/sda: hpt45x  discovering
NOTICE: /dev/sda: isw     discovering
DEBUG: not isw at 64023256064
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 64022174208
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi     discovering
NOTICE: /dev/sda: nvidia  discovering
NOTICE: /dev/sda: pdc     discovering
NOTICE: /dev/sda: sil     discovering
NOTICE: /dev/sda: via     discovering
DEBUG: _find_set: searching jmicron_GRAID
DEBUG: _find_set: not found jmicron_GRAID
DEBUG: _find_set: searching jmicron_GRAID
DEBUG: _find_set: not found jmicron_GRAID
NOTICE: added /dev/sde to RAID set "jmicron_GRAID"
DEBUG: _find_set: searching jmicron_GRAID
DEBUG: _find_set: found jmicron_GRAID
DEBUG: _find_set: searching jmicron_GRAID
DEBUG: _find_set: found jmicron_GRAID
NOTICE: added /dev/sdd to RAID set "jmicron_GRAID"
DEBUG: checking jmicron device "/dev/sdd"
DEBUG: checking jmicron device "/dev/sde"
DEBUG: set status of set "jmicron_GRAID" to 16
RAID set "jmicron_GRAID" already active
INFO: Activating stripe raid set "jmicron_GRAID"
NOTICE: discovering partitions on "jmicron_GRAID"
NOTICE: /dev/mapper/jmicron_GRAID: dos     discovering
NOTICE: /dev/mapper/jmicron_GRAID: dos metadata discovered
DEBUG: _find_set: searching jmicron_GRAID1
DEBUG: _find_set: not found jmicron_GRAID1
NOTICE: created partitioned RAID set(s) for /dev/mapper/jmicron_GRAID
RAID set "jmicron_GRAID1" already active
INFO: Activating partition raid set "jmicron_GRAID1"
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "jmicron_GRAID"
DEBUG: freeing device "jmicron_GRAID", path "/dev/sdd"
DEBUG: freeing device "jmicron_GRAID", path "/dev/sde"
DEBUG: freeing devices of RAID set "jmicron_GRAID1"
DEBUG: freeing device "jmicron_GRAID1", path "/dev/mapper/jmicron_GRAID"

Note that Debian only considers sdf to be removable, which is true (it's a flash drive).

Last edited by schmidtbag (2016-02-12 01:30:21)

jasonwryan · 2016-02-12 01:32:51

What was in the update you ran? New kernel, perhaps?

schmidtbag · 2016-02-12 01:50:13

jasonwryan wrote:

What was in the update you ran? New kernel, perhaps?

I don't remember. Nothing really unusual stood out during the update and everything else was working fine at the time. I've run more updates since then in the hopes that maybe they fixed something, and so far no luck.

I'm running 4.4.1-2 (64 bit) if that makes a difference.

Last edited by schmidtbag (2016-02-12 01:51:56)

jasonwryan · 2016-02-12 01:57:20

schmidtbag wrote:

jasonwryan wrote:
What was in the update you ran? New kernel, perhaps?
I don't remember.

That is why pacman has a log... Look through it and see what candidates for downgrading are in there. If you can isolate your issue to a specific package, you make the next steps so much easier.

schmidtbag · 2016-02-12 02:18:50

Looking in the log all the way back to Feb 1, the kernel, linux-firmware, and most suspiciously, device-mapper seem to be the potential candidates that got updated. I don't appear to have any of the older packages of these anymore. But nothing else really stood out that appears to be relevant to this problem in anyway (stuff like vlc or libovr). This setup is pretty minimal. I run steam, VLC, firefox, and LXQt on it - that's about it.

device-mapper is actually required by dmraid. I'm not yet sure where to get an older version of it, but I wonder if that's the issue. dmraid itself is pretty old, so I doubt that's the source of the problem.

Last edited by schmidtbag (2016-02-12 02:24:25)

jasonwryan · 2016-02-12 02:23:37

You should have the last version in your cache: you could try downgrading to see if that assembles the array.

schmidtbag · 2016-02-12 02:27:43

I don't have it in my cache. The last update to it was in late November; my cache has been cleared since then.

jasonwryan · 2016-02-12 02:31:47

Use the rollback machine.

And read

paccache --help

schmidtbag · 2016-02-12 02:57:57

I installed "downgrade", and with it downloaded mirrors of the last version of lvm2, device-mapper, and "linux" that I'm pretty sure were still working. None of these seemed to fix my problem.

jasonwryan · 2016-02-12 03:03:05

That's all I got. I use mdadm for my RAID arrays, so I have no experience with dmraid. Sorry.

schmidtbag · 2016-02-12 03:09:18

Seeing as I have so few things installed on this system, I might just try doing a fresh new install and see if that helps.

Normally, I would do mdadm, but since Windows uses this same array I figured doing fakeraid would be easier to deal with. And overall I was right - Windows detected the array automatically and doing "dmraid -ay" in Linux is a pretty effortless way to initialize a disk.

severach · 2016-02-12 07:15:55

Hard disk partitions showing up as removable devices

Arch Linux

#1 2016-02-06 19:42:43

dmraid thinks my array devices are removable (they aren't...)

#2 2016-02-10 03:17:51

Re: dmraid thinks my array devices are removable (they aren't...)

#3 2016-02-12 01:27:15

Re: dmraid thinks my array devices are removable (they aren't...)

#4 2016-02-12 01:32:51

Re: dmraid thinks my array devices are removable (they aren't...)

#5 2016-02-12 01:50:13

Re: dmraid thinks my array devices are removable (they aren't...)

#6 2016-02-12 01:57:20

Re: dmraid thinks my array devices are removable (they aren't...)

#7 2016-02-12 02:18:50

Re: dmraid thinks my array devices are removable (they aren't...)

#8 2016-02-12 02:23:37

Re: dmraid thinks my array devices are removable (they aren't...)

#9 2016-02-12 02:27:43

Re: dmraid thinks my array devices are removable (they aren't...)

#10 2016-02-12 02:31:47

Re: dmraid thinks my array devices are removable (they aren't...)

#11 2016-02-12 02:57:57

Re: dmraid thinks my array devices are removable (they aren't...)

#12 2016-02-12 03:03:05

Re: dmraid thinks my array devices are removable (they aren't...)

#13 2016-02-12 03:09:18

Re: dmraid thinks my array devices are removable (they aren't...)

#14 2016-02-12 07:15:55

Re: dmraid thinks my array devices are removable (they aren't...)

Board footer