I have looked through the hooks and I can see there is a typo in the
dmraid hook file.
Open up /usr/share/initramfs-tools/hooks/dmraid, so:
sudo gedit /usr/share/initramfs-tools/hooks/dmraid
look through that file, on line 23 it says force_load dm-raid45. This
should of course be dm-raid4-5.
So
danwood76, nice catch! Some missing QA there. It would also need to be
corrected in /sbin/dmraid-activate. Can you please make a debdiff for
Jaunty, this should be SRU'ed as well.
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug
I will post the updated patch when I get homw from work.
kind regards,
Danny
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I tried your patch, but it did not seem to entirely fix my problem.
I am now receiving a message stating:
Checking file systems...
fsck 1.41.4
/dev/sdb: The file system size (according to the superblock) is 156528672 blocks
The physical size of the device is 73264338 blocks
Either the superblock
You shouldnt be running fsck on the individual drives within an array but on
the devices created by the raid sets.
dmraid devices are in /dev/mapper
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a
I ran an fsck on my actual array, but I am still encountering the same
fsck error. Should any disk in the array be ignored for fsck checks, and
fsck should focus on the actual array itself? Also, do you believe this
is related to this bug report, or should I be looking elsewhere?
--
Kubuntu
Is fsck being invoked by the kernel during boot when you get this error?
If so it could be in your fstab possibly, I dont have a RAID1 array so I'm
unsure if the UUIDs end up being the same for the array and the actual disks.
This could be resolved by replcing UUIDs.
I dont believe this has
I can confirm that the fix provided by danwood76 corrected the problem
for me and I am now running on the latest version of dmraid. Thank you
very much for your help with this sir. From my end this bug is fixed.
YEA!
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
Christopher, fsck is only run on the filesystems listed in /etc/fstab
(and the root fs in the boot parameters, defined in /boot/grub/menu.lst)
so check this first. There should be no reference to the raw devices
(sda* sdb*) whatsoever. If the fs are all correctly listed by UUID the
reason could be
Ok here is the debdiff for the two patches.
** Attachment added: dmraid_1.0.0.rc15-6ubuntu3.debdiff
http://launchpadlibrarian.net/28253322/dmraid_1.0.0.rc15-6ubuntu3.debdiff
** Changed in: dmraid (Ubuntu)
Status: Confirmed = Fix Released
--
Kubuntu Jaunty 9.04 dmraid fails with
Thanks! Works like a charm again now. Was getting pretty fed up with
that !*#@ busybox on every boot.
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: dmraid (Ubuntu)
Status: Fix Released = Confirmed
** Summary changed:
- Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
+ [patch] Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
--
[patch] Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
I upgraded from 8.10 to 9.04 yesterday and I am encountering this bug. I
am able to get the array online by running dmraid -ay then exit, which
boots the server normally. But, in the event of a power failure this
server would be offline until I could physically access it. Does anyone
know if this
Have you tried adding dm-raid4-5 to /etc/initramfs-tools/modules and
then rebuilding the initramfs? (sudo update-initramfs -u -k all)
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of
I just tried that, but it does not fix my problem. I even re-installed
dmraid and libdmraid with aptitude, but I am still encountering this
problem. Thanks for the suggestion. Do you have any others?
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
I can still confirm that this is a problem. I tried installing the
updates again the other day to see if they were fixed however it still
would not mount my raid and resulted with the same error that I started
the bug with.
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
Thank for the comments. I compiled a proxcedure thatr works for me (even
with the latest dmraid 1.0.0rc15-6):
After booting up in command line (as a root or with sudo):
modprobe dm-raid4-5
dmraid -an
dmraid -ay
mount -a
The problem is evident. The module dm-raid4-5 is not pre-loaded in the
@ Jaroslav
Works for me too! Thanks man...
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
2 Jaroslav Sedlacek.
I have the same problem last time, so I do like this -
https://bugs.launchpad.net/ubuntu/+bug/150531/comments/5
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of
As I've mentioned before make sure that you download and install the .14
version of dmraid then reboot. After you are done rebooting exec sudo
dmraid -ay and then sudo mount -a. After that you should have access to
your raid volumes once more. Please be aware that you will have to go
sift
I get the exact same error as thefuzz4.
I'm not rly that desperate to fix it though, but it would be nice to be able to
use my raid ;-P
If anyone needs me to post any debug info or something for further
verification or anything, just tell me.
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel
Hello, I am experiencing similar, but maybe not exactly the same problem.
I just upgraded fron 8.10 to 9.04 and cannot access my fakeraid disks with
dmraid.
I tried following:
sudo dmraid -ay
RAID set isw_eagedjaiic_Volume0 already active
ERROR: dos: reading
thefuzz4, it's realy help me, thank you
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
i have the same problem.
I upgraded to the 9.04 final.
dmraid -ay
RAID set isw_bbafiecdbg_Volume0 already active
ERROR: dos: reading /dev/mapper/isw_bbafiecdbg_Volume0[No such device or
address]
dmraid -ay -vvv -d
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdd: asr discovering
: storm yost...@gmail.com
Date: Thu, 23 Apr 2009 23:20:42
To: jason.hamil...@thefuzz4.net
Subject: [Bug 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
i have the same problem.
I upgraded to the 9.04 final.
dmraid -ay
RAID set isw_bbafiecdbg_Volume0 already active
ERROR: dos
ok I can confirm that after a complete system rebuild this is still a
problem. Let me know what else I can do to help diagnose and fix this.
Thanks.
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a
Ok I just updated today and got a Kernel update. In hopes that maybe
the new kernel will place nice with my dmraid I let apt-get also update
my dmraid to the .15 version. However it still fails with the new
kernel. Just wanted to post this in here to let you know. Thanks.
--
Kubuntu Jaunty
One other item. I am currently working on a rebuild of my machine that
I am testing this on. My thought was that maybe my upgrade from 8.10 to
9.04 had something to do with this. Due to the slow download speeds of
the individual packages I downloaded the alternate install cd. That
wasn't the
I have also encountered this problem.
dmraid output:
ubu...@ubuntu:/dev/mapper$ sudo dmraid -ay
RAID set nvidia_aecdafjf already active
ERROR: dos: reading /dev/mapper/nvidia_aecdafjf[No such file or directory]
Contents of /dev/mapper:
ubu...@ubuntu:/dev/mapper$ ls
control nvidia_aecdafjf
Right now so I can access my files on that drive I have temporarily
installed the 14 version but at the time I did have the version 15
installed. With the 14 installed I can manually activate my raid. If
you need me to install the 15 version for further testing just let me
know and I'll put it
Ok so did you try and use 1.0.0.rc15-6ubuntu1?
--
Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
https://bugs.launchpad.net/bugs/356503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes with the 15 installed I got the errors reported above. I completely
removed the packages and reinstalled them several times to see if they
would work but no go. The only way I could get the dmraid with version
15 to run was to use kernel 2.6.27-7 or the 2.6.27-11. But when using
2.6.28-11
32 matches
Mail list logo
