22_add_pdc_64bit_addressing.patch: breaks some pdc raid sets

[Andrew Hunter]

Binary package hint: dmraid

This is a critical regression for me as much of my data is currently unaccessable after the upgrade.

Running dmraid with verbose output results in the following:

# dmraid -ay -vvv -ddd
WARN: locking /var/lock/dmraid/.lock
NOTICE: skipping removable device /dev/sdd
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 60022479872
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 60021398016
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
DEBUG: checking pdc metadata at 60022448640
DEBUG: checking pdc metadata at 60022350336
DEBUG: checking pdc metadata at 60022349824
DEBUG: checking pdc metadata at 60022472704
DEBUG: checking pdc metadata at 60022276608
DEBUG: checking pdc metadata at 60022178304
DEBUG: checking pdc metadata at 60022135296
DEBUG: checking pdc metadata at 60022104576
DEBUG: checking pdc metadata at 60021982208
DEBUG: checking pdc metadata at 60021973504
DEBUG: checking pdc metadata at 60022014464
DEBUG: checking pdc metadata at 60021993984
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 1000204884992
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 1000203803136
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
DEBUG: checking pdc metadata at 1000204853760
DEBUG: checking pdc metadata at 1000204860928
NOTICE: /dev/sdb: pdc metadata discovered
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 1000204884992
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 1000203803136
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
DEBUG: checking pdc metadata at 1000204853760
DEBUG: checking pdc metadata at 1000204860928
NOTICE: /dev/sda: pdc metadata discovered
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching pdc_bhgbgdbai
DEBUG: _find_set: not found pdc_bhgbgdbai
DEBUG: _find_set: searching pdc_bhgbgdbai
DEBUG: _find_set: not found pdc_bhgbgdbai
NOTICE: added /dev/sdb to RAID set "pdc_bhgbgdbai"
DEBUG: _find_set: searching pdc_bhgbgdbai
DEBUG: _find_set: found pdc_bhgbgdbai
DEBUG: _find_set: searching pdc_bhgbgdbai
DEBUG: _find_set: found pdc_bhgbgdbai
NOTICE: added /dev/sda to RAID set "pdc_bhgbgdbai"
DEBUG: checking pdc device "/dev/sda"
DEBUG: checking pdc device "/dev/sdb"
DEBUG: set status of set "pdc_bhgbgdbai" to 16
DEBUG: checking pdc device "/dev/sda"
DEBUG: checking pdc device "/dev/sdb"
DEBUG: set status of set "pdc_bhgbgdbai" to 16
RAID set "pdc_bhgbgdbai" was not activated
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "pdc_bhgbgdbai"
DEBUG: freeing device "pdc_bhgbgdbai", path "/dev/sda"
DEBUG: freeing device "pdc_bhgbgdbai", path "/dev/sdb"

[Andrew Hunter (rexbron)]

I also noticed the following in dmesg:

device-mapper: table: 252:0: sda too small for target: start=0, len=4100877696, dev_size=1953525168

[Danny Wood (danwood76)]

This may be caused by the 64-bit patch for promise RAID.

Could you run the following commands:
sudo dmraid -D -r /dev/sda
sudo dmraid -D -r /dev/sdb

This will create a directory called dmraid.pdc, tar that directory and attach to this bug report.

[Danny Wood (danwood76)]

Also please post the output of
sudo dmraid -s

Also could you post the disk size information.

[Phillip Susi (psusi)]

Is this a 2 disk, or 3 disk array?

Can you post the output of sudo dmraid -n?

[Taras Zaviryukha (taraszav)]

I have the same problem. After upgrade array does not activated. Two disks - 2Tb raid1 in HP Proliant Microserver

