users March 2006

users@lists.fedoraproject.org

811 participants
1446 discussions

Software Raid 5 (FC5)
by Mark Yarbrough 01 Apr '06

01 Apr '06

During install time I was made 10 raid partitions across 5 500GB SATA drives. The final partition /dev/md8 wouldn't partition format and anaconda would crash telling me that the partition couldn't be formatted, and required a reboot. After the 3rd attempt I figured that the partitions are all the same size so I will just format it when I am in the running operating system. I took a look at my partitions using fdisk (take note that all 5 are the same save the drive number it self) <see paste at bottom> The partitions are there. /dev/sdX11 is the partition that I am trying to use. I tried to make the raid partitions to no avail. I looked at /etc/mdadm.conf and saw that /dev/md8 is there. From my limited understanding I am under the assumption that the raid is made and all I need to do is format it. I try to format it and I get the error reporting the device size to be zero. The partitions are clearly not zero. I am now stuck. What should I do next? Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 28683 230396166 fd Linux raid autodetect /dev/sda2 28684 38882 81923467+ fd Linux raid autodetect /dev/sda3 38883 41432 20482875 fd Linux raid autodetect /dev/sda4 41433 60801 155581492+ 5 Extended /dev/sda5 41433 43344 15358108+ fd Linux raid autodetect /dev/sda6 43345 45256 15358108+ fd Linux raid autodetect /dev/sda7 45257 46658 11261533+ fd Linux raid autodetect /dev/sda8 46659 47933 10241406 fd Linux raid autodetect /dev/sda9 47934 49208 10241406 fd Linux raid autodetect /dev/sda10 49209 49845 5116671 fd Linux raid autodetect /dev/sda11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 28683 230396166 fd Linux raid autodetect /dev/sdb2 28684 38882 81923467+ fd Linux raid autodetect /dev/sdb3 38883 41432 20482875 fd Linux raid autodetect /dev/sdb4 41433 60801 155581492+ 5 Extended /dev/sdb5 41433 43344 15358108+ fd Linux raid autodetect /dev/sdb6 43345 45256 15358108+ fd Linux raid autodetect /dev/sdb7 45257 46658 11261533+ fd Linux raid autodetect /dev/sdb8 46659 47933 10241406 fd Linux raid autodetect /dev/sdb9 47934 49208 10241406 fd Linux raid autodetect /dev/sdb10 49209 49845 5116671 fd Linux raid autodetect /dev/sdb11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 * 1 28683 230396166 fd Linux raid autodetect /dev/sdc2 28684 38882 81923467+ fd Linux raid autodetect /dev/sdc3 38883 41432 20482875 fd Linux raid autodetect /dev/sdc4 41433 60801 155581492+ 5 Extended /dev/sdc5 41433 43344 15358108+ fd Linux raid autodetect /dev/sdc6 43345 45256 15358108+ fd Linux raid autodetect /dev/sdc7 45257 46658 11261533+ fd Linux raid autodetect /dev/sdc8 46659 47933 10241406 fd Linux raid autodetect /dev/sdc9 47934 49208 10241406 fd Linux raid autodetect /dev/sdc10 49209 49845 5116671 fd Linux raid autodetect /dev/sdc11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sdd: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 * 1 28683 230396166 fd Linux raid autodetect /dev/sdd2 28684 38882 81923467+ fd Linux raid autodetect /dev/sdd3 38883 41432 20482875 fd Linux raid autodetect /dev/sdd4 41433 60801 155581492+ 5 Extended /dev/sdd5 41433 43344 15358108+ fd Linux raid autodetect /dev/sdd6 43345 45256 15358108+ fd Linux raid autodetect /dev/sdd7 45257 46658 11261533+ fd Linux raid autodetect /dev/sdd8 46659 47933 10241406 fd Linux raid autodetect /dev/sdd9 47934 49208 10241406 fd Linux raid autodetect /dev/sdd10 49209 49845 5116671 fd Linux raid autodetect /dev/sdd11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sde: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sde1 * 1 28683 230396166 fd Linux raid autodetect /dev/sde2 28684 38882 81923467+ fd Linux raid autodetect /dev/sde3 38883 41432 20482875 fd Linux raid autodetect /dev/sde4 41433 60801 155581492+ 5 Extended /dev/sde5 41433 43344 15358108+ fd Linux raid autodetect /dev/sde6 43345 45256 15358108+ fd Linux raid autodetect /dev/sde7 45257 46658 11261533+ fd Linux raid autodetect /dev/sde8 46659 47933 10241406 fd Linux raid autodetect /dev/sde9 47934 49208 10241406 fd Linux raid autodetect /dev/sde10 49209 49845 5116671 fd Linux raid autodetect /dev/sde11 49846 60796 87963876 fd Linux raid autodetect # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md8 level=raid5 num-devices=5 uuid=fc489661:c7e54273:f9a60c82:fb747b29 ARRAY /dev/md6 level=raid5 num-devices=5 uuid=eac1a77f:5278bfcd:4ae75c92:7ecde09b ARRAY /dev/md3 level=raid5 num-devices=5 uuid=1e94cb1d:f84f5a3b:1e0ff333:408d5bb7 ARRAY /dev/md5 level=raid5 num-devices=5 uuid=f5bfaf8b:8a591cf0:d73b7d31:4c07a93b ARRAY /dev/md1 level=raid5 num-devices=5 uuid=0bf1a445:323d5326:5a7a92fc:1c346c33 ARRAY /dev/md9 level=raid5 num-devices=5 uuid=f5811eae:cfb21182:41881dcf:739f1bad ARRAY /dev/md4 level=raid5 num-devices=5 uuid=348c95b9:df7feee6:41713309:a9324496 ARRAY /dev/md0 level=raid5 num-devices=5 uuid=bf7ef721:318d6d4e:b626b349:5f9c7e15 ARRAY /dev/md7 level=raid5 num-devices=5 uuid=a196ca52:c6700579:ff5a0379:9d6c9084 ARRAY /dev/md2 level=raid5 num-devices=5 uuid=5e0d3003:e65e36d0:25158ed3:f81e126d

