*** This bug is a duplicate of bug 103770 ***
https://bugs.launchpad.net/bugs/103770
** This bug has been marked a duplicate of bug 103770
isw: can't find disk table slot with funky serial numbers
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs
Yep... the drive appears to have a really bizzare serial number using
non alpha-numeric characters which does not match the serial number
recorded in the raid metadata. This is likely due to the bios and
dmraid interpreting the meaning of the non ascii bytes differently. I
will have to investigat
Hello!
Here is the output from hdparm -i /dev/sdb
/dev/sdb:
Model=External Disk 0 , FwRev=RGL10364,
SerialNo=038602F__0_A
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=793
Sorry, I got a bit mixed up with some other bug reports. Now that I
look at the metadata again after reading my previous comments, it does
appear that the metadata on sdb is corrupted and the windows driver just
isn't noticing. To verify, can you post the output of sudo hdparm -i
/dev/sdb?
--
d
Hello!
Ok, Here is the output from dmraid -n and dmesg
I just want you to know, that I one more drive connected now, an
external usb 2 2,5" harddrive (Western Digital - My passport), but I
hope that this does not disturb the other harddrives that are already
connected?
jonssonj, it appears that the windows driver does not do very much
consistency checking to validate that the metadata makes sense before
trying to access the disks, possibly in a way that could cause data
loss. Could you post the output of dmraid -n, and dmesg? I think I may
know what is wrong.
Hello!
Sorry for not answering for a while. No, I'm sorry, I can't recreate the
raid, because I have 600GB of data on that volume and I have nowhere to
store that amount of data, temporarily.
I have updated my bios though, before I created the array.
I also finds it strange that the metadata cou
Hrm the metadata on sdb appears to be broken in that the serial
number recorded in the device section and the serial number recorded in
the disk section do not match. I also notice that the version is an
older one. Can you try updating your bios and recreating the array?
--
dmraid doesn't w
sdd.bz2
That was all three of them.
BR
Jorgen
** Attachment added: "output from dd command sdd.bz2"
http://launchpadlibrarian.net/14626062/sdd.bz2
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because y
sdc.bz2
** Attachment added: "output from dd command sdc.bz2"
http://launchpadlibrarian.net/14625989/sdc.bz2
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello!
Thanks for your quick reply. Here are the first attached file. I guess
that you mean sdb, sdc and sdd and not sda, sdb and sdc :)
Here is sdb.bz2
** Attachment added: "output from dd command sdb.bz2"
http://launchpadlibrarian.net/14625976/sdb.bz2
--
dmraid doesn't work with gigaby
Jonssonj, please do the following in a terminal:
sudo dd if=/dev/sda skip=781418672 bs=512 | bzip2 -c > sda.bz2
sudo dd if=/dev/sdb skip=976769072 bs=512 | bzip2 -c > sdb.bz2
sudo dd if=/dev/sdc skip=781418672 bs=512 | bzip2 -c > sdc.bz2
And attach the output files to this report.
** Changed in
Hello!
I have the exact same problem with my raid set. I have an ASUS P5W DH
Deluxe.
I have two Samsung 400GB harddrives on the Intel ICHR7 controller.
I have one WD 500 GB harddrive on the Intel Matrix Storage controller.
These three drives are in a striped raid that I have configured in the
bi
Yes, you can plug the original drives back in later and the bios will
recognize them.
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
sorry for the late...
the motherboard revision is: GA-K8NF-9 (Rev 1.x)
and the bios version is: F11 released at 2006/01/16 description 1.
Update CPU microcode
i can do what you ask me... but i have a question... i CAN'T format my actual
hd but i can swith off replace them with two blank and m
which revision of motherboard and bios version please.
if you can install on two identical blank HDs, and zero them as Philip
says, it will be a lot easier to figure out the metadata.
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received
the exact chipset name is:
nForce4-4X
and i can try at the weekend to make what you ask...
i hope :D
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
If you could build a raid on two drives that are totally blank ( dd
if=/dev/zero of=/dev/sda ), then look at what is written, it would help.
I had noticed that NVRAID part myself, but that is not the signature
that dmraid is looking for. I am thinking that nvidia has come up with
a new metadata fo
ops i forgot:
[EMAIL PROTECTED]:~$ sudo dd if=/dev/sda of=outputsda skip=312580152
1656+0 records in
1656+0 records out
847872 bytes (848 kB) copied, 0.047372 seconds, 17.9 MB/s
[EMAIL PROTECTED]:~$ sudo dd if=/dev/sdb of=outputsdb skip=320171056
2000+0 records in
2000+0 records out
1
output file sdb in attach
** Attachment added: "outputsdb"
http://launchpadlibrarian.net/9302209/outputsdb
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
output file sdc in attach
** Attachment added: "outputsdc"
http://launchpadlibrarian.net/9302221/outputsdc
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
i have run the command that you had asked to me...
here the results:
[EMAIL PROTECTED]:~$ sudo fdisk -u -l /dev/sdb
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0xd00
pls run:
sudo dd if=/dev/sda of=outputsda skip=312580152
sudo dd if=/dev/sdb of=outputsdb skip=320171056
sudo dd if=/dev/sda of=outputsdc skip=390719968
sudo fdisk -u -l /dev/sdb
sudo fdisk -u -l /dev/sdc
Philip - I found this line in his dump:
0002b070 |...@ ..NVRAI|
0002b080 |D.ROM.. ..(x.
oops I meant:
sudo dd if=/dev/sda of=outputsda skip=312580152
sudo dd if=/dev/sdb of=outputsdb skip=320171056
sudo dd if=/dev/sdc of=outputsdc skip=390719968
sudo fdisk -u -l /dev/sdb
sudo fdisk -u -l /dev/sdc
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net
i can't reformat but maybe i can make a new raid with 2 different hd that are
news... i hope that when i put on back the old drive the raid can be remake
without loosing data...
but so.. i have have a question... why does win work fine??? if it is bugged
the win driver shouldn't work... how is
Going by what you have said, sda is your WD drive which appears to be a
member of the raid, but the drive does not appear to contain the nvidia
metadata. Either that, or the bios is bugged because of the large size
of your disks and is placing it in the wrong location. Could you
reformat these dr
as you tell me that the sda doesn't look like in the raid but the problem
remain... dmraid doesn't recognize my stripe raid...
is useful that i launch the "dd" command to all drive for found the problem
that i have with the dmraid?? if it can help i can do...
thanks matteo
--
dmraid doesn't w
i'm sure that the drive involved in the raid set are:
the WD the first and the second... (i don't know how to screen shoot the
bios page :( ) but now i'm in win and win is running and if i launch the
nvraid utility it say this:
(look the image)
and when the pc boot up the raid chipset on the bi
It does not look like that drive ( sda ) is in the raid. Are you sure
that isn't the one outside the raid set? And the raid set still shows
up in the bios right?
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notificatio
thanks for the answer !!
so i have 3 different HD installed on my pc, i have configurated the
raid0 between the first two... the last is only a data storage for the
data exchange between win e linux.
and i know that in the raid0 configuration the size of the single HD isn't
important because th
Why are all 3 drives different sizes? You should use identical drives
for a raid.
What was the exact command you used to generate that file, and are all 3
of the drives in the raid0 according to the bios?
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bu
any can help me???
--
dmraid doesn't work with gigabyte k8nf-9 nforce4x chipset
https://bugs.launchpad.net/bugs/138130
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
[EMAIL PROTECTED]:~$ sudo fdisk -u -l /dev/sda
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x
Disk /dev/sda doesn't contain a valid partition table
[EMAIL PROTECT
33 matches
Mail list logo
