Re: hard error reading: set fstab mounts to frw: can no longer access filesystem
I am using FreeBSD-4.10, how do I boot it in single user mode? -Ed On 3/21/06, Derek Ragona [EMAIL PROTECTED] wrote: Edwin, Boot the server single user, -s. Then if you need to, bring up the IP stack manually. Depending on your mount points, booting single user only mounts root, so you can try to fsck the other unmounted filesystems. Only if those file systems are readable will you be able to get your files off. You can also try tar'ing files to floppy or other removeable drive you may have on the server. Not a great solution, but it may be all you can do. -Derek At 08:12 PM 3/20/2006, Edwin D. Vinas wrote: Hi, After a power outage my FreeBSD-4.10 server's 40GB HDD had many fragmentations and no matter how I repeatedly do fsck, the errors saying hard error reading fsbn are still there. I tried doing fsck over and over but it seems this is already a hardware error and can no longer be corrected. So my goal now is to recover my files! First, I did a mount -a and was able to copy some of important files but I have more data which I need to backup which I thought would only be possible if I can make the server boot and make it work at least with TCP/IP so I can transfer data to the other PCs in the LAN. But, after mount -a, I edited the fstab to set mounts to frw to force mount all drives and not give me those hard error reading fsbn. So, I rebooted the machine, only to find out that after it mounted all partitions the the /usr/libexec/getty something can't be found or executed for ttys and its giving me unending errors. And there it goes, I can no longer access my filesystem because it hangs or doesn't have a terminal when the machine is about to finish booting. There is no prompt anymore, all I can see are the getty errors. If only I can edit fstab back without f option, I can still manually copy my files to a USB. Is there anyway to still recover my files? Is there a way I can edit fstab to remove f option so I can't have those getty errors? Or is it possible to mount the server's HDD in another FreeBSD machine? Thanks. Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- -- Edwin D. Viñas http://www.wisoy.com http://www.geocities.com/edwin_vinas/ IN THE WORLD OF SCIENCE, NOTHING IS IMPOSSIBLE. -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hard error reading: set fstab mounts to frw: can no longer access filesystem
Edwin, Boot the server single user, -s. Then if you need to, bring up the IP stack manually. Depending on your mount points, booting single user only mounts root, so you can try to fsck the other unmounted filesystems. Only if those file systems are readable will you be able to get your files off. You can also try tar'ing files to floppy or other removeable drive you may have on the server. Not a great solution, but it may be all you can do. -Derek At 08:12 PM 3/20/2006, Edwin D. Vinas wrote: Hi, After a power outage my FreeBSD-4.10 server's 40GB HDD had many fragmentations and no matter how I repeatedly do fsck, the errors saying hard error reading fsbn are still there. I tried doing fsck over and over but it seems this is already a hardware error and can no longer be corrected. So my goal now is to recover my files! First, I did a mount -a and was able to copy some of important files but I have more data which I need to backup which I thought would only be possible if I can make the server boot and make it work at least with TCP/IP so I can transfer data to the other PCs in the LAN. But, after mount -a, I edited the fstab to set mounts to frw to force mount all drives and not give me those hard error reading fsbn. So, I rebooted the machine, only to find out that after it mounted all partitions the the /usr/libexec/getty something can't be found or executed for ttys and its giving me unending errors. And there it goes, I can no longer access my filesystem because it hangs or doesn't have a terminal when the machine is about to finish booting. There is no prompt anymore, all I can see are the getty errors. If only I can edit fstab back without f option, I can still manually copy my files to a USB. Is there anyway to still recover my files? Is there a way I can edit fstab to remove f option so I can't have those getty errors? Or is it possible to mount the server's HDD in another FreeBSD machine? Thanks. Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
hard error reading: set fstab mounts to frw: can no longer access filesystem
Hi, After a power outage my FreeBSD-4.10 server's 40GB HDD had many fragmentations and no matter how I repeatedly do fsck, the errors saying hard error reading fsbn are still there. I tried doing fsck over and over but it seems this is already a hardware error and can no longer be corrected. So my goal now is to recover my files! First, I did a mount -a and was able to copy some of important files but I have more data which I need to backup which I thought would only be possible if I can make the server boot and make it work at least with TCP/IP so I can transfer data to the other PCs in the LAN. But, after mount -a, I edited the fstab to set mounts to frw to force mount all drives and not give me those hard error reading fsbn. So, I rebooted the machine, only to find out that after it mounted all partitions the the /usr/libexec/getty something can't be found or executed for ttys and its giving me unending errors. And there it goes, I can no longer access my filesystem because it hangs or doesn't have a terminal when the machine is about to finish booting. There is no prompt anymore, all I can see are the getty errors. If only I can edit fstab back without f option, I can still manually copy my files to a USB. Is there anyway to still recover my files? Is there a way I can edit fstab to remove f option so I can't have those getty errors? Or is it possible to mount the server's HDD in another FreeBSD machine? Thanks. Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hard error reading: set fstab mounts to frw: can no longer access filesystem
On 3/20/06, Edwin D. Vinas [EMAIL PROTECTED] wrote: Is there anyway to still recover my files? Is there a way I can edit fstab to remove f option so I can't have those getty errors? Or is it possible to mount the server's HDD in another FreeBSD machine? Can't you boot from a FreeBSD CD then mount the bad HD and recover your data? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
server crash: ad0: hard error cmd
Hi Guys, I have a SOHO file server that's become rather grumpy during a move [office to office] it's a 5.1 system with 4 x Western Digital [WD800] hard drives [non RAID] and it's giving me this error: ad0: hard error cmd=read fsbn 86662543 of 86662574 status=51 error =40 Jan 17 18:00:00 init can't exec getty 'usr/libexec/getty' for port /dev/ttyv5: Input/output error the machine has experienced some hard resets over the last month due to the monsoon season here in the tropics! what is a quick work-around? is the drive dead? any suggestions? /carmoda ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk problems - hard error reading fsbn NNNNNNNN (Bullet dodged)
Matt Navarre wrote: After a power outage last night I rebooted my computer and fsck complained of the following : ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn 177 sn 20) status=59 error=40 Then goes on for a while giving the same error on blocks 5103776 - 5103807, except for block 5103777 which has error=01. Does this mean the disk is failing, or can I just reformat? And what's the best way to recover any recoverable data from that slice? Unfortunately I don't have a recent backup, since my tape drive joined the choir invisible a while ago and I haven't had a chance to replace it. I seem to have recovered all the data from the failing disk, just for posterity here's what worked for me. First you need two things: A new hard disk and a FreeSBIE CD. Install the new harddisk and boot from the FreeSBIE cd. Then you need to make a filesystem on the new disk (see the Handbook for the Magic Spells, there's no /stand/sysinstall on the FreeSBIE cd). Mount the new disk. If your damaged drive has data on other slices that don't have errors mount them and recover the data. I used cd /mnt/ufs.2; find ./ -xdev -print0 | cpio -pa0V /mnt/ufs.1/gooddata. Now, on to the damaged sectors, how to recover the data? dd stops when it hits bad blocks, so we can't use that to copy the slice. same with dump(8) as far as I can tell. So. Download dd_rescue from http://www.garlof.de/kurt/linux/ddrescue/ Version 1.10 compiled and worked out of the box. No need to install it, just run it from the build folder: ./dd_rescue /dev/ad1s2e /mnt/ufs.1/ad1s2e.img Wait. a long time. keep in mind that the slice you are writing to needs to be big enough to hold an image of the *entire* slice you are copying. once dd_rescue finishes we're left with a (hopefully) usable image of the bad slice. Now we need to use it. see the handbook entry on Network, Memory and File-Backed File systems: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-virtual.html Here's the basic quick and dirty: mdonfig -a -t vnode -f /mnt/ufs.1/ad1s2e.img -u 6 #change 6 to an unused /mnt/md#, freesbie mounts it's filesystems on md[0-5] on my cd. fsck_ffs /dev/md6 mount /dev/md6 /mnt/ufs.3 Now you should be able to get the data off the image and on to a real filesystem. You can check your data with ls -lR ls.out on the image and the directory where your now hopefully rescued data is and diffing the output. I saw differences in dates on directories, so if that's a concern there's probably a better way to move the data than find/cpio. Now I need to come up with a real backup scheme. This one has proved suboptimal. Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk problems - hard error reading fsbn NNNNNNNN (Bullet dodged)
Matt Navarre [EMAIL PROTECTED] writes: Now, on to the damaged sectors, how to recover the data? dd stops when it hits bad blocks, so we can't use that to copy the slice. same with dump(8) as far as I can tell. So. Download dd_rescue from http://www.garlof.de/kurt/linux/ddrescue/ Just out of interest: how is that different than dd conv=noerror? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk problems - hard error reading fsbn NNNNNNNN (Bullet dodged)
Matt Navarre wrote: Matt Navarre wrote: After a power outage last night I rebooted my computer and fsck complained of the following : ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn 177 sn 20) status=59 error=40 Then goes on for a while giving the same error on blocks 5103776 - 5103807, except for block 5103777 which has error=01. Does this mean the disk is failing, or can I just reformat? And what's the best way to recover any recoverable data from that slice? Unfortunately I don't have a recent backup, since my tape drive joined the choir invisible a while ago and I haven't had a chance to replace it. I seem to have recovered all the data from the failing disk, just for posterity here's what worked for me. First you need two things: A new hard disk and a FreeSBIE CD. Install the new harddisk and boot from the FreeSBIE cd. Then you need to make a filesystem on the new disk (see the Handbook for the Magic Spells, there's no /stand/sysinstall on the FreeSBIE cd). Mount the new disk. If your damaged drive has data on other slices that don't have errors mount them and recover the data. I used cd /mnt/ufs.2; find ./ -xdev -print0 | cpio -pa0V /mnt/ufs.1/gooddata. Now, on to the damaged sectors, how to recover the data? dd stops when it hits bad blocks, so we can't use that to copy the slice. same with dump(8) as far as I can tell. So. Download dd_rescue from http://www.garlof.de/kurt/linux/ddrescue/ Version 1.10 compiled and worked out of the box. No need to install it, just run it from the build folder: ./dd_rescue /dev/ad1s2e /mnt/ufs.1/ad1s2e.img Wait. a long time. keep in mind that the slice you are writing to needs to be big enough to hold an image of the *entire* slice you are copying. once dd_rescue finishes we're left with a (hopefully) usable image of the bad slice. Now we need to use it. see the handbook entry on Network, Memory and File-Backed File systems: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-virtual.html Here's the basic quick and dirty: mdonfig -a -t vnode -f /mnt/ufs.1/ad1s2e.img -u 6 #change 6 to an unused /mnt/md#, freesbie mounts it's filesystems on md[0-5] on my cd. fsck_ffs /dev/md6 mount /dev/md6 /mnt/ufs.3 Now you should be able to get the data off the image and on to a real filesystem. You can check your data with ls -lR ls.out on the image and the directory where your now hopefully rescued data is and diffing the output. I saw differences in dates on directories, so if that's a concern there's probably a better way to move the data than find/cpio. Now I need to come up with a real backup scheme. This one has proved suboptimal. I forgot: Keep in mind that FreeBSD 5.x defaults to UFS2 and the downloadable FreeSBIE isos are 5.x. If your existing system is 4.X you won't be able to read the drive unless you give newfs(8) the -O 1 flag. Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk problems - hard error reading fsbn NNNNNNNN (Bullet dodged)
Lowell Gilbert wrote: Matt Navarre [EMAIL PROTECTED] writes: Now, on to the damaged sectors, how to recover the data? dd stops when it hits bad blocks, so we can't use that to copy the slice. same with dump(8) as far as I can tell. So. Download dd_rescue from http://www.garlof.de/kurt/linux/ddrescue/ Just out of interest: how is that different than dd conv=noerror? Huh, you learn something new every day. Actually dd_rescue looks closer to dd conv=noerror,sync since it replaces input errors with NULs. Anyway dd_rescue worked for me, tho I suspect that dd would have worked also, if I'd read the manpage closer. But, hey, Bad Disk + No Backups = Major Freakout Mode. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk problems - hard error reading fsbn NNNNNNNN
After a power outage last night I rebooted my computer and fsck complained of the following : ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn 177 sn 20) status=59 error=40 Then goes on for a while giving the same error on blocks 5103776 - 5103807, except for block 5103777 which has error=01. Does this mean the disk is failing, or can I just reformat? And what's the best way to recover any recoverable data from that slice? Unfortunately I don't have a recent backup, since my tape drive joined the choir invisible a while ago and I haven't had a chance to replace it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk problems - hard error reading fsbn NNNNNNNN
orville weyrich wrote: Before doing anything to your hard drive, check out your computer's power supply -- if they go off tolerance on voltages, you may start getting disk errors -- often the first sign of power supply problems. Hmmm, Ok, I can see that. The errors are confined to one slice on the disk (ad1s2e) the other slice fsck'd fine. so I should be able to recover that data using a FreeSBIE cd and writing to a new drive. The damaged partition I can *hopefully* recover using dd_recover. Once I do that I'll try the drive in another computer and see if the problem's still there. we'll see. The power surge may have damaged your power supply. orville. --- Matt Navarre [EMAIL PROTECTED] wrote: After a power outage last night I rebooted my computer and fsck complained of the following : ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn 177 sn 20) status=59 error=40 Then goes on for a while giving the same error on blocks 5103776 - 5103807, except for block 5103777 which has error=01. Does this mean the disk is failing, or can I just reformat? And what's the best way to recover any recoverable data from that slice? Unfortunately I don't have a recent backup, since my tape drive joined the choir invisible a while ago and I haven't had a chance to replace it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
You could try using SpinRite. http://www.grc.com It now works with all filesystems and is up to version 6. Mark --- Tuc [EMAIL PROTECTED] wrote: Problem is, unless it fails the Dell Power on IDE test, they won't replace it. :-/ Guess I just keep backing it up until it fails totally. Get a Dell diagnostic disk for your system, and run the hard drive test. It ought to see the problems, which you can then report back to Dell in order to get them to do something. Sorry, I should have mentioned I used the BIOS based disk check and it passed. Maybe I do need to go to the more extensive one. Thanks, Tuc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
Tuc wrote: [ ...and SMART status... ] So is there something I should do? Get a new hard drive, this one is not going to live much longer. Problem is, unless it fails the Dell Power on IDE test, they won't replace it. :-/ Guess I just keep backing it up until it fails totally. Get a Dell diagnostic disk for your system, and run the hard drive test. It ought to see the problems, which you can then report back to Dell in order to get them to do something. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
Problem is, unless it fails the Dell Power on IDE test, they won't replace it. :-/ Guess I just keep backing it up until it fails totally. Get a Dell diagnostic disk for your system, and run the hard drive test. It ought to see the problems, which you can then report back to Dell in order to get them to do something. Sorry, I should have mentioned I used the BIOS based disk check and it passed. Maybe I do need to go to the more extensive one. Thanks, Tuc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
IDE drive - hard error reading fsbn... - recoverable?
4.9-RELEASE-p11 system. Experimenting with cdda2wav this morning, I managed to get my system into a completely non-responsive state- no keyboard, mouse, or console activity; the machine responded to about 20% of ping packets, with many-second delays; attempts to ssh into the box failed. So I power-cycled the machine. After an apparently normal reboot, I noticed I could no longer access certain files: dcf$ ls .mozilla/firefox/dcf/bookmarks.html ls: .mozilla/firefox/dcf/bookmarks.html: Input/output error and these errors were accompanied by kernel warnings: Oct 23 16:58:12 grond /kernel: ad0s1e: hard error reading fsbn 29926527 of 9843232-9843263 (ad0s1 bn 29926527; cn 1862 tn 214 sn 15) status=59 error=40 Other files in /home/dcf were affected, also - many seemed to be related to firefox, which had been running when the system froze/was rebooted. I dropped to single user mode and started fsck - and got the following: ** /dev/ad0s1e ** Last Mounted on /home ** Phase 1 - Check Blocks and Sizes CONTINUE? [yn] THE FOLLOWING DISK SECTORS COULD NOT BE READ: 9843232, 9843233, 9843234, 9843235, 9843236, 9843237, 9843238, 9843239, 9843240, 9843241, 9843242, 9843243, 9843244, 9843245, 9843246, 9843247, 9843248, 9843249, 9843250, 9843251, 9843252, 9843253, 9843254, 9843255, 9843256, 9843257, 9843258, 9843259, 9843260, 9843261, 9843262, 9843263, 9843264, 9843265, 9843266, 9843267, 9843268, 9843269, 9843270, 9843271, 9843272, 9843273, 9843274, 9843275, 9843276, 9843277, 9843278, 9843279, 9843280, 9843281, 9843282, 9843283, 9843284, 9843285, 9843286, 9843287, 9843288, 9843289, 9843290, 9843291, 9843292, 9843293, 9843294, 9843295, CONTINUE? [yn] ...many, many times, interspersed with as many kernel errors: ad0s1e: hard error reading fsbn 9843238 (ad0s1 bn 9843238; cn 612 tn 181 sn 55) status=59 error=40 ad0s1e: hard error reading fsbn 9843239 (ad0s1 bn 9843239; cn 612 tn 181 sn 56) status=59 error=40 ad0s1e: hard error reading fsbn 9843240 (ad0s1 bn 9843240; cn 612 tn 181 sn 57) status=59 error=40 ad0s1e: hard error reading fsbn 9843241 (ad0s1 bn 9843241; cn 612 tn 181 sn 58) status=59 error=40 ad0s1e: hard error reading fsbn 9843242 (ad0s1 bn 9843242; cn 612 tn 181 sn 59) status=59 error=40 ad0s1e: hard error reading fsbn 9843243 (ad0s1 bn 9843243; cn 612 tn 181 sn 60) status=59 error=40 ...etc. So I figure somehow I suffered hard drive damage in the system freeze or my reboot. My questions, now, are: Is this likely a one-time thing, or a symptom of creeping disk death? (The 'hard error' messages only started after the reboot.) If it's one-time, is the disk still usable? Can I flag the affected sectors as bad, and work around them? How can I best determine the extent of the damage? I'd rather not do a manual fsck for a whole afternoon if I can help it. How best can I recover from the damage? Many of the affected files appear to be in my home directory. Can I just blow away the entire /home/dcf and restore from backup (I think I have those...)? Thanks in advance for any advice you might have - -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote: Oct 23 16:58:12 grond /kernel: ad0s1e: hard error reading fsbn 29926527 of 9843232-9843263 (ad0s1 bn 29926527; cn 1862 tn 214 sn 15) status=59 error=40 Is this likely a one-time thing, or a symptom of creeping disk death? (The 'hard error' messages only started after the reboot.) You could try /usr/ports/sysutils/smartmontools to run S.M.A.R.T. selftests on the drive. Try things like this: ### Test 1: # smartctl -a ad0 | more ### Test 2: # smartctl -t offline ad0 then wait for offline selftests to complete, then again: # smartctl -a ad0 | more ### Test 3: # smartctl -t long ad0 again wait for selfttests to complete, then again: # smartctl -a ad0 | more Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
On Sun, 24 Oct 2004 [EMAIL PROTECTED] wrote: On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote: Is this likely a one-time thing, or a symptom of creeping disk death? (The 'hard error' messages only started after the reboot.) You could try /usr/ports/sysutils/smartmontools to run S.M.A.R.T. selftests on the drive. Thanks - unfortunately, that port is marked IGNORE for my version (4.9). Apparently I need 'ATAng', not sure if I can get that in the 4.x series... I suppose I could try moving to 5.2.x, but I was hoping to put that off a little longer - and I'd like to know my hardware is reliable first, really. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
On Sat, Oct 23, 2004 at 07:18:29PM -0500, David Fleck wrote: On Sun, 24 Oct 2004 [EMAIL PROTECTED] wrote: On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote: Is this likely a one-time thing, or a symptom of creeping disk death? (The 'hard error' messages only started after the reboot.) You could try /usr/ports/sysutils/smartmontools to run S.M.A.R.T. selftests on the drive. Thanks - unfortunately, that port is marked IGNORE for my version (4.9). Apparently I need 'ATAng', not sure if I can get that in the 4.x series... I suppose I could try moving to 5.2.x, but I was hoping to put that off a little longer - and I'd like to know my hardware is reliable first, really. Ouch, sorry. I should've checked that this port worked with 4.x before writing. My mistake. You could try your luck with FreeSBIE Live-CD: http://www.freesbie.org/ I didn't try it, but AFAICS, it's 5.x-based, so you should be able to install smartmontools in the memory-based filesystem that FreeSBIE creates and then check your disk from that. Just give it a try. it *may* even work. David Fleck [EMAIL PROTECTED] Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
### Test 1: # smartctl -a ad0 | more ### Test 2: # smartctl -t offline ad0 then wait for offline selftests to complete, then again: # smartctl -a ad0 | more ### Test 3: # smartctl -t long ad0 again wait for selfttests to complete, then again: # smartctl -a ad0 | more Ok, done. (Oh, BTW, I was having errors like : ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=11291 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=112977803 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=112977835 so thought I'd do this too So now I see : Self-test execution status: ( 119) The previous self-test completed having the read element of the test failed. and SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA _of_first_error # 1 Extended offlineCompleted: read failure 70% 4934 259 34873 So is there something I should do? Thanks, Tuc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
Tuc wrote: ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=11291 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=112977803 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=112977835 [ ...and SMART status... ] So is there something I should do? Get a new hard drive, this one is not going to live much longer. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IDE drive - hard error reading fsbn... - recoverable?
Tuc wrote: ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=11291 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=112977803 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=112977835 [ ...and SMART status... ] So is there something I should do? Get a new hard drive, this one is not going to live much longer. Problem is, unless it fails the Dell Power on IDE test, they won't replace it. :-/ Guess I just keep backing it up until it fails totally. Thanks, Tuc/TTSG Internet Services, Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hard Drive going bad? (hard error reading fsbn)
I started seeing the error messages in my logs. When I googled the error some seem to think it may be a hardware issue and some seem to think it's o/s specific. Trying to see what's the general opinon. Running 4.9 Jun 13 00:30:26 santacruz /kernel: ad0s1h: hard error reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn 197442991; cn 12290 tn 65 sn 46) status=59 error=40 Jun 13 00:30:37 santacruz /kernel: ad0s1h: hard error reading fsbn 197443023 of 26369664-26369887 (ad0s1 bn 197443023; cn 12290 tn 66 sn 15) status=59 error=40 Jun 13 00:30:42 santacruz /kernel: ad0s1h: hard error reading fsbn 197443055 of 26369696-26369887 (ad0s1 bn 197443055; cn 12290 tn 66 sn 47) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443087 of 26369728-26369887 (ad0s1 bn 197443087; cn 12290 tn 67 sn 16) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443119 of 26369760-26369887 (ad0s1 bn 197443119; cn 12290 tn 67 sn 48) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443151 of 26369792-26369887 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive going bad? (hard error reading fsbn)
Kevin Greenidge [EMAIL PROTECTED] wrote: I started seeing the error messages in my logs. When I googled the error some seem to think it may be a hardware issue and some seem to think it's o/s specific. Trying to see what's the general opinon. Running 4.9 It's either a failing HDD, or the HDD/controller hardware you're using isn't compatible with FreeBSD. If it's been working for a while without problems, and suddenly started doing this (as you seem to imply) then it's definately failing hardware. If it's been doing this since install, then it'll be just a little harder to debug. If you post dmesg output and hardware details, I'm sure someone who's familiar with that hardware will let you know if this is expected or not. Jun 13 00:30:26 santacruz /kernel: ad0s1h: hard error reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn 197442991; cn 12290 tn 65 sn 46) status=59 error=40 Jun 13 00:30:37 santacruz /kernel: ad0s1h: hard error reading fsbn 197443023 of 26369664-26369887 (ad0s1 bn 197443023; cn 12290 tn 66 sn 15) status=59 error=40 Jun 13 00:30:42 santacruz /kernel: ad0s1h: hard error reading fsbn 197443055 of 26369696-26369887 (ad0s1 bn 197443055; cn 12290 tn 66 sn 47) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443087 of 26369728-26369887 (ad0s1 bn 197443087; cn 12290 tn 67 sn 16) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443119 of 26369760-26369887 (ad0s1 bn 197443119; cn 12290 tn 67 sn 48) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443151 of 26369792-26369887 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive going bad? (hard error reading fsbn)
Here is the /etc/fstab and my dmesg output: # DeviceMountpoint FStype Options DumpPass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1f /home ufs rw,userquota,groupquota 2 2 /dev/ad0s1g /tmpufs rw,noexec,nosuid2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/ad0s1h /varufs rw,userquota,groupquota 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 - 2.2 irq 5 pcib1: PCI to PCI bridge (vendor=10de device=006c) at device 8.0 on pci0 pci1: PCI bus on pcib1 fxp0: Intel 82559 Pro/100 Ethernet port 0xd000-0xd03f mem 0xe500-0xe50f,0xe511-0xe5110fff irq 11 at device 6.0 on pci1 fxp0: Ethernet address 00:90:27:a9:71:66 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci1: SiS 6326 SVGA controller at 9.0 irq 12 atapci0: Generic PCI ATA controller port 0xf000-0xf00f at device 9.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcib2: PCI to PCI bridge (vendor=10de device=01e8) at device 30.0 on pci0 pci2: PCI bus on pcib2 orm0: Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xcc000-0xccfff on isa0 pmtimer0 on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 plip0: PLIP network interface on ppbus0 IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled ata1-slave: ATA identify retries exceeded ad0: 88350MB IC35L090AVV207-0 [179505/16/63] at ata0-master BIOSDMA acd0: CDROM Compaq CRD-8322B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad0s1h: hard error reading fsbn 197442815 of 26369632-26369887 (ad0s1 bn 197442815; cn 12290 tn 62 sn 59) trying PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0s1h: hard error reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn 197442991; cn 12290 tn 65 sn 46) status=59 error=40 ad0s1h: hard error reading fsbn 197443023 of 26369664-26369887 (ad0s1 bn 197443023; cn 12290 tn 66 sn 15) status=59 error=40 ad0s1h: hard error reading fsbn 197443055 of 26369696-26369887 (ad0s1 bn 197443055; cn 12290 tn 66 sn 47) status=59 error=40 ad0s1h: hard error reading fsbn 197443087 of 26369728-26369887 (ad0s1 bn 197443087; cn 12290 tn 67 sn 16) status=59 error=40 ad0s1h: hard error reading fsbn 197443119 of 26369760-26369887 (ad0s1 bn 197443119; cn 12290 tn 67 sn 48) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369887 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive going bad? (hard error reading fsbn)
Kevin Greenidge [EMAIL PROTECTED] wrote: Has it been doing this since you installed? Or was it working before? Looks like a failed HDD from here. Here is the /etc/fstab and my dmesg output: # Device Mountpoint FStype Options DumpPass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1f /home ufs rw,userquota,groupquota 2 2 /dev/ad0s1g /tmpufs rw,noexec,nosuid2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/ad0s1h /varufs rw,userquota,groupquota 2 2 /dev/acd0c/cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 - 2.2 irq 5 pcib1: PCI to PCI bridge (vendor=10de device=006c) at device 8.0 on pci0 pci1: PCI bus on pcib1 fxp0: Intel 82559 Pro/100 Ethernet port 0xd000-0xd03f mem 0xe500-0xe50f,0xe511-0xe5110fff irq 11 at device 6.0 on pci1 fxp0: Ethernet address 00:90:27:a9:71:66 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci1: SiS 6326 SVGA controller at 9.0 irq 12 atapci0: Generic PCI ATA controller port 0xf000-0xf00f at device 9.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcib2: PCI to PCI bridge (vendor=10de device=01e8) at device 30.0 on pci0 pci2: PCI bus on pcib2 orm0: Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xcc000-0xccfff on isa0 pmtimer0 on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 plip0: PLIP network interface on ppbus0 IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled ata1-slave: ATA identify retries exceeded ad0: 88350MB IC35L090AVV207-0 [179505/16/63] at ata0-master BIOSDMA acd0: CDROM Compaq CRD-8322B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad0s1h: hard error reading fsbn 197442815 of 26369632-26369887 (ad0s1 bn 197442815; cn 12290 tn 62 sn 59) trying PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0s1h: hard error reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn 197442991; cn 12290 tn 65 sn 46) status=59 error=40 ad0s1h: hard error reading fsbn 197443023 of 26369664-26369887 (ad0s1 bn 197443023; cn 12290 tn 66 sn 15) status=59 error=40 ad0s1h: hard error reading fsbn 197443055 of 26369696-26369887 (ad0s1 bn 197443055; cn 12290 tn 66 sn 47) status=59 error=40 ad0s1h: hard error reading fsbn 197443087 of 26369728-26369887 (ad0s1 bn 197443087; cn 12290 tn 67 sn 16) status=59 error=40 ad0s1h: hard error reading fsbn 197443119 of 26369760-26369887 (ad0s1 bn 197443119; cn 12290 tn 67 sn 48) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369887 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Hard Drive going bad? (hard error reading fsbn)
The drive is only about 4 months old and freebsd 4.9 has been installed for about 3 1/2 months running flawlessly. I have a spare drive but I sure hate transferring all that data over to the new drive. I took a chance and installed a single drive since I've always had good luck with drives, now it looks like I'll have to invest in that 3ware raid card after all. Thanks, Kevin -Original Message- From: Bill Moran [mailto:[EMAIL PROTECTED] Sent: Monday, June 14, 2004 11:35 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Hard Drive going bad? (hard error reading fsbn) Kevin Greenidge [EMAIL PROTECTED] wrote: Has it been doing this since you installed? Or was it working before? Looks like a failed HDD from here. Here is the /etc/fstab and my dmesg output: # Device Mountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1f /home ufs rw,userquota,groupquota 2 2 /dev/ad0s1g /tmpufs rw,noexec,nosuid 2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/ad0s1h /varufs rw,userquota,groupquota 2 2 /dev/acd0c/cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 - 2.2 irq 5 pcib1: PCI to PCI bridge (vendor=10de device=006c) at device 8.0 on pci0 pci1: PCI bus on pcib1 fxp0: Intel 82559 Pro/100 Ethernet port 0xd000-0xd03f mem 0xe500-0xe50f,0xe511-0xe5110fff irq 11 at device 6.0 on pci1 fxp0: Ethernet address 00:90:27:a9:71:66 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci1: SiS 6326 SVGA controller at 9.0 irq 12 atapci0: Generic PCI ATA controller port 0xf000-0xf00f at device 9.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcib2: PCI to PCI bridge (vendor=10de device=01e8) at device 30.0 on pci0 pci2: PCI bus on pcib2 orm0: Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xcc000-0xccfff on isa0 pmtimer0 on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 plip0: PLIP network interface on ppbus0 IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled ata1-slave: ATA identify retries exceeded ad0: 88350MB IC35L090AVV207-0 [179505/16/63] at ata0-master BIOSDMA acd0: CDROM Compaq CRD-8322B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad0s1h: hard error reading fsbn 197442815 of 26369632-26369887 (ad0s1 bn 197442815; cn 12290 tn 62 sn 59) trying PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0s1h: hard error reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn 197442991; cn 12290 tn 65 sn 46) status=59 error=40 ad0s1h: hard error reading fsbn 197443023 of 26369664-26369887 (ad0s1 bn 197443023; cn 12290 tn 66 sn 15) status=59 error=40 ad0s1h: hard error reading fsbn 197443055 of 26369696-26369887 (ad0s1 bn 197443055; cn 12290 tn 66 sn 47) status=59 error=40 ad0s1h: hard error reading fsbn 197443087 of 26369728-26369887 (ad0s1 bn 197443087; cn 12290 tn 67 sn 16) status=59 error=40 ad0s1h: hard error reading fsbn 197443119 of 26369760-26369887 (ad0s1 bn 197443119; cn 12290 tn 67 sn 48) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369887 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40 ad0s1h: hard error reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn 197443151; cn 12290 tn 68 sn 17) status=59 error=40
libfreetype.a: Bad address -- hard error reading
Greetings all, Due to yesterday error on 4.9-RELEASE of FreeBSD. snip hard error reading fsbn ad0: DMA problem fallback to PIO mode libfreetype.a: Bad address /snip i tried changing some kernel paramaters mainly these two hw.ata.atapi_dma=1 hw.ata.ata_dma=1 However, that didn't change anything. I also recompiled the GENERIC kernel (as is - on first installation) and that produced the same error, when trying to install XFree86-4. So I revereted back to 4.8-RELEASE of FreeBSD. Lo and Behold everything worked fine. No errors nothing. So I again installed 4.9-RELEASE on my laptop and what do I find? Yes thats right, dmesg out of the same sort of error hard error reading fsbn ad0: DMA problem fallback to PIO mode I think my laptop doesn't like 4.9-RELEASE. Has anyone experienced something like this before? My laptop is a Dell Latitude (H model i think). I dont really know how to troubleshoot/fix this. If anyone has any ideas/suggestions, on how to go about this id greatly appreciate it. Im not sure, if it maybe a BIOS thing or a kernel thing. Thanks again Hi, thanks for that. I know it works with 4.8. but ill try re-installing it again and see how i go. Ill post again later if i still have the same problems. Thank-you --- Chuck Swiger [EMAIL PROTECTED] wrote: eodyna wrote: [ ... ] Ive taken out the harddrive and replaced it with a different one and i still see the same sort of error message does anyone have any ideas on how to help me? Try a process of elimination, by swapping out each component and retesting until you figure out what is failing-- ie, swap the cable, try using another motherboard (or swap a drive that was failing on your problem system to another machine), and/or finally try swapping out the OS and try installing Linux or Windows and see whether this is a FreeBSD-specific problem rather than, say, a bad MB, flaky cable, bad power supply, etc -- -Chuck Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
On Fri, 12 Mar 2004 09:59:17 +1100 (EST) eodyna [EMAIL PROTECTED] wrote: Greetings all, Due to yesterday error on 4.9-RELEASE of FreeBSD. snip hard error reading fsbn ad0: DMA problem fallback to PIO mode libfreetype.a: Bad address /snip The two are completely unrelated. For the first what you say below could be a solution, if set them to 0; (an 5.x I would add that also acpi and apic could count) For the second you have to provide more details. hard error reading fsbn ad0: DMA problem fallback to PIO mode However this usually suggest hw trouble. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
Hello, Thanks for your response. I dont think they are totally unrelated, because when i try to install XFree86-4 and that particular library it gets the error messages stated below (one to stdout and the other to dmesg). All other port installations work fine. (Before and after the XFree86-4 install) I orginally thought it was a hardware problem as well. but to have it fail on two disks with the same sort of error? that is highly unlikely, and installing 4.8-RELEASE yeilds no errors. fsck doesn't produce any errors either. And i dont think it is a ports problem because XFree86-4.3.0,1 works on 4.8-RELEASE. So this has left me thinking its either a bios thingy or something in 4.9-RELEASE kernel that doesn't like my laptop. or maybe i jump to too many conculsions? Hence why i would like some advice on how to trouble shoot this. thanks again This is the post from yesterday with the main error msg: large snip further more, when i look in dmesg i get the following: ad0s1g: hard error reading fsbn 17696655 of 7946848-7946879 (ad0s1 bn 17696655; cn 18726 tn 9 sn 18) trying PIO mode ad0: DMA problem fallback to PIO mode ad0s1g: hard error reading fsbn 17696671 of 7946848-7946879 (ad0s1 bn 17696671; cn 18726 tn 9 sn 34) status=59 error=40 ad0s1g: hard error reading fsbn 17696671 of 7946848-7946879 (ad0s1 bn 17696671; cn 18726 tn 9 sn 34) status=59 error=40 vm_fault: pager read error, pid 418 (install) Ive taken out the harddrive and replaced it with a different one and i still see the same sort of error message ive also tried running fsck, but it yields no errors. I have gone to install XFree86-4 and get the following error installing in lib/font/Speedo... installing in lib/font/Speedo/module... /usr/bin/install -c -m 0444 libspeedo.a /usr/X11R6/lib/modules/fonts install in lib/font/Speedo/module done installing in lib/font/Type1... installing in lib/font/Type1/module... /usr/bin/install -c -m 0444 libtype1.a /usr/X11R6/lib/modules/fonts install in lib/font/Type1/module done installing in lib/font/FreeType... installing in lib/font/FreeType/module... /usr/bin/install -c -m 0444 libfreetype.a /usr/X11R6/lib/modules/fonts install: /usr/X11R6/lib/modules/fonts/libfreetype.a: Bad address *** Error code 71 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType/module. *** Error code 1 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType. *** Error code 1 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font. *** Error code 1 Stop in /usr/ports/x11-servers/XFree86-4-Server. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. /snip Ive tried looking for libfreetype.a and it does exist in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType/module. -rw-r--r-- 1 root wheel 281366 Mar 10 23:22 libfreetype.a I have also tried to install it manually /usr/bin/install -c -m 0444 /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType/module/libfreetype.a /usr/X11R6/lib/modules/fonts and i get the same error install: /usr/X11R6/lib/modules/fonts/libfreetype.a: Bad address /snip --- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: On Fri, 12 Mar 2004 09:59:17 +1100 (EST) eodyna [EMAIL PROTECTED] wrote: Greetings all, Due to yesterday error on 4.9-RELEASE of FreeBSD. snip hard error reading fsbn ad0: DMA problem fallback to PIO mode libfreetype.a: Bad address /snip The two are completely unrelated. For the first what you say below could be a solution, if set them to 0; (an 5.x I would add that also acpi and apic could count) For the second you have to provide more details. hard error reading fsbn ad0: DMA problem fallback to PIO mode However this usually suggest hw trouble. -- IOnut Unregistered ;) FreeBSD user Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
[ please don't post on top, it's hard to read ] On Fri, 12 Mar 2004 11:33:08 +1100 (EST) eodyna [EMAIL PROTECTED] wrote: Hello, Thanks for your response. I dont think they are totally unrelated, because when i try to install XFree86-4 and that particular library it gets the error messages stated below (one to stdout and the other to dmesg). All other port installations work fine. (Before and after the XFree86-4 install) I orginally thought it was a hardware problem as well. but to have it fail on two disks with the same sort of error? that is highly unlikely, and installing 4.8-RELEASE yeilds no errors. fsck doesn't produce any errors either. And i dont think it is a ports problem because XFree86-4.3.0,1 works on 4.8-RELEASE. So this has left me thinking its either a bios thingy or something in 4.9-RELEASE kernel that doesn't like my laptop. This happen when an error is detected by the disk driver. This can be caused by hardware failure or incompatibility, or a driver bug. You get a vm_fault if the kernel is trying to page in a block of memory for a process but it can't. You probably get this instead of a regular read error because AFAIR cp and install uses mmap() on files smaller than 8 MB. Since you changed the HDD it's probably a driver bug. However I would be curios if you get the always the same fsbn numbers. I would be very strange. Stage also is that it's failing on the same file. or maybe i jump to too many conculsions? Hence why i would like some advice on how to trouble shoot this. Aside from posting this + boot -v on mobile, I don't know. This is the post from yesterday with the main error msg: missed that, sorry. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
i forgot to include the mailing list. doh! --- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: [ please don't post on top, it's hard to read ] sorry :/ Hello, Thanks for your response. I dont think they are totally unrelated, because when i try to install XFree86-4 and that particular library it gets the error messages stated below (one to stdout and the other to dmesg). All other port installations work fine. (Before and after the XFree86-4 install) I orginally thought it was a hardware problem as well. but to have it fail on two disks with the same sort of error? that is highly unlikely, and installing 4.8-RELEASE yeilds no errors. fsck doesn't produce any errors either. And i dont think it is a ports problem because XFree86-4.3.0,1 works on 4.8-RELEASE. So this has left me thinking its either a bios thingy or something in 4.9-RELEASE kernel that doesn't like my laptop. This happen when an error is detected by the disk driver. This can be caused by hardware failure or incompatibility, or a driver bug. You get a vm_fault if the kernel is trying to page in a block of memory for a process but it can't. You probably get this instead of a regular read error because AFAIR cp and install uses mmap() on files smaller than 8 MB. Since you changed the HDD it's probably a driver bug. Oh. um this is a silly question, but how do i know which driver it is? However I would be curios if you get the always the same fsbn numbers. I would be very strange. Stage also is that it's failing on the same file. i cannot remember if its the same fsbn numbers or not. i didn't keep a log. or maybe i jump to too many conculsions? Hence why i would like some advice on how to trouble shoot this. Aside from posting this + boot -v on mobile, I don't know. well my thanks anyway for your help thus far. This is the post from yesterday with the main error msg: missed that, sorry. thats ok these things happen :D i am very grateful that you have taken the time to answer my post. :) Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
hard error reading
Hi all, This morning I found this entry in the messages: Oct 15 08:20:25 pippi /kernel: ad6: hard error reading fsbn 1783727 of 0-15 (ad6 bn 1783727; cn 1769 tn 9 sn 8) trying PIO mode Oct 15 08:20:27 pippi /kernel: ad6: DMA problem fallback to PIO mode From searching around a bit I noticed that this probably is the beginning of the end of ad6 and chances are the disk will not come up when the server is rebooted; I haven't tried that yet :-) Now ad6 is part of a RAID 1-setup. Does this message mean: - this blocks are not used any more; while mirorring the lost data is restored on ad6 on some other part - you've lost the data and there's no way you ever gonna find out what it was What I'm also wondering about is if any dumps made now will be accurate. Here's some recent atacontrol-output: root (pippi) /var/cron/tabsatacontrol list ATA channel 0: Master: no device present Slave: acd0 Slimtype COMBO LSC-24081M/3M35 ATA/ATAPI rev 5 ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 IC35L090AVV207-0/V23OA63A ATA/ATAPI rev 6 Slave: no device present ATA channel 3: Master: ad6 IC35L090AVV207-0/V23OA63A ATA/ATAPI rev 6 Slave: no device present root (pippi) /var/cron/tabsatacontrol status ar0 ar0: ATA RAID1 subdisks: ad4 ad6 status: READY Any answers and help on how to proceed from here much appreciated! Cheers, Marko http://half2.nl *** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hard error reading
On Wed, Oct 15, 2003 at 02:50:14PM +0200, Marko Leer wrote: Hi all, This morning I found this entry in the messages: Oct 15 08:20:25 pippi /kernel: ad6: hard error reading fsbn 1783727 of 0-15 (ad6 bn 1783727; cn 1769 tn 9 sn 8) trying PIO mode Oct 15 08:20:27 pippi /kernel: ad6: DMA problem fallback to PIO mode From searching around a bit I noticed that this probably is the beginning of the end of ad6 and chances are the disk will not come up when the server is rebooted; I haven't tried that yet :-) Now ad6 is part of a RAID 1-setup. Does this message mean: - this blocks are not used any more; while mirorring the lost data is restored on ad6 on some other part - you've lost the data and there's no way you ever gonna find out what it was What I'm also wondering about is if any dumps made now will be accurate. Here's some recent atacontrol-output: [snip] end of the original message Go to http://www.hgst.com/hdd/support/download.htm, download the Drive Fitness Test (DFT) utility and run it to test the drives. If the drives are fine you may check if the cabling is ok. I once had a 'fallback to PIO mode' error with a Promise TX2 IDE RAID controller and two IBM IC35L040AVER07-0/ER4OA44A. Each drive had a couple of fans in front of it and one of this was failing and noisy. I unplugged the fans and the problem went away. I know this is very strange... but I never had any problem since then! Francesco Casadei -- You can download my public key from http://digilander.libero.it/fcasadei/ or retrieve it from a keyserver (pgpkeys.mit.edu, wwwkeys.pgp.net, ...) Key fingerprint is: 1671 9A23 ACB4 520A E7EE 00B0 7EC3 375F 164E B17B pgp0.pgp Description: PGP signature
ad0s2g: hard error reading fsbn
anyone has an idea why i get this error in /usr, it happens after i recompile my kernel, im running 4.8-RELEASE. thanks ppc0: FIFO with 16/16/16 bytes threshold ad0: 76319MB ST380021A [155061/16/63] at ata0-master PIO4 acd0: CD-RW SONY CD-RW CRX175A at ata1-slave PIO4 Mounting root from ufs:/dev/ad0s2a ad0s2g: hard error reading fsbn 153560175 of 36456416-36456543 (ad0s2 bn 1535601 75; cn 9558 tn 173 sn 6) status=59 error=40 ad0s2g: hard error reading fsbn 36456531 (ad0s2 bn 36456531; cn 2269 tn 80 sn 6) status=59 error=40 ad0s2g: hard error reading fsbn 36456538 (ad0s2 bn 36456538; cn 2269 tn 80 sn 13 ) status=59 error=40 ad0s2g: hard error reading fsbn 153560319 of 36456544-36456671 (ad0s2 bn 1535603 19; cn 9558 tn 175 sn 24) status=59 error=40 ad0s2g: hard error reading fsbn 36456551 (ad0s2 bn 36456551; cn 2269 tn 80 sn 26 ) status=59 error=40 ad0s2g: hard error reading fsbn 3 __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Replacement hard drives, was: Re: Hard error??
Chuck Swiger wrote: Your drive should still be under warrantee, then...? To answer your question: I've been fairly happy with Seagate over the years, and Maxtor has been okay. Seagate's flagship products tend to do well, at least if you've got an open budget available-- one main fileserver I run has four Seagate ST336752LC drives (Cheetah X15 36LP?) in a RAID-1,0. They rock. Maxtor has sometimes seemed to have better price/performance for their normal drives, which is useful when one's budget it more constrained. Avoid Quantum at all costs. While there was an educational benefit to learning how to coax more life from one of those famous 105MB's with stiction, newer Quantum drives are better in the sense that they hold more data, and worse in that they tend to fail more abruptly and more permanently. IBM and Fujitsu have both been having quality control issues recently, although the IBM UltraStar lineup used to be pretty good at one point. I'd also like to give a big thumbs up to recent the Western Digital series of SE drives with 8MB of cache. WD's previous SCSI drives, like the 10K 18GB Vantage were good, too. As for laptop drives, well, what you want is a single platter drive with low power consumption, hence low heat-- ie, ones for ultra-thin/light laptops, something like what Sony's got in their VAIO 505's; expect a slower spindle speed, though. Even so, laptops tend to take a beating, and even good laptop drives seem to have about a 25% mortality rate after 3 years, give or take. Anyone know of a laptop that takes SCA (80-pin SCSI) drives? Failing that, be nice once SATA + individual IDE channels per drive + RAID hardware + SCSI layers (TCQ/command protocol/iSCSI/etc) becomes more common. SATA for the cabling alone will do a world of good. While I'm thinking about it, a platform-spanning PCI-X version of a SATA/RAID card would remind me favorably of Adaptec's 2940 (U/UW/OF/etc) series. -Chuck Disclaimer: Any Clutch fans out there? Last night's show-- in the hinterlands of Brooklyn, New York; Lamours-- is responsible; any opinions represented above I may or may not agree with once I finish recovering. Very good show, finished very late. :-) I'm wondering if whether or not the whole thing was due to my own misdoing. A buddy of mine scolded me after having explained the situation, as I apparently had messed things up (you know, the way newbies do). I guess I bit off more than I could chew when I started cvsupping and rebuilding the world. ;) Anyway, I formatted the drive and did a clean install, and it seems to be working fine now, for the time being at least. No hard errors yet. But still, thanks for the suggestions. In case it starts acting up again, I'll have this reference. -Henrik FreeBSD newbie and fanatic. _ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Replacement hard drives, was: Re: Hard error??
the new Seagate 120gb seems to be real quiet and stable for me I cant even hear it running, they have a new motor design and probably is the best bang for the buck right now about $140.00 I had bad luck with quantum, maxtor and IBM and WD but Seagate seem to be very good for me right now. I think there is a website called drivereview.com or something that can better give you a hint. On Saturday 15 February 2003 02:45 pm, Chuck Swiger wrote: Henrik W Lund wrote: [ ... ] Anyway, it seems like I have just got to get myself a new drive. On that note, has anybody got any idea what I should go for? Any vendors whose drives do NOT cave in after half a year? ;) Your drive should still be under warrantee, then...? To answer your question: I've been fairly happy with Seagate over the years, and Maxtor has been okay. Seagate's flagship products tend to do well, at least if you've got an open budget available-- one main fileserver I run has four Seagate ST336752LC drives (Cheetah X15 36LP?) in a RAID-1,0. They rock. Maxtor has sometimes seemed to have better price/performance for their normal drives, which is useful when one's budget it more constrained. Avoid Quantum at all costs. While there was an educational benefit to learning how to coax more life from one of those famous 105MB's with stiction, newer Quantum drives are better in the sense that they hold more data, and worse in that they tend to fail more abruptly and more permanently. IBM and Fujitsu have both been having quality control issues recently, although the IBM UltraStar lineup used to be pretty good at one point. I'd also like to give a big thumbs up to recent the Western Digital series of SE drives with 8MB of cache. WD's previous SCSI drives, like the 10K 18GB Vantage were good, too. As for laptop drives, well, what you want is a single platter drive with low power consumption, hence low heat-- ie, ones for ultra-thin/light laptops, something like what Sony's got in their VAIO 505's; expect a slower spindle speed, though. Even so, laptops tend to take a beating, and even good laptop drives seem to have about a 25% mortality rate after 3 years, give or take. Anyone know of a laptop that takes SCA (80-pin SCSI) drives? Failing that, be nice once SATA + individual IDE channels per drive + RAID hardware + SCSI layers (TCQ/command protocol/iSCSI/etc) becomes more common. SATA for the cabling alone will do a world of good. While I'm thinking about it, a platform-spanning PCI-X version of a SATA/RAID card would remind me favorably of Adaptec's 2940 (U/UW/OF/etc) series. -Chuck Disclaimer: Any Clutch fans out there? Last night's show-- in the hinterlands of Brooklyn, New York; Lamours-- is responsible; any opinions represented above I may or may not agree with once I finish recovering. Very good show, finished very late. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Replacement hard drives, was: Re: Hard error??
Henrik W Lund wrote: [ ... ] Anyway, it seems like I have just got to get myself a new drive. On that note, has anybody got any idea what I should go for? Any vendors whose drives do NOT cave in after half a year? ;) Your drive should still be under warrantee, then...? To answer your question: I've been fairly happy with Seagate over the years, and Maxtor has been okay. Seagate's flagship products tend to do well, at least if you've got an open budget available-- one main fileserver I run has four Seagate ST336752LC drives (Cheetah X15 36LP?) in a RAID-1,0. They rock. Maxtor has sometimes seemed to have better price/performance for their normal drives, which is useful when one's budget it more constrained. Avoid Quantum at all costs. While there was an educational benefit to learning how to coax more life from one of those famous 105MB's with stiction, newer Quantum drives are better in the sense that they hold more data, and worse in that they tend to fail more abruptly and more permanently. IBM and Fujitsu have both been having quality control issues recently, although the IBM UltraStar lineup used to be pretty good at one point. I'd also like to give a big thumbs up to recent the Western Digital series of SE drives with 8MB of cache. WD's previous SCSI drives, like the 10K 18GB Vantage were good, too. As for laptop drives, well, what you want is a single platter drive with low power consumption, hence low heat-- ie, ones for ultra-thin/light laptops, something like what Sony's got in their VAIO 505's; expect a slower spindle speed, though. Even so, laptops tend to take a beating, and even good laptop drives seem to have about a 25% mortality rate after 3 years, give or take. Anyone know of a laptop that takes SCA (80-pin SCSI) drives? Failing that, be nice once SATA + individual IDE channels per drive + RAID hardware + SCSI layers (TCQ/command protocol/iSCSI/etc) becomes more common. SATA for the cabling alone will do a world of good. While I'm thinking about it, a platform-spanning PCI-X version of a SATA/RAID card would remind me favorably of Adaptec's 2940 (U/UW/OF/etc) series. -Chuck Disclaimer: Any Clutch fans out there? Last night's show-- in the hinterlands of Brooklyn, New York; Lamours-- is responsible; any opinions represented above I may or may not agree with once I finish recovering. Very good show, finished very late. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Hard error??
I'm running 4.7-STABLE on a Compaq Evo1000v, and am generally quite satisfied. During the last couple of hours, however, I have been getting the weirdest messages whenever I try to do anything: ad0s1g: hard error reading fsbn 70863167 of 34268000-34268031 (ad0s1 bn 70863167; cn 4686 tn 172 sn 11) trying PIO mode ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ... ... (repeat to fade) What is this? Please, don't tell me my hard drive is about to go ape. What do I do? Thanks! _ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Henrik W Lund wrote: [ ... ] ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ... ... (repeat to fade) What is this? Please, don't tell me my hard drive is about to go ape. OK. However, your hard drive probably is going to repeat to fade, losing your data along the way, until it becomes not working. What do I do? Verify your backups, and get a new drive. -Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Henrik W Lund wrote: I'm running 4.7-STABLE on a Compaq Evo1000v, and am generally quite satisfied. During the last couple of hours, however, I have been getting the weirdest messages whenever I try to do anything: ad0s1g: hard error reading fsbn 70863167 of 34268000-34268031 (ad0s1 bn 70863167; cn 4686 tn 172 sn 11) trying PIO mode ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ad0s1g: hard error reading fsbn 70863183 of 34268000-34268031 (ad0s1 bn 70863183; cn 4686 tn 172 sn 27) status=59 error=01 ... ... (repeat to fade) What is this? Please, don't tell me my hard drive is about to go ape. What do I do? Yes, barring dirty power or loose cables, it's either your HDD or the controller that's on the fritz. In my experience, it's usually the HDD, although I've seen controllers act up as well. Whatever you attempt to do to fix this, make sure you have backups right away. Data could already be lost. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Verify your backups, and get a new drive. -Chuck Wow... This is a real nightmare come true. :/ And 2.5 drives are sooo cheap! Oh well, at least I won't lose important data. _ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
I used to get this error on a FreeBSD while using a perfectly stable harddrive. That harddrive is managed via Solaris now, but, I determined the issue during its FreeBSD usage was DMA. If you are running two disks on the same ATA channel with different DMA capabilities, the capabilities may be causing scrambles in the negotiation of I/O on the line. The solution is to put ATA drives that use _only_ the same DMA caps on the same ATA channel. If you only have two drives, simply put ATA0.1 on ATA1.0. This stopped my falling back to PIO messages and probably saved the disk from hard failure caused by misuse. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
On Fri, Feb 14, 2003 at 01:19:39PM -0500, northern snowfall wrote: I used to get this error on a FreeBSD while using a perfectly stable harddrive. That harddrive is managed via Solaris now, but, I determined the issue during its FreeBSD usage was DMA. If you are running two disks on the same ATA channel with different DMA capabilities, the capabilities may be causing scrambles in the negotiation of I/O on the line. The solution is to put ATA drives that use _only_ the same DMA caps on the same ATA channel. If you only have two drives, simply put ATA0.1 on ATA1.0. This stopped my falling back to PIO messages and probably saved the disk from hard failure caused by misuse. Don Is this a bug in the FreeBSD ATA driver then? I used an IBM DeskStar drive and had Linux running perfectly well on it. I backed up all my data, deleted the partitions and went to install FreeBSD on it. The installation failed with lots of 'hard error' messages. Did FreeBSD kill my hard drive, or was it just luck that I got my data off the drive with minutes to spare? I know DeskStar drives are notorious for failure, but I did indeed have DMA66 and DMA33 drives on the same channel, and thought it a bit suspicious that the drive died at the instant I tried to install FreeBSD. Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Is this a bug in the FreeBSD ATA driver then? I used an IBM DeskStar drive and had Linux running perfectly well on it. I backed up all my data, deleted the partitions and went to install FreeBSD on it. The installation failed with lots of 'hard error' messages. Did FreeBSD kill my hard drive, or was it just luck that I got my data off the drive with minutes to spare? I know DeskStar drives are notorious for failure, but I did indeed have DMA66 and DMA33 drives on the same channel, and thought it a bit suspicious that the drive died at the instant I tried to install FreeBSD. Bruce Cran Yeah, this also occured to me, as I have been running WinXP on my drive without problems. The really wierd bit is that I only get the messages when writing to (or reading from) /usr (i run a dedicated partition for /usr. You know, the automatic single disk setup when installing FreeBSD). Wait, maybe that isn't so wierd after all. Anyway, I want to know for sure that this disk failure is not due to any FreeBSD shenanigans, as I do not want to buy a new drive and install FreeBSD to it, only to have it crash on me just days later. _ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Henrik W Lund wrote: [ ... ] Anyway, I want to know for sure that this disk failure is not due to any FreeBSD shenanigans, as I do not want to buy a new drive and install FreeBSD to it, only to have it crash on me just days later. Fair enough. Check with the vendor of your hard drive (or the laptop) for their hard-drive test utilities. You should be able to do a non-destructive read test and see what you see -Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Fair enough. Check with the vendor of your hard drive (or the laptop) for their hard-drive test utilities. You should be able to do a non-destructive read test and see what you see -Chuck Oh, just something that occured to me now: do you think this may be due to the harddrive overheating? Maybe a fan isn't working, or a ventilation grill has been covered up. The computer has been turned on for quite extended periods of time lately. Yay, nay? Possible cause? _ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
On Fri, Feb 14, 2003 at 02:19:34PM -0500, Chuck Swiger wrote: Henrik W Lund wrote: [ ... ] Anyway, I want to know for sure that this disk failure is not due to any FreeBSD shenanigans, as I do not want to buy a new drive and install FreeBSD to it, only to have it crash on me just days later. Fair enough. Check with the vendor of your hard drive (or the laptop) for their hard-drive test utilities. You should be able to do a non-destructive read test and see what you see My drive really did fail after attempting to install FreeBSD - I mananged to get the BIOS and Windows to recognise it long enough to run IBM's smartdefender program. It told me the drive was basically dead. Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Thanks for all your help, even though the situation turned out to be rather grim. Definitely moreso than I had hoped. Anyway, it seems like I have just got to get myself a new drive. On that note, has anybody got any idea what I should go for? Any vendors whose drives do NOT cave in after half a year? ;) Again, thanks for all your help. I appreciate it. -Henrik _ MSN Messenger http://www.msn.no/messenger - Den korteste veien mellom deg og dine venner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Is this a bug in the FreeBSD ATA driver then?
Its entirely possible, but, I, personally, wouldn't know for sure.
I'm just getting in to the depths of the ATA specs. It may not be
a bug so much as a lack of handling specific DMA issues.
Maybe someone should CC freebsd-{hardware,hackers}@
Don
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Hard error??
Anyway, it seems like I have just got to get myself a new drive. On that note, has anybody got any idea what I should go for? Any vendors whose drives do NOT cave in after half a year? ;) I choose Maxtor for several reasons. First off, I've been using Maxtor disks the most since I started out in computers and haven't had one fail yet (running every OS i've tested). Now that I'm alittle more experienced, I use Maxtor because of its standing credibility with me, and, because the Chairman of the T13[1] (technical committee for ATA[-ATAPI] development) is from Maxtor Corporation. They are most likely to want to adhere to a published specification (along with other T13 members), rather than develop chipsets that are rushed to keep up with a $25 billion a year industry. Don [1] T13 technical committee http://www.t13.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
hard error reading fsbn and file name
hi I get the same: ad0s2f: hard error reading fsbn 3978952 of 1207492-1207495 (ad0s2 bn 3978952; cn 3947 tn 5 sn 61) status=59 error=40 every day. I believe it happens during the periodic daily scripts at night. Is there a way to tell what file lives on that particular block on the HDD? thank you in advance, -- slava To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
IDE Disk hard error
Hi all, my machine crashed due to a power failure during a make installworld. Now I get this: /kernel: ad0s1f: hard error reading fsbn 35393727 of 17236032-17236047 (ad0s1 bn 35393727; cn 2203 tn 40 sn 12) status=59 error=40 It is always the same, so I guess there's only a small area damaged. I know the Handbook says to replace the disk (this is a Maxtor 20GB disk), but since is not a production system, just my private Dial-In Server, I am not really looking forward into getting a new disk. Any chance to fix this error? What about badsect? How does this work? TIA, Jan -- Jan Lentfer System Administrator Molecular Cell Biology / AG Holstein, Darmstadt University of Technology, Schnittspahnstr. 10, 64287 Darmstadt, Germany Tel: +49 6151 16 5563 / Tel private: +49 6155 899393 / mobile: +49 163 4712037 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
