*** This bug is a duplicate of bug 449876 ***
https://bugs.launchpad.net/bugs/449876
** This bug has been marked a duplicate of bug 449876
raid degraded after update to Karmic beta
--
Some sata drives are now /dev/mapper/nvidia_xx
https://bugs.launchpad.net/bugs/459485
You received
NaSH, any chance you could reinstall dmsetup or dmraid (one at a time)
and see which of the two caused this breakage? (I suppose it was dmraid,
but let's check). After you identified the package, can you please do
sudo udevadm test `udevadm info --query=path
--name=/dev/mapper/nvidia_xx`
You probably have fakeraid signatures on the disks. Since Ubuntu 9.10
has fakeraid support by default, your fakeraids will be discovered and
activated unless you use the nodmraid boot option.
The fake raid is on the disks, not on the motherboard. Linux/dmraid can
not see if you have disabled the
Tormod Volden [2009-11-10 16:27 -]:
The fake raid is on the disks, not on the motherboard. Linux/dmraid can
not see if you have disabled the fakeraid support in the BIOS, but it
sees the fakeraid signatures on the disks. If your BIOS does not have an
option to delete the fakeraid
Yes, blkid detects that it is a raid, and udev calls dmraid to search for and
setup the raid (see /lib/udev/rules.d/85-dmraid.rules).
To see what dmraid finds, run: dmraid -vvv -ddd -ay
This will also activate the raids, so to deactivate again run: dmraid -an
--
Some sata drives are now
I am having the same problem and it is as of yet unresolved. I kept
getting NFS stale file handle when trying to mount either of my two
SATA drives. I removed dmraid, dmsetup and kpartx and now the drives
show up properly in gparted.
The partition table on one drive (/dev/sdc1 aka Dumpster) seems
digism...@digismack:~$ sudo fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xeacaeaca
Device Boot Start End Blocks Id System
/dev/sda1 * 1
:(
digism...@digismack:~$ sudo gpart /dev/sdb -W /dev/sdb
Begin scan...
End scan.
Checking partitions...
Ok.
Guessed primary partition table:
Primary partition(1)
type: 000(0x00)(unused)
size: 0mb #s(0) s(0-0)
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
Primary partition(2)
type:
ok think i found the reason..
i removed dmraid, dmsetup and kpartx that where installed during the upgrade
and broke my system.
I donno why they where installed, is it automatic during the upgrade for any
reason ?
anyway, removing them resolve my pblm.
--
Some sata drives are now
** Attachment added: .etc.fstab.txt
http://launchpadlibrarian.net/34299540/.etc.fstab.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34299541/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34299542/CurrentDmesg.txt
** Attachment
oups..
the fstab sent with the report is the one i tried to tweak.
after going back to the original one, and reboot, the pblm still the same.
the original is the one attached here
** Attachment added: fstab
http://launchpadlibrarian.net/34299975/fstab
--
Some sata drives are now
11 matches
Mail list logo
