Metadata File
by Leon Vergottini
Hi
I am having problems updating FC9. I receive the following error message
when it comes to the updates-newkey repo:
[Errno -1] Metadata file does not match checksum
This message comes back from all mirror sites. This is now happening for the
last week and a half. What can I do to fix this.
Regards
Leon
12 years, 3 months
eSATA drive won't mount. Wrong data rate ?
by linux guy
Some of this was previously discussed in the "External eSATA drive
doesn't fdisk properly ? F8 eSATA hotplug ?" thread.
Computer: HP hdx9494. T8100 processor, 4 GB RAM, running 32 bit Fedora
8.
Drive: Azio SATA/USB enclosure, Hitachi 500GB 3.5" hard drive. The
drive works excellent under USB access.
$ uname -a
Linux localhost.localdomain 2.6.26.5-28.fc8 #1 SMP Sat Sep 20 09:32:58
EDT 2008 i686 i686 i386 GNU/Linux
If I shut the machine off, power up the external drive and then boot the
computer, I get the following in /var/logs/messages:
Oct 2 11:10:37 localhost kernel: sdb: sdb1
Oct 2 11:10:37 localhost kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Oct 2 11:10:37 localhost kernel: ACPI: PCI Interrupt 0000:20:00.0[A] ->
GSI 19 (level, low) -> IRQ 19
Oct 2 11:10:37 localhost kernel: scsi3 : sata_sil24
Oct 2 11:10:37 localhost kernel: ata4: SATA max UDMA/100 host
m128@0xe0100000 port 0xe0102000 irq 19
Oct 2 11:10:37 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct 2 11:10:37 localhost kernel: ata4.00: ATA-8: Hitachi
HDP725050GLA360, GM4OA52A, max UDMA/133
Oct 2 11:10:37 localhost kernel: ata4.00: 976773168 sectors, multi 0:
LBA48 NCQ (depth 31/32)
Oct 2 11:10:37 localhost kernel: ata4.00: configured for UDMA/100
Oct 2 11:10:37 localhost kernel: scsi 3:0:0:0: Direct-Access ATA
Hitachi HDP72505 GM4O PQ: 0 ANSI: 5
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] 976773168 512-byte
hardware sectors (500108 MB)
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write Protect is off
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] 976773168 512-byte
hardware sectors (500108 MB)
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write Protect is off
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Oct 2 11:10:37 localhost kernel: sdc: sdc1
Oct 2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
Oct 2 11:10:37 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] ->
GSI 16 (level, low) -> IRQ 16
Oct 2 11:10:37 localhost kernel: scsi4 : ata_piix
Oct 2 11:10:37 localhost kernel: scsi5 : ata_piix
Oct 2 11:10:37 localhost kernel: ata5: PATA max UDMA/100 cmd 0x1f0 ctl
0x3f6 bmdma 0x70a0 irq 14
Oct 2 11:10:37 localhost kernel: ata6: PATA max UDMA/100 cmd 0x170 ctl
0x376 bmdma 0x70a8 irq 15
Oct 2 11:10:37 localhost kernel: ata5.00: ATAPI: Optiarc BD ROM
BC-5500A, 1.86, max MWDMA2
If I run hwbrowser and look at it, it shows the drive under sdc with the
correct geometry and such, but without a partition, ie no sdc1 or file
sizes.
So it appears to be recognized by the computer on some level.
However, if I mount it with "mount /dev/sdc1 temp" or "mount
-text3 /dev/sdc1 temp", the console will hang for a minute or so before
returning without any errors. However, the drive is unusable (ls
returns an empty directory) and /var/logs/messages shows the following:
Oct 2 11:16:49 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct 2 11:16:49 localhost kernel: ata4.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Oct 2 11:16:49 localhost kernel: ata4.00: revalidation failed
(errno=-5)
Oct 2 11:16:49 localhost kernel: ata4: failed to recover some devices,
retrying in 5 secs
Oct 2 11:16:54 localhost kernel: ata4: hard resetting link
Oct 2 11:16:56 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct 2 11:17:26 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct 2 11:17:26 localhost kernel: ata4.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Oct 2 11:17:26 localhost kernel: ata4.00: revalidation failed
(errno=-5)
Oct 2 11:17:26 localhost kernel: ata4: failed to recover some devices,
retrying in 5 secs
Oct 2 11:17:31 localhost kernel: ata4: hard resetting link
Oct 2 11:17:33 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct 2 11:18:03 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct 2 11:18:03 localhost kernel: ata4.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Oct 2 11:18:03 localhost kernel: ata4.00: revalidation failed
(errno=-5)
Oct 2 11:18:03 localhost kernel: ata4.00: disabled
Oct 2 11:18:04 localhost kernel: ata4: hard resetting link
Oct 2 11:18:06 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct 2 11:18:06 localhost kernel: ata4: EH complete
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 976767935
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383936
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383937
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383938
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383939
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 976767935
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383936
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 976767937
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383937
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383938
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383939
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 63
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 0
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct 2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 1
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 63
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct 2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct 2 11:18:06 localhost kernel: hfs: unable to find HFS+ superblock
Oct 2 11:23:03 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct 2 11:23:03 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct 2 11:23:03 localhost kernel: EXT3-fs: unable to read superblock
One thing that sticks out for me in all this is the SATA data rate.
Both the computer and the drive are supposed to be 3.0Gb/s devices. Yet
the driver wants to connect at 1.5 Gbps.
The Serial ATA Controller is listed as ahci in hwbrowser.
# /sbin/lsmod | grep sat
sata_sil24 16069 0
libata 131937 3 ata_piix,sata_sil24,ahci
How should I proceed to get my external drive working ?
Thanks
12 years, 3 months
Nvidia drivers, screen redraws
by Reid Rivenburgh
The combination of Gnome and fvwm has been working well for me (though
it ain't easy to configure!). I used kde for several years, though,
so I thought I'd check out the latest (F9, 4.1.1). It definitely
seems better than the early 4.0 releases in terms of polish and
goodies, but one thing I noticed is that switching desktops is
relatively slow. If it's a desktop with firefox on it, it'll take 3-4
seconds to redraw the firefox window. With fvwm, it's less than a
second. Turning off the nifty desktop effects helps some. Now, I
also tried switching to the nvidia driver from livna at the same time,
so that could be a factor, though it is still fast with nvidia drivers
and fvwm. I admit I haven't tried the combo of xorg driver and kde.
Seems like I've seen some web page glitchiness when scrolling, too.
Just curious if anyone has any comments on this behavior. (At this
point, though, I'm happy to go back to fvwm/gnome, what with the
little issues and feeling like it'd be quite a bit of work to set
things up the way I like them.)
The computer is about six months old: core duo 8400, 4 GB memory,
GeForce 8600 GTS, 64-bit packages.
Thanks,
reid
12 years, 3 months
display hw info from command line
by Mark Haney
I know there are several semi-related tools for displaying hardware
installed in a system, and I can use all those if I must. But what I"m
interested in is any new tools that can compile and display the hardware
installed in a server or export it to a text file in an easy to read format.
I've been looking at sysinfo, hwinfo and others, but most of those seem
dead development wise. So are there any recent ones I"ve missed?
--
Libenter homines id quod volunt credunt -- Caius Julius Caesar
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
12 years, 3 months
Boot hangs on modprobe errors
by Laura Speck
Hi all,
I have a fresh install of Fedora 9 on a Dell poweredge 2650. Install
went fine, no errors or warnings. Rebooted it, and it hangs after:
serial 00:06: unable to assign resources
Red Hat nash version 6.0.52 starting
INFO: task modprobe:<number here that I cannot remember> blocked for
more than 120 seconds
"echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
INFO: task scsi_scan_0:449 blocked for more than 120 seconds
"echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
We used 32bit fedora 9 to install onto a 3 dish scsi raid5. I am not
sure if this machine is 32bit or 64bit, but I figured 32bit fedora
should work on both?
Rebooted again, and now it's not doing anything. It gave the error
about the serial, then started nash up, but now nothing. And it's been
a half hour.
I am completely clueless right about now and any help would be greatly
appreciated, even a point in the right direction :)
--
Laura Speck
12 years, 3 months
Rawhide installation question.
by Erik P. Olsen
I have tried to install rawhide via anaconda. As mentioned in the docs I
downloaded images/boot.iso and burned it to a dvd but it turned out that the dvd
did not have a boot record. Is it missing or have I misunderstood what I should do?
--
Erik.
12 years, 3 months
install the Korn SHELL program
by 최용주
Dear.
I installed the ksh program using yum.
>yum install ksh
Then executed the program as I made for test, but error echoed,
>./filter
Bash : ./filter:/bin/ksh^M: bad interpreter: No such file or directory
What is the problem?
Thank you
Yongjoo CHOI
12 years, 3 months
Re: [OT] CentOS 3rd party repositories?
by Vandaman
> Just to note, so far I have enabled the default base, extras, updates
> repositories from CentOS, and in addition the Dag repository for RHEL5 and
> adobe repository for flash.
> Excuse me again for not going to CentOS list for this, it seems obvious that a
> lot of people here use CentOS as well, so... ;-)
You are running an enterprise server and getting support for it from a cutting
edge mailing list because of laziness/pride or both? Read up the Wikis on
CentOS and see how to get community support "properly".
Regards,
Vandaman.
12 years, 3 months
Watchdog, and supporting programs
by Seann Clark
All,
I have been playing with watchdog on my systems in the past few
months. One Fedora 8 older Tyan board with hardware watchdog, and one
new Fedora 9 Asus server board with hard ware watchdog. While using this
in its normal configuration everything works fine, and stable. I have
run into one problem with it. While over using my new server for I/O
intensive activities, I launched the load to 27 (one minute load
average) which triggered the default software watchdogs limit of 24 max
1 minute load average. It did what it was supposed to, and rebooted the
system. Tweaking problems remain on this box and I need to set it up to
live through a full reboot (it fails a check during boot and reboots the
box half way through a box, which is a glaring personal error in
configuration).
The other system I have is rather stable and has no problems with
the watchdog and it runs as I require it. What I am after from the group
with this is what repair style programs are being used, and examples of
such, if anyone is using this. I am working on writing my own, but I am
not sure where I want to go, and am looking for good idea's and gotcha's
on this as well.
Thanks in advance,
Seann
12 years, 3 months