# dmraid -ay -vvv -ddd
WARN: locking /var/lock/dmraid/.lock
WARN: missing dm serial file for /dev/dm-0
WARN: missing dm serial file for /dev/dm-1
NOTICE: /dev/dm-1: asr discovering
NOTICE: /dev/dm-1: ddf1 discovering
NOTICE: /dev/dm-1: hpt37x discovering
NOTICE: /dev/dm-1: hpt45x discovering
NOTICE: /dev/dm-1: isw discovering
DEBUG: not isw at 2675964928
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 2674883072
NOTICE: /dev/dm-1: jmicron discovering
NOTICE: /dev/dm-1: lsi discovering
NOTICE: /dev/dm-1: nvidia discovering
NOTICE: /dev/dm-1: pdc discovering
DEBUG: checking pdc metadata at 2675933696
DEBUG: checking pdc metadata at 2675835392
DEBUG: checking pdc metadata at 2675834880
DEBUG: checking pdc metadata at 2675957760
DEBUG: checking pdc metadata at 2675761664
DEBUG: checking pdc metadata at 2675663360
DEBUG: checking pdc metadata at 2675620352
DEBUG: checking pdc metadata at 2675589632
DEBUG: checking pdc metadata at 2675467264
DEBUG: checking pdc metadata at 2675458560
DEBUG: checking pdc metadata at 2675499520
DEBUG: checking pdc metadata at 2675479040
NOTICE: /dev/dm-1: sil discovering
NOTICE: /dev/dm-1: via discovering
NOTICE: /dev/dm-0: asr discovering
NOTICE: /dev/dm-0: ddf1 discovering
NOTICE: /dev/dm-0: hpt37x discovering
NOTICE: /dev/dm-0: hpt45x discovering
NOTICE: /dev/dm-0: isw discovering
DEBUG: not isw at 157106043904
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 157104962048
NOTICE: /dev/dm-0: jmicron discovering
NOTICE: /dev/dm-0: lsi discovering
NOTICE: /dev/dm-0: nvidia discovering
NOTICE: /dev/dm-0: pdc discovering
DEBUG: checking pdc metadata at 157106012672
DEBUG: checking pdc metadata at 157105914368
DEBUG: checking pdc metadata at 157105913856
DEBUG: checking pdc metadata at 157106036736
DEBUG: checking pdc metadata at 157105840640
DEBUG: checking pdc metadata at 157105742336
DEBUG: checking pdc metadata at 157105699328
DEBUG: checking pdc metadata at 157105668608
DEBUG: checking pdc metadata at 157105546240
DEBUG: checking pdc metadata at 157105537536
DEBUG: checking pdc metadata at 157105578496
DEBUG: checking pdc metadata at 157105558016
DEBUG: checking pdc metadata at 137438913024
NOTICE: /dev/dm-0: sil discovering
NOTICE: /dev/dm-0: 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 2000398932992
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 2000397851136
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
DEBUG: checking pdc metadata at 2000398901760
DEBUG: checking pdc metadata at 2000398908928
NOTICE: /dev/sdc: pdc metadata discovered
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
N...

[Andrew Hunter (rexbron)]

Here is the output of dmraid -D

Unfortunately, since I was able to successfully mount the array under an Ubuntu 10.10 livecd I've backed up my data and switched to soft raid.

It was a 2 drive raid0 array, each 1Tb for a total of 2Tb.

Hopefully one of the other people with the bug will be able to help.

For what it's worth, my chipset was an AMD 890fx.

Cheers,

Andrew

[Phillip Susi (psusi)]

I have prepared a new version of dmraid with the 22_add_pdc_64bit_addressing patch disabled as I think this is causing the several reported problems with Natty. Please test and let me know if this fixes it. It looks like it is going to be in the build queue for a few more hours, but once it finishes, do the following to test:

sudo apt-add-repository ppa:psusi/ppa
sudo apt-get update
sudo apt-get install dmraid=1.0.0.rc16-4.1ubuntu4~ppa0

[Andrew Hunter (rexbron)]

I realised I'd saved the output of some dmraid commands before I formatted.

$ sudo dmraid -s
*** Set
name : pdc_bhgbgdbai
size : 8201755392
stride : 128
type : stripe
status : ok
subsets: 0
devs : 2
spares : 0

$ sudo dmraid -r
/dev/sdb: pdc, "pdc_bhgbgdbai", stripe, ok, 4100877696 sectors, data@ 0
/dev/sda: pdc, "pdc_bhgbgdbai", stripe, ok, 4100877696 sectors, data@ 0

[Kyle (paultheastronomer)]

@psusi

I installed the new version of dmraid and it did not make any changes what so ever. Thank you for making the new version though.

[Kyle (paultheastronomer)]

I installed an update today which solved the problem.

[Phillip Susi (psusi)]