8 12

FC5 RAID 1 - booting off either drive
by Laurence Vanek 01 Apr '06

01 Apr '06

Greetings - To my surprise, fresh install of FC5 with RAID 1 configured at install time went without a hitch. I have /dev/md0 defined on /boot partitions. It boots fine with this setup. I had my FC4 system setup this exact way except I found that I had to manually install grub on one of the disks to permit booting off either one if the other is down. Does anyone know of a way to check for the presence of grub on each drive (obviously its on hda since it boots presently) to see if this needs to be done for FC5 also without powering down each drive in turn & attempting to boot?

3 10

Problem with accents on mounted partitions
by Paul Smith 01 Apr '06

01 Apr '06

Dear All When I mount, from FC5, a partition of FC4 with the command mount /dev/hdc1 /mnt/fc4 I get 'm\341tica' as the name of the directory 'mática'. How can I get the accents correctly? Thanks in advance, Paul

3 4

Fedora Core 5 -- slow GUI performance
by Motor 01 Apr '06

01 Apr '06

I have an AMD Athlon XP2000+ with a Matrox G550 card. I used to use it with satisfactorily with FC4. I recently upgraded to FC5, and I'm finding that the graphics performance is quite poor. The major problem was Firefox, and I solved that by telling firefox not to use Pango (and by extension Cairo -- as I understand it) with the MOZ_DISABLE_PANGO=1 environment variable. However, the same problem afflicts all GNOME applications. Slow redraws and generally sluggish feelings and high CPU usage generally -- gfx seem particularly badly affected when heavy CPU using programs are used. I notice it particularly with Nautilus in List view mode... which, as a naive assumption, I take to be because it has lots of text. The slow down doesn't seem to affect Nedit (which doesn't use Pango). For example, resizing a GNOME terminal window when it is sitting on top of GNOME app with lots of text, I can practically watch the GNOME terminal window redraw itself. This... well... sucks, and is a pretty major regression from FC4, especially since the Matrox G550 has Free software drivers. Is it ever likely to get fixed, or am I just stuck? Is there anyway to get Pango in FC5 not to use Cairo (assuming that is the culprit)?

2 4

Adding CPU temp to Ksensors
by Douglas Phillipson 01 Apr '06

01 Apr '06

Is it possible to add CPU temp to Ksensors? If not, is there another package that allows me to see the CPU temperature? Thanks Doug P

3 2

OT: bind question
by Steven J Lamb 01 Apr '06

01 Apr '06

I am setting up a domain on a bind 9 server, I want to forward all of the subdomains as a CNAME to a different domain. An example zone file is bellow @ IN SOA ns1.domain.net. administrator.domain.net. ( 2006033165 ; serial 3600 ; refresh 600 ; retry 86400 ; expire 3600 ; default_ttl ) www 3600 IN A 254.254.36.5 @ IN MX 0 ms1.domain.net. @ IN MX 0 ms2.domain.net. @ IN NS ns1.domain.net. @ IN NS ns2.domain.net. @ IN A 254.254.36.5 admin 3600 IN CNAME www.CCC.com. *.BBB.com. 3600 IN CNAME *.CCC.com. This seems to work fine. However when A record requests go to BBB.com and get forwarded to CCC.com they need to keep the specific subdomain attached to the front of it as it is going to a webserver with virtual hosts. Without setting up all of the subdomins specificly is there anyway to accomplish this Any suggestions welcome Thanks Steven Lamb ADI Internet Solutions

2 1

FC5 127.0.0.1 refuses connection
by Geoffrey Leach 01 Apr '06

01 Apr '06

New update of FC5. Connection to internet (via eth0 and satellite) OK. However ... #sendmail -v root test . root... Connecting to [127.0.0.1] via relay... root... Deferred: Connection refused by [127.0.0.1] telnet, fetchmail, binmail (of course) have same problem. Can ping 127.0.0.1 Presumably related to update. Any suggestions?

3 2

NX bit: AMD vs Intel?
by Jurgen Kramer 01 Apr '06

01 Apr '06

On my Intel system (Xeon with EMT64 support) which runs the 32-bit version of FC5 I can see that NX support is active (from dmesg): NX (Execute Disable) protection: active On my other system, a AMD64 system running the 64-bit version of FC4, there is no message regarding NX support being enabled of disabled at all. Checking init.c in the kernel sources it seems that NX support is depended on PAE support and NX support from the processor. As the AMD processor supports both I aspect to see a NX procection active message on my AMD system as well. Does NX support suppose to work on 64-bit kernels ? Both systems run kernel 2.6.16. Jurgen

5 7

Problem with installing ipe
by Paul Smith 01 Apr '06

01 Apr '06

Dear All I am trying to install ipe with yum, but getting: --> Processing Dependency: libQtCore.so.4 for package: ipe --> Processing Dependency: libQtGui.so.4 for package: ipe --> Finished Dependency Resolution Error: Missing Dependency: libQtCore.so.4 is needed by package ipe Error: Missing Dependency: libQtGui.so.4 is needed by package ipe Any ideas to go further? Thanks in advance, Paul

3 6

Rebuild src.rpm kernel driver for non-running kernel
by Jonathan Berry 01 Apr '06

01 Apr '06

Hi all, I have a few kernel drivers that I like to install that are not included in the kernel itself but have rpms or src.rpms available from Livna (ntfs, nvidia, etc) . These of course have to be rebuilt or reinstalled for a new kernel. Sometimes I update my kernel before Livna gets the rpms rebuilt, so it can be easier to just rebuild the src.rpm. However, it would be really convenient to be able to rebuild the src.rpms before rebooting to the new kernel, so everything just works. So, now to my question: is it possible to rebuild a kernel driver src.rpm for a non-running kernel? Is there a standard way to do it? I tried doing this with the nvidia driver for FC5T3 once with very poor results. I had to go hack into the spec file to change the way it got the kernel version (it used some self-contained script to get the kernel version (or versions)). Not at all an ideal way to do it. It would be really nice to just pass in a KVER=2.6.16-1.2069_FC4 or something with the rpmbuild --rebuild command. Jonathan

2 3

← Newer
1
...
6
7
8
9
10
11
12
...
145
Older →

Jump to page: