On Monday 22 June 2009 05:30:20 pm Heinz Mauelshagen wrote:

David,

you can run "dmraid -an" after closing (e.g. unmounting) nvidia_ecaejfdip9, which ain't work now any more, because you already deleted the partition. It'll of course not reappear on reboot.

"dmsetup remove nvidia_ecaejfdip9" will do the trick without a reboot.

Regards, Heinz

Heinz, I may have run into a bug with dmraid-1.0.0rc15, you may want to look at. Tobias (on the Arch list), you may want to look into this as well. I have included the new information at the end of tis message to try and keep the information in context:

On Mon, 2009-06-22 at 14:48 -0500, David C. Rankin wrote:

...

Heinz,

I thought I would forward this one to you just in case there is a bug on the delete. It is probably just my limited understanding of dmraid, but I thought after I deleted the partition in cfdisk and then deactivated the device (nvidia_ecaejfdi) node nvidia_ecaejfdip9 should disappear? It is still there. How do I get rid of it? This is on Archlinux. Here is a bit more info about my setup:

[14:17 archangel:/home/david/archlinux/dmraid] # l /dev/mapper total 0 drwxr-xr-x 2 root root 0 2009-06-22 13:44 . drwxr-xr-x 23 root root 0 2009-06-22 13:44 .. crw-rw---- 1 root root 10, 60 2009-06-22 01:40 control brw------- 1 root disk 254, 0 2009-06-22 13:48 nvidia_ecaejfdi brw------- 1 root disk 254, 2 2009-06-22 01:40 nvidia_ecaejfdip5 brw------- 1 root disk 254, 3 2009-06-22 01:40 nvidia_ecaejfdip6 brw------- 1 root disk 254, 4 2009-06-22 01:40 nvidia_ecaejfdip7 brw------- 1 root disk 254, 5 2009-06-22 01:40 nvidia_ecaejfdip8 brw------- 1 root disk 254, 10 2009-06-22 13:44 nvidia_ecaejfdip9 (I have deleted this in cfdisk) ^^^^^^^^^^^^^^^^^^ brw------- 1 root disk 254, 1 2009-06-22 01:40 nvidia_fdaacfde brw------- 1 root disk 254, 6 2009-06-22 01:40 nvidia_fdaacfdep5 brw------- 1 root disk 254, 7 2009-06-22 01:40 nvidia_fdaacfdep6 brw------- 1 root disk 254, 8 2009-06-22 01:40 nvidia_fdaacfdep7 brw------- 1 root disk 254, 9 2009-06-22 01:40 nvidia_fdaacfdep8

[14:13 archangel:/home/david/archlinux/dmraid] # dmraid -rd -v -v 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 NOTICE: /dev/sdd: jmicron discovering NOTICE: /dev/sdd: lsi discovering NOTICE: /dev/sdd: nvidia discovering NOTICE: /dev/sdd: nvidia metadata discovered 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 NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: nvidia metadata discovered 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 NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: nvidia metadata discovered 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 NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: nvidia metadata discovered NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering INFO: RAID devices discovered:

/dev/sdd: nvidia, "nvidia_ecaejfdi", mirror, ok, 1465149166 sectors, data@ 0 /dev/sdc: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0 /dev/sdb: nvidia, "nvidia_ecaejfdi", mirror, ok, 1465149166 sectors, data@ 0 /dev/sda: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0 [14:13 archangel:/home/david/archlinux/dmraid] # mc

All was fine yesterday. Everything seemed to work well. Today, I am dead in the water and for some reason, all my partitions are gone from my Archlinux install with the new dmraid. Here is the problem: Today, I rebooted the Archlinux (hostname Archangel) install that is using dmraid-1.0.0rc15 the boot failed. Archlinux is running on nvidia_ecaejfdi (sdb/sdd - 2 500 Gig. Seagate Drives: ST3500630AS). However, when I booted to openSuSE 11.0 (hostname Ecstasy) running dmraid-1.0.0.rc14-63.1 sdb/sdd - 2 750 Gig. Seagate Drives: ST3750330AS), I lost all the nvidia_ecaejfdi devices and could not mount any of my archlinux partitions while running openSuSE. Here are the errors and information: 12:52 ecstasy:~> mount_arch Mounting 750G dmraid partitions under /mnt/arch mounting /dev/mapper/nvidia_ecaejfdi_part5 --> /mnt/arch/ mount: special device /dev/mapper/nvidia_ecaejfdi_part5 does not exist /mnt/arch/root/ -- Failed, Cancelling mount & exiting... (OK, I thought I just needed to adjust the mapper label to "ecaejfdip5" here. That wasn't the case) 12:52 ecstasy:~> l /dev/mapper total 0 drwxr-xr-x 2 root root 200 2009-06-23 12:48 ./ drwxr-xr-x 12 root root 4960 2009-06-23 12:49 ../ lrwxrwxrwx 1 root root 16 2009-06-23 12:48 control -> ../device-mapper brw------- 1 root root 253, 0 2009-06-23 12:48 nvidia_ecaejfdi brw------- 1 root root 253, 1 2009-06-23 12:48 nvidia_fdaacfde brw------- 1 root root 253, 2 2009-06-23 12:48 nvidia_fdaacfde_part1 brw------- 1 root root 253, 3 2009-06-23 12:48 nvidia_fdaacfde_part5 brw------- 1 root root 253, 4 2009-06-23 12:48 nvidia_fdaacfde_part6 brw------- 1 root root 253, 5 2009-06-23 12:48 nvidia_fdaacfde_part7 brw------- 1 root root 253, 6 2009-06-23 12:48 nvidia_fdaacfde_part8 12:53 ecstasy:~> su - Password: [12:53 ecstasy:~] # dmraid -ay RAID set "nvidia_ecaejfdi" already active RAID set "nvidia_fdaacfde" already active [12:53 ecstasy:~] # l /dev/mapper total 0 drwxr-xr-x 2 root root 280 Jun 23 12:53 ./ drwxr-xr-x 12 root root 5040 Jun 23 12:54 ../ lrwxrwxrwx 1 root root 16 Jun 23 12:48 control -> ../device-mapper brw------- 1 root root 253, 0 Jun 23 12:48 nvidia_ecaejfdi brw------- 1 root root 253, 1 Jun 23 12:48 nvidia_fdaacfde brw------- 1 root root 253, 7 Jun 23 12:53 nvidia_fdaacfde5 brw------- 1 root root 253, 8 Jun 23 12:53 nvidia_fdaacfde6 brw------- 1 root root 253, 9 Jun 23 12:53 nvidia_fdaacfde7 brw------- 1 root root 253, 10 Jun 23 12:53 nvidia_fdaacfde8 brw------- 1 root root 253, 2 Jun 23 12:48 nvidia_fdaacfde_part1 brw------- 1 root root 253, 3 Jun 23 12:48 nvidia_fdaacfde_part5 brw------- 1 root root 253, 4 Jun 23 12:48 nvidia_fdaacfde_part6 brw------- 1 root root 253, 5 Jun 23 12:48 nvidia_fdaacfde_part7 brw------- 1 root root 253, 6 Jun 23 12:48 nvidia_fdaacfde_part8 You can see above that when booting opensuse with (dmraid-1.0.0.rc14-63.1), All nvidia_fdaacfde partitions have been "Duplicated". Once with a simple number '5-8' and again with the old style '_part5-_part8', -- and -- no partitions were created for "nvidia_ecaejfdi." Now this should not be happening. It is also confirmed with: 16:04 ecstasy:~> cat /proc/partitions major minor #blocks name 8 0 488386584 sda 8 1 1 sda1 8 5 72229 sda5 8 6 2104483 sda6 8 7 20972826 sda7 8 8 465234336 sda8 8 16 732574584 sdb 8 32 488386584 sdc 8 33 1 sdc1 8 37 72229 sdc5 8 38 2104483 sdc6 8 39 20972826 sdc7 8 40 465234336 sdc8 8 48 732574584 sdd 253 0 732574583 dm-0 253 1 488386583 dm-1 253 2 488384001 dm-2 253 3 72229 dm-3 253 4 2104483 dm-4 253 5 20972826 dm-5 253 6 465234336 dm-6 Now this is very scary looking. The sdb[5-8] and sdd[5-8] partitions are GONE?? (Bummer..) Obviously, I can no longer boot archlinux?? As I mentioned earlier, the Archlinux install on this box is just for testing and if there is no way to recover it, I'll just reinstall, but I would like to try and get it back. I have saved all the 'fdisk -l' information for the partitions and I might have the dmraid -D information around somewhere. One more potential culprit is the kernel update that was applied before I rebooted the machine: -rw-r--r-- 1 root root 35338866 2009-06-23 14:23 /var/cache/pacman/pkg/kernel26-2.6.30-5-x86_64.pkg.tar.gz I strongly suspect that is a player in this problem. So I need help from anyone on the Arch list or you Heinz or Tobias that might be able to suggest a way to recover from this problem. Any thoughts? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com