Hi Vertago1,
Yes the patch appeared to work, we merged it to the Ubuntu dev packages and it
worked for some people.
The sector size was still an issue in some setups as windows appeared to use
both 512 and 1024 byte sectors sizes.
However once we hit the release we quite a few people then repor
After some digging I found it was added to the raring kernel git 39 hours ago:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-raring.git;a=commit;h=1657e988a4c14ca953b77048c6c25b90c09a5bd9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
This issue has been fixed upstream with the patch named "drm/radeon: fix
resume on some rs4xx boards (v2)", git commit:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=acf88deb8ddbb73acd1c3fa32fde51af9153227f
I have built the current 3.8 ubuntu kernel with this
Hi Christopher,
Sorry its taken me a while to get around to testing this.
I have downloaded live CDs going back to Ubuntu 8.04 testing each as I go, and
8.04 (kernel 2.6.24) suspends correctly.
All my hardware functions in 8.04 as well as getting reasonable frame rates in
glxgears (~665 fps).
Hi Christopher,
I am happy to try the latest BIOS again if you think it will aid us in
finding the cause of the problem?
The latest mainline kernel behaves in exactly the same way.
Danny
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Hi,
I was previously running the latest BIOS and it had issues in booting,
it would only get to the desktop about 9 times out of 10.
Commands:
danny@danny-laptop:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for danny:
V3.00
08/17/2007
--
You rec
Thanks Joseph, I hav tested the latest upstream kernel as you have asked
with the same results.
As some further information the hibernate function works correctly.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received thi
Public bug reported:
I have had issues with resuming from suspend for a long time (possibly from
just after the KMS migration).
Suspend is one of those features that I have never really used, but now I am
doing a lot of long train journeys it is a very nice feature to have, so I
thought I would
Sorry Phillip if I wasn't clear, what I meant to say was that with
virtual drives in both virtualbox and qemu windows 7 created a GPT with
a 512 bytes per sector size no matter the drive size.
So I concluded that it must be the promise raid driver itself that
creates the larger sector size which w
I can't see where dmraid advertises its sector size!
Phillip do you have any idea?
I did find a thread where someone described the same symptoms of large arrays
on the promise raid controller and the sector counts:
http://ubuntuforums.org/showthread.php?t=1768724
(Phillip you commented on this th
Ok,
After some testing I think I can confirm that the sector size is coming from
the pdc driver and not windows.
All the drives I created of various sizes with windows and gparted show up in
both operating systems and always have a sector size of 512.
So we need to change the sector size adver
That is interesting.
I have been doing various searches online and can't find any other references
to windows doing this.
Are you using 64-bit windows?
I am just setting up a virtual machine with a rather large virtual drive
to see if I can replicate.
--
You received this bug notification beca
Does the gparted version work in Ubuntu?
It doesn't appear to have a protective MBR as in the GPT spec but this may not
be an issue.
It appears that windows believes the LBA of the drive is 2048 (0x800)
bytes where as ubuntu thinks it is 512 bytes (0x200) as the GPT header
is located at LBA1.
I
If you have created a correct GPT then kpartx should find them.
Does dmraid detect the correct RAID layout?
Ie stride size, count, etc.
You need to investigate the partitioning on the disk, you need to make
sure your data is backup up as you are likely to loose partitioning
here.
Dump the curren
Looking back I think this was the issue Nishihama Kenkowo had with the
original patch.
Sorry if you are already working on this offset issue but I thought I
would add some thoughts.
Looking through the dmraid code I cannot see where it would add an offset.
Would the offset simply be the metadata
What is irritating about this is the backlight on laptops is usually the
highest power item.
So on battery I want it to always be low power to maximise the battery
life, I don't want it to continuously go bright when I touch my laptop
as this consumes excess battery.
As I can't have that my displ
Hi Phillip,
Attached is a patch that should fix the issue based on the ubuntu 12.10 version
of dmraid.
It compiles but is untested, are you able to test this for me?
Do you need me to create a debdiff or is it easy for you to do?
I haven't had my build environment set up at home since I first at
Excellent, thank you for doing that.
I will cook up a patch later, similar to my old one, that uses this new
offset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/599255
Title:
dmraid fails to read
Henry if you manage to backup your data you could confirm this if you
create several different sized arrays.
2TB will create 0x at 0x2E8
3TB will create 0x0001 at 0x2E8
6TB will create 0x0002 at 0x2E8
8TB will create 0x0003 at 0x2E8
After each array creation dump the meta data and post please
Metadata from here also seems to agree:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/770600/+attachment/2094374/+files/dmraid.pdc.tar.gz
His has high bits of 0x at 0x2E8 for a 2TB array
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Hi Phillip and Henry,
I have taken a quick look at this and compared the latest metadata with
Nishes from before and it looks like the offset for the high bits might
actually be at 0x2E8 (in filler 2).
Basically we have 3 metadata sets in this bug report.
Nishes exist in metadata.tar.gz, the fir
This appears to be a bug in the way Java 1.7 handles the 'Ubuntu Normal'
System font.
Every other font I have tried works fine, its only when Ubuntu Normal is
selected as the system font that all netbeans text goes bold.
Interestingly this happened to me after installing wine as well, re-
install
@Path
Off topic for a bug report but I will set you straight on a few things.
Dmraid support is good but for later hardware is crappy at best but
don't blame the Ubuntu devs. The original developer (a red hat guy)
stopped developing the project a while ago and we have been trying to
get him to me
This is a rather annoying issue.
Looking through all the power manager settings it seems they have
removed the brightness_battery and brightness_ac settings that used to
achieve this. Hopefully it will be back in 12.04
Until then a possible solution is to write a script that sets the back-
light
Well really it was a bug before in 10.04 as the partition naming was
wrong then. One of the issues in the Ubuntu development is that there
are lots of people who don't talk to each other. Ubiquity (the
installer) breaks dmraid at least once during every development cycle.
Ideally you should have b
This is an unfortunate side effect of pulling dmraid inline with the
rest of the linux kernel.
If a partition name ends with a number a 'p' is added before the partition
number to avoid confusion.
If you didn't have a number at the end of the volume label this wouldn't have
been an issue.
I thi
*** This bug is a duplicate of bug 770600 ***
https://bugs.launchpad.net/bugs/770600
I have marked this bug as a duplicate.
Any comments you have should be posted in the other bug report.
** This bug has been marked a duplicate of bug 770600
22_add_pdc_64bit_addressing.patch: breaks some p
This may be related to this bug:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/770600
Unfortunately a patch was included to enable large disk support that was
untested and broke many configurations.
Phillip has a PPA in that thread that might fix the issue for you.
--
You received this
Also please post the output of
sudo dmraid -s
Also could you post the disk size information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770600
Title:
dmraid fails to mount raid0 array after upgr
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.
--
You received this bug notification because yo
I meant confirmed in Natty (11.04) not maverick!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/568090
Title:
ath5k should be loaded with nohwcrypt parameter
--
ubuntu-bugs mailing list
ubuntu-bugs
I can confirm this is still a bug for the latest maverick.
The nohwcrypt option solves it for me.
lspci -vnn
09:04.0 Ethernet controller [0200]: Atheros Communications Inc. AR2413 802.11bg
NIC [168c:001a] (rev 01)
Subsystem: Askey Computer Corp. Device [144f:7094]
Flags: bus maste
Installing using CD media made no difference, I still get the slideshow
after the migration screen!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767317
Title:
installation stalls after migration sc
I also have this issue and am running the iso in loopback of USB.
I will try from CD media if I get the chance!
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
The solution you found indicates that a BIOS fakeraid was setup on those
disks, you may have done it accidentally when playing with BIOS
settings.
Unfortunately the useful information was erased when you did dmraid -E.
In Ubuntu 9.10 fakeraid became a default option during setup, you could
actual
As phillip previously said there is a dm-raid456 on the way (dm-raid is
the module and it exists in 2.6.38 but is still listed experimental).
I believe that most standard RAID5 arrays do work or we would see more bugs
(RAID5 is a common setup with dm).
Obviously yours is a special case and requir
Ignore my previous comment, I hadn't read the last couple of comments!
There is still heinz's dm-raid45 module in the ubuntu kernel.
When you say it doesn't work in 11.04 is that with this module or the
one you tried to compile?
--
You received this bug notification because you are a member of
Isn't the raid4-5 driver deprecated?
Ubuntu hasn't used it for 2 releases which is why you had to manually compile
it.
It has now been replaced in the linux kernel by the new kernel driver
'raid456' hasn't it?
Dmraid probably needs to be re-worked to use this newer driver for it to
accept raid5
Antonio your drives must have had dmraid metadata on them!
This is the only way for Ubuntu to detect this type of RAID and as a result it
activated your disks in that way.
Removing the metadata (with dmraid -E) fixed your issue.
You must have created a RAID array at some point or bought second ha
(By backport system I meant SRU system!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/356503
Title:
[patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28
--
ubuntu-bugs mailing list
ubuntu-b
The reason this patch was never accepted is not because of the incorrect status.
And its no vague excuse.
It could not be tested in karmic due to there not being a dm-raid-45
module there, this is the usual backporting process which stopped the
whole system as originally we missed the initial 9.04
The documentation is unavailable so it was found through
experimentation, the only bits in the metadata that were free and
happened to be the correct values were these ones.
Thats why I made my comments about testing in post 87.
The upper 8 could be used for anything, I guess they just happened t
Hi phillip.
I have just tested the version in your PPA, it works with both my fakeraid
controllers! Good work!
Here is the contents of my /dev/mapper:
control
isw_bgafaifadd_DATA
isw_bgafaifadd_DATA1
jmicron_HD2
jmicron_HD2p5
jmicron_HD2p6
jmicron_HD2p7
jmicron_HD2p8
jmicron_HD2p9
So it has inse
I have just tested the latest alpha of natty and the bug still remains.
I also tested with the final release of 10.10 and the bug remains there as well.
Testing the upstream change results in the same issue as described
originally, ie does not fix the issue.
The patch I proposed fixes the issue,
Tested on natty narwhal and bug still exists.
Upstream change does not fix the issue!
** Changed in: dmraid (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/576289
I don't mind at all Phillip.
Do what you like!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/599255
Title:
dmraid fails to read promise RAID sector count larger than 32-bits
--
ubuntu-bugs mailing
Hi Phillip,
Sorry for the late response, I don't get much time for launchpad these
days.
The jmicron name fixing patch is because I have jmicron raid on my testing
machine and its running 10.04.
Interestingly I tried 10.10 the other day and that patch had been dropped. I
think my jmicron patch
I was wondering if that was possible.
metadata.tar.gz is a full dump.
You should see a second raid set which is 300 GB or so, this is supposed to be
2.5TB but has the top bits truncated.
With my patch it detects the raid set correctly but windows was using a larger
sector size and so Ubuntu and
If the 'normal' drive doesn't have any raid metadata, ie not been used in a
fakeraid before, then you shouldn't suffer from this bug.
This bug is primarily to do with the metadata not being read properly by dmraid
and so the device isn't exposed properly to the rest of the system.
In particular
Unfortunately no I didn't. I don't have the actual promise hardware and so
debugging this issue was very hard.
Nishihama Kenkowo helped me a lot but I never completed the work. Debugging
hardware is much easier when it is sat infront of you.
I think I was close but I decided to give up as I coul
@bash.vi
The reason that dmraid will halt your system from booting is that the raid
metadata will still be in your disks.
To stop dmraid from recognising your disks as a raid you have to purge this
data from your disks.
Dmraid can only identify disks as in a raid set by this metadata.
I get th
How are you compiling the Ubuntu kernel source?
You will need to use dpkg as there will be a lot of debian/ubuntu patches to
the main source!
This will quite often leave you with errors like you got above.
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
Y
Are you able to do a fresh install and have it boot correctly?
(To distinguish if this is an upgrade issue or a dmraid bug)
--
Upgrade fails from 8.04 LTS to 10.04 LTS (beta)
https://bugs.launchpad.net/bugs/560748
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Packages like FGLRX wont work upon upgrade if you have a card that is not
supported by the latest version of ATIs driver.
Running unsupported pacakges will give you errors.
I have a feeling your initramfs isn't being created properly.
If you are able to boot can you give us the version info of d
Hi,
I will try again later. I've been busy moving house the last couple of
weeks so I haven't had the time.
thanks,
Danny
--
Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid)
https://bugs.launchpad.net/bugs/348353
You received this bug notification because you are a member of Ubu
*** sorry Shannon Jacobs (misread name due to late night)
--
[MASTER] various unrelated crashes for firefox-3.0 and xulrunner-1.9
https://bugs.launchpad.net/bugs/228806
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
@ Shannon Jones
Quite obviously you have an issue with firefox (this is not under the main
control of the ubuntu dev team).
It is most probably caused by a plugin you have running and nothing to do with
Ubuntu at its core, disable your plugins and see if that helps then complain to
who wrote th
Well dmraid doesn't have the ability to rebuild the array so I seriously doubt
dmraid did this.
I would be looking in to something else and be fortunate that you had the
backups.
--
Server disk was reverted as it were 1 month ago. How?
https://bugs.launchpad.net/bugs/611188
You received this bu
Oh,
Just looking through again.
It seems the disk that is failing is not in your sil raid set?
So maybe the disk dying is unrelated.
The files you found in the original post of this report are outputted
when you run `dmraid -rD`, it dumps the metadata so you can restore it
if something goes wron
I don't see how a disk failure would cause disk to return to the state
of 3-4 months ago.
Do you have any backup software running that could have caused this?
Is this the first power down of the machines since 3 months ago?
Is it possible that the drives just haven't been synced since then?
Also
Not exactly the same as buf is 2 bytes longer than i in my patch but it should
work.
I will test this later and let you know!
--
Jmicorn controller bad names cause installer to crash
https://bugs.launchpad.net/bugs/576289
You received this bug notification because you are a member of Ubuntu
Bugs
I have tried this.
Unfortunately the build system didnt create it.
I will have to upload the source package later with the full buil-
depends.
--
Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid)
https://bugs.launchpad.net/bugs/348353
You received this bug notification because you
I have managed to incorporate the alsa config into my pulseaudio file now.
Adding the config to /usr/share/alsa/a52.conf and adding a hook into the
pulse.conf within the same directory works perfectly.
My PPA now contains the packages and configs require to get this working
from scratch.
So to d
Just removing the card line works.
It binds to the first SPDIF it finds I think which will usually be the correct
one.
--
Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid)
https://bugs.launchpad.net/bugs/348353
You received this bug notification because you are a member of Ubuntu
Perfect. The extra in thread rewind fixed it for me.
I now have a fully working a52 through pulseaudio.
I have updated my PPA and the new patch is attached.
** Patch added: "Working version of the patch"
http://launchpadlibrarian.net/51859149/0098-fix-a52-surround.patch
** Patch removed: "Pat
Forgot to say that any audio app causes this crash and the device just
disappears then I have to restart pulseaudio.
I can get sound out just fine using the speaker-test to the alsa device
only.
--
Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid)
https://bugs.launchpad.net/bugs/3
Well unfortunatly it appears to not work for me.
Pulseaudio detects the card and profiles correctly but when it comes to playing
it dies.
Here is my verbose output:
I: alsa-sink.c: Trying resume...
D: alsa-util.c: Maximum hw buffer size is 21824 ms
D: alsa-util.c: Set buffer size first (to 4608 s
Oh yeah, forgot to delete that line.
I have made the changes you have suggested, in the ppa and in this patch.
The .asoundrc will need user input anyway for the card name, but the
configuration will be reduced to only editing that line now.
A native pulseaudio ac3 would be the best but if this w
Thanks and nice work, I will have to test this when I get home.
For now I have created a debian patch against the latest pulseaudio
build in Ubuntu which can be put into the debian/patches (and added to
the debian/patches/series file) folder to enable building the .deb
package using dpkg (and patc
Well obviously something isn't reading the MBR correctly.
The MBR is read by the dmraid code so this could be why.
Could you dump the MBR again and post it up?
sudo dd if=/dev/mapper/pdc_cdgjdcefic of=linmbr2.img bs=512 count=1
--
dmraid fails to read promise RAID sector count larger than 32-bit
For completeness I am attaching the debdiff for my attempt at enabling the
extended LBA.
I think the offset is wrong but it is documented in the header file.
I am sorry we could not fix this.
** Patch added: "not_complete.debdiff"
http://launchpadlibrarian.net/51584787/not_complete.debdiff
-
Hmmm.
I think there is an issue with the offset in that case.
And earlier I was fooling myself by reading the same MBR back twice.
Its hard to reverse engineer over a long distance. If I could find a
cheap promise controller I would buy one to have a go at fixing this but
unfortunately it looks l
I have done some further digging and it seems that kpartx can read the gpt
partition table from dmraid.
(sudo apt-get install kpartx)
Usage:
kpartx -a /dev/mapper/pdc_cdgjdcefic
Use that command once you have booted or created the gpt structure and
you should then have the /dev/mapper/X block de
Oh dear.
It seems this version of dmraid won't handle gpt!
So you may be a little stuck with using partitions of that size.
There is a thread here where someone has made a patch:
http://ubuntuforums.org/showthread.php?t=1369224
I will have a look at it later to see if I can incorporate it into m
Hmmm, that is interesting.
Both MBRs have the same structure, which means the offset is correct.
I can see one issue though.
In the windows MBR the sector size is listed as 0x7800 = 2147481600
sectors. The normal block size is 512 bytes so 2147481600 x 512 =
1099510579200 = 1TB (This is what
It seems the partition table is getting corrupted, possibly by an incorrect
offset being used.
I would like you to dump the MBR created by both windows and Ubuntu.
First in windows create an MBR structure with the partitions as you just have
then boot into Ubuntu.
When in Ubuntu run the followin
Hi,
Windows cannot use EXT4 unfortunately.
Also the ubuntu installer (ubiquity) can't use dmraid. There is a bug somewhere
on this.
Disk utility also seems to have issues with my dmraid devices, my volumes are
listed twice, one saying free and the other with the partitions.
Are you sure the pa
If you reformat in gparted does it then become NTFS?
This is what I found.
Could you try it on a non dmraided drive as well?
Most people will only use NTFS in linux with premade partitions when dual
booting so its possibly a bug between gparted and ntfs-3g.
--
gparted with dmraid causes incorre
Hi,
You can test the 4.5TB array in your own time. I am a patient man!
Also could you please post the output of `dmraid -s` with the current patch?
I want to check some numbers.
In the end you might be better off with 2 RAID arrays as the first array
will be quicker as it will be closer in on th
** Summary changed:
- dmraid cannot use over 2TB raid0
+ dmraid fails to read promise RAID sector count larger than 32-bits
--
dmraid fails to read promise RAID sector count larger than 32-bits
https://bugs.launchpad.net/bugs/599255
You received this bug notification because you are a member of
Interesting.
I just reformatted an NTFS partition on my jmicron RAID using gparted.
The first time I formatted it the filesystem was then listed as 'unknown' by
gparted. But reformatting again turned it back into an NTFS. (this can be
repeated as many times as you like)
I have also just tried r
Hi Nish,
I think I have found what I needed and I have made a patched version of dmraid
and uploaded to my ppa.
This will affect the way that it detects the pdc raids so please make sure you
have everything backed up (its probably best done from a live CD).
If it works as I expect it will you s
Yep that's perfect.
The second metadata chunk is there for me to investigate.
I will let you know when I find a solution.
Thanks!
--
dmraid cannot use over 2TB raid0
https://bugs.launchpad.net/bugs/599255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
To use the script open a terminal and make a clean directory to work in and
place the thh dump-pdc-metadata.sh in there (extracted from the archive I
uploaded).
Make the script executable and then run it.
chmod a+x dump-pdc-metadata.sh
./dump-pdc-metadata.sh
It will ask you for your password as
The version of gparted in my ppa doesn't rely on kpartx like the repository
version. It should leave dev names alone but the repository version seems to
screw them up adding a p in sometimes.
The next version of dmraid will leave the p in there, there is a discussion on
this in this bug: https:/
Hmmm. It didn't quite output what I wanted, sorry about that.
I have made another patched version which is more verbose and should
show each meta location it tries (weather it finds it or not).
Unfortunately there is a bit of a wait in the ppa build queue at the moment.
The new version is 1.0.0.r
Hi,
The 64-bit version has now been built.
So you should be able to upgrade.
To check the installed version you can use dpkg, the program version will
always remain the same.
dpkg -p dmraid | grep Version
Once upgraded it should output:
da...@danny-desktop:~$ dpkg -p dmraid | grep Version
Versi
Hi,
Unfortunately the package is still waiting to be built by the Ubuntu servers.
It should be complete in 7 hours from now, it seems there is quite a queue for
building.
You can check the progress by looking on the ppa page
(https://launchpad.net/~danwood76/+archive/ppa-testing) and checking th
Hi,
I have patched dmraid to show the metadata locations in the debug output
(hopefully)
This can be found in my ppa
https://launchpad.net/~danwood76/+archive/ppa-testing
Update the dmraid packages from my ppa and then run `dmraid -ay -d -vvv` again
and post the output.
This should hopefully d
Annoyingly the metadata only contains the information for the first raid set
(which is fine of course). The other set will be another metadata block.
We can dump this metadata manually but we need to know where its located.
To do this I will patch a version of dmraid that will output these
locati
It dumps to a directory without saying anything.
In your current working directory.
So for example if I run it in the terminal I get this output (I have jmicron
and intel raids):
da...@danny-desktop:~/dmraid$ sudo dmraid -rD
/dev/sda: isw, "isw_bgafaifadd", GROUP, ok, 1465149166 sectors, data@ 0
Right.
The bug is definitely in dmraid. (Disk size reported my dmraid is wrong by
32-bits probably due to truncation)
Could you post a metadata dump please. This will allow me to explore the
metadata and see if something is different to what it expects.
To do a metadata dump run the following co
The AMD RAID control panel has nothing to do with linux.
To debug the issue I need the output of the commands I have asked for.
--
dmraid cannot use over 2TB raid0
https://bugs.launchpad.net/bugs/599255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
OK well the debug stuff all looks fine.
Could you also post the output of `dmraid -s` (this will list all disk
sizes and status seen by dmraid)
What software are you trying to partition with?
And how are you working out how much disk they are seeing?
Also can you post the output of an fdisk list
I have just been looking at the sources for the centos dmraid package for the
pdc. (Promise controller)
The only difference is a Raid10 patch but won't affect you as you are not using
that.
I am inclined to believe the bug is in whatever program you are using
for partitioning.
The dmraid debug
Well we need to determine which software the bug is in.
How are you determining that Ubuntu and Fedora can't see the full amount?
E.g what program are you using for partitioning.
Could you please post the output of (in ubuntu and centos):
sudo dmraid -ay -vvv -d
This will help us!
--
dmraid can
I've just had another thought.
Are you trying the 64-bit version of Ubuntu?
32-bit addressing will only go up to 2.2TB so it might be worth trying 64-bit
Ubuntu instead.
2.5TB - 2.2TB = 300GB (Sound familiar?)
But dmraid will not handle two separate arrays on one disk.
If 64-bit sees the array j
Also what RAID controller is it?
--
dmraid cannot use over 2TB raid0
https://bugs.launchpad.net/bugs/599255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
Ok,
Could you please output the result of the following command from a live session:
sudo dmraid -ay -vvv -d
Can windows see the 2.5TB drive ok?
--
dmraid cannot use over 2TB raid0
https://bugs.launchpad.net/bugs/599255
You received this bug notification because you are a member of Ubuntu
Bugs,
I think your issue may be caused by the fact that dmraid cannot handle
two seperate arrays on one disk set.
The best way to do it is have the RAID0 set as the entire set (all 4.5TB) and
then partition into smaller chunks.
Please try this first!
--
dmraid cannot use over 2TB raid0
https://bugs.l
1 - 100 of 107 matches
Mail list logo