What update? You mean the version from my PPA? What version are you running according to apt-cache policy dmraid?

[Kyle (paultheastronomer)]

Hello Phillip.

I think it is the one you provided. I did the sudo commands you had given.
Then I restared the machine but that did not help. Then I did another update
where it this time around found the libdmraid. After installing this and the
restarting one more time it worked. The only minor problem now is that is
does not mount to the desktop.

Cheers,

Paul
On 30 April 2011 18:43, Phillip Susi <email address hidden> wrote:

> What update? You mean the version from my PPA? What version are you
> running according to apt-cache policy dmraid?
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (772483).
> https://bugs.launchpad.net/bugs/770600
>
> Title:
> 22_add_pdc_64bit_addressing.patch: breaks some pdc raid sets
>
> Status in “dmraid” package in Ubuntu:
> In Progress
>
> Bug description:
> Binary package hint: dmraid
>
> This is a critical regression for me as much of my data is currently
> unaccessable after the upgrade.
>
> Running dmraid with verbose output results in the following:
>
>
> # dmraid -ay -vvv -ddd
> WARN: locking /var/lock/dmraid/.lock
> NOTICE: skipping removable device /dev/sdd
> 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 60022479872
> DEBUG: isw trying hard coded -2115 offset.
> DEBUG: not isw at 60021398016
> NOTICE: /dev/sdc: jmicron discovering
> NOTICE: /dev/sdc: lsi discovering
> NOTICE: /dev/sdc: nvidia discovering
> NOTICE: /dev/sdc: pdc discovering
> DEBUG: checking pdc metadata at 60022448640
> DEBUG: checking pdc metadata at 60022350336
> DEBUG: checking pdc metadata at 60022349824
> DEBUG: checking pdc metadata at 60022472704
> DEBUG: checking pdc metadata at 60022276608
> DEBUG: checking pdc metadata at 60022178304
> DEBUG: checking pdc metadata at 60022135296
> DEBUG: checking pdc metadata at 60022104576
> DEBUG: checking pdc metadata at 60021982208
> DEBUG: checking pdc metadata at 60021973504
> DEBUG: checking pdc metadata at 60022014464
> DEBUG: checking pdc metadata at 60021993984
> 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 1000204884992
> DEBUG: isw trying hard coded -2115 offset.
> DEBUG: not isw at 1000203803136
> NOTICE: /dev/sdb: jmicron discovering
> NOTICE: /dev/sdb: lsi discovering
> NOTICE: /dev/sdb: nvidia discovering
> NOTICE: /dev/sdb: pdc discovering
> DEBUG: checking pdc metadata at 1000204853760
> DEBUG: checking pdc metadata at 1000204860928
> NOTICE: /dev/sdb: pdc metadata discovered
> 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: is...

[Kyle (paultheastronomer)]

I think it is the one you provided. I did the sudo commands you had given. Then I restared the machine but that did not help. Then I did another update where it this time around found the libdmraid. After installing this and the restarting one more time it worked. The only minor problem now is that is does not mount to the desktop.

[Andrew Hunter (rexbron)]

dmraid (1.0.0.rc16-4.1ubuntu3) natty; urgency=low

  * Fix typo in 23_pdc_dump_extended_metadata.patch.

 -- Colin Watson <email address hidden> Sat, 26 Mar 2011 00:32:44 +0000

[Phillip Susi (psusi)]

Andrew, can you try the version in my ppa please?

[Andrew Hunter (rexbron)]

Hey Phillip,

Unfortunately I can not. As I mentioned in a previous reply, I got fed
up and switched over to softraid.

On Sun, May 1, 2011 at 9:13 PM, Phillip Susi <email address hidden> wrote:
> Andrew, can you try the version in my ppa please?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/770600
>
> Title:
>  22_add_pdc_64bit_addressing.patch: breaks some pdc raid sets
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/770600/+subscribe
>

[paul candela (devguy)]

I'd like to chime in that your update worked great for me too Philip. I have dual raid arrays, one striped, the other mirrored, and the striped array showed up fine. My mirrored array was giving me trouble.

Like the astronomer, I had to install your dmraid, reboot, do a sudo apt-get update, and then get the remaining downloads from the update manager. Reboot one more time, and the fix worked!

Thanks!

[Phillip Susi (psusi)]

