Hard disk error
Hi, I have a SEAGATE 500G HD.I got the following errors in dmesg when I connect it thro' USB to fedora 10. Anyone can tell me what is the error means? Any chance to get back the data from this HD, how? ango May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Add. Sense: No additional sense information May 15 00:29:42 localhost kernel: usb 1-6: USB disconnect, address 5 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: Dev sdd: unable to read RDB block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 15 00:29:42 localhost kernel: end_request: I/O error, dev sdd, sector 0 May 15 00:29:42 localhost kernel: Buffer I/O error on device sdd, logical block 0 May 15 00:29:42 localhost kernel: unable to read partition table May 15 00:29:42 localhost kernel: sd 5:0:0:0: [sdd] Attached SCSI disk May 15 00:29:42 localhost kernel: sd 5:0:0:0: Attached scsi generic sg5 type 0 ^C -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hard disk error
Below is my comment. Thanks. On Fri, May 15, 2009 at 11:23 AM, g gel...@bellsouth.net wrote: Rilawich Ango wrote: I have a SEAGATE 500G HD. is this a new drive? It is not a new drive. It uses for 1 year. have you check seagate site for problems with these drives? There is no info about this drive in the web. have you tried connecting internally to see if a usb problem? When I connect it internally, the BIOS can't detect it. have you tried different drive in usb housing to see if a usb problem? USB housing works fine as I can use it in different drives. have you dropped, knocked, or banged drive that might have caused problems? No. Actually, the drive used without problem almost for one year. A week ago, I found PC can't be booted up as it can't detect the drive. So I use USB to see what's wrong. According to the message, I am not sure whether it is a drive physical problem. I just want to get back the data from the drive. Any data recovery tools available in Linux to recover data from a crash drive? have you opened case and insured that connections a good? Connection is ok. have you tried on another computer? Yes. Result is the same. Anyone can tell me what is the error means? fedora can see there is a hard drive there, but can not see drive's disk. Any chance to get back the data from this HD, how? depends on answers to above questions. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: server hanged per hour
Two issues that I would look at. 1. How far out is your time? Manually synchronize your time to see if the realtime clock is causing the issue. If you can turn the server off and see how accurate the time stays without power. May only require a new battery on the motherboard. Also turn off automatic time update and see if the reboots stop. I have already stop ntpd in the system but abnormal hourly reboot still here. 2. Check each application in cron.hourly and see if one of them is crashing our system. I am sure there is no process in cron.hourly. Finally, I still suspect there is a hardware problem or kernel problem. How can I determine the source of the problem in the message? -- Robin Laing -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
server hanged per hour
Recently, I find that the server FC8 installed is very unstable. It always restart itself per every hour. Below is the message. From internal, some ppl say it is a kernel bug. I am not quite sure. Anyone can tell me what the problem is? Jun 11 22:38:41 risegame ntpd[1711]: kernel time sync status change 0001 Jun 11 23:33:08 risegame rsyslogd: [origin software=rsyslogd swVersion=1.19.10 x-pid=1622][x-configInfo udpReception=No udpPort=514 tcpReception=No tcpPort=0] restart Jun 11 23:42:15 risegame ntpd[1695]: synchronized to 210.0.235.14, stratum 2 Jun 12 00:33:27 risegame rsyslogd: [origin software=rsyslogd swVersion=1.19.10 x-pid=1640][x-configInfo udpReception=No udpPort=514 tcpReception=No tcpPort=0] restart Jun 12 00:33:27 risegame kernel: rklogd 1.19.10, log source = /proc/kmsg started. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: server hanged per hour
The hourly reboot is abnormal. I have no rebooting job in /etc/cron.hourly. The reboot seems caused by something (hardward, kernel) that I don't know. The server runs for several months without problem. Hourly reboot is found this week but it keeps rebooting. We have hard reset the server but reboot still alive. Below is the complete log message when it rebooted. You can see 09:36:07 the server rebooted itself. Next reboot will be 10:3x. Anyone can help to find out what problem it is? Fedora 8 kernel: 2.6.23.1-49.fc8 Intel(R) Core(TM)2 Duo CPU E4500 @2.20GHz Jun 12 08:35:51 localhost ntpd[1710]: frequency initialized 148.719 PPM from /var/lib/ntp/drift Jun 12 08:36:19 localhost gpm[1841]: *** info [startup.c(95)]: Jun 12 08:36:19 localhost gpm[1841]: Started gpm successfully. Entered daemon mode. Jun 12 08:36:23 localhost acpid: client connected from 2002[68:68] Jun 12 08:36:24 localhost kernel: Zaptel Transcoder support loaded Jun 12 08:40:36 localhost ntpd[1710]: synchronized to 203.129.68.14, stratum 2 Jun 12 08:40:37 localhost ntpd[1710]: time reset +0.143514 s Jun 12 08:40:37 localhost ntpd[1710]: kernel time sync status change 0001 Jun 12 08:45:36 localhost ntpd[1710]: synchronized to 203.129.68.14, stratum 2 Jun 12 09:28:06 localhost ntpd[1710]: ntpd exiting on signal 15 Jun 12 09:36:07 localhost rsyslogd: [origin software=rsyslogd swVersion=1.19.10 x-pid=1637][x-configInfo udpReception=No udpPort=514 tcpReception=No tcpPort=0] restart Jun 12 09:36:07 localhost kernel: rklogd 1.19.10, log source = /proc/kmsg started. Jun 12 09:36:07 localhost kernel: Linux version 2.6.23.1-49.fc8 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu Nov 8 21:41:26 EST 2007 Jun 12 09:36:07 localhost kernel: BIOS-provided physical RAM map: Jun 12 09:36:07 localhost kernel: BIOS-e820: - 0009ec00 (usable) Jun 12 09:36:07 localhost kernel: BIOS-e820: 0009ec00 - 000a (reserved) Jun 12 09:36:07 localhost kernel: BIOS-e820: 000e - 0010 (reserved) Jun 12 09:36:07 localhost kernel: BIOS-e820: 0010 - 3ec2 (usable) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3ec2 - 3ec22000 (reserved) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3ec22000 - 3ed1e000 (usable) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3ed1e000 - 3edea000 (ACPI NVS) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3edea000 - 3edee000 (usable) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3edee000 - 3edf3000 (ACPI data) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3edf3000 - 3edf4000 (usable) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3edf4000 - 3edff000 (ACPI data) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3edff000 - 3ee0 (usable) Jun 12 09:36:07 localhost kernel: BIOS-e820: 3ee0 - 3f80 (reserved) Jun 12 09:36:07 localhost kernel: BIOS-e820: f000 - f800 (reserved) Jun 12 09:36:07 localhost kernel: BIOS-e820: fff0 - 0001 (reserved) Jun 12 09:36:07 localhost kernel: 110MB HIGHMEM available. Jun 12 09:36:07 localhost kernel: 896MB LOWMEM available. Jun 12 09:36:07 localhost kernel: found SMP MP-table at 000fe200 Jun 12 09:36:07 localhost kernel: Using x86 segment limits to approximate NX protection Jun 12 09:36:07 localhost kernel: Zone PFN ranges: Jun 12 09:36:07 localhost kernel: DMA 0 - 4096 Jun 12 09:36:07 localhost kernel: Normal 4096 - 229376 Jun 12 09:36:07 localhost kernel: HighMem229376 - 257536 Jun 12 09:36:07 localhost kernel: Movable zone start PFN for each node Jun 12 09:36:07 localhost kernel: early_node_map[1] active PFN ranges Jun 12 09:36:07 localhost kernel: 0:0 - 257536 Jun 12 09:36:07 localhost kernel: DMI 2.4 present. Jun 12 09:36:07 localhost kernel: Using APIC driver default Jun 12 09:36:07 localhost kernel: ACPI: RSDP 000FE020, 0014 (r0 INTEL ) Jun 12 09:36:07 localhost kernel: ACPI: RSDT 3EDFD038, 004C (r1 INTEL DG33FB D8 113) Jun 12 09:36:07 localhost kernel: ACPI: FACP 3EDFC000, 0074 (r1 INTEL DG33FB D8 MSFT 113) Jun 12 09:36:07 localhost kernel: ACPI: DSDT 3EDF8000, 3C7D (r1 INTEL DG33FB D8 MSFT 113) Jun 12 09:36:07 localhost kernel: ACPI: FACS 3ED9E000, 0040 Jun 12 09:36:07 localhost kernel: ACPI: APIC 3EDF7000, 0078 (r1 INTEL DG33FB D8 MSFT 113) Jun 12 09:36:07 localhost kernel: ACPI: WDDT 3EDF6000, 0040 (r1 INTEL DG33FB D8 MSFT 113) Jun 12 09:36:07 localhost kernel: ACPI: MCFG 3EDF5000, 003C (r1 INTEL DG33FB D8 MSFT 113) Jun 12 09:36:07 localhost kernel: ACPI: ASF! 3EDF4000, 00A6 (r32 INTEL DG33FB D8 MSFT 113) Jun 12 09:36:07 localhost kernel: ACPI: SSDT 3EDF2000, 01B4 (r1 INTEL CpuPm D8 MSFT 113) Jun 12 09:36:07 localhost kernel:
