pdc fakeraid not recognized

After discussion in the question, it appears that blkid is not recognizing the disks as members of the pdc raid array.

Attached the output of dmraid -rD as requested by Phillip

I have uploaded a patched version of util-linux to my ppa, could you test it and see if it fixes this for you?

Could you please elaborate a little bit on how to apply the patched
version? I'll be hapy to test if I only knew how...
Op 14 nov. 2012 17:05 schreef "Phillip Susi" <email address hidden> het
volgende:

> I have uploaded a patched version of util-linux to my ppa, could you
> test it and see if it fixes this for you?
>
>
> ** Changed in: util-linux (Ubuntu)
> Status: New => In Progress
>
> ** Changed in: util-linux (Ubuntu)
> Assignee: (unassigned) => Phillip Susi (psusi)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1078407
>
> Title:
> pdc fakeraid not recognized
>
> Status in “util-linux” package in Ubuntu:
> In Progress
>
> Bug description:
> I have a fresh install of Ubuntu Desktop on my old Dell Dimension
> 8300. This box has a Promise Fasttrak raid controller a.k.a. softraid
> or fakeraid. It is setup with two identical drives in raid0, stiped.
>
> I had a hard time getting the installer to run without errors. Did all
> kind of manual steps to make the installer complete.
> I installed from a pendrive, booted the liveCD. Used dmraid -ay and
> gparted to partition the drive. Did nothing special with the partitions one
> swap and one root partition. The installer ends up grubbing my pendrive
> instead of my harddisk so I followed a manual to purge an reinstall grub2
> on the correct disk here (http://ubuntuforums.org/showthread.php?t=1581099
> )
>
> Now when I boot, the computer shows a graphical off-black screen
> (ubuntu boot color???) and nothing happens. When I then reboot with
> Ctrl+Alt+Delete a second time. I get GNU GRUB menu and I choose
> "Ubuntu, with Linux 3.2.0-29-generic-pae". After a while I got thrown
> in busybox because of the root device was not found: ALERT! /dev/disk
> /by-uuid/8693f1c2-3eb1-41a4-ba10-3fbe860144a1 does not exist.
>
> When I type "dmraid -ay" [Enter]
> I see three messages like RAID set "pdc_ccgcdegci" was activated.
> Press Crtl+D the computer will continue to boot normally.
>
> The next time I boot I need to reboot to get pass the off-black screen
> and into the GNU Grub menu again.
>
> I found bug report 941874, but I checked and the fixes described there
> seem to be in place on my machine...
> I tried the steps described in "
> http://www.humans-enabled.com/2012/03/how-to-fix-ubuntu-1204beta-boot-problem.html"
> to no avail.
>
> I'm new to the whole Ubuntu/linux thing and I just want my computer to
> boot without manual intervention. Please help.
>
> Thanx!
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1078407/+subscriptions
>

Sure, add my ppa to your sources:

sudo apt-add-repository ppa:psusi/ppa

Then updating your system should pull in the new packages:

sudo apt-get update
sudo apt-get upgrade

You also may need to update your initramfs for it to take effect:

sudo update-initramfs -u

It seems that I'm unable to get your patch by using the commands that you gave me. I have ran the commands in a terminal window after I booted my machine with the work around.

