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
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]
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]
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]
