I am confused as to what this issue has to do with casper. The problem
is that udev should not even be running vol_id on the partitions on a
raid disk since those partitions are not even really valid ideally
the kernel should not even be detecting those partitions.
--
livecd auto mounting
I see what you mean, there shouldn't even exist /dev/sda1 etc, only
/dev/sda if /dev/sda is a raid device. Yes, that would be a proper
solution.
** Changed in: udev (Ubuntu)
Sourcepackagename: dmraid = udev
Status: Invalid = New
--
livecd auto mounting swap partitions detected on dmraid
It seems to me that if vol_id reports the usage of the entire disk
device as being raid, then that should carry over to all partitions on
it, and a usage type of raid should preclude its use by anything other
than raid.
--
livecd auto mounting swap partitions detected on dmraid volume members
Yes, that would make sense for udev or anything else that enumerates
through devices and partitions. But I think vol_id is just a simple one-
block-device sniffer: it looks at a given block device like /dev/sda1
without looking at what would be the parent device. Those utilities
using vol_id need
** Changed in: casper (Ubuntu)
Status: Confirmed = Fix Committed
--
livecd auto mounting swap partitions detected on dmraid volume members
https://bugs.launchpad.net/bugs/136804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package casper - 1.133
---
casper (1.133) intrepid; urgency=low
[ Tormod Volden ]
* Do not use swap on RAID raw devices (LP: #136804)
[ Agostino Russo ]
* Test if livemedia is a directory before trying to mount it as a
loopfile
* Reverted
May I draw your attention to https://wiki.ubuntu.com/DmraidSupport. The
issues with vol_id etc are documented in this spec.
--
livecd auto mounting swap partitions detected on dmraid volume members
https://bugs.launchpad.net/bugs/136804
You received this bug notification because you are a member
D'oh, that should have been ID_FS_USAGE and not ID_FS_TYPE. Anyway, I
have tested that it works here, and I will try to get it pushed to
casper. To test this out you can 1) modify the initrd.gz file on the
live CD or 2) boot with break=casper-bottom and hand-edit the script
file with ed or 3) boot
** Attachment added: new scripts/casper-bottom/13swap
http://launchpadlibrarian.net/15378498/13swap
** Changed in: dmraid (Ubuntu)
Assignee: Vojta Grec (vojtagrec) = (unassigned)
Status: Confirmed = Invalid
** Description changed:
Binary package hint: dmraid
Hello,
Did anyone experience data loss or desync of the RAID because of this
bug? We should try to get this fixed in 8.04.1 or at least 8.04.2 since
it must be fixed on the CD itself.
** Changed in: casper (Ubuntu)
Assignee: Tormod Volden (tormodvolden) = (unassigned)
Status: In Progress =
Hello!
Yes, I also get very similar output as Tiger!P in all the three stages,
when invoking sudo vol_id /dev/sda:
ID_FS_USAGE=raid
ID_FS_TYPE=promise_fasttrack_raid_member
ID_FS_VERSION=
ID_FS_UUID=
ID_FS_UUID_ENC=
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=
--
livecd auto mounting swap
We could add this to the mentioned 13swap script:
vol_id ${device%%[0-9]*} | grep -q ^ID_FS_TYPE=raid continue
(unless the script gets fixed up to be less brute force)
--
livecd auto mounting swap partitions detected on dmraid volume members
https://bugs.launchpad.net/bugs/136804
You received
The output I get is the same for every instance I run (just after
booting the live CD, after swapoff -a and after install of dmraid).
[EMAIL PROTECTED]:~$ sudo vol_id /dev/sda
ID_FS_USAGE=raid
ID_FS_TYPE=via_raid_member
ID_FS_VERSION=1
ID_FS_UUID=
ID_FS_UUID_ENC=
ID_FS_LABEL=
ID_FS_LABEL_ENC=
Hello Phillip!
Here is also the printout of my sudo blkid:
1) The first output (after booting the live CD):
/dev/sda1: UUID=9470295F702948F6 TYPE=ntfs
/dev/sda2: UUID=36D4ED0DD4ECCFE3 LABEL=Local Disk TYPE=ntfs
/dev/sda5: UUID=e5bae0bd-02ff-4932-8dca-3f3e2a8d2bf4 SEC_TYPE=ext2
TYPE=ext3
Hello Phillip!
One more thing: the sudo blkid /dev/sda doesn't output anything,
even if I execute it once the RAID is working.
--
livecd auto mounting swap partitions detected on dmraid volume members
https://bugs.launchpad.net/bugs/136804
You received this bug notification because you are a
It seems from /scripts/casper-bottom/13swap on the live CD initrd that
it does not use blkid nor vol_id, but just looks for SWAPSPACE etc
4086 bytes into the partition.
--
livecd auto mounting swap partitions detected on dmraid volume members
https://bugs.launchpad.net/bugs/136804
You received
Hrm... it should definitely be respecting the volume identifiers udev
gets from blkid rather than probing every block device it can find for
that signature. At any rate, blkid should not be identifying partitions
on a block device that is identified as a raid member. Or maybe dmraid
should be
How can the initrd identify it as a raid member, when it doesn't have
dmraid? Has blkid become fakeraid-aware? Also, last time I checked, udev
used vol_id and not blkid, and they do not share the partition probing
code for some reason.
--
livecd auto mounting swap partitions detected on dmraid
I think Tormod hit the nail on the head on that (but I don't know blkid
internals too). The system solution would be to include dmraid on the
live CD. It's very small package so it should fit there. If that's not
possible, I propose following ugly hack: modify the dmraid initscript
(or maybe .deb
Oops, I mixed up blkid and vol_id. Please try running vol_id /dev/sda
and see if it identifies it as a raid member. Last I checked, vol_id
has bits of the signature detection code hacked out of dmraid built into
it so it recognizes the disk device as a whole as being a raid member
and exports
Yea, I think the bug is in blkid... if you run blkid /dev/sda it should
identify it as being a disk that is part of a raid set... the problem is
that it still identifies the partitions detected on it as being valid
partitions, when they are actually not.
--
livecd auto mounting swap partitions
I have run blkid 3 times, first after booting the live CD, second after
`swapoff -a` en third after `apt-get install dmraid`
The first output (after booting the live CD):
/dev/sda1: UUID=D4DC7D78DC7D55A8 LABEL=XP_c_ntfs TYPE=ntfs
/dev/sda5: UUID=3A30D91E30D8E1C5 LABEL=XP_d_ntfs TYPE=ntfs
It might be that my /dev/mapper/via_bfdbdagceh8 didn't have reiserfs
after all.
--
livecd auto mounting swap partitions detected on dmraid volume members
https://bugs.launchpad.net/bugs/136804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If swapoff fixes the issue for you, please post the output of blkid. My
guess is that blkid is not correctly identifying the disks as raid
members, which would prevent them being auto mounted.
** Summary changed:
- dmraid not correctly detecting nforce raid
+ livecd auto mounting swap
Right, I've just tripped over this issue after re-installing my windows
partition. Swapoff -a solved it, Here's the output of blkid:
[EMAIL PROTECTED]:~$ sudo blkid
/dev/sda1: UUID=040C25400C252E5C TYPE=ntfs
/dev/sda2: UUID=1a74b366-7af2-4d05-a8cd-ccef1ee0dc9b SEC_TYPE=ext2
TYPE=ext3
25 matches
Mail list logo
