Questions[dmraid](ubuntu)

Background : this trouble appears after an upgrade from ubuntu 16.04 to 18.04. My /home partition was on my Ubunutu 16.04 a raid 5 partition from 3 disk, manage with lvm2. I have absolutly no trouble. After upgrade with command "do-release-upgrade" from Ubuntu 16.04 to 18.04, the first reboot failed. I send a first message on this trouble : Trouble after upgrade 16.04 -> 18.04 - device mapper? Now, it's more clear about my comprehension of trouble.

Actually, I have disactivate use of raid disk, by editing /etc/fstab and comment mounting point of /home . So now I have a starting server under Ubuntu 18.04, without any data from my raid disks.

So now, I try to recover data that are on my 3 disks, previously use in RAID 5.

So now, I try :

root@xxx:~# dmraid -s
*** Group superset isw_eaabdhefe
--> Subset
name   : isw_eaabdhefe_raid5
size   : 7814048256
stride : 256
type   : raid5_la
status : ok
subsets: 0
devs   : 3
spares : 0
root@xxx:~#  dmraid -r
/dev/sdc: isw, "isw_eaabdhefe", GROUP, ok, 3907029166 sectors, data@ 0
/dev/sde: isw, "isw_eaabdhefe", GROUP, ok, 3907029166 sectors, data@ 0
/dev/sdd: isw, "isw_eaabdhefe", GROUP, ok, 3907029166 sectors, data@ 0
root@xxx:~# 

So according most of documentation, I'm ready to activate raid group with :

root@xxx:~# dmraid -ay
RAID set "isw_eaabdhefe_raid5" was not activated
root@xxx:~#

more precise

root@xxx:~# dmraid -tay
isw_eaabdhefe_raid5: 0 7814048256 raid raid5_la 4 256 nosync region_size 131072 3 - /dev/sdc - /dev/sdd - /dev/sde
root@xxx:~# 

Each time I try to activate, I have theses lines in dmesg :

[xxx] device-mapper: table: 253:0: raid: RAID device lookup failure
[xxx] device-mapper: ioctl: error adding target to table

I have also try :

root@xxx:~# dmraid -ay -vvv -d
WARN: locking /var/lock/dmraid/.lock
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 180045765632
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 180044683776
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
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: isw metadata found at 2000398932992 from probe at 2000398932992

NOTICE: /dev/sdc: isw metadata discovered
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/sde: asr     discovering
NOTICE: /dev/sde: ddf1    discovering
NOTICE: /dev/sde: hpt37x  discovering
NOTICE: /dev/sde: hpt45x  discovering
NOTICE: /dev/sde: isw     discovering
DEBUG: isw metadata found at 2000398932992 from probe at 2000398932992

NOTICE: /dev/sde: isw metadata discovered
NOTICE: /dev/sde: jmicron discovering
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/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 160041884672
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 160040802816
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/sdd: asr     discovering
NOTICE: /dev/sdd: ddf1    discovering
NOTICE: /dev/sdd: hpt37x  discovering
NOTICE: /dev/sdd: hpt45x  discovering
NOTICE: /dev/sdd: isw     discovering
DEBUG: isw metadata found at 2000398932992 from probe at 2000398932992

