Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk
Unfortunately the answer presented itself very soon after posting the message. I pulled the hard drive out of the box, and tried to format it in a Windows machine. It occurred to me that the drive had not been formated and therefore had not had data written to all parts of the disk. Half way through the format I got an 'Unsafe removal of device' message, and upon reboot the drive was TOTALLY dead. It would be nice if FreeBSD had a SMARTY utility - it would have allowed me to possibly detect this failure. I've been told that work is underway to write one and it might be ready for 5.0. Cheers, Andrew On Mon, 2002-12-09 at 09:10, philipp wrote: hey, i just browsed through the freebsd-questions archive and found your mail (see below). i am just wondering if you found out what the problem was and/or how to solve it since i am in the same situation on Thu, Nov 28, 2002 at 12:11:48AM +1100, Andrew Cutler wrote: I recently built a FreeBSD 4.7 Release file server that has a brand new 80GB Wester Digital 7200RPM drive in it. Yesterday the box suffered two power outages and a possible powersurge. Today I decided that it would be a good idea to check on the state of the file system and the result is attached below. I was unable to clean the file system. I've got just two questions that hopefully someone can help with: 1) What does the result below mean? (Is my drive failing? Why can't I clean the FS?) 2) Are there any BSD tools for reading the SMART data off the Hard Disk so that I can see whether it is about to fail or currently experiencing HW failure. TIA Andrew Cutler - START SCREEN SNIPPET mojo# fsck /dev/ad2s1e ** /dev/ad2s1e ** Last Mounted on /data ** Phase 1 - Check Blocks and Sizes CANNOT READ: BLK 152744928 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, CANNOT READ: BLK 152745312 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152745393, CANNOT READ: BLK 152746208 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152746289, CANNOT READ: BLK 152747104 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152747184, CANNOT READ: BLK 152748128 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748173, CANNOT READ: BLK 152748512 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748621, CANNOT READ: BLK 152749024 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749068, CANNOT READ: BLK 152749408 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749516, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 33755 files, 16020305 used, 22442867 free (12539 frags, 2803791 blocks, 0.0% fragmentation) * FILE SYSTEM MARKED DIRTY * * PLEASE RERUN FSCK * To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message regards -- Andrew Cutler [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk
On Mon, Dec 09, 2002 at 10:21:39AM +1100, Andrew Cutler wrote: Unfortunately the answer presented itself very soon after posting the message. I pulled the hard drive out of the box, and tried to format it in a Windows machine. It occurred to me that the drive had not been formated and therefore had not had data written to all parts of the disk. Half way through the format I got an 'Unsafe removal of device' message, and upon reboot the drive was TOTALLY dead. It would be nice if FreeBSD had a SMARTY utility - it would have allowed me to possibly detect this failure. I've been told that work is underway to write one and it might be ready for 5.0. Mmm. Well to pass on something I do with every new disk I buy. If I do not have it already I get the diagnostics for it from the disk manafacturers website, which they all have for free. I then run all the tests on the disk and format it. These are almost always standalone boot images that fit on a DOS floppy. Later on it is always handy if you suspect disk problems -- then you can run the non-destructive drive tests as well. I do as many other kinds of test as possible on new hardware before I start using the machine (usually one I am buiding) -- on the fairly well-known principle that anything electronic or electro-mechanical usually fails early in it's life if it is borderline. [ As an aside this is harder with memory, the famous Memtest86 program gives false positives on certain hardware combinations and on certain tests. ] -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Unexpected Soft Update Inconsistency / Cannot Read: Blk
I recently built a FreeBSD 4.7 Release file server that has a brand new 80GB Wester Digital 7200RPM drive in it. Yesterday the box suffered two power outages and a possible powersurge. Today I decided that it would be a good idea to check on the state of the file system and the result is attached below. I was unable to clean the file system. I've got just two questions that hopefully someone can help with: 1) What does the result below mean? (Is my drive failing? Why can't I clean the FS?) 2) Are there any BSD tools for reading the SMART data off the Hard Disk so that I can see whether it is about to fail or currently experiencing HW failure. Any other ways to check for bad sectors? TIA - START SCREEN SNIPPET mojo# fsck /dev/ad2s1e ** /dev/ad2s1e ** Last Mounted on /data ** Phase 1 - Check Blocks and Sizes CANNOT READ: BLK 152744928 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, CANNOT READ: BLK 152745312 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152745393, CANNOT READ: BLK 152746208 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152746289, CANNOT READ: BLK 152747104 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152747184, CANNOT READ: BLK 152748128 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748173, CANNOT READ: BLK 152748512 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748621, CANNOT READ: BLK 152749024 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749068, CANNOT READ: BLK 152749408 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749516, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 33755 files, 16020305 used, 22442867 free (12539 frags, 2803791 blocks, 0.0% fragmentation) * FILE SYSTEM MARKED DIRTY * * PLEASE RERUN FSCK * _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk
On Fri, 29 Nov 2002, Vinco Maldini wrote: 1) What does the result below mean? (Is my drive failing? Why can't I clean the FS?) [ ... snip ... ] CANNOT READ: BLK 152744928 UNEXPECTED SOFT UPDATE INCONSISTENCY [ ... snip ... ] THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, [ ... etc, etc, snip ... ] Were there any kernel messages displayed on the consoles (the bright white text)? If you don't have console access, run the /sbin/dmesg command. If you see any ad2 read errors from the console, then you likely have a bad drive. On the other hand, if you don't see any errors being reported by the kernel, then the CANNOT READ errors are probably just caused by incompleted meta-data writes to the drive. However, THE FOLLOWING DISK SECTORS COULD NOT BE READ makes me think it is a hardware problem. 2) Are there any BSD tools for reading the SMART data off the Hard Disk so that I can see whether it is about to fail or currently experiencing HW failure. Any other ways to check for bad sectors? I thought that someone asked this same questions a few days ago, but I can't find it in the archives. I'm honestly not sure if anything like that is available. Searching the FreeBSD site did not yield any results. My best suggestions is to check google. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk
On Fri, 29 Nov 2002, Vinco Maldini wrote: 1) What does the result below mean? (Is my drive failing? Why can't I clean the FS?) [ ... snip ... ] CANNOT READ: BLK 152744928 UNEXPECTED SOFT UPDATE INCONSISTENCY [ ... snip ... ] THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, [ ... etc, etc, snip ... ] Were there any kernel messages displayed on the consoles (the bright white text)? If you don't have console access, run the /sbin/dmesg command. If you see any ad2 read errors from the console, then you likely have a bad drive. On the other hand, if you don't see any errors being reported by the kernel, then the CANNOT READ errors are probably just caused by incompleted meta-data writes to the drive. However, THE FOLLOWING DISK SECTORS COULD NOT BE READ makes me think it is a hardware problem. 2) Are there any BSD tools for reading the SMART data off the Hard Disk so that I can see whether it is about to fail or currently experiencing HW failure. Any other ways to check for bad sectors? I thought that someone asked this same questions a few days ago, but I can't find it in the archives. I'm honestly not sure if anything like that is available. Searching the FreeBSD site did not yield any results. My best suggestions is to check google. Or check with [EMAIL PROTECTED] If there was something like this out there, he'd know :) -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk
2) Are there any BSD tools for reading the SMART data off the Hard Disk so that I can see whether it is about to fail or currently experiencing HW failure. Any other ways to check for bad sectors? JH I thought that someone asked this same questions a few days ago, but I JH can't find it in the archives. I'm honestly not sure if anything like JH that is available. Searching the FreeBSD site did not yield any results. JH My best suggestions is to check google. FYI, from -stable, Eduard Martinescu is in the process of porting the Smartmon tools (http://sourceforge.net/projects/smartmontools/) to FreeBSD. He's waiting for Soren Schmidt to commit some changes to the ATA driver to support the SMART ATAPI commands before he can finish the port. -Neill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Unexpected Soft Update Inconsistency / Cannot Read: Blk
I recently built a FreeBSD 4.7 Release file server that has a brand new 80GB Wester Digital 7200RPM drive in it. Yesterday the box suffered two power outages and a possible powersurge. Today I decided that it would be a good idea to check on the state of the file system and the result is attached below. I was unable to clean the file system. I've got just two questions that hopefully someone can help with: 1) What does the result below mean? (Is my drive failing? Why can't I clean the FS?) 2) Are there any BSD tools for reading the SMART data off the Hard Disk so that I can see whether it is about to fail or currently experiencing HW failure. TIA Andrew Cutler - START SCREEN SNIPPET mojo# fsck /dev/ad2s1e ** /dev/ad2s1e ** Last Mounted on /data ** Phase 1 - Check Blocks and Sizes CANNOT READ: BLK 152744928 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, CANNOT READ: BLK 152745312 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152745393, CANNOT READ: BLK 152746208 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152746289, CANNOT READ: BLK 152747104 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152747184, CANNOT READ: BLK 152748128 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748173, CANNOT READ: BLK 152748512 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748621, CANNOT READ: BLK 152749024 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749068, CANNOT READ: BLK 152749408 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749516, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 33755 files, 16020305 used, 22442867 free (12539 frags, 2803791 blocks, 0.0% fragmentation) * FILE SYSTEM MARKED DIRTY * * PLEASE RERUN FSCK * To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