On 5/5/2011 12:55 AM, paul candela wrote:
> I'd like to chime in that your update worked great for me too Philip. I
> have dual raid arrays, one striped, the other mirrored, and the striped
> array showed up fine. My mirrored array was giving me trouble.

Are they both pdc arrays or do you have two different controllers? If
they are both pdc, could you please dump the metadata and attach it?

sudo dmraid -rD
tar czf dmraid.pdc.tgz dmraid.pdc

[paul candela (devguy)]

Sorry I didn't make that clear. I meant that from a stock Natty install, the RAID 0 array showed up fine, but the RAID 1 array did not. After using your ppa, now both function correctly. Both are pdc_xxxxxx arrays.

[dc46and2 (dc46and2)]

I just upgraded to Natty... and my root is on a pdc RAID. After rebooting, all I got was the initramfs BusyBox prompt with nary an error message or a single hint what was wrong. However, a quick glance in /dev/mapper revealed the problem. I managed to chroot in from an older version, add Phillip's PPA to my source list, and upgrade dmraid. Rebooted and everything works. THANK YOU--you just saved my ass. If I can assist with further information, testing, etc. please let me know.

[toggles (ubuntu-com-tommywatson)]

Thanks, this solution worked for a broken machine here.

[Mosin (mosin+)]

Thanks Phillip - updating the dmraid packages (both of them) with your PPA worked great. Any chance to get the official repos updated accordingly? It's a pretty nasty bug.

[Jonathan (eldaaran)]

My experience was much like dc46and2 above, only I wasn't able to solve it with the chroot trick. However, in the end, Phillip's ppa fix did work for me as well. So, I reinstalled 10.10. After it started, I used the GUI upgrade to 11.04 and when it asks to reboot at the end, I said No.

Using Terminal, I changed my /etc/apt/sources.list to include the dmraid ppa (remember to use sudo), including the following:

deb http://ppa.launchpad.net/psusi/ppa/ubuntu natty main
deb-src http://ppa.launchpad.net/psusi/ppa/ubuntu natty main

After that's added to the file, more or less as above:

sudo apt-get update
sudo apt-get remove dmraid
sudo apt-get install dmraid=1.0.0.rc16-4.1ubuntu4~ppa0

Then I rebooted and it was good.

[nutznboltz (nutznboltz-deactivatedaccount)]

@psusi Oh, you saved my desktop! How can I ever repay you?

Admittedly I copied your dmraid packing into a PPA by itself because I don't like PPAs with too many different packages.

https://launchpad.net/~nutznboltz/+archive/natty-dmraid

But as they say across the point "works a treat!"

[nutznboltz (nutznboltz-deactivatedaccount)]

I built 10.10 with LVM on DMRAID because GRUB2 lets you boot from that without any /boot filesystems.

I upgraded to 11.04 and *kaboom*

I installed the PPA with the newer version of DMRAID while in a chroot booted off a usb stick with Gentoo amd64 stage1 made with unetbootin. Had to remember how to

dmraid -ay
pvchange -xy /dev/mapper/pdc_xxxxxxxxxx1
vgchange -ay
mount /dev/vg0/lv0 /a
mount -t proc proc /a/proc
mount -o bind /dev /a/dev
mount -t devpts devpts /a/dev/pts
mount -o bind /sys /a/sys
chroot /a

[Phillip Susi (psusi)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/28/2011 09:30 AM, nutznboltz wrote:
> I built 10.10 with LVM on DMRAID because GRUB2 lets you boot from that
> without any /boot filesystems.

FYI, grub2 can do the same with mdadm raid.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3i73gACgkQJ4UciIs+XuL90wCguAd8RGSMe1jZ0I7+JOSfMuc3
hB8Anic0o/xEcHWn4wW45YG8UWrQ8NYv
=pL8w
-----END PGP SIGNATURE-----

[Launchpad Janitor (janitor)]

This bug was fixed in the package dmraid - 1.0.0.rc16-4.1ubuntu4

---------------
dmraid (1.0.0.rc16-4.1ubuntu4) oneiric; urgency=low

  * Drop 22_add_pdc_64bit_addressing.patch: breaks some
    pdc raid sets (LP: #770600)
 -- Phillip Susi <email address hidden> Thu, 28 Apr 2011 20:28:07 -0400