NOTICE: /dev/sdd: isw metadata discovered
NOTICE: /dev/sdd: jmicron discovering
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
DEBUG: _find_set: searching isw_eaabdhefe
DEBUG: _find_set: not found isw_eaabdhefe
DEBUG: _find_set: searching isw_eaabdhefe_raid5
DEBUG: _find_set: searching isw_eaabdhefe_raid5
DEBUG: _find_set: not found isw_eaabdhefe_raid5
DEBUG: _find_set: not found isw_eaabdhefe_raid5
NOTICE: added /dev/sdc to RAID set "isw_eaabdhefe"
DEBUG: _find_set: searching isw_eaabdhefe
DEBUG: _find_set: found isw_eaabdhefe
DEBUG: _find_set: searching isw_eaabdhefe_raid5
DEBUG: _find_set: searching isw_eaabdhefe_raid5
DEBUG: _find_set: found isw_eaabdhefe_raid5
DEBUG: _find_set: found isw_eaabdhefe_raid5
NOTICE: added /dev/sde to RAID set "isw_eaabdhefe"
DEBUG: _find_set: searching isw_eaabdhefe
DEBUG: _find_set: found isw_eaabdhefe
DEBUG: _find_set: searching isw_eaabdhefe_raid5
DEBUG: _find_set: searching isw_eaabdhefe_raid5
DEBUG: _find_set: found isw_eaabdhefe_raid5
DEBUG: _find_set: found isw_eaabdhefe_raid5
NOTICE: added /dev/sdd to RAID set "isw_eaabdhefe"
DEBUG: set status of set "isw_eaabdhefe_raid5" to 16
DEBUG: dm_raid: low level dev /dev/sdc
DEBUG: dm_raid: low level dev /dev/sdd
DEBUG: dm_raid: low level dev /dev/sde
RAID set "isw_eaabdhefe_raid5" was not activated
INFO: Activating GROUP raid set "isw_eaabdhefe"
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "isw_eaabdhefe_raid5"
DEBUG: freeing device "isw_eaabdhefe_raid5", path "/dev/sdc"
DEBUG: freeing device "isw_eaabdhefe_raid5", path "/dev/sdd"
DEBUG: freeing device "isw_eaabdhefe_raid5", path "/dev/sde"
DEBUG: freeing devices of RAID set "isw_eaabdhefe"
DEBUG: freeing device "isw_eaabdhefe", path "/dev/sdc"
DEBUG: freeing device "isw_eaabdhefe", path "/dev/sdd"
DEBUG: freeing device "isw_eaabdhefe", path "/dev/sde"
root@xxx:~# 

Can anybody help me to understand theses lines ?

more information :

root@xxx:~# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/Ivy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 05)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation C204 Chipset LPC Controller (rev 05)
00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
06:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 07)
root@xxx:~# 

root@xxx:~# ls -al /dev/mapper/
total 0
drwxr-xr-x  2 root root      60 avril  1 12:30 .
drwxr-xr-x 22 root root    4340 avril  1 17:33 ..
crw-------  1 root root 10, 236 avril  1 12:30 control
root@xxx:~# 

root@xxx:~# cat /proc/partitions 
major minor  #blocks  name

   8        0  175825944 sda
   8        1     975872 sda1
   8        2  174848000 sda2
   8       16  156290904 sdb
   8       17   31249408 sdb1
   8       18    9765888 sdb2
   8       19    2097152 sdb3
   8       20  113176576 sdb4
   8       64 1953514584 sde
   8       32 1953514584 sdc
   8       48 1953514584 sdd
   9      126 3907023872 md126
root@xxx:~# 

root@xxx:~# dmraid -V
dmraid version:     1.0.0.rc16 (2009.09.16) shared 
dmraid library version: 1.0.0.rc16 (2009.09.16)
device-mapper version:  4.37.0
root@xxx:~# 

root@xxx:~# uname -a
Linux xxx 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
root@xxx:~# 

sdc, sdd, sde are disks used for raid volume.

I can send more information, just request.

I got a new Lenovo Ideapad Flex 5, recently. Previously, I had been using a 10-year-old system. A lot of things have changed since then and I wasn't up-to-date with the latest tech.

So this new system has a single 500GB NVMe SSD and had Windows 10 pre-installed on it. Now I want to install Ubuntu as well (dual boot). For this, I shrunk my Windows partition to half (originally, there was only a single partition with Windows 10 installed on it).

Now I started the Ubuntu 18.04 setup (from a USB) and proceeded with installing it. But it couldn't recognize my SSD :(

So, I started digging in for a solution. I found that there's an option in the BIOS namely, SATA Controller Mode which was set to "Intel RST Premium" (the other option is AHCI).

A little bit lookup on the Internet tells me that Intel RST premium technology is an application for managing RAID arrays. So I am not sure what this BIOS option is.

I decided to just switch to AHCI mode but then I would have to re-install Windows 10 (which I don't want to). Furthermore, while changing to AHCI mode it gives me a warning - "Existing data stored on drivers will be erased when resetting controller mode. Proceed?", to which obviously I say No, because I don't know which "data" and "driver" is it talking about.

Also, let's say if I change to AHCI mode, do I lose some performance for Windows? (Oh c'mon, Intel RST Premium has cool words like rapid and premium in it. Don't tell me they are just for name's sake?!!)

Next, I also came across very similar questions on SE but some of them talk about how to switch to AHCI mode without re-installing Windows, while someone else talked about utilities such as dmraid and mdadm to configure things.

I am unsure what to do next. I just want to dual boot Windows and Ubuntu ...and live a peaceful life.