I was able to add the repository but apt-get update did not list your repository (anything with psusi)) among all the others.
apt-get upgrade did do a lot of stuff because this was a first time. But i'm not sure your fix was among the many things that got installed. I didn't see your repository uri (http://ppa.launchpad.net/psusi/ppa/ubuntu) anywhere in the output.

It is blkid that you've patched, correct?
blkid still does not output anything when I run it.
blkid -v shows me "blkid from util-linux 2.20.1 (libblkid 2.20.0, 19-Oct-2011)"

The computer still does not start without me running dmraid -ay manually

I'm sorry. What is it that I do wrong? How do I get your patch installed?

You are running quantal right? You might try repeating the process and check apt-cache policy util-linux

No I'm running precise.

Ahh, that would be why. I will upload a version for precise, then try again in an hour or two.

I got an upgrade for util-linux and a few other things this time...
unfortunately nothing changed in regard to my system not booting...

blkid is still not giving me any output. Did you change the version because it reports the same version as before.

however "sudo blkid" does give me results. After sudo blkid, just blkid without sudo it also working...

Could you be more specific? What exactly does sudo blkid show now?

sudo blkid
[sudo] password for guidol:
/dev/mapper/pdc_ccgcdegci1: UUID="8693f1c2-3eb1-41a4-ba10-3fbe860144a1" TYPE="ext4"
/dev/mapper/pdc_ccgcdegci5: UUID="b2a3a93d-451f-4066-8f48-de5cb30bf048" TYPE="swap"

But we don't know whether this worked before or not because I never tried blkid with sudo before...

You did it from the initramfs before where sudo is not needed. Can you run apt-cache policy util-linux and sudo blkid -p /dev/sda?

here you go...

apt-cache policy util-linux
util-linux:
  Installed: 2.20.1-5.1ubuntu3~ppa0precise
  Candidate: 2.20.1-5.1ubuntu3~ppa0precise
  Version table:
 *** 2.20.1-5.1ubuntu3~ppa0precise 0
        500 http://ppa.launchpad.net/psusi/ppa/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status
     2.20.1-1ubuntu3 0
        500 http://nl3.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

sudo blkid -p /dev/sda
/dev/sda: PTTYPE="dos"

Could you provide the output of sudo fdisk -lu?

sudo fdisk -lu
fdisk: unable to seek on /dev/sda: Invalid argument

sudo fdisk -lu /dev/sda1

Disk /dev/sda1: 120.0 GB, 119999868928 bytes
255 heads, 63 sectors/track, 14589 cylinders, total 234374744 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

sudo fdisk -lu /dev/sdb
Warning: invalid flag 0x0000 of partition table 5 will be corrected by w(rite)

Disk /dev/sdb: 120.0 GB, 120000000000 bytes
255 heads, 63 sectors/track, 14589 cylinders, total 234375000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000223

   Device Boot Start End Blocks Id System
/dev/sdb1 2048 234373119 117185536 5 Extended

Which disks are part of the raid? Can you run fdisk -lu on those? Also could you run sudo dd bs=512 skip=234374049 count=1 if=/dev/sda | hd

Use the correct drive if sda isn't one of the raid disks.

My system has two 120GB disks. Both are used in a RAID0 configuration with the fakeraid controller.
ls /dev/sd* gives me sda, sda1, sdb and sdb1.

sudo fdisk -lu /dev/sda does not give any results, no output at all
sudo fdisk -lu /dev/sda1 you can see in comment 18
sudo fdisk -lu /dev/sdb you can see in comment 19
sudo fdisk -lu /dev/sdb1 does not give any results, no output at all

i've attached the output of sudo dd bs=512 skip=234374049 count=1 if=/dev/sda | hd in a file called dd_dev_sda

I want to thank you for your patience and not giving up on me already. Thanks!

You run fdisk on the whole disk, not an individual partition. The error you mentioned before makes no sense. Could you try running sudo fdisk -lu /dev/sda again, and check dmesg for more detailed errors if it still fails.

sudo fdisk -lu /dev/sda realy does not give any output.
sudo fdisk -lu gives the following output: "fdisk: unable to seek on /dev/sda: Invalid argument"

I've attached the results of dmesg > boot.messages. Near the end of this file you can find stuff about sda, sdb. Here are some lines that looked interesting to me... Although I don't have a clue of what to do with this information.

[ 6.150644] sda: sda1 sda2 < >
[ 6.150650] sda: partition table partially beyond EOD, enabling native capacity
[ 6.151314] sda: sda1 sda2 < >
[ 6.151318] sda: partition table partially beyond EOD, truncated
[ 6.151325] sda: p1 size 462747904 extends beyond EOD, truncated
[ 6.151427] sda: p2 start 462748414 is beyond EOD, truncated
[ 6.151865] sd 4:0:0:0: [sda] Attached SCSI disk
[ 6.672041] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 6.680571] ata6.00: ATA-6: ST3120026AS, 8.05, max UDMA/133
[ 6.680575] ata6.00: 234375000 sectors, multi 0: LBA48
[ 6.696575] ata6.00: configured for UDMA/133
[ 6.696724] scsi 5:0:0:0: Direct-Access ATA ST3120026AS 8.05 PQ: 0 ANSI: 5
[ 6.697044] sd 5:0:0:0: [sdb] 234375000 512-byte logical blocks: (120 GB/111 GiB)
[ 6.697139] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 6.697207] sd 5:0:0:0: [sdb] Write Protect is off
[ 6.697214] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 6.697288] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.716451] sdb: sdb1 < >
[ 6.716929] sd 5:0:0:0: [sdb] Attached SCSI disk
[ 41.421548] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)

