RE: Disk problems?
check to see if the drive mfgr has a firmware update for your disks Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jack Barnett Sent: Wednesday, May 09, 2007 1:15 AM To: freebsd-questions@freebsd.org Subject: Re: Disk problems? hrm... ? Doing it again: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 twa0: INFO: (0x04: 0x0005): Rebuild completed: unit=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=0, port=0 twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=1 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 twa0: ERROR: (0x04: 0x000A): Drive error detected: unit=0, port=1 now says both disks are having problems (I removed the other two disks and just keeping the two root drives in array unit 1): Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) u0 RAID-1DEGRADED* - - - - 74.4951 u0-0 DISK WARNING- - p1- 74.4951 u0-1 DISK DEGRADED - - p0- 74.4951 What the ? I tested both of these under WinXP and they come up fine. No errors, nothing when running windows. Under FreeBSD, it throws those errors above and then sets them degraded (and then the bios flags them on reboot) - but if I run windows, it never flags them and everything is fine. Another thing I noticed is that under FreeBSD the drives will starts clicking and making god awful noises, really loud clicking like the heads are jerking back and forth really fast. Doesn't happen in windows, they run really quite and smooth. Is this some sort of bad driver messing up my disks? I don't know what the hell it's doing to my drives, but it sounds god awful... I have it booted in windows now and it doesn't do that. I've never seen this before. Why does it keep clicking my drives like that and why is it throwing errors? I've rebuild this array about a half dozen times already. I synced to 6.2 rel and rebuild both kernel and world, but something doesn't seem right :( On 5/7/07, Jack Barnett [EMAIL PROTECTED] wrote: I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 Mirror 1 arrays: Unit 1: 2 x 80 gigs Unit 2: 2 x 400 gigs Under windows this was working fine. Both disks where healthy and running (I could test this by unplugging one or the other): Under FreeBSD though, it says it's not working: May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0 May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=1 May 7 13:57:48 fire kernel: twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 The rebuild message is fine, but keeps getting Drive power on reset detected: port=0 In the 3ware BIOS, it shows all drives as active (ie. powered on and connected), so don't know why the kernel thinks it's powered down? Does it mean something else? If I just wait for about 20 minutes, the drives start rebuilding: Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy -- u0RAID-1REBUILDING 37 - - 74.4951 OFFOFF u1RAID-1REBUILDING 13 - - 372.519 OFFOFF (it's in Unit one above, 37% complete). So even though it's getting this Drive power on reset detected it eventually rebuilds it's self. ? Any ideas what this message means? I thought it was an error, but seems fine since it's rebuilding it's self. ? Thanks. ___ 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]
Re: Disk problems?
hrm... ? Doing it again: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 twa0: INFO: (0x04: 0x0005): Rebuild completed: unit=0 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=0, port=0 twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=1 twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 twa0: ERROR: (0x04: 0x000A): Drive error detected: unit=0, port=1 now says both disks are having problems (I removed the other two disks and just keeping the two root drives in array unit 1): Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) u0 RAID-1DEGRADED* - - - - 74.4951 u0-0 DISK WARNING- - p1- 74.4951 u0-1 DISK DEGRADED - - p0- 74.4951 What the ? I tested both of these under WinXP and they come up fine. No errors, nothing when running windows. Under FreeBSD, it throws those errors above and then sets them degraded (and then the bios flags them on reboot) - but if I run windows, it never flags them and everything is fine. Another thing I noticed is that under FreeBSD the drives will starts clicking and making god awful noises, really loud clicking like the heads are jerking back and forth really fast. Doesn't happen in windows, they run really quite and smooth. Is this some sort of bad driver messing up my disks? I don't know what the hell it's doing to my drives, but it sounds god awful... I have it booted in windows now and it doesn't do that. I've never seen this before. Why does it keep clicking my drives like that and why is it throwing errors? I've rebuild this array about a half dozen times already. I synced to 6.2 rel and rebuild both kernel and world, but something doesn't seem right :( On 5/7/07, Jack Barnett [EMAIL PROTECTED] wrote: I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 Mirror 1 arrays: Unit 1: 2 x 80 gigs Unit 2: 2 x 400 gigs Under windows this was working fine. Both disks where healthy and running (I could test this by unplugging one or the other): Under FreeBSD though, it says it's not working: May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0 May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=1 May 7 13:57:48 fire kernel: twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 The rebuild message is fine, but keeps getting Drive power on reset detected: port=0 In the 3ware BIOS, it shows all drives as active (ie. powered on and connected), so don't know why the kernel thinks it's powered down? Does it mean something else? If I just wait for about 20 minutes, the drives start rebuilding: Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy -- u0RAID-1REBUILDING 37 - - 74.4951 OFFOFF u1RAID-1REBUILDING 13 - - 372.519 OFFOFF (it's in Unit one above, 37% complete). So even though it's getting this Drive power on reset detected it eventually rebuilds it's self. ? Any ideas what this message means? I thought it was an error, but seems fine since it's rebuilding it's self. ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk problems?
I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 Mirror 1 arrays: Unit 1: 2 x 80 gigs Unit 2: 2 x 400 gigs Under windows this was working fine. Both disks where healthy and running (I could test this by unplugging one or the other): Under FreeBSD though, it says it's not working: May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0 May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): Rebuild started: unit=1 May 7 13:57:48 fire kernel: twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 The rebuild message is fine, but keeps getting Drive power on reset detected: port=0 In the 3ware BIOS, it shows all drives as active (ie. powered on and connected), so don't know why the kernel thinks it's powered down? Does it mean something else? If I just wait for about 20 minutes, the drives start rebuilding: Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy -- u0RAID-1REBUILDING 37 - - 74.4951 OFFOFF u1RAID-1REBUILDING 13 - - 372.519 OFFOFF (it's in Unit one above, 37% complete). So even though it's getting this Drive power on reset detected it eventually rebuilds it's self. ? Any ideas what this message means? I thought it was an error, but seems fine since it's rebuilding it's self. ? Thanks. ___ 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?
6.2 Release/stable (synced source as of yesterday, rebuilt and still getting it) On 5/7/07, Peter A. Giessel [EMAIL PROTECTED] wrote: On 2007/05/07 11:16, Jack Barnett seems to have typed: I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 Mirror 1 arrays: Unit 1: 2 x 80 gigs Unit 2: 2 x 400 gigs Under windows this was working fine. Both disks where healthy and running (I could test this by unplugging one or the other): Under FreeBSD though, it says it's not working: What version of FreeBSD? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Serious disk problems
My power supply died and now my root file system seems to be having major problems. I run fsck -y on it and after complaining about dozens of sectors having problems being read and Unexpected soft updates, fsck ends with: fsck_ufs: cannot alloc 3962308096 bytes for inoinfo Can anything be done about this? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Jiggle The Handle, a personal bloghttp://jiggle.anaze.us Some days, it's not even worth chewing through the restraints ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Serious disk problems
I would try moving the disk to another server and doing the fsck there. If you get the same error you can try increasing the memory limits. You could also try booting the live CD and run the fsck. If you do this you may need to us sysctl to raise the memory limits if you get that error. -Derek At 11:49 AM 7/25/2006, Jonathan Arnold wrote: My power supply died and now my root file system seems to be having major problems. I run fsck -y on it and after complaining about dozens of sectors having problems being read and Unexpected soft updates, fsck ends with: fsck_ufs: cannot alloc 3962308096 bytes for inoinfo Can anything be done about this? -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Jiggle The Handle, a personal bloghttp://jiggle.anaze.us Some days, it's not even worth chewing through the restraints ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Hard Disk problems
[mailto:[EMAIL PROTECTED] On Behalf Of Shane Ambler Sent: Saturday, April 01, 2006 3:10 AM To: FreeBSD Mailing Lists Subject: Hard Disk problems A few days ago I started getting some disk errors and can't seem to find a reference to find a way to fix them (other than the obvious re-format) The daily security run output contains the following (abbreviated) Checking setuid files and devices: find: /usr/ports/databases/db43/work/db-4.3.28/db: Input/output error find: /usr/ports/devel/git/Makefile: Input/output error ~ repeated 32 times for different files (thankfully all in the ports tree) tower.home.com kernel log messages: ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=139102367 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102367 These 2 error codes are repeated a total of 38 times all with the same LBA If I start in single user mode and do fsck it takes about half an hour to get through and repeats similar errors many times for just about every check it does. Running #fsck -y fsckout (while in multiuser mode) is as follows - followed by dmesg output since boot cat fsckout ** /dev/ad0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2259 files, 44188 used, 82651 free (251 frags, 10300 blocks, 0.2% fragmentation) ** /dev/ad0s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 591 files, 4501 used, 122338 free (242 frags, 15262 blocks, 0.2% fragmentation) ** /dev/ad0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 135486944 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 135486944, 135486945, 135486946, 135486947, 135486948, 135486949, 135486950, 135486951, 135486952, 135486953, 135486954, 135486955, 135486956, 135486957, 135486958, 135486959, 135486960, 135486961, 135486962, 135486963, 135486964, 135486965, 135486966, 135486967, 135486968, 135486969, 135486970, ** Phase 2 - Check Pathnames UNALLOCATED I=5049385 OWNER=squid MODE=100600 SIZE=15032 MTIME=Apr 1 21:07 2006 FILE=/local/squid/cache/00/26/26C2 UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=5049875 OWNER=squid MODE=100600 SIZE=10825 MTIME=Apr 1 21:07 2006 FILE=/local/squid/cache/00/26/26CA UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=5049896 OWNER=squid MODE=100600 SIZE=15008 MTIME=Apr 1 21:07 2006 FILE=/local/squid/cache/00/26/26D1 UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts LINK COUNT FILE I=5740857 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:09 2006 COUNT 0 SHOULD BE -1 ADJUST? no LINK COUNT FILE I=5792561 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:07 2006 COUNT 0 SHOULD BE -1 ADJUST? no LINK COUNT FILE I=5875155 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:09 2006 COUNT 0 SHOULD BE -1 ADJUST? no LINK COUNT FILE I=5970461 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:09 2006 COUNT 0 SHOULD BE -1 ADJUST? no ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? no ALLOCATED FRAGS 1936880-1936911 MARKED FREE ALLOCATED FRAGS 1936976-1936983 MARKED FREE BLK(S) MISSING IN BIT MAPS SALVAGE? no ALLOCATED FILE 5740857 MARKED FREE ALLOCATED FRAG 22922007 MARKED FREE ALLOCATED FILE 5792561 MARKED FREE ALLOCATED FILE 5856663 MARKED FREE ALLOCATED FILE 5875155 MARKED FREE ALLOCATED FRAG 23448111 MARKED FREE ALLOCATED FILE 5970461 MARKED FREE ALLOCATED FRAG 23889647 MARKED FREE ALLOCATED FILE 6077762 MARKED FREE ALLOCATED FRAG 24353503 MARKED FREE ALLOCATED FRAGS 26021808-26021813 MARKED FREE ALLOCATED FRAGS 26301688-26301690 MARKED FREE 1534559 files, 15746410 used, 21222026 free (2172530 frags, 2381187 blocks, 5.9% fragmentation) ** /dev/ad0s1d (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=8278 OWNER=mysql MODE=100600 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no UNREF FILE I=8301 OWNER=mysql MODE=100600 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no UNREF FILE I=8306 OWNER=mysql MODE=100600 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no UNREF FILE I=25696 OWNER=root MODE=140666 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no ** Phase 5 - Check Cyl groups 3681 files, 59732 used, 67107 free (1275 frags, 8229 blocks, 1.0% fragmentation) cat dmesg output ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102367
RE: Hard Disk problems
You'll probably want to reread the section in the Handbook on Moving to a Larger Disk, since this is a good time to rethink the sizes of your partitions. Sorry, this info is in FAQs 9.1 and 9.2 not in the Handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html -gayn Bristol Systems Inc. 714/532-6776 www.bristolsystems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Disk problems
On 3/4/06 2:49 AM, Gayn Winters [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] On Behalf Of Shane Ambler Sent: Saturday, April 01, 2006 3:10 AM To: FreeBSD Mailing Lists Subject: Hard Disk problems A few days ago I started getting some disk errors and can't seem to find a reference to find a way to fix them (other than the obvious re-format) The daily security run output contains the following (abbreviated) Checking setuid files and devices: find: /usr/ports/databases/db43/work/db-4.3.28/db: Input/output error find: /usr/ports/devel/git/Makefile: Input/output error ~ repeated 32 times for different files (thankfully all in the ports tree) tower.home.com kernel log messages: ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=139102367 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102367 These 2 error codes are repeated a total of 38 times all with the same LBA If I start in single user mode and do fsck it takes about half an hour to get through and repeats similar errors many times for just about every check it does. Running #fsck -y fsckout (while in multiuser mode) is as follows - followed by dmesg output since boot cat fsckout ** /dev/ad0s1a (NO WRITE) ** Last Mounted on / Snip ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102393 -- Shane Ambler Looks to me like your disk subsystem is dying. Most likely it is just the disk ad0. If you don't have a good backup, do that immediately. Get a new disk in there and test it thoroughly (with the manufacturer's diagnostics.) If all is well, restore to it. You'll probably want to reread the section in the Handbook on Moving to a Larger Disk, since this is a good time to rethink the sizes of your partitions. Incidentally, you can just install the new disk (as ad1), install FBSD on it, and dump|restore from ad0 to ad1. Once restored, you'll still have to clean up the damage. This is easier if your new new disk has a separate partition for user data, since you can use a fresh install of the OS, the ports, etc. and worry about repairing the user data as best you can. Good luck! -gayn Bristol Systems Inc. 714/532-6776 www.bristolsystems.com Thanks. I was kinda thinking that might be the case. Space isn't an issue (it's a 120GB drive) this is mostly a testing/learning server at home - runs squid and dns cache for home use (my other half does a lot of auto-surfing to try and make a few bucks) and apache/mysql for testing web devel. The files that showed up as i/o errors are all in /usr/ports so no probs there, I should be able to copy across what is readable to another drive without any problems or real loss and worthwhile data there is easy to replace. I am fairly new to *nix and was looking to see if I could learn more disaster recovery - thought there might be a chance that it was just bad sectors that weren't getting mapped out automagicaly and I could learn to fix it manually without reformatting. Now I know that if I see it happen again I should just replace the disk as soon as I can. -- Shane Ambler Sales Department 007Marketing.com [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 Disk problems
A few days ago I started getting some disk errors and can't seem to find a reference to find a way to fix them (other than the obvious re-format) The daily security run output contains the following (abbreviated) Checking setuid files and devices: find: /usr/ports/databases/db43/work/db-4.3.28/db: Input/output error find: /usr/ports/devel/git/Makefile: Input/output error ~ repeated 32 times for different files (thankfully all in the ports tree) tower.home.com kernel log messages: ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=139102367 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102367 These 2 error codes are repeated a total of 38 times all with the same LBA If I start in single user mode and do fsck it takes about half an hour to get through and repeats similar errors many times for just about every check it does. Running #fsck -y fsckout (while in multiuser mode) is as follows - followed by dmesg output since boot cat fsckout ** /dev/ad0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2259 files, 44188 used, 82651 free (251 frags, 10300 blocks, 0.2% fragmentation) ** /dev/ad0s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 591 files, 4501 used, 122338 free (242 frags, 15262 blocks, 0.2% fragmentation) ** /dev/ad0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 135486944 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 135486944, 135486945, 135486946, 135486947, 135486948, 135486949, 135486950, 135486951, 135486952, 135486953, 135486954, 135486955, 135486956, 135486957, 135486958, 135486959, 135486960, 135486961, 135486962, 135486963, 135486964, 135486965, 135486966, 135486967, 135486968, 135486969, 135486970, ** Phase 2 - Check Pathnames UNALLOCATED I=5049385 OWNER=squid MODE=100600 SIZE=15032 MTIME=Apr 1 21:07 2006 FILE=/local/squid/cache/00/26/26C2 UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=5049875 OWNER=squid MODE=100600 SIZE=10825 MTIME=Apr 1 21:07 2006 FILE=/local/squid/cache/00/26/26CA UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=5049896 OWNER=squid MODE=100600 SIZE=15008 MTIME=Apr 1 21:07 2006 FILE=/local/squid/cache/00/26/26D1 UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts LINK COUNT FILE I=5740857 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:09 2006 COUNT 0 SHOULD BE -1 ADJUST? no LINK COUNT FILE I=5792561 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:07 2006 COUNT 0 SHOULD BE -1 ADJUST? no LINK COUNT FILE I=5875155 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:09 2006 COUNT 0 SHOULD BE -1 ADJUST? no LINK COUNT FILE I=5970461 OWNER=squid MODE=0 SIZE=0 MTIME=Apr 1 21:09 2006 COUNT 0 SHOULD BE -1 ADJUST? no ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? no ALLOCATED FRAGS 1936880-1936911 MARKED FREE ALLOCATED FRAGS 1936976-1936983 MARKED FREE BLK(S) MISSING IN BIT MAPS SALVAGE? no ALLOCATED FILE 5740857 MARKED FREE ALLOCATED FRAG 22922007 MARKED FREE ALLOCATED FILE 5792561 MARKED FREE ALLOCATED FILE 5856663 MARKED FREE ALLOCATED FILE 5875155 MARKED FREE ALLOCATED FRAG 23448111 MARKED FREE ALLOCATED FILE 5970461 MARKED FREE ALLOCATED FRAG 23889647 MARKED FREE ALLOCATED FILE 6077762 MARKED FREE ALLOCATED FRAG 24353503 MARKED FREE ALLOCATED FRAGS 26021808-26021813 MARKED FREE ALLOCATED FRAGS 26301688-26301690 MARKED FREE 1534559 files, 15746410 used, 21222026 free (2172530 frags, 2381187 blocks, 5.9% fragmentation) ** /dev/ad0s1d (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=8278 OWNER=mysql MODE=100600 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no UNREF FILE I=8301 OWNER=mysql MODE=100600 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no UNREF FILE I=8306 OWNER=mysql MODE=100600 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no UNREF FILE I=25696 OWNER=root MODE=140666 SIZE=0 MTIME=Apr 1 19:13 2006 CLEAR? no ** Phase 5 - Check Cyl groups 3681 files, 59732 used, 67107 free (1275 frags, 8229 blocks, 1.0% fragmentation) cat dmesg output ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102367 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=139102368 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102369 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH LBA=139102370 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=1ILLEGAL_LENGTH
CF disk problems in 5-STABLE
(Please Cc: me on all replies.) I bought a USB CF reader/writer. When I plug it in, the system sees it as: kernel: umass0: VIA Technologies Inc. USB 2.0 Card Reader, rev 2.00/0.03, addr 2 but no matter what I do the system cannot see the CF disk in the unit. I then tried the same card in an older device: kernel: umass0: mediaGear Transport USB2.0 9 in 1 Reader , rev 2.00/1.28, addr 2 It sees the card just fine. I am able to fdisk the card and slice it up the way I want. (I still need to newfs it, but that's a job for tomorrow.) How difficult will it be to get the VIA dongle to work with FreeBSD? Harlan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Hard disk problems
On Jan 1, 2006, at 11:28 PM, Anthony M. Agelastos wrote: Hello all, In doing some routine items on my FreeBSD box, it started behaving oddly. I rebooted and to my surprise, I started receiving many messages displaying information regarding that /usr has issues. It puts me directly into single user mode and tells me to run fsck manually. When I run fsck all by itself, here is what it tells me: ** /dev/ad0s1f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=496000 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? [yn] This is the first time that I have ever run fsck and I have no idea what this message means or what the best course of action on CLEAR to take. Any input at all would be greatly appreciated (FreeBSD 6.0- STABLE if it helps). Thank you all so much for your assistance. -Anthony After not getting any feedback, I decided to do fsck -y This returned my machine to usable. Before doing this while I was just hitting y to the questions I did not understand, one of them mentioned that it had to create a lost+found directory and after a while that the directory was out of space. It asked me the question to expand. So, I hit yes. Anyways, after all is said and done, that filesystem has 500MB of more free space than it did before (it doesn't take into account the fact that /usr/src is now empty and the size of lost+found). What does the expand option do? Can I safely delete lost+found? Like I mentioned before, this is my first time in going through these types of issues and I have not found any documentation that I can fully understand on fsck and what it does. In any event, thank you all for your assistance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Hard disk problems
On Jan 2, 2006, at 10:31 AM, Anthony M. Agelastos wrote: On Jan 1, 2006, at 11:28 PM, Anthony M. Agelastos wrote: Hello all, In doing some routine items on my FreeBSD box, it started behaving oddly. I rebooted and to my surprise, I started receiving many messages displaying information regarding that /usr has issues. It puts me directly into single user mode and tells me to run fsck manually. When I run fsck all by itself, here is what it tells me: ** /dev/ad0s1f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=496000 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? [yn] This is the first time that I have ever run fsck and I have no idea what this message means or what the best course of action on CLEAR to take. Any input at all would be greatly appreciated (FreeBSD 6.0-STABLE if it helps). Thank you all so much for your assistance. -Anthony After not getting any feedback, I decided to do fsck -y This returned my machine to usable. Before doing this while I was just hitting y to the questions I did not understand, one of them mentioned that it had to create a lost+found directory and after a while that the directory was out of space. It asked me the question to expand. So, I hit yes. Anyways, after all is said and done, that filesystem has 500MB of more free space than it did before (it doesn't take into account the fact that /usr/src is now empty and the size of lost+found). What does the expand option do? Can I safely delete lost+found? Like I mentioned before, this is my first time in going through these types of issues and I have not found any documentation that I can fully understand on fsck and what it does. In any event, thank you all for your assistance. Also, what methods are there in backtracking what the cause of the errors could have been? How can I tell if there is something wrong with the hard disk (bad blocks that cannot be used anymore, etc.)? I suppose what I intend to gather by these questions is if this drive can still be trusted, or if I should start looking at getting a new one. Any insight would be appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help! Hard disk problems
Hello all, In doing some routine items on my FreeBSD box, it started behaving oddly. I rebooted and to my surprise, I started receiving many messages displaying information regarding that /usr has issues. It puts me directly into single user mode and tells me to run fsck manually. When I run fsck all by itself, here is what it tells me: ** /dev/ad0s1f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=496000 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? [yn] This is the first time that I have ever run fsck and I have no idea what this message means or what the best course of action on CLEAR to take. Any input at all would be greatly appreciated (FreeBSD 6.0- STABLE if it helps). Thank you all so much for your assistance. -Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk problems
Hi I'm having some problems with my FreeBSD 5.3 server, running on an AMD using IDE disks. The disk is having some problems: # dmesg ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986207 ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986335 ...cut... ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18973151 I'm suspecting some bad blocks, but how do i test for them, and mark them bad? I'm extremely new in FreeBSD so be gentle ;o) -- Sincerely yours Martin Kruse Jensen PixelPoint ___ 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
Martin Kruse Jensen [EMAIL PROTECTED] writes: I'm having some problems with my FreeBSD 5.3 server, running on an AMD using IDE disks. The disk is having some problems: # dmesg ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986207 ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986335 ...cut... ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18973151 I'm suspecting some bad blocks, but how do i test for them, and mark them bad? I'm extremely new in FreeBSD so be gentle ;o) What do I do when I have bad blocks on my hard drive? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#AWRE But in this case, it doesn't look like bad blocks to me. Much more like electronics problems. [Have you opened the case lately? Try replacing the ATA cable.] ___ 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
Back up those HD right now before you lose all the data and then replace them with new ones. There is nothing you can do with them in FreeBSD. Check the HD mfg web site for daig program which runs under ms/dos. But in most cases this daig program will just confirm HD has bad sectors and tell you to replace the bad HD with new one. Check mfg product warrantee, if HD is less than 3 years old mfg will swap your bad HD for new one. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Kruse Jensen Sent: Monday, May 23, 2005 1:22 PM To: freebsd-questions@freebsd.org Subject: Disk problems Hi I'm having some problems with my FreeBSD 5.3 server, running on an AMD using IDE disks. The disk is having some problems: # dmesg ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986207 ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986335 ...cut... ad0: FAILURE - READ_DMA timed out ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18973151 I'm suspecting some bad blocks, but how do i test for them, and mark them bad? I'm extremely new in FreeBSD so be gentle ;o) -- Sincerely yours Martin Kruse Jensen PixelPoint ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Weird disk problems
Heh, should've mentioned; I'm installing FreeBSD 5.3 Ulf Magnusson wrote: Today I decided to install FreeBSD, and so I grabbed a FreeBSD installation CD off the net. The first time I booted from the installation CD, everything went fine (seemingly), and I soon found myself in sysinstall. Not quite ready to install at that point, and needing to shut down the system, I quit sysinstall without having initiated any install or changed any settings (except maybe for the keymap, I can't remember). I returned later to commence the installation only to find that the boot process now hangs, the last message being GEOM configure ad0s1, start 32256 length 112785007104 end 112785039359 (verbose logging). I did not start my computer between the two occasions, and didn't change my hardware configuration either. Windows, which I have installed on the same disk (I shrunk the NTFS partition by 10 GiB using Partition Magic to make way for FreeBSD), still boots fine. Help appreciated, Ulf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Weird disk problems
Heh, should've mentioned: I'm installing FreeBSD 5.3-RELEASE. The disk only has one partition (and 10 GiB of unallocated space) right now by the way, and that's the one Window's on. ad0s1 should represent that partition if I'm reading the manual correctly. Ulf Magnusson wrote: Today I decided to install FreeBSD, and so I grabbed a FreeBSD installation CD off the net. The first time I booted from the installation CD, everything went fine (seemingly), and I soon found myself in sysinstall. Not quite ready to install at that point, and needing to shut down the system, I quit sysinstall without having initiated any install or changed any settings (except maybe for the keymap, I can't remember). I returned later to commence the installation only to find that the boot process now hangs, the last message being GEOM configure ad0s1, start 32256 length 112785007104 end 112785039359 (verbose logging). I did not start my computer between the two occasions, and didn't change my hardware configuration either. Windows, which I have installed on the same disk (I shrunk the NTFS partition by 10 GiB using Partition Magic to make way for FreeBSD), still boots fine. Help appreciated, Ulf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Weird disk problems
Today I decided to install FreeBSD, and so I grabbed a FreeBSD installation CD off the net. The first time I booted from the installation CD, everything went fine (seemingly), and I soon found myself in sysinstall. Not quite ready to install at that point, and needing to shut down the system, I quit sysinstall without having initiated any install or changed any settings (except maybe for the keymap, I can't remember). I returned later to commence the installation only to find that the boot process now hangs, the last message being GEOM configure ad0s1, start 32256 length 112785007104 end 112785039359 (verbose logging). I did not start my computer between the two occasions, and didn't change my hardware configuration either. Windows, which I have installed on the same disk (I shrunk the NTFS partition by 10 GiB using Partition Magic to make way for FreeBSD), still boots fine. Help appreciated, Ulf ___ 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]
Hard Disk problems when installing FreeBSD 5.3BETA7
{REVISED POST}
Hello experts,
I have experienced so much problems installing FreeBSD 5.3BETA7 I guess
it's time for me to ask the experts.
I have two disks:
1. Maxtor (DiamondMax Plus 9)
120GB ATA/133
Mfg Date: 30 Jan 2004
Code: YAR41BW0
E-H011-02-3880 (3.5 SERIES)
2. Western Digital (WD800) EIDE Drive
80GB
WD Caviar
MDL: WD800LB-00DNA0
Mfg Date: 19 Jan 2004
DCM: HSBHCVJAH
Motherboard: VIA VT8233.
Those are as much as I can read on the disks.
Now my woes:
I have tried more than 20 times installing FreeBSD 5.3 on these disks.
I have tried this since 5.3BETA1 all the way to 5.3BETA7, hoping at
each stage that I will get lucky.
Always things fail. After the disk label stage, I choose the minimal
distro and commit. That is when I get the message that I must create
at least the root and swap partitions.
Ordinarily, I want to install like this (take the 80GB disk):
74GB = /
2GB = swap
What I am presented with is just 76GB.
Even for the 120 GB disk:
112GB = /
2GB = swap
Here what I am presented with is 114GB.
The reason I want to partition like that is because I have another old
box with 36GB that kinda I managed to install 5.3 on. It's now running
5.3-RELEASE and it was partitioned the same way. I simply want to tar
it up, move the tarball to my problematic box and extract, then change
a few things in fstab and rc.conf and have a machine to enjoy!
Note that during labelling, I have even used the Auto option. The
thing still fails when it comes to newfs!!!
I have left the BIOS setting as AUTO as well as LBA.
I have even changed the disk geometry on the partition editor to match
what the BIOS thinks is correct.
I have even attempted to manually commit my changes at the disk label
stage.
Whatever I do, the installation does not succeed! I sometimes end up
installing, but when it comes to mounting the root partition on reboot
(after install finishes), the thing fails.
I have even flashed my Award BIOS by getting latest firmware from
esupport.com and US $25.
That is how much I would like to run 5.3.
Do I get any errors at all?
On Main Console:
No root device found - you must label a partition as / in the label
editor
[I press Enter]
No swap devices found - you should create at least one sap partition
blah ..
[I press Enter again]
Couldn't make filesystems properly. Aborting.
On vtys - Alt+F2:
DEBUG: ioctl (3, TIOCCONS, NULL) = 0 (Success)
DEBUG: Add mapping for /dev/cuaa0 to sl0
DEBUG: Add mapping for /dev/cuaa1 to sl0
DEBUG: Scanning disk ad0 for root filesystem
DEBUG: Scanning disk ad0 for swap partitions
And that's it. I have checked all the vtys, and the msg is the same.
Someone please tell me that this has nothing to do with the BIOS at all.
Winblows apparently has no problems at all installing on these disks,
but I hate to use Microshit as a yard stick.
What shall I do???
-Wash
http://www.netmeister.org/news/learn2quote.html
--
+==+
|\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED]
Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com
|,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922
'---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121
+==+
Hindsight is an exact science.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk Problems
In which log file should I look to find disk error messages, and which variable controls the log level for this kind of Problems (if there is any) Background. I have FreeBSD 5.2.1-RELEASE-p11 running and serving my windows client a few samba shares. (2 shares from 2 physicaly different disks to be exact) Now when I safe something from a Firefox session running on the Windows machine to samba share 1 my Firefox slows to a crawl. I suspect that the Disk share 1 is located on is faulty because I do not experience any strange behavior when saving to another disk (including share 2) I have cranked the Samaba Log variable up and got this error messages: - [2004/10/27 22:28:45, 3] smbd/error.c:error_packet(113) error packet at smbd/trans2.c(1721) cmd=50 (SMBtrans2) NT_STATUS_OBJECT_NAME_NOT_FOUND [2004/10/27 22:28:45, 3] smbd/error.c:error_packet(113) error packet at smbd/trans2.c(1042) cmd=50 (SMBtrans2) NT_STATUS_NO_SUCH_FILE - Thx for any help Hexren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb v1.1 external 2.0 hard disk problems with FreeBSD 5.1-RELEASE
Jesse Guardiani wrote: Howdy list, I'm running FreeBSD 5.1-RELEASE. I just bought a generic USB 1.1/2.0/firewire external drive enclosure for my 32gb Travelstar 12.5mm hard drive. The device shows up like this: Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Storage Device, rev 2.00/1.03, addr 3 Nov 18 14:06:16 trevarthan kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 18 14:06:17 trevarthan kernel: da0: USB 2.0 Storage Device 0100 Fixed Direct Access SCSI-0 device Nov 18 14:06:17 trevarthan kernel: da0: 1.000MB/s transfers Nov 18 14:06:17 trevarthan kernel: da0: 30520MB (62506080 512 byte sectors: 255H 63S/T 3890C) But `ls -al /dev/da*` reveals no slices: crw-r- 1 root operator4, 22 Nov 18 13:35 /dev/da0 The hard disk inside this enclosure was formatted with a 10gig FAT32 partition. It works fine in a Coolmax Gemini 2.5 USB 2.0/1.1 drive enclosure, and it works fine in this enclosure as long as I'm running Windows XP. But it just doesn't want to work under FreeBSD 5.1-RELEASE for some reason... Does anyone have any clues to help get this drive working? Anyone? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
usb v1.1 external 2.0 hard disk problems with FreeBSD 5.1-RELEASE
Howdy list, I'm running FreeBSD 5.1-RELEASE. I just bought a generic USB 1.1/2.0/firewire external drive enclosure for my 32gb Travelstar 12.5mm hard drive. The device shows up like this: Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Storage Device, rev 2.00/1.03, addr 3 Nov 18 14:06:16 trevarthan kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 18 14:06:17 trevarthan kernel: da0: USB 2.0 Storage Device 0100 Fixed Direct Access SCSI-0 device Nov 18 14:06:17 trevarthan kernel: da0: 1.000MB/s transfers Nov 18 14:06:17 trevarthan kernel: da0: 30520MB (62506080 512 byte sectors: 255H 63S/T 3890C) But `ls -al /dev/da*` reveals no slices: crw-r- 1 root operator4, 22 Nov 18 13:35 /dev/da0 The hard disk inside this enclosure was formatted with a 10gig FAT32 partition. It works fine in a Coolmax Gemini 2.5 USB 2.0/1.1 drive enclosure, and it works fine in this enclosure as long as I'm running Windows XP. But it just doesn't want to work under FreeBSD 5.1-RELEASE for some reason... Does anyone have any clues to help get this drive working? Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PICOBSD /dev/mdxx memory disk problems
Dear Sirs. I use FreeBSD 5.0-CURRENT on several experimental systems. I try to test new diskless and picobsd facilities and abilities of the newest FBSD 5.0-CURRENT stuff and I am a little bit disappointed. First there is a little bug in the picobsd shell-script/command: newfs does no longer support option '-p', so this runs into a failure. When buidling a picobsd image I get this error: ---snap *** init_fs_image() /usr/src/release/picobsd/build_dir-bastion/fs.PICOBSD 8192 *** Labeling MFS image *** Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md1c 79830 7983 0%/var/tmp/picobsd.S98gZK4mQz *** Copy mfs tree into file *** Status of mfs image Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md1c 7983 1458 652518% 81 10697% /var/tmp/picobsd.S98gZK4mQz fsck: exec /usr/sbin/fsck_4.2BSD for /dev/md1c: No such file or directory Warning: creating filesystem that does not conform to ISO-9660. --- snap The last warning is due to several special mkisofs options that are not conform. Important is the failure of building the MFS filesystem. It seems that /dev/md1c is really present, but when fsck tries to check it, it gets an error. I have a similar error on diskless boot process in FreeBSD 5.0-CURRENT, where obviously no memory disk can be created. Can someon verify or falsify these oberservations? Thanks a lot ... Oliver -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk Problems
Dmitry, If you have the smart start CD that came with the server, it will have those utiliies on it. If you do not, I suggest that you visit Compaq/HP's web site, download the CD, burn it and use that. It contains a utility to create a system partition on one of the drives. I HIGHLY recommend doing this on ANY Compaq server that you have. It gives you access to all sorts of diagnostic and repair tools that are designed to talk to things like your BIOS, the firmware on your System Board, RAID controller, RIBLOE, and even your hard drives. Thanks, Ms. Jimi Thompson Those who are too smart to engage in politics are punished by being governed by those who are dumber. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dmitry Ternovoy Sent: Monday, December 23, 2002 9:50 AM To: [EMAIL PROTECTED] Subject: it is IDE. As it all the same to make? (Disk low level format or other format) 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