I have a single hard drive that the OS is installed on and I have Sil raid card installed with two matching 500GB hdds set up in Raid 0 and formatted- they're completely empty. For whatever reason they are showing up as /dev/sdb and /dev/sdc and not as a single hard drive. I used fdisk to format both raid drives as Linux raid auto (fd) but I cannot mount either device and dmraid doesn't seem to want to work, what step am I missing?

When I installed 9.04 oh so long ago it seems like it recognized and automatically did everything that needed to be done, now I'm stuck.

dmraid Output

root@tripoli:~# dmraid -r

/dev/sdc: sil, "sil_biaebhadcfcb", stripe, ok, 976771072 sectors, data@ 0
/dev/sdb: sil, "sil_biaebhadcfcb", stripe, ok, 976771072 sectors, data@ 0

root@tripoli:~# dmraid -ay

RAID set "sil_biaebhadcfcb" already active

fdisk Output

root@tripoli:~# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b9b01

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          32      248832   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              32       60802   488134657    5  Extended
/dev/sda5              32       60802   488134656   8e  Linux LVM

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6ead5c9a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       60801   488384001   fd  Linux raid autodetect

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe6e2af28

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       60801   488384001   fd  Linux raid autodetect

I'm trying to get dmraid to properly detect an existing RAID 10 array, which is working fine within windows 7. In summary, the drive setup and bios partitioning is as following:

• 2 x SSD (120 GB), RAID 0.

  Partitioned into: 180 GB (win7) and 58 GB (Ubuntu).

  Both detected and mounting fine in Ubuntu.

• 4 x HDD (2 TB), RAID 1+0. Single 4TB partition.

  Not working in ubuntu.

The Ubuntu installation itself is on a partitioned striped disk pair, and works fine. The two partitions (180 GB and 58 GB) correspond to the following LVM's (I've taken the liberty to format the data for readability):

#$ sudo dmsetup info /dev/dm-{1,2,3,4,5}
|----------+--------+---------------+-----------+----------+--------|
| dev/dm-0 | ubuntu | pdc_hjijcjji  | container |          | 58 GB  |
| dev/dm-1 | ubuntu | pdc_hjijcjji1 | /         | ext4     | 54 GB  |
| dev/dm-2 | ubuntu | pdc_hjijcjji2 |           | extended | 4.3 GB |
| dev/dm-3 | win 7  | pdc_fjhhdeeg  | container |          | 180 GB |
| dev/dm-4 | ubuntu | pdc_hjijcjji5 |           | swap     | 4.3 GB |
| dev/dm-5 | win 7  | pdc_fjhhdeeg1 |           | ntfs     | 180 GB |
|----------+--------+---------------+-----------+----------+--------|

The Raid 10 array (which is the one I need help to get it working within Ubuntu) consists of four 2TB disks, and give a resulting 4TB array. It seems as if dmraid is aware of this array, given the following output:

#$ sudo dmraid -r
|----------+--------+------------------+--------+---------+----------------+---------|
| Device   | Format | Name             | Type   | Status? | Size (sectors) | ?       |
|----------+--------+------------------+--------+---------+----------------+---------|
| /dev/sdf | pdc    | pdc_fjhhdeeg     | stripe | ok      |      175781248 | data@ 0 |
| /dev/sde | pdc    | pdc_fjhhdeeg     | stripe | ok      |      175781248 | data@ 0 |
| /dev/sdd | pdc    | pdc_bjibibahah-1 | stripe | ok      |     1758766336 | data@ 0 |
| /dev/sdc | pdc    | pdc_bjibibahah-1 | stripe | ok      |     1758766336 | data@ 0 |
| /dev/sda | pdc    | pdc_bjibibahah-0 | stripe | ok      |     1758766336 | data@ 0 |
| /dev/sdb | pdc    | pdc_bjibibahah-0 | stripe | ok      |     1758766336 | data@ 0 |
|----------+--------+------------------+--------+---------+----------------+---------|

Which throws me off a bit, since I'd expect the array, pdc_hjijcjji, to show up here as well. Perhaps, since it's a partition within a striped disk, it is included within pdc_fjhhdeeg. In any case, the striped array is running fine, so I'm not too worried about it.

pdc_hjijcjji shows up when running dmraid -s:

#$ sudo dmraid -s
|-----------+----------------+--------------+--------------|
| Name      | pdc_bjibibahah | pdc_fjhhdeeg | pdc_hjijcjji |
|-----------+----------------+--------------+--------------|
|           |       Superset |   Active Set |   Active Set |
| Size (-h) |       1.677 TB |     167.6 GB |      54.0 GB |
| Size      |     3517532672 |    351562496 |    113281024 |
| Stride    |            128 |          128 |          128 |
| Type      |         raid10 |       stripe |       stripe |
| Status    |             ok |           ok |           ok |
| Subsets   |              2 |            0 |            0 |
| Devs      |              4 |            2 |            2 |
| Spares    |              0 |            0 |            0 |
|-----------+----------------+--------------+--------------|
# Size is in blocks of 512 bytes.

Where pdc_bjibibahah seems to correspond to the Raid10 array, except that it has a weird size (1.677 TB, as apposed to approx 4 TB). Trying to activate this using dmraid -ay results in a mounted 1.677 TB device with is reported as unallocated data.

Running sudo dmraid -s -si on the bjibibahah array:

#$ sudo dmraid -s -si
|-----------+----------------+------------------+------------------|
| Name      | pdc_bjibibahah | pdc_bjibibahah-0 | pdc_bjibibahah-1 |
|-----------+----------------+------------------+------------------|
|           |       Superset |           Subset |           Subset |
| Size (-h) |       1.638 TB |         1.638 TB |         1.638 TB |
| Size      |     3517532672 |       3517532672 |       3517532672 |
| Stride    |            128 |              128 |              128 |
| Type      |         raid10 |           stripe |           stripe |
| Status    |             ok |               ok |               ok |
| Subsets   |              2 |                0 |                0 |
| Devs      |              4 |                2 |                2 |
| Spares    |              0 |                0 |                0 |
|-----------+----------------+------------------+------------------|

I've tried configuring the arrays manually, but with no success, and the man page isn't proving all too helpful either. If anyone has a suggestion as to how to configure dmraid, or to convince it to change the configuration of the RAID10 array, I would be really grateful.

Here are a few outputs, should it be relevant:

$ sudo dmraid -V
dmraid version:     1.0.0.rc16 (2009.09.16) shared
dmraid library version: 1.0.0.rc16 (2009.09.16)
device-mapper version:  4.20.0

$ sudo dmsetup --version
Library version:   1.02.48 (2010-05-20)
Driver version:    4.20.0

$ uname -srvm
Linux 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012 x86_64

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 11.10
Release:    11.10
Codename:   oneiric

Also, the BIOS raid setup of the RAID10 array match the following disks within ubuntu: Code:

|---------+------------+--------------|
| Port:ID | Assignment | OS Disk Name |
|---------+------------+--------------|
|   01:01 | LD 1-1     | /dev/sda     |
|   02:01 | LD 1-2     | /dev/sdb     |
|   03:01 | LD 1-3     | /dev/sdc     |
|   04:01 | LD 1-4     | /dev/sdd     |
|---------+------------+--------------|

Update: I forgot to mention that I'm on a Crosshair V motherboard, using the built in AMD SB950 controller.

Update 2: When running sudo dmraid -s -ccs pdc I get the following error messages:

ERROR: pdc: wrong # of devices in RAID set "pdc_fjhhdeeg" [1/2] on /dev/sdf
ERROR: pdc: wrong # of devices in RAID set "pdc_fjhhdeeg" [1/2] on /dev/sde
ERROR: pdc: wrong # of devices in RAID set "pdc_bjibibahah-1" [1/2] on /dev/sdd
ERROR: pdc: wrong # of devices in RAID set "pdc_bjibibahah-1" [1/2] on /dev/sdc
ERROR: pdc: wrong # of devices in RAID set "pdc_bjibibahah-0" [1/2] on /dev/sdb
ERROR: pdc: wrong # of devices in RAID set "pdc_bjibibahah-0" [1/2] on /dev/sda
*ERR*

If I omit the specifier pdc, and just write sudo dmraid -s -ccs I get the even more cryptic:

*ERR*
*ERR*
*ERR*

Update 3: I've managed to remove the badly configured array using sudo dmraid -rE as suggested in an askubuntu QA here. I'm still getting the "ERROR: pdc: wrong # of devices in RAID set ..." errors, which seem to be impeding further progress. I'll keep searching for solutions to this problem.

Edit: Is there any information I can add that would help anyone help me?

If I install Ubuntu on hard drive A and mount (via nautilus) hard drive B that has Windows 7 installed on it with a RAID1, could Ubuntu even remotely screw up the RAID Controller? Or would it look at it like a normal single hard drive not in RAID?

I believe the RAID 1 is FakeRAID since I don't have a hardware raid controller card.

I can't afford to risk losing the RAID1 setup so I'm just double checking. ^^

-Thanks