Is there anything else I can run for you?

I can try to re-install and write down the steps I take to partition my disks in case the problem still exists after re-installing. But then we might lose this particular setup and we can't debug it any further...

Yes, can you run cat /sys/block/sda/size?

Also dd if=/dev/sda count=1 | xxd

cat /sys/block/sda/size
234375000

sudo dd if=/dev/sda count=1 | xxd
[sudo] password for guidol:
0000000: eb63 9010 8ed0 bc00 b0b8 0000 8ed8 8ec0 .c..............
0000010: fbbe 007c bf00 06b9 0002 f3a4 ea21 0600 ...|.........!..
0000020: 00be be07 3804 750b 83c6 1081 fefe 0775 ....8.u........u
0000030: f3eb 16b4 02b0 01bb 007c b280 8a74 018b .........|...t..
0000040: 4c02 cd13 ea00 7c00 00eb fe00 0000 0000 L.....|.........
0000050: 0000 0000 0000 0000 0000 0080 0100 0000 ................
0000060: 0000 0000 fffa 9090 f6c2 8074 05f6 c270 ...........t...p
0000070: 7402 b280 ea79 7c00 0031 c08e d88e d0bc t....y|..1......
0000080: 0020 fba0 647c 3cff 7402 88c2 52bb 1704 . ..d|<.t...R...
0000090: 8027 0374 06be 887d e817 01be 057c b441 .'.t...}.....|.A
00000a0: bbaa 55cd 135a 5272 3d81 fb55 aa75 3783 ..U..ZRr=..U.u7.
00000b0: e101 7432 31c0 8944 0440 8844 ff89 4402 ..t21..D.@.D..D.
00000c0: c704 1000 668b 1e5c 7c66 895c 0866 8b1e ....f..\|f.\.f..
00000d0: 607c 6689 5c0c c744 0600 70b4 42cd 1372 `|f.\..D..p.B..r
00000e0: 05bb 0070 eb76 b408 cd13 730d f6c2 800f ...p.v....s.....
00000f0: 84d0 00be 937d e982 0066 0fb6 c688 64ff .....}...f....d.
0000100: 4066 8944 040f b6d1 c1e2 0288 e888 f440 @f.D...........@
0000110: 8944 080f b6c2 c0e8 0266 8904 66a1 607c .D.......f..f.`|
0000120: 6609 c075 4e66 a15c 7c66 31d2 66f7 3488 f..uNf.\|f1.f.4.
0000130: d131 d266 f774 043b 4408 7d37 fec1 88c5 .1.f.t.;D.}7....
0000140: 30c0 c1e8 0208 c188 d05a 88c6 bb00 708e 0........Z....p.
0000150: c331 dbb8 0102 cd13 721e 8cc3 601e b900 .1......r...`...
0000160: 018e db31 f6bf 0080 8ec6 fcf3 a51f 61ff ...1..........a.
0000170: 265a 7cbe 8e7d eb03 be9d 7de8 3400 bea2 &Z|..}....}.4...
0000180: 7de8 2e00 cd18 ebfe 4752 5542 2000 4765 }.......GRUB .Ge
0000190: 6f6d 0048 6172 6420 4469 736b 0052 6561 om.Hard Disk.Rea
00001a0: 6400 2045 7272 6f72 0d0a 00bb 0100 b40e d. Error........
00001b0: cd10 ac3c 0075 f4c3 f0a9 0200 0000 0004 ...<.u..........
00001c0: 0500 83fe ffff 0001 0000 00f9 941b 00fe ................
00001d0: ffff 05fe ffff fefa 941b 02f8 1f00 0000 ................
00001e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00001f0: 0000 0000 0000 0000 0000 0000 0000 55aa ..............U.
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.00180132 s, 284 kB/s

Ok, it looks like fdisk has a bug which was preventing it from working correctly for you. I will file a separate bug report for that.

Can you please run this command now:

sudo dd if=/dev/sda count=1 skip=234374049 | xxd

Ok, here you go...

sudo dd if=/dev/sda count=1 skip=234374049 | xxd
[sudo] password for guidol:
1+0 records in
1+0 records out
512 bytes (512 B) copied0000000: 5072 6f6d 6973 6520 5465 6368 6e6f 6c6f Promise Technolo
, 0.0164472 s, 31.1 kB/s
0000010: 6779 2c20 496e 632e 0000 0200 0411 2d00 gy, Inc.......-.
0000020: 0000 0000 0411 7c0d 0000 d6d5 d4d3 d2d1 ......|.........
0000030: d0cf cecd cccb cac9 c8c7 c6c5 c4c3 c2c1 ................
0000040: c0bf bebd bcbb bab9 b8b7 b6b5 b4b3 b2b1 ................
0000050: b0af aead acab aaa9 a8a7 a6a5 a4a3 a2a1 ................
0000060: a09f 9e9d 9c9b 9a99 9897 9695 9493 9291 ................
0000070: 908f 8e8d 8c8b 8a89 8887 8685 8483 8281 ................
0000080: 807f 7e7d 7c7b 7a79 7877 7675 7473 7271 ..~}|{zyxwvutsrq
0000090: 706f 6e6d 6c6b 6a69 6867 6665 6463 6261 ponmlkjihgfedcba
00000a0: 605f 5e5d 5c5b 5a59 5857 5655 5453 5251 `_^]\[ZYXWVUTSRQ
00000b0: 504f 4e4d 4c4b 4a49 4847 4645 4443 4241 PONMLKJIHGFEDCBA
00000c0: 403f 3e3d 3c3b 3a39 3837 3635 3433 3231 @?>=<;:987654321
00000d0: 302f 2e2d 2c2b 2a29 2827 2625 2423 2221 0/.-,+*)('&%$#"!
00000e0: 201f 1e1d 1c1b 1a19 1817 1615 1413 1211 ...............
00000f0: 100f 0e0d 0c0b 0a09 0807 0605 0403 0201 ................
0000100: 00ff fefd fcfb faf9 f8f7 f6f5 f4f3 f2f1 ................
0000110: f0ef eeed eceb eae9 e8e7 e6e5 e4e3 e2e1 ................
0000120: e0df dedd dcdb dad9 d8d7 d6d5 d4d3 d2d1 ................
0000130: d0cf cecd cccb cac9 c8c7 c6c5 c4c3 c2c1 ................
0000140: c0bf bebd bcbb bab9 b8b7 b6b5 b4b3 b2b1 ................
0000150: b0af aead acab aaa9 a8a7 a6a5 a4a3 a2a1 ................
0000160: a09f 9e9d 9c9b 9a99 9897 9695 9493 9291 ................
0000170: 908f 8e8d 8c8b 8a89 8887 8685 8483 8281 ................
0000180: 807f 7e7d 7c7b 7a79 7877 7675 7473 7271 ..~}|{zyxwvutsrq
0000190: 706f 6e6d 6c6b 6a69 6867 6665 6463 6261 ponmlkjihgfedcba
00001a0: 605f 5e5d 5c5b 5a59 5857 5655 5453 5251 `_^]\[ZYXWVUTSRQ
00001b0: 504f 4e4d 4c4b 4a49 4847 4645 4443 4241 PONMLKJIHGFEDCBA
00001c0: 403f 3e3d 3c3b 3a39 3837 3635 3433 3231 @?>=<;:987654321
00001d0: 302f 2e2d 2c2b 2a29 2827 2625 2423 2221 0/.-,+*)('&%$#"!
00001e0: 201f 1e1d 1c1b 1a19 1817 1615 1413 1211 ...............
00001f0: 100f 0e0d 0c0b 0a09 0807 0605 0403 0201 ................

Sorry, my tools were playing tricks on me saying patches were applied when they were not. After taking them out to the woodshed and beating them with a two by four, I have uploaded a new version. Please upgrade and test, this time should do it.

Note that it may take a while for the package to build, when it does you should update && upgrade and should get ~ppa1 version.

Get:2 http://ppa.launchpad.net/psusi/ppa/ubuntu/ precise/main util-linux i386 2.20.1-5.1ubuntu3~ppa1 [658 kB]

Preparing to replace util-linux 2.20.1-5.1ubuntu3~ppa0precise (using .../util-linux_2.20.1-5.1ubuntu3~ppa1_i386.deb) ...
Unpacking replacement util-linux ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up util-linux (2.20.1-5.1ubuntu3~ppa1) ...

Rebooting...

Congrats! You've done it! The computer now boots all by itself. This fix is CONFIRMED.

What happens next? How long until this fix makes it into the official Precise distribution? I would like to re-install once more without any issues.