Re: OT: Installing 9.1 without re-partitioning hard drive
On Mon, 18 Mar 2013, Ralf Mardorf wrote: On Mon, 2013-03-18 at 09:00 -0600, Warren Block wrote: On Mon, 18 Mar 2013, Ralf Mardorf wrote: Standard practice for this list is to Cc the responder and the list, because people are not required to subscribe to post. That makes sense and does explain why my last mail came through the list, while my broken MUA didn't use the address, I used to subscribe to this list. So a smarter MUA should provide different reply settings for replying to different lists. I should take a look at the mailman settings, since at the moment I receive 2 mails in case of Cc'ing, IIRC this can be disabled. Mailing list settings may not help, since it's really up to the sender. But it's easy to filter out duplicates with maildrop or procmail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
OT: Installing 9.1 without re-partitioning hard drive
On Sun, 2013-03-17 at 15:37 -0700, leeoliveshackelf...@surewest.net wrote: Please Cc responses to the mailing list I know that it's tolerated by the FreeBSD lists, but for most mailing lists nowadays it's common to reply to the list only. Most MUA nowadays provide an option to automatically reply to the list only. So IMO even for this list the advice should at least be, _if possible_ reply to the list only, if you want receive a copy directly, than ask the OP reply to the list and (carbon copy) me, but don't address it to somebody else. 2 Cents, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OT: Installing 9.1 without re-partitioning hard drive
On Mon, 18 Mar 2013, Ralf Mardorf wrote: On Sun, 2013-03-17 at 15:37 -0700, leeoliveshackelf...@surewest.net wrote: Please Cc responses to the mailing list Actually, I had written that in a reply. I know that it's tolerated by the FreeBSD lists, but for most mailing lists nowadays it's common to reply to the list only. Most MUA nowadays provide an option to automatically reply to the list only. So IMO even for this list the advice should at least be, _if possible_ reply to the list only, if you want receive a copy directly, than ask the OP reply to the list and (carbon copy) me, but don't address it to somebody else. Standard practice for this list is to Cc the responder and the list, because people are not required to subscribe to post. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OT: Installing 9.1 without re-partitioning hard drive
On Mon, 2013-03-18 at 09:00 -0600, Warren Block wrote: On Mon, 18 Mar 2013, Ralf Mardorf wrote: Standard practice for this list is to Cc the responder and the list, because people are not required to subscribe to post. That makes sense and does explain why my last mail came through the list, while my broken MUA didn't use the address, I used to subscribe to this list. So a smarter MUA should provide different reply settings for replying to different lists. I should take a look at the mailman settings, since at the moment I receive 2 mails in case of Cc'ing, IIRC this can be disabled. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OT: Installing 9.1 without re-partitioning hard drive
On Mon, Mar 18, 2013 at 09:15:43AM +0100, Ralf Mardorf wrote: On Sun, 2013-03-17 at 15:37 -0700, leeoliveshackelf...@surewest.net wrote: Please Cc responses to the mailing list I know that it's tolerated by the FreeBSD lists, but for most mailing lists nowadays it's common to reply to the list only. Most MUA nowadays provide an option to automatically reply to the list only. As a matter of fact, on the FreeBSD Questions list it is recommended to send to both the poster and the list. On this list it is not required to be subscribed to post. It is an open list. jerry So IMO even for this list the advice should at least be, _if possible_ reply to the list only, if you want receive a copy directly, than ask the OP reply to the list and (carbon copy) me, but don't address it to somebody else. 2 Cents, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: Re: Installing 9.1 without re-partitioning hard drive
---BeginMessage--- On Sat, 16 Mar 2013, leeoliveshackelf...@surewest.net wrote: Dear Mr. Block, Greetings. Thank you for your response to my message. Your instruction to change the name of the disk drive from ah0 to aha0 worked. I can now boot FreeBSD. The next trick will be to attempt to load X-windows, then gnome. Even in man gpart, some paragraphs refer to the first disk drive as ah0, while other paragraphs refer to the first disk drive as aha0. Currently, I am trying to determine how to change my login shell to BASH. I get the error message that BASH is not an approved shell. (Apparently, I must somehow download it from some unspecified place.) Please Cc responses to the mailing list, so others can help and learn. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html about installing applications. All of these applications are available in ports. ---End Message--- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Installing 9.1 without re-partitioning hard drive
On Fri, 15 Mar 2013, leeoliveshackelf...@surewest.net wrote: Good evening, Free BSD enthusiasts. Thank you to each of the several people who have responded to my previous messages. I have made significant progress, but am now flummoxed at the installation of the boot loader. The handbook says to run this command, boot0cfg -B ad0. When I run this command, I get the following error message: Unable to get providername for ad0. This message means there is no disk called ad0. On FreeBSD 9.x, it is likely to be called ada0 instead. I can't find that command in the Handbook. Could you please point out where it is? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installing 9.1 without re-partitioning hard drive
Good evening, Free BSD enthusiasts. Thank you to each of the several people who have responded to my previous messages. I have made significant progress, but am now flummoxed at the installation of the boot loader. The handbook says to run this command, boot0cfg -B ad0. When I run this command, I get the following error message: Unable to get providername for ad0. What is a provider name? How do I determine the provider name for ad0? How do I communicate that information to boot0cfg? I know that this problem has something to do with the geom command, but the man geom goes on for many pages. While I think the answer may be in there somewhere, I could not find it. Any and all comments will be appreciated. Sincerely, Newby Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Installing 9.1 without re-partitioning hard drive
Hi, On Fri, 15 Mar 2013 20:11:24 -0700 (PDT) leeoliveshackelf...@surewest.net wrote: Good evening, Free BSD enthusiasts. Thank you to each of the several good morning, people who have responded to my previous messages. I have made significant progress, but am now flummoxed at the installation of the this is good to hear. boot loader. The handbook says to run this command, boot0cfg -B ad0. When I run this command, I get the following error message: Unable to get providername for ad0. What is a provider name? How do I determine the provider name for ad0? How do I communicate that information to boot0cfg? I know that this problem has something to do with the geom command, but the man geom goes on for many pages. While I think the answer may be in there somewhere, I could not find it. Any and all comments will be appreciated. Sincerely, Newby Lee ad0? This sounds like that it would overwrite the loader from your Windows installation. Did you read man gpart? gpart should be able to show you the current layout of the disk. It is also able to install the boot code you need. If I remember, you want to have Windows and FreeBSD on the same disk. So, you should have some kind of boot manager which will give you the choice between them. Of course, you can use whatever boot manager you want. The one which comes with FreeBSD is a bit simple but does its job. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installing 9.1 without re-partitioning hard drive
Good afternoon, FreeBSD enthusiasts. I am attempting to install FreeBSD 9.1 on a dual-boot configuration with Windows XP. I am using bsdinstall. I do not wish for the partition table to be changed. How do I instruct bsdinstall to skip the re-partitioning step? It gives an error message that it cannot write a certain file because the medium is write-only. Any suggestions would be appreciated. Yours truly, Newby Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Installing 9.1 without re-partitioning hard drive
On Mar 15, 2013 12:48 AM, leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. I am attempting to install FreeBSD 9.1 on a dual-boot configuration with Windows XP. I am using bsdinstall. I do not wish for the partition table to be changed. How do I instruct bsdinstall to skip the re-partitioning step? It gives an error message that it cannot write a certain file because the medium is write-only. Any suggestions would be appreciated. Yours truly, Newby Lee You're trying to install to your windows partition, that won't work. You need free space on the drive which implies shrinking your existing partition. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Installing 9.1 without re-partitioning hard drive
Hi Lee, One option to have a FreeBSD system on winxp, without any partitioning to the existing hard disk, is to have freebsd as a vm on virtualbox. For having a dual boot system you would need to partition the existing disk . If you have a second had disk you could select it and let FreeBSD partition it with the default configuration using Entire Disk . The FreeBSD handbook should help you http://www.freebsd.org/doc/handbook/bsdinstall-partitioning.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#windows-coexist Bejoy Thomas On 15-Mar-2013, at 5:14 AM, leeoliveshackelf...@surewest.net leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. I am attempting to install FreeBSD 9.1 on a dual-boot configuration with Windows XP. I am using bsdinstall. I do not wish for the partition table to be changed. How do I instruct bsdinstall to skip the re-partitioning step? It gives an error message that it cannot write a certain file because the medium is write-only. Any suggestions would be appreciated. Yours truly, Newby Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installing 9.1 without re-partitioning hard drive
Good afternoon, FreeBSD enthusiasts. I am attempting to install FreeBSD 9.1 on a dual-boot configuration with Windows XP. I am using bsdinstall. I do not wish for the partition table to be changed. How do I instruct bsdinstall to skip the re-partitioning step? It gives an error message that it cannot write a certain file because the medium is write-only. Any suggestions would be appreciated. Yours truly, Newby Lee I forgot to mention some additional facts: The FreeBSD operating system is being installed from a d.v.d. I partitioned the hard drive into two equal partitions before re-installing Windows XP. Also, the following cryptic instruction was given to me by the bsdinstall program: When finished, mount the system at /mnt and place an fstab file for the new system at tmp/bsdinstall_etc/fstab. Then type exit. Please, can anyone explain to me what this instruction is telling me to do, and give me some details as to how to perform these tasks? Perhaps, also explain to me why I am supposed to do these things? How do I mount the system at /mnt? How do I compose an fstab file? How do I place the fstab file at tmp/bsdinstall_etc/fstab, a directory that does not exist until the filesystem is built? If the answers to any of these questions are explained in writing anywhere, please tell me where to look. Thank you. Again, yours truly, Newby Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Installing 9.1 without re-partitioning hard drive
Lee, Are you using DOS-style or GPT partitions? I'm assuming DOS-style, and the rest of this email is only correct if that's the case, so correct me if I'm wrong. There's actually two partition tables at work here -- the big one, that lives at the start of the physical disk and divides up the FreeBSD from the Windows. Inside the FreeBSD slice (slice, partition, same thing, but just to be clear, call it a slice) there's going to be *another* partition table, to divide up the FreeBSD partitions amongst themselves. At a bare minimum you're going to have two partitions (which are really sub-partitions at this point), root and swap. Maybe even more. So it seems to me like, if you can get to the point where the FreeBSD installer recognizes the slice you've set aside for it, as its own, then you can let it rewrite the partition table *inside that slice* as much as it wants to. OK? Make sense? You just don't want it to touch the *outer* one. I honestly don't know enough about how the boot blocks work to know if that's going to work, in the end. You might still end up having to say yes to let it install FreeBSD boot blocks -- I don't know. But it seems to me like a prerequisite, in any case, is going to be to set the FreeBSD partition to partition type 165, so that the installer will recognize it as a FreeBSD slice. Is it already partition type 165? If not, can you make it type 165 and see if that changes anything? ~Ben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot-time hard drive errors
This is not very helpful, but you can try Pause, Scroll Lock, high FPS filming and pause or taking pictures with short exposure. On Mon, Feb 25, 2013 at 6:20 AM, Martin Alejandro Paredes Sanchez mapsw...@prodigy.net.mx wrote: On Sunday 24 February 2013 14:33:06 Ronald F. Guilmette wrote: I have a somewhat eclectic system, currently running (or at any rate, trying to run) 9.1-RELEASE. The system in question contains three drives, to wit: WDC WD1002FAEX-00Z3A0 05.01D05 ATA-8 SATA 3.x device ST3500320AS SD1A ATA-8 SATA 1.x device Hitachi HTS541010A9E680 JA0OA480 ATA-8 SATA 3.x device Previously, I had the ST3500320AS in this system, along with one other entirely different Seagate drive, i.e. one not shown in the list above. (Also, I was previously running 8.3-RELEASE and only recently updated to 9.1-RELEASE.) Since I reconfigured the system to its current state, i.e. with the set of three drives listed above, whenever I reboot the system, about 50% of the time, when the boot process gets down to the point where it would ordinarily be printing out the messages relating to ada0, ada1, etc. suddenly I start to get a massive and apparently endless stream of error messages, apparently relating to one of the drives listed above, but the stream actually alternates between two consecutive error messages, both undoubtedly related to each other. Does your HDD controller is SATA 3? I had a similar problem (some times could not boot) and was caused because my HDD controller is SATA 1 Intel ICH5 SATA150 controller And my hard disk is SATA 2 WDC WD2500AVVS-00L2B0 01.03A01 The problem disapear when I lock the HDD at 150 MB/s (jumper settings the HDD to SATA 1) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Boot-time hard drive errors
I have a somewhat eclectic system, currently running (or at any rate, trying to run) 9.1-RELEASE. The system in question contains three drives, to wit: WDC WD1002FAEX-00Z3A0 05.01D05 ATA-8 SATA 3.x device ST3500320AS SD1A ATA-8 SATA 1.x device Hitachi HTS541010A9E680 JA0OA480 ATA-8 SATA 3.x device Previously, I had the ST3500320AS in this system, along with one other entirely different Seagate drive, i.e. one not shown in the list above. (Also, I was previously running 8.3-RELEASE and only recently updated to 9.1-RELEASE.) Since I reconfigured the system to its current state, i.e. with the set of three drives listed above, whenever I reboot the system, about 50% of the time, when the boot process gets down to the point where it would ordinarily be printing out the messages relating to ada0, ada1, etc. suddenly I start to get a massive and apparently endless stream of error messages, apparently relating to one of the drives listed above, but the stream actually alternates between two consecutive error messages, both undoubtedly related to each other. The boot process never completes, and I am just left staring at a screen that's displaying, in very rapid succession, first the one error message and then the other, and then the first one again, and then the second one again, and on and on like that. Unfortunately, the two error messages are being printed on the screen so fast (and alternating, as described above) that I cannot even read them, but I could just barely make out that they seem to relate to ada2... well, anyway, one or another of the hard drives. I do not know the proper way to rectify whatever is causing these flaky errors. I use the term flaky because, as I have said, this boot-time problem only seems to occur maybe about 50% of the time, and the rest of the time when I boot up there is no problem whatsoever. Because I am able to boot up successfully, with no problems whatsoever, a significant fraction of the time, I am inclined to think that whatever is causing the failure is not actually a hardware fault. (And by the way, the WDC drive and the Hitachi drive are both practically brand new. That doesn't prove anything, of course, but it does make me think that they are unlikely to have serious hardware faults.) I would report this problem by filing a standard PR, but as I've said above, I can't even read the error messages, because they are being printed in such rapid succession, so I'm not sure that filing a PR would be useful to anybody. I mean what would it say? That I'm getting some unspecified failure at boot time that seems to relate to the hard drives in this system? That kind of PR would clearly not be very helpful. Has anyone else ever encountered symptoms like those I have listed above, either with 9.1-RELEASE or with any other version of FreeBSD? Regards, rfg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot-time hard drive errors
Have you tried Pause/Break to see if you could feeze the screen to get the error message? I would stress test all three drives to see if they pass with flying colors. One or more of your drives could be indeed flaky, regardless being new, that means little. Also, something could be conflicting from time to time, that could also show up under stress testing. Make backup if you have important data before stress testing. -Simon On Sun, 24 Feb 2013 13:33:06 -0800, Ronald F. Guilmette wrote: I have a somewhat eclectic system, currently running (or at any rate, trying to run) 9.1-RELEASE. The system in question contains three drives, to wit: WDC WD1002FAEX-00Z3A0 05.01D05 ATA-8 SATA 3.x device ST3500320AS SD1A ATA-8 SATA 1.x device Hitachi HTS541010A9E680 JA0OA480 ATA-8 SATA 3.x device Previously, I had the ST3500320AS in this system, along with one other entirely different Seagate drive, i.e. one not shown in the list above. (Also, I was previously running 8.3-RELEASE and only recently updated to 9.1-RELEASE.) Since I reconfigured the system to its current state, i.e. with the set of three drives listed above, whenever I reboot the system, about 50% of the time, when the boot process gets down to the point where it would ordinarily be printing out the messages relating to ada0, ada1, etc. suddenly I start to get a massive and apparently endless stream of error messages, apparently relating to one of the drives listed above, but the stream actually alternates between two consecutive error messages, both undoubtedly related to each other. The boot process never completes, and I am just left staring at a screen that's displaying, in very rapid succession, first the one error message and then the other, and then the first one again, and then the second one again, and on and on like that. Unfortunately, the two error messages are being printed on the screen so fast (and alternating, as described above) that I cannot even read them, but I could just barely make out that they seem to relate to ada2... well, anyway, one or another of the hard drives. I do not know the proper way to rectify whatever is causing these flaky errors. I use the term flaky because, as I have said, this boot-time problem only seems to occur maybe about 50% of the time, and the rest of the time when I boot up there is no problem whatsoever. Because I am able to boot up successfully, with no problems whatsoever, a significant fraction of the time, I am inclined to think that whatever is causing the failure is not actually a hardware fault. (And by the way, the WDC drive and the Hitachi drive are both practically brand new. That doesn't prove anything, of course, but it does make me think that they are unlikely to have serious hardware faults.) I would report this problem by filing a standard PR, but as I've said above, I can't even read the error messages, because they are being printed in such rapid succession, so I'm not sure that filing a PR would be useful to anybody. I mean what would it say? That I'm getting some unspecified failure at boot time that seems to relate to the hard drives in this system? That kind of PR would clearly not be very helpful. Has anyone else ever encountered symptoms like those I have listed above, either with 9.1-RELEASE or with any other version of FreeBSD? Regards, rfg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot-time hard drive errors
On Sunday 24 February 2013 14:33:06 Ronald F. Guilmette wrote: I have a somewhat eclectic system, currently running (or at any rate, trying to run) 9.1-RELEASE. The system in question contains three drives, to wit: WDC WD1002FAEX-00Z3A0 05.01D05 ATA-8 SATA 3.x device ST3500320AS SD1A ATA-8 SATA 1.x device Hitachi HTS541010A9E680 JA0OA480 ATA-8 SATA 3.x device Previously, I had the ST3500320AS in this system, along with one other entirely different Seagate drive, i.e. one not shown in the list above. (Also, I was previously running 8.3-RELEASE and only recently updated to 9.1-RELEASE.) Since I reconfigured the system to its current state, i.e. with the set of three drives listed above, whenever I reboot the system, about 50% of the time, when the boot process gets down to the point where it would ordinarily be printing out the messages relating to ada0, ada1, etc. suddenly I start to get a massive and apparently endless stream of error messages, apparently relating to one of the drives listed above, but the stream actually alternates between two consecutive error messages, both undoubtedly related to each other. Does your HDD controller is SATA 3? I had a similar problem (some times could not boot) and was caused because my HDD controller is SATA 1 Intel ICH5 SATA150 controller And my hard disk is SATA 2 WDC WD2500AVVS-00L2B0 01.03A01 The problem disapear when I lock the HDD at 150 MB/s (jumper settings the HDD to SATA 1) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hard drive LED always on
I've got an issue, that regarding to http://forums.freebsd.org/showthread.php?t=13467 is an issue for several users. Since I've got to fix many other issues, ALSA doesn't work, the GUI of QjackCtl does behave strange, Ardour 2 doesn't build, only 2 IOs are available for the sound card, by OSS using the snd_hdspe driver etc., I wonder if I can ignore the LED. As long as the LED only will give light and it shouldn't cause serious issues, such as data loss, it's ok for me. Until now it seems not to cause serious issues. Is it safe to ignore it, to keep i as is? Regards, Ralf -- FreeBSD 9.1-RELEASE amd64 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Do I need to use sysutils/ataidle to avoid high LCC for my hard drive?
On 8 October 2012 08:14, Denise H. G. darc...@gmail.com wrote: Hi list. I am currently running FreeBSD 9.1-PRERELEASE on my laptop. And I am wondering if I still need to use sysutiles/ataidle to avoid high Load Cyle Count for my hard drive. Is there still a need to run this utility to avoid LCC under FreeBSD 9.1-PRERELEASE? I believe so, as my Load Cycle Count still increments fairly quickly when let. Though as long as you have options ATA_CAM (it appears to be in GENERIC, so you should, I suppose) you can also use variations on: /sbin/camcontrol cmd ada0 -a EF 85 00 00 00 00 00 00 00 00 00 00 to shut off naps such as well. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Do I need to use sysutils/ataidle to avoid high LCC for my hard drive?
Hi list. I am currently running FreeBSD 9.1-PRERELEASE on my laptop. And I am wondering if I still need to use sysutiles/ataidle to avoid high Load Cyle Count for my hard drive. Is there still a need to run this utility to avoid LCC under FreeBSD 9.1-PRERELEASE? Thanks for your attention! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.2 Add second hard drive multi-boot
Good morning, FreeBSD enthusiasts. On my Hewlett-Packard xw4400 workstation, I had one hard drive. I partitioned it with two slices, the first one for FreeBSD 8.2 with its native file system, and the second one for a future re-installation of Windows XP, to be formatted with NTFS file system. FreeBSD 8.2 was then installed. The Windows XP re-installation has not yet taken place. Recently, I installed a second hard drive on the machine that was already formatted with two slices, both NTFS. Already installed on the first of these slices is the Windows XP operating system with a special application program. Already installed on the second slice is data. It is my understanding that the FreeBSD loader is supposed to be able to load any operating system. Upon power-up, the FreeBSD loader presents the following screen: F1 Win F2 FreeBSD F5 Drive 1 F6 PXE If I depress F1, I receive the response BOOTMGR is missing. Press Ctrl+Alt+Del to restart. If I depress F2, FreeBSD loads normally. If I depress F5, I receive the response Missing operatin system. How can I get the FreeBSD loader to load the Windows XP operating system from the second hard drive? The G.P.T. disklabel is not used by either of these operating systems, so I do not believe that that is the problem. Although the FreeBSD operating system seems to see the second hard drive, it does not mount it upon startup. It does not appear in the fstab file. I attempted to mount it manually using the mount command, without success, just to see if any of the data files could be read. I ran fsidk -B on the zeroeth sector of the second hard drive, but that did not seem to help. I know that this type of issue comes up repeatedly in the mailing lists, some of which I have read, but I am flummoxed. Any and all suggestions would be appreciated. Your truly, Lee Shackelfo r! d ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.2 Add second hard drive multi-boot
On Thu, Jun 21, 2012 at 09:59:19AM -0700, leeoliveshackelf...@surewest.net wrote: You need to put the FreeBSD boot manager on both disks. Use bootcfg. jerry Good morning, FreeBSD enthusiasts. On my Hewlett-Packard xw4400 workstation, I had one hard drive. I partitioned it with two slices, the first one for FreeBSD 8.2 with its native file system, and the second one for a future re-installation of Windows XP, to be formatted with NTFS file system. FreeBSD 8.2 was then installed. The Windows XP re-installation has not yet taken place. Recently, I installed a second hard drive on the machine that was already formatted with two slices, both NTFS. Already installed on the first of these slices is the Windows XP operating system with a special application program. Already installed on the second slice is data. It is my understanding that the FreeBSD loader is supposed to be able to load any operating system. Upon power-up, the FreeBSD loader presents the following screen: F1 Win F2 FreeBSD F5 Drive 1 F6 PXE If I depress F1, I receive the response BOOTMGR is missing. Press Ctrl+Alt+Del to restart. If I depress F2, FreeBSD loads normally. If I depress F5, I receive the response Missing operatin system. How can I get the FreeBSD loader to load the Windows XP operating system from the second hard drive? The G.P.T. disklabel is not used by either of these operating systems, so I do not believe that that is the problem. Although the FreeBSD operating system seems to see the second hard drive, it does not mount it upon startup. It does not appear in the fstab file. I attempted to mount it manually using the mount command, without success, just to see if any of the data files could be read. I ran fsidk -B on the zeroeth sector of the second hard drive, but that did not seem to help. I know that this type of issue comes up repeatedly in the mailing lists, some of which I have read, but I am flummoxed. Any and all suggestions would be appreciated. Your truly, Lee Shackelfo r! d ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.2 Add second hard drive multi-boot
On Thu, 21 Jun 2012 09:59:19 -0700 (PDT), leeoliveshackelf...@surewest.net wrote: Although the FreeBSD operating system seems to see the second hard drive, it does not mount it upon startup. FreeBSD won't mount anything until explicitely told so. Check the output of dmesg (e. g. dmesg | grep ^ad or dmesg | grep ^da) for the drive designation and issue the command yourself. If everything works, you can add an entry to /etc/fstab to make it mount on startup, e. g. # device target type options d p # -- - - - /dev/ad1s1 /xp/system ntfs ro,noauto 0 0 /dev/ad1s2 /xp/data ntfs ro,noauto 0 0 It might be worth applying other options like -M (mask) to have the missing attributes and misinterpretation as executables of NTFS file systems corrects. See the manual for details. It does not appear in the fstab file. This file is not generated automatically. It's an entirely user serviceable part of the OS. I attempted to mount it manually using the mount command, without success, just to see if any of the data files could be read. Can you show the mount command? I think it will be something like # mount_ntfs -o ro /dev/ad1s1 /mnt If you need write access, ntfs3g / FUSE would be a good tool. Also see the port ntfsprogs which contains useful tools for dealing with NTFS. I ran fsidk -B on the zeroeth sector of the second hard drive, but that did not seem to help. You need to apply boot0cfg to install the initial boot blocks. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
On Thu, Jan 5, 2012 at 7:16 PM, Bill Tillman btillma...@yahoo.com wrote: Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. ... Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. ... So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Hi Bill, What was going on with this drive before the install? ie, it was sitting on the self not being used, it was a daily use machine running something else, ... etc. At the moment it sounds to me like an inconvenient hardware failure. Waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
From: Waitman Gobble gobble...@gmail.com To: Bill Tillman btillma...@yahoo.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Sent: Friday, January 6, 2012 5:09 AM Subject: Re: 9.0-RELEASE amd64 Bricked My Hard Drive On Thu, Jan 5, 2012 at 7:16 PM, Bill Tillman btillma...@yahoo.com wrote: Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. ... Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. ... So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Hi Bill, What was going on with this drive before the install? ie, it was sitting on the self not being used, it was a daily use machine running something else, ... etc. At the moment it sounds to me like an inconvenient hardware failure. Waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote: I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. Weirdness.. ok, i was wondering - you said you installed an old drive to check it out, and I was thinking hmm 80gb, maybe setting on the shelf for a decade :) I do recall having a similar issue with a drive, but it was years and years ago- my memory hazed, and not necessarily (probably not) related to FreeBSD install. If you aren't getting POST then it sounds hardware related to me. Good Luck, Waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
On Thu, 5 Jan 2012, Bill Tillman wrote: Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. The BIOS on some systems expects a particular partition layout. In the old days, Compaq had a BIOS partition on the disk. Today, there are there are still weird things that can be vendor-specific. Or new standards like UEFI. So the problem could be specific to that particular computer model or brand. Attaching the drive to a USB to IDE adapter might avoid the problem, allowing a boot from another drive. Before rewriting the do-nothing drive, use 'gpart show' or fdisk to see the partition layout that is the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
El día Friday, January 06, 2012 a las 06:37:02AM -0800, Waitman Gobble escribió: On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote: I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. It seems that there are BIOS features which need to have access to certain sectors of the disk with additional (Winblows) software. Once you format the entire disk for FreeBSD you will not enter the BIOS dialogue, nor it will boot anymore; google for a thread of FreeBSD installation on Acer laptops. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
acer ?? i had this with acer.. remove hdd...acess bios change ahci mode and try installing again. On Fri, Jan 6, 2012 at 8:16 PM, Matthias Apitz g...@unixarea.de wrote: El día Friday, January 06, 2012 a las 06:37:02AM -0800, Waitman Gobble escribió: On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote: I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. It seems that there are BIOS features which need to have access to certain sectors of the disk with additional (Winblows) software. Once you format the entire disk for FreeBSD you will not enter the BIOS dialogue, nor it will boot anymore; google for a thread of FreeBSD installation on Acer laptops. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Best Regards, Mubeesh Ali.V.M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
On 5 January 2012 22:16, Bill Tillman btillma...@yahoo.com wrote: ... then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. The keyboard was still responding as I could press the CapLock key and toggle the light on and off, but outside of that the computer would not boot. On the advice of some of the techs in #FreeBSD channel I moved the drive over to another computer which was working fine, and the same thing happened. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. Now it gets really wierd. I thought that I could just make this IDE drive a slave and boot with another drive and cleanup the mess. But no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If I removed it everything was fine. So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Any suggestions would be appreciated. I have an old IDE-USB adapter that I think I picked up for $15 a few years ago. (amazon has them for that right now http://amzn.to/xfyeOW Your local Beast Buy or MicroSinter may have such as well the newer once seem to all have eSATA ports too) Silly things like that come in handy once in a great while. Though you may have that rare case when your HDD's board cooked itself for some reason. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
Waitman Gobble wrote: On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote: I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. Weirdness.. ok, i was wondering - you said you installed an old drive to check it out, and I was thinking hmm 80gb, maybe setting on the shelf for a decade :) I do recall having a similar issue with a drive, but it was years and years ago- my memory hazed, and not necessarily (probably not) related to FreeBSD install. If you aren't getting POST then it sounds hardware related to me. Good Luck, Waitman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Aloha, I had this happen with using [Cable Select] on an 80G ISA drive jumper and after I switched to [Master] it worked fine. In any case it does sound like hardware. Try switching the cable. It may be broken. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
Bill Tillman wrote: Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. I was very surprised at the (1) the dvd is actually a live CD if you wanted it to be and (2) the installers screens have all been revamped. I can't say for sure if the partitioning part was where it went south on me because I was attempting to setup some additional partitions but the input screens had me confused and I pressed Auto so it took off and made the default paritions. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. snip This is a known problem with bsdinstall in 9.0. Newer pc's have bios that use gpart format disk partition layouts (IE windows7) so for FreeBSD to be compatible with new PC hardware, Bsdinstall defaults to using the gpart format disk partition layouts. Bsdinstall provides no automatic way to create (mbr, Dos) format partitions. The user is suppose to know before installing 9.0 that their pc hardware requires (mbr, Dos) format partitions and instead of using the automatic gpart format disk partition layouts they must select the manual option which opens a shell where the installer must enter the native commands to create the (mbr, Dos) format partitions like sysinstall did in 8.2 and older releases. This puts a unfair burden on users to know beforehand whether their pc bios are gpart aware. Bsdinstall provides no displayed information informing the user of what they need to know about their equipment before selecting the disk format to use. I believe this user is just the tip of the iceberg of users installing 9.0 on older hardware. At this time the only way to automate the creation of the (mbr, Dos) format partitions using the 9.0 bsdinstall is to select the manual option in the disk config screen and them launch sade, this is the disk configuration dialog from sysinstall that has been turned into a standalone utility. If you think sade should be made a option of the bsdinstall disk config dialog then post your comments here and cc to nwhiteh...@freebsd.org the author of bsdinstall. The bsdinstall has absolutely no built in HELP, But there is some new documentation in the online freebsd manual. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall.html It's under constant revision so it may not be totally accurate, but it will provide you some insight to your disk config problems. Note: before you can use that gpart disk to create mbr you have to delete the (crap) gpart writes at the end of the physical disk. This script works great to do that. http://www.wonkity.com/~wblock/docs/html/disksetup.html After running the script, then on same disk pc install 8.2 and reboot. If it boots fine then you know for sure your pc bios is not gpart aware, and you will always have to use mbr disk format on that pc hardware combination. The SADE utility will become your long time friend. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
9.0-RELEASE amd64 Bricked My Hard Drive
Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. I was very surprised at the (1) the dvd is actually a live CD if you wanted it to be and (2) the installers screens have all been revamped. I can't say for sure if the partitioning part was where it went south on me because I was attempting to setup some additional partitions but the input screens had me confused and I pressed Auto so it took off and made the default paritions. I thought cool, I'll let the install finish and check things out then reinstall later with the partition setup I wanted. Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. The keyboard was still responding as I could press the CapLock key and toggle the light on and off, but outside of that the computer would not boot. On the advice of some of the techs in #FreeBSD channel I moved the drive over to another computer which was working fine, and the same thing happened. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. Now it gets really wierd. I thought that I could just make this IDE drive a slave and boot with another drive and cleanup the mess. But no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If I removed it everything was fine. So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Any suggestions would be appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
On Jan 5, 2012, at 7:16 PM, Bill Tillman wrote: Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. I was very surprised at the (1) the dvd is actually a live CD if you wanted it to be and (2) the installers screens have all been revamped. I can't say for sure if the partitioning part was where it went south on me because I was attempting to setup some additional partitions but the input screens had me confused and I pressed Auto so it took off and made the default paritions. I thought cool, I'll let the install finish and check things out then reinstall later with the partition setup I wanted. Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. The keyboard was still responding as I could press the CapLock key and toggle the light on and off, but outside of that the computer would not boot. On the advice of some of the techs in #FreeBSD channel I moved the drive over to another computer which was working fine, and the same thing happened. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. Now it gets really wierd. I thought that I could just make this IDE drive a slave and boot with another drive and cleanup the mess. But no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If I removed it everything was fine. So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Any suggestions would be appreciated. Can you get into the BIOS of the original machine *while the bad drive is disconnected* ? If so, I'd try changing the boot options in the BIOS to boot from something like external USB but not from IDE. You'll want to find settings that are geared towards totally eliminating the possibility that the BIOS will scan the drive as a boot device. Depending on your BIOS settings, this may involve changing the Boot Order to not include IDE (or ATA), or if you find it as a numbered boot device, disabling that numbered device (e.g. you see Boot Device 2 and it says IDE, see if it offers Disabled as an option). If you can successfully change your boot options in the BIOS to not scan the IDE channels, ... remember, the drive is still not connected at this point ... then you should be able to connect the drive and get the same result -- the BIOS will tell you there's no bootable devices attached (as you've, hopefully, been able to disable that source of devices from the list of those probed/scanned). At this point, you now need to find something other than IDE to boot from (as you've now disabled that type of device -- including CD/ROM). Hopefully your system is new enough to boot from USB media. Grab DruidBSD Tools disk on another (working) machine ... http://sourceforge.net/projects/druidbsd/files/Druid-0.0.iso/download Descriptions here: http://sourceforge.net/projects/druidbsd/files/ Get yourself a USB thumb drive. NOTE: Say goodbye to what's currently on your thumb drive -- make backups to another machine before you do this. 1. Execute before you attach your thumb drive: sysctl kern.disks 2. Insert thumb drive 3. Execute after you've attached the thumb drive: sysctl kern.disks 4. Identify the newly-available da# device 5. Execute (replacing da# with the appropriate device name) as root (or sudo(8)): dd if=Druid-0.0.iso of=/dev/da# bs=512k conv=sync HINT: You can press Ctrl-T while it's writing the ISO file to the thumb drive to get a (somewhat) helpful progress indication. When finished, you can use your USB thumb drive to do all sorts of rescue-work, including wiping the bad drive with Darik's Boot and Nuke (lol) -- used for secure government wipes -- or Active (R) Kill Disk Free Edition, both on the disk linked-to above. There's also Seagate Disk Utilities, which some of our field engineers found useful (I think it-too has a disk-wiper). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
Bill Tillman btillma...@yahoo.com wrote: ... no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If you have an oldish machine with a spare PCI slot, you could try plugging in a PCI-IDE controller card and connect the drive to that. Many of the older BIOS won't look for drives on add-in controllers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive 2TB
On 06/29/11 15:57, Joshua Boyd wrote: 2011/6/29 O. Hartmann ohart...@zedat.fu-berlin.de mailto:ohart...@zedat.fu-berlin.de Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? Hi Oliver, Neither, unfortunately. The 1068E based cards do not support drives over 2TB. See here: http://kb.lsi.com/KnowledgebaseArticle16399.aspx -- Joshua Boyd E-mail: boy...@jbip.net mailto:boy...@jbip.net http://www.jbip.net Hello Joshua. Thanks for the fast response. Yes, you're right. I revealed by several postings in the net that the controller in question is not capable of handling disks 2TB. It's a pitty. Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive 2TB
On a Dell PowerEdge 1950, BIOS from 2007, a freshly installed WD 3 TB SATA 6GB harddrive doesn't get recognized as 3 TB disk, it is reported as 2TB disk only. The box is running FreeBSD 8.2-STABLE (see below the dmesg excerpt). The drive is configured as ZFS pool on top of a GPT partition. I tried the 3 TB harddrive on a FreeBSD 9.0-CURRENT box with Intel ICH10R SATA chipset and it worked fine, was reported as 2.7TB drive as expected. I found some postings concerning mptutil not dealing with HD 2TB, but this issue seems not to be a tool-issue. Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? b) regarding to a), how can I update the BIOS/MPT firmware of the Dell PowerEdge 1950? Is there an option to do this via USB? As I said, the firmware is quite old, it's from 2007. Thanks in advance, Oliver == Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-STABLE #266 r223622: Tue Jun 28 09:38:38 CEST 2011 r...@thusnelda.geoinf.fu-berlin.de:/usr/obj/usr/src/sys/THUSNELDA amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2493.76-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Family = 6 Model = 17 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 17179869184 (16384 MB) avail memory = 16522498048 (15757 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard aesni0: No AESNI support. acpi0: DELL PE_SC3 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) ipmi0: KCS mode found at io 0xca8 on acpi ipmi0: KCS error: ff Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 [...] mpt0: LSILogic SAS/SATA Adapter port 0xec00-0xecff mem 0xfc4fc000-0xfc4f,0xfc4e-0xfc4e irq 16 at device 0.0 on pci1 mpt0: [ITHREAD] mpt0: MPI Version=1.5.14.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (14 Max) [...] ipmi0: IPMI device rev. 0, firmware rev. 2.10, version 2.0 ipmi0: Number of channels 4 ipmi0: Attached watchdog da0 at mpt0 bus 0 scbus0 target 0 lun 0 da0: ATA Hitachi HUA72107 A74A Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 715404MB (1465149168 512 byte sectors: 255H 63S/T 91201C) da1 at mpt0 bus 0 scbus0 target 1 lun 0 da1: ATA WDC WD30EZRX-00M 0A80 Fixed Direct Access SCSI-5 device da1: 300.000MB/s transfers da1: Command Queueing enabled da1: 2097151MB (4294967295 512 byte sectors: 255H 63S/T 267349C) ses0 at mpt0 bus 0 scbus0 target 8 lun 0 ses0: DP BACKPLANE 1.05 Fixed Enclosure Services SCSI-5 device ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device cd0 at ata0 bus 0 scbus2 target 0 lun 0SMP: AP CPU #3 Launched! cd0: TEAC DVD-ROM DV28EV D.AE Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #5 Launched! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive 2TB
On 6/29/11 9:58 AM, O. Hartmann wrote: On a Dell PowerEdge 1950, BIOS from 2007, a freshly installed WD 3 TB SATA 6GB harddrive doesn't get recognized as 3 TB disk, it is reported as 2TB disk only. I almost stopped reading at BIOS from 2007. You should definitely upgrade the BIOS before barging in and saying you've got a problem ;) The box is running FreeBSD 8.2-STABLE (see below the dmesg excerpt). The drive is configured as ZFS pool on top of a GPT partition. I tried the 3 TB harddrive on a FreeBSD 9.0-CURRENT box with Intel ICH10R SATA chipset and it worked fine, was reported as 2.7TB drive as expected. Was the drive handled by mpt too, or by mps ? I found some postings concerning mptutil not dealing with HD 2TB, but this issue seems not to be a tool-issue. Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? Let's see you update the firmware and tell us ;) b) regarding to a), how can I update the BIOS/MPT firmware of the Dell PowerEdge 1950? Is there an option to do this via USB? As I said, the firmware is quite old, it's from 2007. Usually, this is done using dell's ISO image. You can either do that directly in front of the server, or remotely with dell's DRAC and by using virtual media. Keep in mind that virtual media might or might not be supported by your DRAC firmware version. If you can't use the virtual media, you may also boot dell's ISO via PXE. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive 2TB
On Wed, Jun 29, 2011 at 09:58:02AM +0200, O. Hartmann wrote: On a Dell PowerEdge 1950, BIOS from 2007, a freshly installed WD 3 TB SATA 6GB harddrive doesn't get recognized as 3 TB disk, it is reported as 2TB disk only. The box is running FreeBSD 8.2-STABLE (see below the dmesg excerpt). The drive is configured as ZFS pool on top of a GPT partition. I tried the 3 TB harddrive on a FreeBSD 9.0-CURRENT box with Intel ICH10R SATA chipset and it worked fine, was reported as 2.7TB drive as expected. I found some postings concerning mptutil not dealing with HD 2TB, but this issue seems not to be a tool-issue. Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? b) regarding to a), how can I update the BIOS/MPT firmware of the Dell PowerEdge 1950? Is there an option to do this via USB? As I said, the firmware is quite old, it's from 2007. The answer is here: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/147572 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive 2TB
2011/6/29 O. Hartmann ohart...@zedat.fu-berlin.de Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? Hi Oliver, Neither, unfortunately. The 1068E based cards do not support drives over 2TB. See here: http://kb.lsi.com/KnowledgebaseArticle16399.aspx -- Joshua Boyd E-mail: boy...@jbip.net http://www.jbip.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mounting a hard drive via usb
I am attempting to clone a drive by connecting the prospective copy drive via usb. I've just recently upgraded to FBSD 8.2 Here is what I get when I insert the drive; Jun 18 14:36:29 3s1 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Jun 18 14:36:29 3s1 kernel: da0:Fixed Direct Access SCSI-2 device Jun 18 14:36:29 3s1 kernel: da0: 40.000MB/s transfers Jun 18 14:36:29 3s1 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) I notice that the /dev/da0s1.. entries are gone now from my /dev directly (maybe this is part of the upgrade to 8.2) so all I have in /dev is /dev/da0 My first thought was using MAKEDEV but that is redundant now I understand. I also read that mounting drives via usb have to be done with the -a msdosfs option because they are seen as SCSI drives. Wondering how I would go about mounting this drive - right now it's an old FreeBSD drive which I just want to wipe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a hard drive via usb
2011-06-18 20:53, David Banning skrev: I am attempting to clone a drive by connecting the prospective copy drive via usb. I've just recently upgraded to FBSD 8.2 Here is what I get when I insert the drive; Jun 18 14:36:29 3s1 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Jun 18 14:36:29 3s1 kernel: da0: Fixed Direct Access SCSI-2 device Jun 18 14:36:29 3s1 kernel: da0: 40.000MB/s transfers Jun 18 14:36:29 3s1 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) I notice that the /dev/da0s1.. entries are gone now from my /dev directly (maybe this is part of the upgrade to 8.2) so all I have in /dev is /dev/da0 My first thought was using MAKEDEV but that is redundant now I understand. I also read that mounting drives via usb have to be done with the -a msdosfs option because they are seen as SCSI drives. Not really. I do something like mount -t filesystem /dev/da0 /mnt Then I'll check /dev/da* and viola there is /dev/da0sX, you get an error when trying to mount /dev/da0 Device not configured I'm running FreeBSD 8.2-STABLE #0: Wondering how I would go about mounting this drive - right now it's an old FreeBSD drive which I just want to wipe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a hard drive via usb - solved
As it turns out - my usb adapter was defective. Once I used an operational adapter all the devices appeared and the disk works like a charm! Thanks for your input. On 6/18/2011 3:48 PM, Bernt Hansson wrote: 2011-06-18 20:53, David Banning skrev: I am attempting to clone a drive by connecting the prospective copy drive via usb. I've just recently upgraded to FBSD 8.2 Here is what I get when I insert the drive; Jun 18 14:36:29 3s1 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Jun 18 14:36:29 3s1 kernel: da0: Fixed Direct Access SCSI-2 device Jun 18 14:36:29 3s1 kernel: da0: 40.000MB/s transfers Jun 18 14:36:29 3s1 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jun 18 14:36:29 3s1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) I notice that the /dev/da0s1.. entries are gone now from my /dev directly (maybe this is part of the upgrade to 8.2) so all I have in /dev is /dev/da0 My first thought was using MAKEDEV but that is redundant now I understand. I also read that mounting drives via usb have to be done with the -a msdosfs option because they are seen as SCSI drives. Not really. I do something like mount -t filesystem /dev/da0 /mnt Then I'll check /dev/da* and viola there is /dev/da0sX, you get an error when trying to mount /dev/da0 Device not configured I'm running FreeBSD 8.2-STABLE #0: Wondering how I would go about mounting this drive - right now it's an old FreeBSD drive which I just want to wipe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hard drive detection
Hi all, I'm having an issue getting my installation of FreeBSD to detect all the drives in the system. It has 48 total, 46 2TB, and 2 250GB. The system consists of six controllers, with eight drives on each. The two 250GB hard drives are the first drives on controllers 0 and 1. There are two of these machines with the exact same configurations, having the same problem. A very odd thing is that every time the systems are rebooted, the drives that go undetected vary. Also, when the systems were full of 250GB drives, all were detected. All drives are detected in the BIOS of the controllers, just not by FreeBSD. Any and all help is greatly appreciated. (output of dmesg attached) -- ds dmesg.out Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hard drive detection
Hi all, I'm having an issue getting my installation of FreeBSD to detect all the drives in the system. It has 48 total, 46 2TB, and 2 250GB. The system consists of six controllers, with eight drives on each. The two 250GB hard drives are the first drives on controllers 0 and 1. There are two of these machines with the exact same configurations, having the same problem. A very odd thing is that every time the systems are rebooted, the drives that go undetected vary. Also, when the systems were full of 250GB drives, all were detected. All drives are detected in the BIOS of the controllers, just not by FreeBSD. Any and all help is greatly appreciated. (output of dmesg attached) dmesg.out Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hard drive detection
People sleep peaceably in their beds at night only because rough men stand ready to do violence on their behalf. George Orwell --- On Thu, 5/12/11, Dillin Smith dilli.ns.m...@gmail.com wrote: From: Dillin Smith dilli.ns.m...@gmail.com Subject: Hard drive detection To: freebsd-questions@freebsd.org Date: Thursday, May 12, 2011, 2:17 PM Hi all, I'm having an issue getting my installation of FreeBSD to detect all the drives in the system. It has 48 total, 46 2TB, and 2 250GB. The system consists of six controllers, with eight drives on each. The two 250GB hard drives are the first drives on controllers 0 and 1. There are two of these machines with the exact same configurations, having the same problem. A very odd thing is that every time the systems are rebooted, the drives that go undetected vary. Also, when the systems were full of 250GB drives, all were detected. All drives are detected in the BIOS of the controllers, just not by FreeBSD. Any and all help is greatly appreciated. (output of dmesg attached) Look in the output from pciconf -lv | more Are all the controller cards listed?? If not then look to the controller driver man page for hints to get them to play nice together. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop [solved]
On Thu, 6 Jan 2011 21:41:11 -0500, Chris Brennan wrote: On Thu, Jan 6, 2011 at 6:04 PM, Bruce Cran br...@cran.org.uk wrote: http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition has a good guide for installing the base manually (you can ignore the gpart and zfs commands if you want). I found I had to copy the base and kernel directories from the install ISO to a UFS-formatted USB stick first though since the LiveFS CD doesn't have the distributions. -- Bruce Cran Bruce, your a lifesaver! +1 for you and your wiki page. +1 for Warren's page ( http://www.wonkity.com/~wblock/docs/html/disksetup.html#_the_old_standard_way_tt_fdisk_8_tt_and_tt_bsdlabel_8_tt) and +5 for Ian and his incredible patience. Hodgepodging Warren's and Bruce's pages together got me a working base. Laptop is now installed w/o the assistance of a boot cd or the usb hard-drive I was using. That's great news Chris, congratulations for perseverance. It could be argued that it shouldn't be this hard, but I don't need any argument .. I did have to grab a DVD of 8.1 and burn it to a DVDRW, just so I could get access to /dist/8.1-*. That being said, I think I am going to look at setting up that same external hd w/ a full 8.2-R root when it's ready, so I have a full, local tree to utilize for weird installs like this (I don't know why I never did that before) Excellent idea. Just for curiousity's sake, after all that what do you wind up with for: # fdisk -s ad4 # bsdlabel ad4s1 ?, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop [solved]
On Fri, Jan 7, 2011 at 9:58 AM, Ian Smith smi...@nimnet.asn.au wrote: fdisk -s ad4 bsdlabel ad4s1 [r...@blackdragon /usr/src]# fdisk -s ad4; bsdlabel ad4s1 /dev/ad4: 1453521 cyl 16 hd 63 sec PartStartSize Type Flags 1: 63 1465149105 0xa5 0x80 # /dev/ad4s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2097152 164.2BSD0 0 0 b: 16777216 2097168 swap c: 14651491050unused0 0 # raw part, don't edit d: 2097152 188743844.2BSD0 0 0 e: 20971520 209715364.2BSD0 0 0 f: 1423206049 419430564.2BSD0 0 0 [r...@blackdragon /usr/src]# ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Wed, 5 Jan 2011, Chris Brennan wrote:
On Wed, Jan 5, 2011 at 12:44 AM, Ian Smith smi...@nimnet.asn.au wrote:
Saw Chris' later message that -F isn't there for him, but here's what
should be, on the data, the sure-fire way to clobber that last sector:
dd if=/dev/zero of=/dev/ad4 oseek=1465149167
which command SHOULD report just 512 bytes written (we're sure it can't
write past the end of the disk with no count specified), after which:
dd if=/dev/ad4 iseek=1465149167 | hd
SHOULD show zeroes from to 01ff (ie next block 0200)
If not, there really must be some hardware issue with writing?
Hopefully getting there!
Fixit# sysctrl kern.geom.debugflags=16
kern.geom.debugflags: 0 - 16
Fixit# dd if=/dev/zero of=/dev/ad4 oseek=1465149167
dd: /dev/ad4: end of device
2+0 records in
1+0 records out
512 bytes transferred in 0.011 secs (51195 bytes/sec)
So that's right.
Fixit# dd if=/dev/ad4 iseek=1465149167 | hd
1+0 records in
1+0 records out
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
||
512 bytes transferred om 0.009863 secs (51912 bytes/sec)
*
0200
And that's right - the GPT secondary header is now gone.
restarting and back to sysinstall from BETA1 is nice dice ... same original
error ... can I just zero the whole drive?
Sure you can - but I'd be (happy to be) surprised at this point if it's
going to do much good. If nothing else it's a full surface write test,
and you could check afterwards that it's all been zeroed, hd showing
just a few lines (as above) over the whole disk (dd if=/dev/ad4 | hd)
We seem to have ruled out the remnants of a GPT problem, having Bruce
and Warren to thank for pointing it out; it's bound to catch others.
Your dd of the first 71 sectors looked right, MBR looks ok, sectors 1-62
are zeroes, boot1 and boot2 from sector 63-70 seem normal, after you
used 'W' to write anyway; can't say for sure that the bsdlabel is ok,
but see no reason to suppose otherwise. What says 'bsdlabel ad4s1'
while you've still got one?
Just be sure NOT to use the 'A' option for auto-partitioning again; I'm
sure I saw some problem with that on 8.1, not sure if it's fixed on 8.2
(Bruce?) so I suggest allocating the BSD partitioning you really want.
Failing that, I can't see other than a hardware issue, unless somehow
sysinstall is broken and you may do better manually running fdisk and
bsdlabel and newfs per Handbook and manuals? If that worked you could
still use sysinstall, skip fdisk and labelling steps and install the
distributions, ports tree, doc packages and other sysinstall goodies.
If it still persisted after that I'd subscribe and report the issue to
freebsd-stable in as much detail as needed for some more fresh eyes.
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, 6 Jan 2011 20:06:42 +1100 (EST) Ian Smith smi...@nimnet.asn.au wrote: Just be sure NOT to use the 'A' option for auto-partitioning again; I'm sure I saw some problem with that on 8.1, not sure if it's fixed on 8.2 (Bruce?) so I suggest allocating the BSD partitioning you really want. I've not fixed anything related to that. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 3:06 AM, Ian Smith smi...@nimnet.asn.au wrote Your dd of the first 71 sectors looked right, MBR looks ok, sectors 1-62 are zeroes, boot1 and boot2 from sector 63-70 seem normal, after you used 'W' to write anyway; can't say for sure that the bsdlabel is ok, but see no reason to suppose otherwise. What says 'bsdlabel ad4s1' while you've still got one? This is a pretty easy problem to replicate if you are pressing W, and that issue has existed for quite some time. If you press W then Q at sysinstall fdisk then attempt to force write disklabel screens you will get the error. Just setup the slices and partitions as you want and let sysinstall handle the writing of information. There is a big warning box that says not to use force write except under certain conditions and this is not one of them. If you google the error message in the OP, the first result is: http://forums.freebsd.org/showthread.php?t=1675 Failing that, I can't see other than a hardware issue, unless somehow sysinstall is broken and you may do better manually running fdisk and bsdlabel and newfs per Handbook and manuals? This doesn't say hardware error to me at all, at least not a disk hardware issue. The message was present across two disks, and if there truly is a problem writing to the media a complete zeroing of the drive would be apparent then. While we're getting people to look at sysinstall and the auto resizing, it would be nice to get the Unable to create the partition. Too big? issue resolved. You can trigger this by auto-sizing the partitions, deleting a couple and recreating one that a different size than one autosize suggested. Then create the second partion using the auto-populated value in partition size box. Typically run into this when making / a little bigger on amd64 installs by borrowing some space from /usr. It's very tedious to slowly decrease the size of the second partition in your attempts to create it if you're trying to utilize the whole drive. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, 6 Jan 2011 09:11:55 +, Bruce Cran wrote: On Thu, 6 Jan 2011 20:06:42 +1100 (EST) Ian Smith smi...@nimnet.asn.au wrote: Just be sure NOT to use the 'A' option for auto-partitioning again; I'm sure I saw some problem with that on 8.1, not sure if it's fixed on 8.2 (Bruce?) so I suggest allocating the BSD partitioning you really want. I've not fixed anything related to that. Oh, I must have dreamed it all; found nothing in local -stable archives, went hunting on sysinstall cvsweb but found anything there, don't know how to search svn yet; life's too short. Thanks for teaching some GPT. Sorry, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, 6 Jan 2011, Adam Vande More wrote: On Thu, Jan 6, 2011 at 3:06 AM, Ian Smith smi...@nimnet.asn.au wrote Your dd of the first 71 sectors looked right, MBR looks ok, sectors 1-62 are zeroes, boot1 and boot2 from sector 63-70 seem normal, after you used 'W' to write anyway; can't say for sure that the bsdlabel is ok, but see no reason to suppose otherwise. What says 'bsdlabel ad4s1' while you've still got one? This is a pretty easy problem to replicate if you are pressing W, and that issue has existed for quite some time. If you press W then Q at sysinstall fdisk then attempt to force write disklabel screens you will get the error. Just setup the slices and partitions as you want and let sysinstall handle the writing of information. There is a big warning box that says not to use force write except under certain conditions and this is not one of them. Adam, I think you may have missed a lot from the earlier messages in this thread. Admittedly it's long and likely tedious, but trying to help somebody get the OS installed is about as basic as it gets for me; I'd be hugely relieved if someone with more / better clues took it on. We didn't get to try W)rite from the fdisk and label screens until long after all attempts at letting sysinstall deal with things had failed to even slice the disk, bombing on this error every time. Chris' disk is brand new, nothing installed. W)riting from sysinstall succeeded at least in creating ad4s1 in the MBR and writing the bootblocks to that slice. I made it very clear this is not something to do without due care; in the circumstances there was absolutely nothing to be lost. And then the GPT issue, of which I was totally ignorant. Fixed. If you google the error message in the OP, the first result is: http://forums.freebsd.org/showthread.php?t=1675 I can't see anything there that informs any solution to this issue, that doesn't cover everything Chris has tried. If you can, please elaborate? Failing that, I can't see other than a hardware issue, unless somehow sysinstall is broken and you may do better manually running fdisk and bsdlabel and newfs per Handbook and manuals? This doesn't say hardware error to me at all, at least not a disk hardware issue. The message was present across two disks, and if there truly is a problem writing to the media a complete zeroing of the drive would be apparent then. Chris has this issue with one disk only, so I'm not sure what you mean? If it's not hardware related (or HP firmware, as Mike suggested), maybe it is an issue with sysinstall. Manual fdisk bsdlabel newfs would confirm that or otherwise, but Chris will have to hunt up mans, docs and howtos on doing that himself, they're out there. On the other hand it's useful learning, and nothing he tries can make matters any worse. [ I can't comment on auto-allocated partitions, the last time I thought that was even vaguely a useful idea was my first install of 2.2.6 :^] If you have any spare magic dust to sprinkle on this, please do so. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 7:11 AM, Ian Smith smi...@nimnet.asn.au wrote: Adam, I think you may have missed a lot from the earlier messages in this thread. Admittedly it's long and likely tedious, but trying to help somebody get the OS installed is about as basic as it gets for me; I'd be hugely relieved if someone with more / better clues took it on. Actually, I've been following every post since the thread's inception. Despite your listing of generally good advice, the most obvious cause theis error msg(of an admitted newbie) was not explicitly ruled out. I'm simply saying you should start there. Chris has this issue with one disk only, so I'm not sure what you mean? Earlier in the thread, the OP stated he tried to install on a Micro SD card and got the exact same result. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 1:32 PM, Adam Vande More amvandem...@gmail.comwrote: On Thu, Jan 6, 2011 at 7:11 AM, Ian Smith smi...@nimnet.asn.au wrote: Adam, I think you may have missed a lot from the earlier messages in this thread. Admittedly it's long and likely tedious, but trying to help somebody get the OS installed is about as basic as it gets for me; I'd be hugely relieved if someone with more / better clues took it on. Actually, I've been following every post since the thread's inception. Despite your listing of generally good advice, the most obvious cause theis error msg(of an admitted newbie) was not explicitly ruled out. I'm simply saying you should start there. Chris has this issue with one disk only, so I'm not sure what you mean? Earlier in the thread, the OP stated he tried to install on a Micro SD card and got the exact same result. I see now the SD Card was not the install target, but regarding the the original point to OP was able to preform other normal operations on the card eg different FS. I don't really think the OP was pressing W initially which is why I didn't say anything earlier, just saying it's worth a check. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 1:51 PM, Adam Vande More amvandem...@gmail.comwrote: I see now the SD Card was not the install target, but regarding the the original point to OP was able to preform other normal operations on the card eg different FS. I don't really think the OP was pressing W initially which is why I didn't say anything earlier, just saying it's worth a check. There is also this issue here which looks to be quite similar. http://www.freebsd.org/cgi/query-pr.cgi?pr=135040cat= You can try to upgrade your BIOS and reduced physical memory or use the suggested loader.conf setting(or boot prompt) -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Fri, 7 Jan 2011, Ian Smith wrote: Manual fdisk bsdlabel newfs would confirm that or otherwise, but Chris will have to hunt up mans, docs and howtos on doing that himself, they're out there. Aha! http://www.wonkity.com/~wblock/docs/html/disksetup.html May/may not be helpful, but the price is right. Feedback welcome. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
GMail threadding don't fail me now! On Thu, Jan 6, 2011 at 4:54 AM, Adam Vande More amvandem...@gmail.comwrote: This is a pretty easy problem to replicate if you are pressing W, and that issue has existed for quite some time. If you press W then Q at sysinstall fdisk then attempt to force write disklabel screens you will get the error. Just setup the slices and partitions as you want and let sysinstall handle the writing of information. There is a big warning box that says not to use force write except under certain conditions and this is not one of them. If you google the error message in the OP, the first result is: http://forums.freebsd.org/showthread.php?t=1675 pressing 'W' was a last resort option, by no means was I starting off that way. Failing that, I can't see other than a hardware issue, unless somehow sysinstall is broken and you may do better manually running fdisk and bsdlabel and newfs per Handbook and manuals? This doesn't say hardware error to me at all, at least not a disk hardware issue. The message was present across two disks, and if there truly is a problem writing to the media a complete zeroing of the drive would be apparent then. No, only one disk. While we're getting people to look at sysinstall and the auto resizing, it would be nice to get the Unable to create the partition. Too big? issue resolved. You can trigger this by auto-sizing the partitions, deleting a couple and recreating one that a different size than one autosize suggested. Then create the second partion using the auto-populated value in partition size box. Typically run into this when making / a little bigger on amd64 installs by borrowing some space from /usr. It's very tedious to slowly decrease the size of the second partition in your attempts to create it if you're trying to utilize the whole drive. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 8:11 AM, Ian Smith smi...@nimnet.asn.au wrote: Adam, I think you may have missed a lot from the earlier messages in this thread. Admittedly it's long and likely tedious, but trying to help somebody get the OS installed is about as basic as it gets for me; I'd be hugely relieved if someone with more / better clues took it on. We didn't get to try W)rite from the fdisk and label screens until long after all attempts at letting sysinstall deal with things had failed to even slice the disk, bombing on this error every time. Chris' disk is brand new, nothing installed. W)riting from sysinstall succeeded at least in creating ad4s1 in the MBR and writing the bootblocks to that slice. I made it very clear this is not something to do without due care; in the circumstances there was absolutely nothing to be lost. And then the GPT issue, of which I was totally ignorant. Fixed. I agree, you seem to be lumping me into a generalization based on the errormsg. If you google the error message in the OP, the first result is: http://forums.freebsd.org/showthread.php?t=1675 I read this, while that PR Reporter claims the same error message, the conditions in which s/he gets it _are not_ the same conditions in which I am getting this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 2:32 PM, Adam Vande More amvandem...@gmail.comwrote: On Thu, Jan 6, 2011 at 7:11 AM, Ian Smith smi...@nimnet.asn.au wrote: Adam, I think you may have missed a lot from the earlier messages in this thread. Admittedly it's long and likely tedious, but trying to help somebody get the OS installed is about as basic as it gets for me; I'd be hugely relieved if someone with more / better clues took it on. Actually, I've been following every post since the thread's inception. Despite your listing of generally good advice, the most obvious cause theis error msg(of an admitted newbie) was not explicitly ruled out. I'm simply saying you should start there. ... Chris has this issue with one disk only, so I'm not sure what you mean? Earlier in the thread, the OP stated he tried to install on a Micro SD card and got the exact same result. Ney, I was having general issues w/ my card-reader and slow write speeds, that has been solved. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
If you google the error message in the OP, the first result is: http://forums.freebsd.org/showthread.php?t=1675 I read this, while that PR Reporter claims the same error message, the conditions in which s/he gets it _are not_ the same conditions in which I am getting this. Thread poster* sorry for that one ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 4:27 PM, Warren Block wbl...@wonkity.com wrote: On Fri, 7 Jan 2011, Ian Smith wrote: Manual fdisk bsdlabel newfs would confirm that or otherwise, but Chris will have to hunt up mans, docs and howtos on doing that himself, they're out there. Aha! http://www.wonkity.com/~wblock/docs/html/disksetup.htmlhttp://www.wonkity.com/%7Ewblock/docs/html/disksetup.html May/may not be helpful, but the price is right. Feedback welcome. Can I bow at your feet?!? This gave me just enough of a clue to go back and arbitraility pass 'gpart delete -i 1 ad4' which actually deleted a partition! I then zeroed the first 73 and the last 33 blocks of the drive. fdisk still complained about 'Class not found' which I googled and found to be an artifact of gpart(8). So my question is this now, once gpart has touched a disk, does it have the partition-aids now? Moving on, I then continued the standard process listed by your link, bsdlabel'd my layout and saved it, when I do an 'ls -lsga /dev | grep ad4' I see that I have partitions a,b,d,e,f and I was able to newfs each one of them Next question, from this point (at the fixit prompt) can I preform a manual install of just base? if I can get the system installed at this point then all should be good when I reboot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, 6 Jan 2011 17:54:32 -0500 Chris Brennan xa...@xaerolimit.net wrote: Next question, from this point (at the fixit prompt) can I preform a manual install of just base? if I can get the system installed at this point then all should be good when I reboot. http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition has a good guide for installing the base manually (you can ignore the gpart and zfs commands if you want). I found I had to copy the base and kernel directories from the install ISO to a UFS-formatted USB stick first though since the LiveFS CD doesn't have the distributions. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop [solved]
On Thu, Jan 6, 2011 at 6:04 PM, Bruce Cran br...@cran.org.uk wrote: http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition has a good guide for installing the base manually (you can ignore the gpart and zfs commands if you want). I found I had to copy the base and kernel directories from the install ISO to a UFS-formatted USB stick first though since the LiveFS CD doesn't have the distributions. -- Bruce Cran Bruce, your a lifesaver! +1 for you and your wiki page. +1 for Warren's page ( http://www.wonkity.com/~wblock/docs/html/disksetup.html#_the_old_standard_way_tt_fdisk_8_tt_and_tt_bsdlabel_8_tt) and +5 for Ian and his incredible patience. Hodgepodging Warren's and Bruce's pages together got me a working base. Laptop is now installed w/o the assistance of a boot cd or the usb hard-drive I was using. I did have to grab a DVD of 8.1 and burn it to a DVDRW, just so I could get access to /dist/8.1-*. That being said, I think I am going to look at setting up that same external hd w/ a full 8.2-R root when it's ready, so I have a full, local tree to utilize for weird installs like this (I don't know why I never did that before) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, 6 Jan 2011, Chris Brennan wrote: On Thu, Jan 6, 2011 at 4:27 PM, Warren Block wbl...@wonkity.com wrote: On Fri, 7 Jan 2011, Ian Smith wrote: Manual fdisk bsdlabel newfs would confirm that or otherwise, but Chris will have to hunt up mans, docs and howtos on doing that himself, they're out there. Aha! http://www.wonkity.com/~wblock/docs/html/disksetup.html May/may not be helpful, but the price is right. Feedback welcome. Can I bow at your feet?!? This gave me just enough of a clue to go back and arbitraility pass 'gpart delete -i 1 ad4' which actually deleted a partition! I then zeroed the first 73 and the last 33 blocks of the drive. fdisk still complained about 'Class not found' which I googled and found to be an artifact of gpart(8). destroy -F is supposed to mean Forced destroying of the partition table even if it is not empty. But compare to this thread on the forum earlier today: http://forums.freebsd.org/showthread.php?t=20731 Maybe -F isn't quite as brutal as it needs to be. So my question is this now, once gpart has touched a disk, does it have the partition-aids now? GPT does seem to be tenacious, and I'm wondering if maybe there's something left in RAM that's written back to the disk on shutdown. Moving on, I then continued the standard process listed by your link, bsdlabel'd my layout and saved it, when I do an 'ls -lsga /dev | grep ad4' I see that I have partitions a,b,d,e,f and I was able to newfs each one of them Next question, from this point (at the fixit prompt) can I preform a manual install of just base? if I can get the system installed at this point then all should be good when I reboot. I would just boot the install CD, enter q and the fdisk screen, enter the mountpoints and q at the label screen, and let it do the rest.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Jan 6, 2011 at 11:48 PM, Warren Block wbl...@wonkity.com wrote: destroy -F is supposed to mean Forced destroying of the partition table even if it is not empty. But compare to this thread on the forum earlier today: http://forums.freebsd.org/showthread.php?t=20731 Maybe -F isn't quite as brutal as it needs to be. I still can't find any documentation on this in the manpages? HA! I just finished skimming the above thread, -F is indeed new and not in 8.1. I am going to set up a local mirror of 7.x, 8.x and HEAD over the next week and if I remember, I'll be sure to check it out and see if it does infact exist in 8.2. So my question is this now, once gpart has touched a disk, does it have the partition-aids now? GPT does seem to be tenacious, and I'm wondering if maybe there's something left in RAM that's written back to the disk on shutdown. Sneaky ... but possibly not likely since I more then once pulled the plug and didn't give it time to actually write anything. Either way, between your link and Bruce's, all is well. Moving on, I then continued the standard process listed by your link, bsdlabel'd my layout and saved it, when I do an 'ls -lsga /dev | grep ad4' I see that I have partitions a,b,d,e,f and I was able to newfs each one of them Next question, from this point (at the fixit prompt) can I preform a manual install of just base? if I can get the system installed at this point then all should be good when I reboot. I would just boot the install CD, enter q and the fdisk screen, enter the mountpoints and q at the label screen, and let it do the rest. See, I did that the first time and it all came to a screaming halt. That's when I started to get creative with Ian. I'm going to take a stab in the dark and blame Seagate for kludging the disk on me. Either way, a manual fdisk and bsdlabel did the trick, it's got to be something in sysinstall not liking what ever was written there by gpart... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Wed, Jan 5, 2011 at 12:44 AM, Ian Smith smi...@nimnet.asn.au wrote: Saw Chris' later message that -F isn't there for him, but here's what should be, on the data, the sure-fire way to clobber that last sector: dd if=/dev/zero of=/dev/ad4 oseek=1465149167 which command SHOULD report just 512 bytes written (we're sure it can't write past the end of the disk with no count specified), after which: dd if=/dev/ad4 iseek=1465149167 | hd SHOULD show zeroes from to 01ff (ie next block 0200) If not, there really must be some hardware issue with writing? Hopefully getting there! cheers, Ian [..] Fixit# sysctrl kern.geom.debugflags=16 kern.geom.debugflags: 0 - 16 Fixit# dd if=/dev/zero of=/dev/ad4 oseek=1465149167 dd: /dev/ad4: end of device 2+0 records in 1+0 records out 512 bytes transferred in 0.011 secs (51195 bytes/sec) Fixit# dd if=/dev/ad4 iseek=1465149167 | hd 1+0 records in 1+0 records out 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || 512 bytes transferred om 0.009863 secs (51912 bytes/sec) * 0200 Fixit# [..] restarting and back to sysinstall from BETA1 is nice dice ... same original error ... can I just zero the whole drive? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
BIOS menu is very limited in detail and changable options. But nothing about SATA modes. Ok. Something else you could try is W)riting the slice table + MBR out from the fdisk menu, then quit sysinstall and reboot. You can do the same after labelling but before newfs'ing .. not generally recommended, but safe enough on a blank disk. From the FDISK Partition Editor in sysinstall, I don't see a means to actually write the slice to disk, immediatly from that menu. Same for the slice editor. If you do the latter, you'll have to reenter your mount points later, so make a note of the order and size of partitions that you specified. See above :P Hmm, certainly still in 7.4-PRE there's a 'W' menu option in both fdisk and label screens. It might still work, but be hidden in 8.2? [Bruce?] Hopefully somebody else has a take on all this, I'm out of ideas .. No worries, I appreciate yours and everyone elses help. Only helpful when it actually helps :) On Sun, Jan 2, 2011 at 5:19 AM, Bruce Cran br...@cran.org.uk wrote: This can happen if you've had it partitioned using GPT at some point - in that case you need to use dd to zero the first _and_ last sectors of the disk. So this is two dd operations, one for the first 63 bytes and one for the last 63 bytes? Can you ellaborate a little? dd's more advanced operations are still new to me :D Not bytes but sectors, and the right number seems to be 33. See below. On Sun, Jan 2, 2011 at 5:22 AM, Bruce Cran br...@cran.org.uk wrote: See my post later in the thread: this most likely has nothing to do with the partition layout but the fact that FreeBSD is finding an old partition scheme. Later in the thread suggests a post after this one, this is none, or are you referring to another thread? If so, which one? :) The message you quoted immediately before this one, above. On Sun, Jan 2, 2011 at 10:15 AM, Ian Smith smi...@nimnet.asn.au wrote: Hmm, should we bet against a gentoo install using GPT these days? gpart is part of the gentoo LiveCD, I didn't use it to create any partitions, just to make sure fbsd deleted anything that might have been present. I used cfdisk to slice the drive and mkfs.ext4 and mkswap to create and write the partitions. Ok, but you still should check the last track of the disk for cruft. Finding out about the actual disk layout in gpt(8), gpart(8) etc proving fruitless and finding nothing in Handbook, FAQ or wiki, I resorted to http://en.wikipedia.org/wiki/GUID_Partition_Table for hopefully correct information. I hadn't even known that sectors 1-33 were used for the GPT (making Mike's zeroing of sector 1 sensible even on sliced disks), nor that the last 33 sectors were for its backup table, thanks. So: dd if=/dev/zero of=/dev/da4 seek=N where N is the known total number of sectors minus 34, should do it? I think you mean ad4 and not da4 here si that's (ST)-34? 1465149168-34? I'm just trying to make sure I understand what you want me to do here. Actually, double checking the maths, 1465149168 - 34 = 1465149134 but that actually gets you the last 34 sectors (since size-1 gets the last 1 sector) so I should have said size - 33 = 1465149135. Add count=33 to be sure. After which, dd it back to check it's all zeroes: dd if=/dev/ad4 iseek=1465149135 count=33 | hd As my brief late followup to that message pointed out, I made a TERRIBLE mistake there, saying skip instead of seek. I see you incorporated that correction, phew. Just to point out how bad a slip it was, what it'd do using skip is read - and discard - ~700GB of zeroes from the input, then zero the entire disk! My new years' resolution is to 'skip using skip' and to only ever use the more explicit iseek and oseek from now on! Careful with that axe, Eugene! -- Pink Floyd If not, we can't rule out Mike's concerns about BIOS incompatibility or such, but this sure sounds like the next thing Chris should try. A BIOS incompatibility has been in the back of my mind. But given that the laptop is of a recently modern make, switching to a larger hard-drive shouldn't be this big of an issue. Indeed it shouldn't. Good luck, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Tue, Jan 4, 2011 at 3:56 AM, Ian Smith smi...@nimnet.asn.au wrote: On Mon, 3 Jan 2011 16:31:17 -0500, Chris Brennan wrote: [.. trimming ccs, selectively quoting and de-gmailing a bit ..] Trimmings! Oh nevermind. I don't know what possessed me to go and look at the debug window. But I do and I see the following. GEOM: ad4: the primary GPT table is corrupt or invalid. GEOM: ad4: using the secondary instead -- recovery strongly advised. This is even after zero the beginning and the end of the drive Something is hinky! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Tue, 4 Jan 2011, Chris Brennan wrote: On Tue, Jan 4, 2011 at 3:56 AM, Ian Smith smi...@nimnet.asn.au wrote: On Mon, 3 Jan 2011 16:31:17 -0500, Chris Brennan wrote: [.. trimming ccs, selectively quoting and de-gmailing a bit ..] Trimmings! Oh nevermind. I don't know what possessed me to go and look at the debug window. But I do and I see the following. GEOM: ad4: the primary GPT table is corrupt or invalid. GEOM: ad4: using the secondary instead -- recovery strongly advised. This is even after zero the beginning and the end of the drive Something is hinky! Today I also found that zeroing the beginning and end of the drive didn't seem to be enough. I had the start of a huffy email about how hard it was to calculate the end of a drive in blocks, and how dd didn't have a negative oseek to seek backwards from the end. But then I checked gpart(8)... and it turns out that # gpart destroy -F da0 works. Be very careful that you've got the right drive there, of course. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Tue, Jan 4, 2011 at 8:44 PM, Warren Block wbl...@wonkity.com wrote: On Tue, 4 Jan 2011, Chris Brennan wrote: On Tue, Jan 4, 2011 at 3:56 AM, Ian Smith smi...@nimnet.asn.au wrote: On Mon, 3 Jan 2011 16:31:17 -0500, Chris Brennan wrote: [.. trimming ccs, selectively quoting and de-gmailing a bit ..] Trimmings! Oh nevermind. I don't know what possessed me to go and look at the debug window. But I do and I see the following. GEOM: ad4: the primary GPT table is corrupt or invalid. GEOM: ad4: using the secondary instead -- recovery strongly advised. This is even after zero the beginning and the end of the drive Something is hinky! Today I also found that zeroing the beginning and end of the drive didn't seem to be enough. I had the start of a huffy email about how hard it was to calculate the end of a drive in blocks, and how dd didn't have a negative oseek to seek backwards from the end. But then I checked gpart(8)... and it turns out that # gpart destroy -F da0 works. Be very careful that you've got the right drive there, of course. Fixit# gpart destroy -F /dev/node# says gpart: illegal option -- F it would appear that the gpart on the 8.1-RELEASE and 8.2BETA1 images do not contain this switch and I get pattern not found when I search 'man 8 gpart' ... there is a '-f flags' but no mention of '-F' C- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Tue, 4 Jan 2011, Warren Block wrote: On Tue, 4 Jan 2011, Chris Brennan wrote: On Tue, Jan 4, 2011 at 3:56 AM, Ian Smith smi...@nimnet.asn.au wrote: On Mon, 3 Jan 2011 16:31:17 -0500, Chris Brennan wrote: [.. trimming ccs, selectively quoting and de-gmailing a bit ..] Trimmings! Oh nevermind. I don't know what possessed me to go and look at the debug window. But I do and I see the following. GEOM: ad4: the primary GPT table is corrupt or invalid. GEOM: ad4: using the secondary instead -- recovery strongly advised. This is even after zero the beginning and the end of the drive Something is hinky! Indeed. Well Chris attached the following to his prior email, which made it to the list being text, dmesg didn't, application/octet-stream: http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20110104/c370dd77/dmesg-0001.obj But confirming the GEOM messages shown above, here's the 'smoking gun': 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 4000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART\...| 4010 2b b3 b7 fa 00 00 00 00 ef 66 54 57 00 00 00 00 |+fTW| 4020 01 00 00 00 00 00 00 00 22 00 00 00 00 00 00 00 |...| 4030 ce 66 54 57 00 00 00 00 45 51 13 4c 0e 0e e0 11 |.fTWEQ.L| 4040 95 6e 00 1d 72 5b f5 d6 cf 66 54 57 00 00 00 00 |.n..r[...fTW| 4050 80 00 00 00 80 00 00 00 86 d2 54 ab 00 00 00 00 |..T.| 4060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 4200 So that is really the last 33 sectors of the disk (0x4200 = 16896d, / 512 = 33) and the last sector does indeed have the 'GPT EFI' signature (ref: http://en.wikipedia.org/wiki/GUID_Partition_Table), so the seek and count looks right, matching the read command I'd suggested: dd if=/dev/ad4 iseek=1465149135 count=33 | hd Seems odd that it hasn't been zeroed, but all the sectors before it are (ie there's just the header, no actual 128-byte partition entries if I'm interpreting this correctly), so maybe there's still some off-by-one in counting from the end of the disk for writing, not knowing the actual dd command used .. you're not wrong that negative offsets can be tricky! Today I also found that zeroing the beginning and end of the drive didn't seem to be enough. I had the start of a huffy email about how hard it was to calculate the end of a drive in blocks, and how dd didn't have a negative oseek to seek backwards from the end. But then I checked gpart(8)... and it turns out that # gpart destroy -F da0 works. Be very careful that you've got the right drive there, of course. Saw Chris' later message that -F isn't there for him, but here's what should be, on the data, the sure-fire way to clobber that last sector: dd if=/dev/zero of=/dev/ad4 oseek=1465149167 which command SHOULD report just 512 bytes written (we're sure it can't write past the end of the disk with no count specified), after which: dd if=/dev/ad4 iseek=1465149167 | hd SHOULD show zeroes from to 01ff (ie next block 0200) If not, there really must be some hardware issue with writing? Hopefully getting there! cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
a misconfigured bsdlabel there, for later. I'm not convinced this is likely your problem, but it can't hurt before slice 1 exists (by virtue of having an entry in the MBR, when it should show up in /dev) I'll give this a shot and let the list know what I find. Do you mean you dd'd the memstick.img to the external USB drive? And that booted ok? And sysinstall found it ok, as /dev/ad0a? Details! Haha! yes, I dd'd the memstick image to the external USB drive. It did boot just fine, but not ad /dev/ad0a, it booted the drive as /dev/da0a. Which is a 1gb partition, the other 59gb remained unused/unsliced. I don't have and media where I could write a 1GB image to w/o wasting a DVD and just couldn't justify that loss of space lol. Given you've shown previously that s1 starts at sector 63, so will: sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/ad4 oseek=63 count=8 Fixit# sysctl kern.geom.debugflags=16 sysctl kern.geom.debugflags: 0 - 16 Fixit# dd if=/dev/zero of=/dev/ad4 oseek=63 count=8 8+0 Records in 8+0 records out 4096 bytes transferred in 0.431880 secs (9484 bytes/sec) Getting yours fine; that was re my reply to Mike's message. Understood. Of course that's not impossible, but you did say you'd installed some linux on it ok? Clutching at straws, is there anything in your BIOS regarding different SATA modes you can play with? (No SATA disks here) Yes, as I said in Mike's reply above, I did write a simple ext4 partition to the drive just to prove to myself that it could be done (and it worked). No, I've checked and rechecked, this laptop's BIOS menu is very limited in detail and changable options. But nothing about SATA modes. Something else you could try is W)riting the slice table + MBR out from the fdisk menu, then quit sysinstall and reboot. You can do the same after labelling but before newfs'ing .. not generally recommended, but safe enough on a blank disk. From the FDISK Partition Editor in sysinstall, I don't see a means to actually write the slice to disk, immediatly from that menu. Same for the slice editor. If you do the latter, you'll have to reenter your mount points later, so make a note of the order and size of partitions that you specified. See above :P Hopefully somebody else has a take on all this, I'm out of ideas .. No worries, I appreciate yours and everyone elses help. On Sun, Jan 2, 2011 at 5:19 AM, Bruce Cran br...@cran.org.uk wrote: This can happen if you've had it partitioned using GPT at some point - in that case you need to use dd to zero the first _and_ last sectors of the disk. So this is two dd operations, one for the first 63 bytes and one for the last 63 bytes? Can you ellaborate a little? dd's more advanced operations are still new to me :D On Sun, Jan 2, 2011 at 5:22 AM, Bruce Cran br...@cran.org.uk wrote: See my post later in the thread: this most likely has nothing to do with the partition layout but the fact that FreeBSD is finding an old partition scheme. Later in the thread suggests a post after this one, this is none, or are you referring to another thread? If so, which one? On Sun, Jan 2, 2011 at 10:15 AM, Ian Smith smi...@nimnet.asn.au wrote: Hmm, should we bet against a gentoo install using GPT these days? gpart is part of the gentoo LiveCD, I didn't use it to create any partitions, just to make sure fbsd deleted anything that might have been present. I used cfdisk to slice the drive and mkfs.ext4 and mkswap to create and write the partitions. Finding out about the actual disk layout in gpt(8), gpart(8) etc proving fruitless and finding nothing in Handbook, FAQ or wiki, I resorted to http://en.wikipedia.org/wiki/GUID_Partition_Table for hopefully correct information. I hadn't even known that sectors 1-33 were used for the GPT (making Mike's zeroing of sector 1 sensible even on sliced disks), nor that the last 33 sectors were for its backup table, thanks. So: dd if=/dev/zero of=/dev/da4 seek=N where N is the known total number of sectors minus 34, should do it? I think you mean ad4 and not da4 here si that's (ST)-34? 1465149168-34? I'm just trying to make sure I understand what you want me to do here. If not, we can't rule out Mike's concerns about BIOS incompatibility or such, but this sure sounds like the next thing Chris should try. A BIOS incompatibility has been in the back of my mind. But given that the laptop is of a recently modern make, switching to a larger hard-drive shouldn't be this big of an issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Sun, 02 Jan 2011 01:39:13 -0500 Michael Powell nightre...@hotmail.com wrote: Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted. Then pressing OK brings this: Couldn't make filesystems properly. Aborting. This from sysinstall and occurs after fdisk, labeling, at the point when sysinstall then tries to write out the config to the disk and newfs. This can happen if you've had it partitioned using GPT at some point - in that case you need to use dd to zero the first _and_ last sectors of the disk. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Fri, 31 Dec 2010 01:13:57 -0500 Chris Brennan xa...@xaerolimit.net wrote: No worries on missing it, I'm not sure that helped, I farted around with it again earlier today with little more in the way of success. What I tried was to just set up '/' and swamp and it still prompted me about not being able to find /dev/ad4s1b. See my post later in the thread: this most likely has nothing to do with the partition layout but the fact that FreeBSD is finding an old partition scheme. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Sun, 2 Jan 2011 10:22:55 +, Bruce Cran wrote: On Fri, 31 Dec 2010 01:13:57 -0500 Chris Brennan xa...@xaerolimit.net wrote: No worries on missing it, I'm not sure that helped, I farted around with it again earlier today with little more in the way of success. What I tried was to just set up '/' and swamp and it still prompted me about not being able to find /dev/ad4s1b. See my post later in the thread: this most likely has nothing to do with the partition layout but the fact that FreeBSD is finding an old partition scheme. Even dodgier than waiting to quote a message from a digest that hasn't arrived yet is hand-indenting a paste from pipermail :) but I'll hang this off your thread, thanks Bruce .. On Sun, 02 Jan 2011 01:39:13 -0500 Michael Powell nightrecon at hotmail.com wrote: Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted. Then pressing OK brings this: Couldn't make filesystems properly. Aborting. This from sysinstall and occurs after fdisk, labeling, at the point when sysinstall then tries to write out the config to the disk and newfs. This can happen if you've had it partitioned using GPT at some point - in that case you need to use dd to zero the first _and_ last sectors of the disk. Although it's a brand new disk, quoting Chris' original message after skipping the shutdown when too hot issue: gonna let it cool down and try the smart tests again. Incidentally, I was able to boot a gentoo disc and set up an ext4 filesystem on the same disk and it worked fine, so I don't understand why freebsd can't preform a newfs on the drive. Hmm, should we bet against a gentoo install using GPT these days? Finding out about the actual disk layout in gpt(8), gpart(8) etc proving fruitless and finding nothing in Handbook, FAQ or wiki, I resorted to http://en.wikipedia.org/wiki/GUID_Partition_Table for hopefully correct information. I hadn't even known that sectors 1-33 were used for the GPT (making Mike's zeroing of sector 1 sensible even on sliced disks), nor that the last 33 sectors were for its backup table, thanks. So: dd if=/dev/zero of=/dev/da4 skip=N where N is the known total number of sectors minus 34, should do it? If not, we can't rule out Mike's concerns about BIOS incompatibility or such, but this sure sounds like the next thing Chris should try. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Mon, 3 Jan 2011, Ian Smith wrote: dd if=/dev/zero of=/dev/da4 skip=N where N is the known total number of sectors minus 34, should do it? Argh .. that should be seek=N, not skip. Up way too late .. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
Yes - true enough. Was thinking partition table and typed 'mbr'. It's all good, I got the cmd right in the end, but alas, it helped me not! Mmm .. it's not clear from Chris' original message exactly what he did. I clarified that in a subsequent reply with considerably more detail :D In my case, a temporary replacement disk had FreeBSD 6.2 on it. Something changed wrt to disklabeling on the way to 8-Release and the old 6.2 being present created a situation where that region on the disk was invisible to the new labeling and wouldn't write out. A new install of 8-Release (sysinstall) would error out with the same message as Chris when it came to the point of writing out to the disk. For me, the above 2 commands fixed my situation. Even though his error is the same, I think his problem may be different from mine. -Mike I have a 2GB MicroSD card that I am going to toss 8.2BETA1 on, hopefully later today and see where that gets me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
In freebsd-questions Digest, Vol 343, Issue 10, Message: 23 On Fri, 31 Dec 2010 19:37:10 -0500 Michael Powell nightre...@hotmail.com wrote: Ian Smith wrote: In freebsd-questions Digest, Vol 343, Issue 5, Message: 10 On Tue, 28 Dec 2010 11:02:45 -0500 Chris Brennan xa...@xaerolimit.net wrote: On Tue, Dec 28, 2010 at 2:23 AM, Michael Powell nightre...@hotmail.comwrote: Try zeroing out the mbr: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. Er, no, Mike. The MBR is in sector 0 of the disk; that would zero out sector 1 as oseek=1 skips over sector 0. What's in sector 1 depends on how/whether the disk is sliced. In a 'dangerously dedicated' (unsliced) disk like a memory stick perhaps, this would usually be /boot/boot1 and include the bsdlabel. In a sliced disk, sectors 1 to 62 are typically unused, the first slice usually starting at sector 63. t23% fdisk -s ad0 /dev/ad0: 232581 cyl 16 hd 63 sec PartStartSize Type Flags 1: 63 8385867 0x0b 0x00 2: 8385930 125821080 0xa5 0x80 3: 13420701033543342 0xa5 0x00 4: 16775073066685815 0xa5 0x00 If you really want to zero out sector 0, leave out the oseek (or use oseek=0) - but you're better off using 'fdisk -Bi' to init a new disk. Yes - true enough. Was thinking partition table and typed 'mbr'. Well, what's commonly called 'the partition table' is bytes 0x1be-1ff of the MBR, so I was confused by your writing to sector 1 rather than 0, but have a new theory to test, seeing Chris isn't making any progress; this maybe a victim of the old 'slice vs partition' terminology issue. In my case, a temporary replacement disk had FreeBSD 6.2 on it. Something changed wrt to disklabeling on the way to 8-Release and the old 6.2 being present created a situation where that region on the disk was invisible to the new labeling and wouldn't write out. A new install of 8-Release (sysinstall) would error out with the same message as Chris when it came to the point of writing out to the disk. For me, the above 2 commands fixed my situation. Even though his error is the same, I think his problem may be different from mine. The bsdlabel lives in sector 1 (counting from 0) of the slice concerned, specifically the first 0x114 (276d) bytes, in the second sector of the boot blocks. As noted above, in unsliced disks such as memstick.img that's sector 1 of the entire disk, but in ordinary sliced disks it's in sector 1 of the _slice_, so if you'd used (here using Chris' ad4) dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1 - rather than of=/dev/ad4 - then you would indeed be zeroing out the label, ie the 'partition table' in FreeBSD-speak. Is that perhaps what you had to do to that 6.2 disk, which I suppose was a sliced disk? At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie unsliced .. which option has been removed in 8.x _except_ regarding the memstick.img (appearing as /dev/daXa) .. not half confusing, eh? In any case, it'd be a cheap trick for Chris to try from Fixit, and though it seems unlikely there'd be anything 'leftover' from an earlier install, maybe earlier failure/s have left a broken bsdlabel there? So at this still-uninstalled stage it couldn't hurt to zero that sector, or even the first 4KB of ad4s1 .. which is /boot/boot1 plus /boot/boot2 (which equals /boot/boot !) before the label section gets written. ie: sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8 will remove slice 1's boot blocks entirely, including the bsdlabel. cheers, Ian [excuse broken threading, but unless cc'd I have to reply to the digest] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Sat, Jan 1, 2011 at 11:25 AM, Chris Brennan xa...@xaerolimit.net wrote: I have a 2GB MicroSD card that I am going to toss 8.2BETA1 on, hopefully later today and see where that gets me. 2GB MicroSD card was a bust, use a 60GB hard-drive and wrote the image to that, it booted it just fine, but the install failed w/ the exact same error. Could this be the new drive? *shudder* Defective in some way? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Sat, Jan 1, 2011 at 10:20 PM, Ian Smith smi...@nimnet.asn.au wrote: Well, what's commonly called 'the partition table' is bytes 0x1be-1ff of the MBR, so I was confused by your writing to sector 1 rather than 0, but have a new theory to test, seeing Chris isn't making any progress; this maybe a victim of the old 'slice vs partition' terminology issue. I think I was able to figure this part out, his meaning at least. The bsdlabel lives in sector 1 (counting from 0) of the slice concerned, specifically the first 0x114 (276d) bytes, in the second sector of the boot blocks. As noted above, in unsliced disks such as memstick.img that's sector 1 of the entire disk, but in ordinary sliced disks it's in sector 1 of the _slice_, so if you'd used (here using Chris' ad4) dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1 I would happily run this, but ad4s1 doesn't exist, and hasn't (that I know of), I did do oseek=0 and oseek=1 on /dev/ad4 tho and that didn't change anything, it still says it can't find /dev/ad4s1b (swap obviously) - rather than of=/dev/ad4 - then you would indeed be zeroing out the label, ie the 'partition table' in FreeBSD-speak. Is that perhaps what you had to do to that 6.2 disk, which I suppose was a sliced disk? At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie unsliced .. which option has been removed in 8.x _except_ regarding the memstick.img (appearing as /dev/daXa) .. not half confusing, eh? I actually noticed this today, I had issues writing 8.2BETA1 to a 2GB MicroSD card, so I used a 2.5 external hard-drive and from the fixit prompt I noticed that it wrote a 1gb partition for the BETA1 image and left the rest of the desk untouched (ann 59gb of it). In any case, it'd be a cheap trick for Chris to try from Fixit, and though it seems unlikely there'd be anything 'leftover' from an earlier install, maybe earlier failure/s have left a broken bsdlabel there? So at this still-uninstalled stage it couldn't hurt to zero that sector, or even the first 4KB of ad4s1 .. which is /boot/boot1 plus /boot/boot2 (which equals /boot/boot !) before the label section gets written. ie: sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8 will remove slice 1's boot blocks entirely, including the bsdlabel. cheers, Ian [excuse broken threading, but unless cc'd I have to reply to the digest] I've been trying to keep you in my replies but your down-under, so I don't get your replies till after 1am my time... Anywho, it's late and I need to be up in 8hrs, hopefully this can be figured out ... I would hate for the disk to be defective in some way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
Ian Smith wrote: In freebsd-questions Digest, Vol 343, Issue 10, Message: 23 On Fri, 31 Dec 2010 19:37:10 -0500 Michael Powell nightre...@hotmail.com wrote: [snip] Try zeroing out the mbr: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. Er, no, Mike. The MBR is in sector 0 of the disk; that would zero out sector 1 as oseek=1 skips over sector 0. What's in sector 1 depends on how/whether the disk is sliced. In a 'dangerously dedicated' (unsliced) disk like a memory stick perhaps, this would usually be /boot/boot1 and include the bsdlabel. In a sliced disk, sectors 1 to 62 are typically unused, the first slice usually starting at sector 63. t23% fdisk -s ad0 /dev/ad0: 232581 cyl 16 hd 63 sec PartStartSize Type Flags 1: 63 8385867 0x0b 0x00 2: 8385930 125821080 0xa5 0x80 3: 13420701033543342 0xa5 0x00 4: 16775073066685815 0xa5 0x00 If you really want to zero out sector 0, leave out the oseek (or use oseek=0) - but you're better off using 'fdisk -Bi' to init a new disk. Yes - true enough. Was thinking partition table and typed 'mbr'. Well, what's commonly called 'the partition table' is bytes 0x1be-1ff of the MBR, so I was confused by your writing to sector 1 rather than 0, but have a new theory to test, seeing Chris isn't making any progress; this maybe a victim of the old 'slice vs partition' terminology issue. [snip] The bsdlabel lives in sector 1 (counting from 0) of the slice concerned, specifically the first 0x114 (276d) bytes, in the second sector of the boot blocks. As noted above, in unsliced disks such as memstick.img that's sector 1 of the entire disk, but in ordinary sliced disks it's in sector 1 of the _slice_, so if you'd used (here using Chris' ad4) dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1 - rather than of=/dev/ad4 - then you would indeed be zeroing out the label, ie the 'partition table' in FreeBSD-speak. Is that perhaps what you had to do to that 6.2 disk, which I suppose was a sliced disk? No. I used the of=/dev/ad4 as described above. However, I think you've hit the nail on the head on one aspect. I believe that 6.2 disk was originally set up as dangerously dedicated. It was so long ago and I had forgotten all about it, but this does dovetail with what your are getting at. The machine that disk went into had been upgraded completely through the 7.x series and on to 8.0-Release before it's disk went up in smoke(literally). I was attempting to do a fresh 'minimal' install of 8.0-Release to the old 6.2 disk pulled off a shelf prior to doing restore(s) of a dump from just the day before. It was only done because it could be done immediately, and a newer, larger, better replacement procured after the fact. Exact copy of error from my notes here: Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted. Then pressing OK brings this: Couldn't make filesystems properly. Aborting. This from sysinstall and occurs after fdisk, labeling, at the point when sysinstall then tries to write out the config to the disk and newfs. At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie unsliced .. which option has been removed in 8.x _except_ regarding the memstick.img (appearing as /dev/daXa) .. not half confusing, eh? In any case, it'd be a cheap trick for Chris to try from Fixit, and though it seems unlikely there'd be anything 'leftover' from an earlier install, maybe earlier failure/s have left a broken bsdlabel there? Or any other form of 'garbage'. I'd use the 8.1 LiveFS CD myself just as a personal preference - but either approach should do the job. So at this still-uninstalled stage it couldn't hurt to zero that sector, or even the first 4KB of ad4s1 .. which is /boot/boot1 plus /boot/boot2 (which equals /boot/boot !) before the label section gets written. ie: sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8 will remove slice 1's boot blocks entirely, including the bsdlabel. Yes - I agree. Would also be nice to examine it afterward with a hex editor to actually see *if* all writes were zero. Any 'ones' sprinkled in there, especially in the region of the disk we are talking about would indicate corruption. And my wild guess if this is the situation it may possibly indicate some form of subtle hardware incompatibility most likely a clash of firmwares, e.g. controller and disk(s). Some form of non-standard controller implementation, especially wrt to its firmware being buggy. In the OEM world of the likes of HP, DELL, etc, when this happens a
Re: a new hard-drive in a 2y/o laptop
On Sun, 2 Jan 2011 01:15:35 -0500, Chris Brennan wrote: On Sat, Jan 1, 2011 at 10:20 PM, Ian Smith smi...@nimnet.asn.au wrote: [..] The bsdlabel lives in sector 1 (counting from 0) of the slice concerned, specifically the first 0x114 (276d) bytes, in the second sector of the boot blocks. As noted above, in unsliced disks such as memstick.img that's sector 1 of the entire disk, but in ordinary sliced disks it's in sector 1 of the _slice_, so if you'd used (here using Chris' ad4) dd if=/dev/zero of=/dev/ad4s1 oseek=1 bs=512 count=1 I would happily run this, but ad4s1 doesn't exist, and hasn't (that I know of), I did do oseek=0 and oseek=1 on /dev/ad4 tho and that didn't change anything, it still says it can't find /dev/ad4s1b (swap obviously) On /dev/ad4, oseek=0 zeroes sector 0, the MBR including DOS partition (FreeBSD slice) table, so that would kill all the slice data, so sure, ad4s1 won't exist. oseek=1 just zeroes an unused sector as we've seen. What you _can_ do from that state is: dd if=/dev/zero of=/dev/ad4 oseek=63 count=8 which will remove the first 4K of (what will be) slice 1, in case there's a misconfigured bsdlabel there, for later. I'm not convinced this is likely your problem, but it can't hurt before slice 1 exists (by virtue of having an entry in the MBR, when it should show up in /dev) At 6.x (and 7.x, I think) it could have been 'dangerously dedicated' ie unsliced .. which option has been removed in 8.x _except_ regarding the memstick.img (appearing as /dev/daXa) .. not half confusing, eh? I actually noticed this today, I had issues writing 8.2BETA1 to a 2GB MicroSD card, so I used a 2.5 external hard-drive and from the fixit prompt I noticed that it wrote a 1gb partition for the BETA1 image and left the rest of the desk untouched (ann 59gb of it). Do you mean you dd'd the memstick.img to the external USB drive? And that booted ok? And sysinstall found it ok, as /dev/ad0a? Details! sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/ad4s1 bs=512 count=8 will remove slice 1's boot blocks entirely, including the bsdlabel. Given you've shown previously that s1 starts at sector 63, so will: sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/ad4 oseek=63 count=8 [excuse broken threading, but unless cc'd I have to reply to the digest] I've been trying to keep you in my replies Getting yours fine; that was re my reply to Mike's message. but your down-under, so I don't get your replies till after 1am my time... Anywho, it's late and I need to be up in 8hrs, hopefully this Yeah North America is so yesterday from here (well, 16 hours for you :) can be figured out ... I would hate for the disk to be defective in some way. Of course that's not impossible, but you did say you'd installed some linux on it ok? Clutching at straws, is there anything in your BIOS regarding different SATA modes you can play with? (No SATA disks here) Something else you could try is W)riting the slice table + MBR out from the fdisk menu, then quit sysinstall and reboot. You can do the same after labelling but before newfs'ing .. not generally recommended, but safe enough on a blank disk. If you do the latter, you'll have to reenter your mount points later, so make a note of the order and size of partitions that you specified. Hopefully somebody else has a take on all this, I'm out of ideas .. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
Ian Smith wrote: In freebsd-questions Digest, Vol 343, Issue 5, Message: 10 On Tue, 28 Dec 2010 11:02:45 -0500 Chris Brennan xa...@xaerolimit.net wrote: On Tue, Dec 28, 2010 at 2:23 AM, Michael Powell nightre...@hotmail.comwrote: Try zeroing out the mbr: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. Er, no, Mike. The MBR is in sector 0 of the disk; that would zero out sector 1 as oseek=1 skips over sector 0. What's in sector 1 depends on how/whether the disk is sliced. In a 'dangerously dedicated' (unsliced) disk like a memory stick perhaps, this would usually be /boot/boot1 and include the bsdlabel. In a sliced disk, sectors 1 to 62 are typically unused, the first slice usually starting at sector 63. t23% fdisk -s ad0 /dev/ad0: 232581 cyl 16 hd 63 sec PartStartSize Type Flags 1: 63 8385867 0x0b 0x00 2: 8385930 125821080 0xa5 0x80 3: 13420701033543342 0xa5 0x00 4: 16775073066685815 0xa5 0x00 If you really want to zero out sector 0, leave out the oseek (or use oseek=0) - but you're better off using 'fdisk -Bi' to init a new disk. Yes - true enough. Was thinking partition table and typed 'mbr'. Mmm .. it's not clear from Chris' original message exactly what he did. In my case, a temporary replacement disk had FreeBSD 6.2 on it. Something changed wrt to disklabeling on the way to 8-Release and the old 6.2 being present created a situation where that region on the disk was invisible to the new labeling and wouldn't write out. A new install of 8-Release (sysinstall) would error out with the same message as Chris when it came to the point of writing out to the disk. For me, the above 2 commands fixed my situation. Even though his error is the same, I think his problem may be different from mine. -Mike [snip] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, Dec 30, 2010 at 12:24 AM, Ian Smith smi...@nimnet.asn.au wrote:
I don't expect this to be anything like that. Please show a) how many
slices you allocated and how big this FreeBSD slice is and b) how you
partitioned the FreeBSD slice into (and sizes of) / /var/ /usr [/tmp?]
and especially swap.
I wouldn't allocate any less than 1GB for your root (/) partition esp.
if building custom kernel/s; maybe that's fixed in sysinstall for 8.2?
cheers, Ian (please cc me on any reply; I take -questions as a digest)
I cleaned out the thread, leaving only your last bit of questions here.
I did apparently screw up the 'dd' cmd, I retyped it correctly, below is my
(very carefully) retyped recreation of the Fixit prompt;
[..]
Fixit# dd if=/dev/zero of=/dev/ad4 oseek-0 bs=512 count=1
1+0 records in
1+0 records out
512 bytes transferred ub 0.044723 secs (11448 bytes/sec)
Fixit# fdisk -Bi /dev/ad4
*** Working on device /dev/ad4 ***
parameters extracted from in-core disklabel are:
cylinders=1453521 heads=16 sectors/tracks=63 (1008 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1453521 heads=16 sectors/tracks=63 (1008 blks/cyl)
Do you want to change our idea of what BIOS thinks ? [n]
[..]
This is where I stopped, admittedly, I do not know how to use FreeBSD's
fdisk. For the sake of brevity and to move along, I'll break fdisk here and
move back to sysinstall and provide what information I can this way.
From sysinstalls menu, I choose 'Standard', next is the usual message about
fdisk partitioning schemes. After this, I get a 'User Confirmation Request',
which is very similar to the warning I received above. It says
[..]
WARNING: It is safe to use a geometry of 1453521/16/63 for ad4 on computers
with modern BIOS versions. If this disk is to be uised on an old machine it
is recommended that it does not have more then 65535 cylinders, more then
255 heads, or more then 63 sectors per track.
Would you like to keep using the current geometry?
Yes No
[..]
This is where I have two choices
Choice 1 (YES) produces the following in fdisk when choosing 'a' to use the
whole disk.
[..]
OffsetSize(ST)EndNamePTypeDescSubtype
Flags
06362-12unused0
6314651491051465149167ad4s18freebsd165
[..]
Choice 2 (NO) produces the following in fdisk when choosing 'a' to use the
whole disk.
[..]
If you are not sure about this, please consult the Hardware Guide in the
Documentation submenu or use the {G}eometry command to change it. Remember:
You need to eneter whatever your BIOS thinks the geometry is! For IDE, it's
what you were told in the BIOS setup. For SCSI, It's the translation mode
your controller is using. Do NOT use a ''physical geometry''.
OK
[..]
[..]
OffsetSize(ST)EndNamePTypeDescSubtype
Flags
06362-12unused0
6314651440021465144064ad4s18freebsd165
146514406551031465149167-12unused0
[..]
Decidedly, the end result is approximately 698GB for the usable partition,
the second choice giving me a padding on both sides of the freebsd slice.
Moving on now, I choose the following
Standard MBR
Disklebel Editor
[..]
PartMountSizenewfs
--
ad4s1a/512MBUFS2 Y
ad4s1bswap4096MBSWAP
ad4s1d/var4973MBUFS2+S Y
ad4s1e/tmp512MBUFS2+S Y
ad4s1f/usr688GBUFS2+S Y
[..]
Decidedly not my first choice for 8.1/amd64, but I can fix that layout
later, once I know how to get the system installed correctly.
'Q' to quick and continue, I choose 'Minimal' then 'CD/DVD' as my
installation media. I got the usual 'Last Chance' warning and then bam, I
get
[..]
Unable to find device node for /dev/ad4s1b in /dev!
The creation of filesystems will be aborted.
OK
Couldn't make filesystems properly. Aborting.
OK
Installation completed with some errors. You may wish to scroll through the
debugging messages on VTY1 with the scroll-lock feature. You can also choose
No at the next prompt and go back into the installation menus to retry
whichever operations have failed.
OK
[..]
And this is where I am left. Hopefully, I've been explicit enough this time
:D Again, if I've missed something, please let me know and I shall provide
it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On Thu, 30 Dec 2010 11:17:48 -0500, Chris Brennan wrote:
On Thu, Dec 30, 2010 at 12:24 AM, Ian Smith smi...@nimnet.asn.au wrote:
I don't expect this to be anything like that. Please show a) how many
slices you allocated and how big this FreeBSD slice is and b) how you
partitioned the FreeBSD slice into (and sizes of) / /var/ /usr [/tmp?]
and especially swap.
I wouldn't allocate any less than 1GB for your root (/) partition esp.
if building custom kernel/s; maybe that's fixed in sysinstall for 8.2?
I cleaned out the thread, leaving only your last bit of questions here.
Goodo. I'll try chopping a bit too ..
I did apparently screw up the 'dd' cmd, I retyped it correctly, below is my
(very carefully) retyped recreation of the Fixit prompt;
[..]
Fixit# dd if=/dev/zero of=/dev/ad4 oseek-0 bs=512 count=1
Assuming that's 'oseek=0', which is the default anyway.
1+0 records in
1+0 records out
512 bytes transferred ub 0.044723 secs (11448 bytes/sec)
Fixit# fdisk -Bi /dev/ad4
*** Working on device /dev/ad4 ***
parameters extracted from in-core disklabel are:
cylinders=1453521 heads=16 sectors/tracks=63 (1008 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1453521 heads=16 sectors/tracks=63 (1008 blks/cyl)
Do you want to change our idea of what BIOS thinks ? [n]
[..]
This is where I stopped, admittedly, I do not know how to use FreeBSD's
fdisk. For the sake of brevity and to move along, I'll break fdisk here and
move back to sysinstall and provide what information I can this way.
Fair enough. 'what BIOS thinks' here is fine on modern disks/boxes, but
the issue here is what a new(ish) user might conceive of as 'modern'!
From sysinstalls menu, I choose 'Standard', next is the usual message about
fdisk partitioning schemes. After this, I get a 'User Confirmation Request',
which is very similar to the warning I received above. It says
[..]
WARNING: It is safe to use a geometry of 1453521/16/63 for ad4 on computers
with modern BIOS versions. If this disk is to be uised on an old machine it
is recommended that it does not have more then 65535 cylinders, more then
255 heads, or more then 63 sectors per track.
Would you like to keep using the current geometry?
Yes No
[..]
This is where I have two choices
Choice 1 (YES) produces the following in fdisk when choosing 'a' to use the
whole disk.
[..]
OffsetSize(ST)EndNamePTypeDescSubtype
Flags
06362-12unused0
6314651491051465149167ad4s18freebsd165
[..]
Yes, you should go with this. 'modern BIOS versions' here refers to
anything later than (roughly) the mid-90s! An 'old machine' in this
context - remembering sysinstall was originally written then - was one
not using LBA (logical block addressing), when 8GB was a fairly big HD
at least for IDE, when the 'big guys' were mostly using SCSI disks.
That message is actually a lot less scary than it was until a couple of
years ago, when it used to cause much more angst and regular posts, see:
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/disks.c.diff?r1=1.160;r2=1.161;f=h
Choice 2 (NO) produces the following in fdisk when choosing 'a' to use the
whole disk.
[..]
If you are not sure about this, please consult the Hardware Guide in the
Documentation submenu or use the {G}eometry command to change it. Remember:
You need to eneter whatever your BIOS thinks the geometry is! For IDE, it's
what you were told in the BIOS setup. For SCSI, It's the translation mode
your controller is using. Do NOT use a ''physical geometry''.
OK
[..]
[..]
OffsetSize(ST)EndNamePTypeDescSubtype
Flags
06362-12unused0
6314651440021465144064ad4s18freebsd165
146514406551031465149167-12unused0
[..]
Decidedly, the end result is approximately 698GB for the usable partition,
the second choice giving me a padding on both sides of the freebsd slice.
You don't say what alternative geometry you entered here, if any .. but
really this whole thing needs to go away. Maybe it needs some heuristic
to see if it could _even possibly_ be an ancient HD needing alternative
geometry? In any case, anything after 2000 is definitely 'modern'.
Copying this to Bruce Cran, who's been hacking on sysinstall lately.
Moving on now, I choose the following
Standard MBR
Disklebel Editor
[..]
PartMountSizenewfs
--
ad4s1a/512MBUFS2 Y
ad4s1bswap4096MBSWAP
ad4s1d/var4973MBUFS2+S Y
ad4s1e/tmp512MBUFS2+S Y
ad4s1f/usr688GBUFS2+S Y
[..]
Re: a new hard-drive in a 2y/o laptop
On Thu, Dec 30, 2010 at 9:19 PM, Ian Smith smi...@nimnet.asn.au wrote: Goodo. I'll try chopping a bit too .. Cleaning out my cruft, leaving only yours :D Assuming that's 'oseek=0', which is the default anyway. yes, a typo in my e-mail only, I got the cmd right in the installer. Fair enough. 'what BIOS thinks' here is fine on modern disks/boxes, but the issue here is what a new(ish) user might conceive of as 'modern'! I'm left to assume that I have a modern system w/ a modern hard-drive (duh lol) Yes, you should go with this. 'modern BIOS versions' here refers to anything later than (roughly) the mid-90s! An 'old machine' in this context - remembering sysinstall was originally written then - was one not using LBA (logical block addressing), when 8GB was a fairly big HD at least for IDE, when the 'big guys' were mostly using SCSI disks. That message is actually a lot less scary than it was until a couple of years ago, when it used to cause much more angst and regular posts, see: http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/disks.c.diff?r1=1.160;r2=1.161;f=h I think it's fair to say, this is still causing some angst. :( I will check out your link when my brain is far less foggy then it is right now. I'm a bit woozy you could say, nyquil works fast on an empty stomach! You don't say what alternative geometry you entered here, if any .. but really this whole thing needs to go away. Maybe it needs some heuristic to see if it could _even possibly_ be an ancient HD needing alternative geometry? In any case, anything after 2000 is definitely 'modern'. Indeed, I didn't, because I wasn't given a choice by sysinstall, it made the choice for me. Copying this to Bruce Cran, who's been hacking on sysinstall lately. Left Bruce in the CC, hopefully he'll offer some useful advice. :D *crosses fingers* Ok, I've been hunting for a commit message I noticed relatively recently and can't find just now, but I think it was to the effect that Bruce had fixed some breakage when choosing 'A' for auto-partitioning, which you indicated having chosen above. It would appear that the layout changes with each new major revision of FBSD, I have different defaults on the old Sony VAIO on the floor next to me that is running 7.3/i386. Indeed you have, and sorry I missed recalling this issue till now. Bruce may have something to add, but if I'm not mistaken you may just need to NOT use 'A' with your 8.1 install media, but to enter values manually. Alternatively, this may be a good time to grab an 8.2-BETA1 disc1 or memstick image where this is likely fixed, but in any case, if I had a FreeBSD slice with even half of ~700GB I'd be very much more generous with / and /tmp, and /var if you'll be using eg big databases. HTH, Ian No worries on missing it, I'm not sure that helped, I farted around with it again earlier today with little more in the way of success. What I tried was to just set up '/' and swamp and it still prompted me about not being able to find /dev/ad4s1b. I will grab an 8.2B1 image tomorrow when I get up and try that, see if it fairs better. Right now, I must sleep, this side of the world is now just after 1am! C- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
On 12/28/10 16:02, Chris Brennan wrote: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. [..] GARBAGEInvalid partition tableError loading operating systemMissing operating systemGARBAGEGARBAGEGARBAGE1+0 records in 1+0 records out 512 bytes transferred in 2.712151 secs (189 bytes/sec) [..] Hi Chris, Are you sure that you got the command right when DDing If you saw Invalid partition tableError loading operating systemMissingoperating system, that suggests to me that you had the equivalent of dd if=/dev/ad4 oseek=1 bs=512 count=1 Here is what I get is I run that DD command on a Windows HDD demophon# dd if=/dev/ada2 bs=512 count=1 3Àм|ûPPü¾¿W¹åó¤Ë½¾±8n| uÅâôÍ▒õÆIt8,tö µ´ð¬tü»´ÍëòNèFs*þF~ t ~ t ¶uÒFV è!s ¶ë¼þ}Uªt ~tÈ ·ë©üWõË¿VÍr#Á$?ÞüC÷ãÑÖ±ÒîB÷â9V w#r9s¸»|NVÍsQOtN2äVÍëäV`»ªU´AÍr6ûUªu0öÁt+a`jjÿv ÿjh|jj´BôÍaasOt 2äVÍëÖaùÃInvalid partition tableError loading operating systemMissing operating system,Dcéêþÿÿ?Á¥P Uª1+0 records in 1+0 records out 512 bytes transferred in 0.363712 secs (1408 bytes/sec) demophon# Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
In freebsd-questions Digest, Vol 343, Issue 5, Message: 10 On Tue, 28 Dec 2010 11:02:45 -0500 Chris Brennan xa...@xaerolimit.net wrote: On Tue, Dec 28, 2010 at 2:23 AM, Michael Powell nightre...@hotmail.comwrote: Try zeroing out the mbr: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. Er, no, Mike. The MBR is in sector 0 of the disk; that would zero out sector 1 as oseek=1 skips over sector 0. What's in sector 1 depends on how/whether the disk is sliced. In a 'dangerously dedicated' (unsliced) disk like a memory stick perhaps, this would usually be /boot/boot1 and include the bsdlabel. In a sliced disk, sectors 1 to 62 are typically unused, the first slice usually starting at sector 63. t23% fdisk -s ad0 /dev/ad0: 232581 cyl 16 hd 63 sec PartStartSize Type Flags 1: 63 8385867 0x0b 0x00 2: 8385930 125821080 0xa5 0x80 3: 13420701033543342 0xa5 0x00 4: 16775073066685815 0xa5 0x00 If you really want to zero out sector 0, leave out the oseek (or use oseek=0) - but you're better off using 'fdisk -Bi' to init a new disk. I have seen this exact error before, and this is what took care of it. -Mike Mmm .. it's not clear from Chris' original message exactly what he did. Mike, Thanks for that little tip, I tried it this morning and it hung for about 30 second w/ no cd/hd activity, then it resumed w/ a beep, it printed some garbage on the console, the only ledgeable was the following [..] GARBAGEInvalid partition tableError loading operating systemMissing operating systemGARBAGEGARBAGEGARBAGE1+0 records in 1+0 records out 512 bytes transferred in 2.712151 secs (189 bytes/sec) [..] This doesn't make sense. Rather than 'I tried it' please show the exact command/s you are issuing. Given it's a new disk you can afford to make mistakes, but once you have anything valuable on a disk you need to take extreme care with dd(1), it's so easy to fatfinger something wrong. eg, what you show above would indicate just what you'd get by running: dd if=/dev/ad4 count=1 ie, using 'if=' not 'of=', with of=/dev/stdout implied, ie to console. If you do want to look at one or more raw sectors, it's very much safer piping dd's stdout to hd (hexdump), as the delays and beep you mention are consistent with piping raw bytes out to the console .. often this can blow your console settings away (I've done it too many times :) If you initialise a disk with the default MBR (or it came that way) then that's usually what's in /boot/mbr - or /boot/boot0 if you've chosen the FreeBSD boot manager, or something else if using (say) grub. t23% dd if=/boot/mbr | hd fc 31 c0 8e c0 8e d8 8e d0 bc 00 7c be 1a 7c bf |.1.|..|.| 0010 1a 06 b9 e6 01 f3 a4 e9 00 8a 31 f6 bb be 07 b1 |..1.| 0020 04 38 2f 74 08 7f 75 85 f6 75 71 89 de 80 c3 10 |.8/t..u..uq.| 0030 e2 ef 85 f6 75 02 cd 18 80 fa 80 72 0b 8a 36 75 |u..r..6u| 0040 04 80 c6 80 38 f2 72 02 8a 14 89 e7 8a 74 01 8b |8.r..t..| 0050 4c 02 bb 00 7c f6 06 bd 07 80 74 2d 51 53 bb aa |L...|.t-QS..| 0060 55 b4 41 cd 13 72 20 81 fb 55 aa 75 1a f6 c1 01 |U.A..r ..U.u| 0070 74 15 5b 66 6a 00 66 ff 74 08 06 53 6a 01 6a 10 |t.[fj.f.t..Sj.j.| 0080 89 e6 b8 00 42 eb 05 5b 59 b8 01 02 cd 13 89 fc |B..[Y...| 0090 72 0f 81 bf fe 01 55 aa 75 0c ff e3 be b9 06 eb |r.U.u...| 00a0 11 be d1 06 eb 0c be f0 06 eb 07 bb 07 00 b4 0e || 00b0 cd 10 ac 84 c0 75 f4 eb fe 49 6e 76 61 6c 69 64 |.u...Invalid| 00c0 20 70 61 72 74 69 74 69 6f 6e 20 74 61 62 6c 65 | partition table| 00d0 00 45 72 72 6f 72 20 6c 6f 61 64 69 6e 67 20 6f |.Error loading o| 00e0 70 65 72 61 74 69 6e 67 20 73 79 73 74 65 6d 00 |perating system.| 00f0 4d 69 73 73 69 6e 67 20 6f 70 65 72 61 74 69 6e |Missing operatin| 0100 67 20 73 79 73 74 65 6d 00 90 90 90 90 90 90 90 |g system| 0110 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 || * 01b0 90 90 90 90 90 90 90 90 90 90 90 90 90 80 00 00 || 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..U.| 0200 1+0 records in 1+0 records out 512 bytes transferred in 0.079548 secs (6436 bytes/sec) Look familiar? :) That's what 'dd if=/dev/ad4 count=1 | hd' would show on a disk with default MBR, except there'd be the slice data in the MBR section of the boot sector, starting at 0x1be, ending with 'sig' 55aa. Restarting the install process, again accepting defaults, I am again Again, please be more explicit. Defaults for what? One slice covering the
Re: a new hard-drive in a 2y/o laptop
On Tue, Dec 28, 2010 at 2:23 AM, Michael Powell nightre...@hotmail.comwrote: Try zeroing out the mbr: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. I have seen this exact error before, and this is what took care of it. -Mike Mike, Thanks for that little tip, I tried it this morning and it hung for about 30 second w/ no cd/hd activity, then it resumed w/ a beep, it printed some garbage on the console, the only ledgeable was the following [..] GARBAGEInvalid partition tableError loading operating systemMissing operating systemGARBAGEGARBAGEGARBAGE1+0 records in 1+0 records out 512 bytes transferred in 2.712151 secs (189 bytes/sec) [..] Restarting the install process, again accepting defaults, I am again presented with [..] 'Unable to find device node for /dev/ad4s1b in dev! The creation of filesystems will be aborted.' OK [..] My question is this now, could this be the fact that this is a really large drive and the bios is 'freaking' out (for lack of a better term) and not properly presenting the disk to the system? While I don't think this is something to consider, something in the back of my head suggests it is. The disk is a different spindle-speed then the old one. [..] 250G - 5400RPM 750G - 7200RPM [..] maybe a (stab in the dark here) bus translation issue, disk is giving the bus too much information? *shrug I dunno, I'm babeling now and I don't have an obnoxious fish in my ear :(. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
Chris Brennan xa...@xaerolimit.net wrote: ... could this be the fact that this is a really large drive and the bios is 'freaking' out (for lack of a better term) and not properly presenting the disk to the system? ... The disk is a different spindle-speed then the old one. [..] 250G - 5400RPM 750G - 7200RPM [..] The RPM is unlikely to be a factor, but the BIOS could well be having trouble with the size / geometry. It might help to let sysinstall use different dimensions for compatibility with older BIOS. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
a new hard-drive in a 2y/o laptop
I've got an HP Business Class laptop (dv2700) and the original 250G SATAII drive is going bad. So I bought a new drive, got a great deal on an SATAII 750G drive for it, bios sees the drive fine. The old drive had FBSD8.2/amd64 installed and it ran fine. I wanted to reinstall to make some partition changes anyway so when I tossed in any install medium I get the following error 'Unable to find device node for /dev/ad4s1b in dev! The creation of filesystems will be aborted.' I didn't select anything crazy and accepted defaults for everything. I figured out the advanced bios option and am in the bios now letting the bios' smart features run there tests (and it just shut down on me, this happens in the winter when the heat is on :( ). Anyway, gonna let it cool down and try the smart tests again. Incidentally, I was able to boot a gentoo disc and set up an ext4 filesystem on the same disk and it worked fine, so I don't understand why freebsd can't preform a newfs on the drive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a new hard-drive in a 2y/o laptop
Chris Brennan wrote: I've got an HP Business Class laptop (dv2700) and the original 250G SATAII drive is going bad. So I bought a new drive, got a great deal on an SATAII 750G drive for it, bios sees the drive fine. The old drive had FBSD8.2/amd64 installed and it ran fine. I wanted to reinstall to make some partition changes anyway so when I tossed in any install medium I get the following error 'Unable to find device node for /dev/ad4s1b in dev! The creation of filesystems will be aborted.' I didn't select anything crazy and accepted defaults for everything. I figured out the advanced bios option and am in the bios now letting the bios' smart features run there tests (and it just shut down on me, this happens in the winter when the heat is on :( ). Anyway, gonna let it cool down and try the smart tests again. Incidentally, I was able to boot a gentoo disc and set up an ext4 filesystem on the same disk and it worked fine, so I don't understand why freebsd can't preform a newfs on the drive. ___ Try zeroing out the mbr: Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. This will zero out any old MBR. I have seen this exact error before, and this is what took care of it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB Hard Drive Dock
Bill Tillman wrote: I just purchased a setup which will allow me to access IDE and/or SATA drives through a USB port. Of course I was hoping for it to work with FreeBSD and in spite of the reviews which said it needed no Windows drivers as soon as I opened it up there was a CD with the drivers for Windows on it. When I hook this thing up to my FreeBSD server it shows up like this: Jul 31 15:06:29 FreeBSD1 root: Unknown USB device: vendor 0x152d product 0x2338 bus uhub1 Jul 31 15:06:29 FreeBSD1 kernel: usbd_set_config_index: could not read device status: USB_ERR_SHORT_XFER Jul 31 15:06:29 FreeBSD1 kernel: ugen1.2: JMicron at usbus1 Jul 31 15:06:29 FreeBSD1 kernel: umass0: MSC Bulk-Only Transfer on usbus1 Jul 31 15:06:29 FreeBSD1 kernel: umass0: SCSI over Bulk-Only; quirks = 0x4000 Jul 31 15:06:30 FreeBSD1 kernel: umass0:0:0:-1: Attached to scbus0 Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 31 15:06:31 FreeBSD1 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Jul 31 15:06:31 FreeBSD1 kernel: da0: Fixed Direct Access SCSI-2 device Jul 31 15:06:31 FreeBSD1 kernel: da0: 40.000MB/s transfers Jul 31 15:06:31 FreeBSD1 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) So apparently the FreeBSD server senses when this thing is connected but it cannot see the drive connected to it. BTW - The FreeBSD server only reports anything when I power up the drive on the device. So again I see there might be hope to access it. Of course I cannot mount anything as /dev/da0s1...etc are not there, only /dev/da0. The drive I'm attempting to mount was the main drive in another FreeBSD server I had working. The drive is ok and I can mount it using other methods. But this hot-swap USB method has some advantaged I'd like to use. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Maybe a firewire hdd dock can help you:handshake: http://www.espow.com/wholesale-sata-hdd-docking-station-for-mac-support-1394b-1394a-firewire-port.html http://www.espow.com/wholesale-sata-hdd-docking-station-for-mac-support-1394b-1394a-firewire-port.html - http://www.espow.com/wholesale-sata-hdd-docking-station-for-mac-support-1394b-1394a-firewire-port.html mac hard drive dock -- View this message in context: http://old.nabble.com/USB-Hard-Drive-Dock-tp29327790p30226090.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB Hard Drive Dock
On Mon, Aug 02, 2010 at 06:03:03PM -0700, Bill Tillman wrote: I will give the drivers on the CD the once over as you suggest. I'm curious about the touch command you recommend. By that do you mean I should # touch /dev/da0s1 This one, I think. Doing a 'camcontrol rescan' might also help. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp4b1R36tKVd.pgp Description: PGP signature
USB Hard Drive Dock
I just purchased a setup which will allow me to access IDE and/or SATA drives through a USB port. Of course I was hoping for it to work with FreeBSD and in spite of the reviews which said it needed no Windows drivers as soon as I opened it up there was a CD with the drivers for Windows on it. When I hook this thing up to my FreeBSD server it shows up like this: Jul 31 15:06:29 FreeBSD1 root: Unknown USB device: vendor 0x152d product 0x2338 bus uhub1 Jul 31 15:06:29 FreeBSD1 kernel: usbd_set_config_index: could not read device status: USB_ERR_SHORT_XFER Jul 31 15:06:29 FreeBSD1 kernel: ugen1.2: JMicron at usbus1 Jul 31 15:06:29 FreeBSD1 kernel: umass0: MSC Bulk-Only Transfer on usbus1 Jul 31 15:06:29 FreeBSD1 kernel: umass0: SCSI over Bulk-Only; quirks = 0x4000 Jul 31 15:06:30 FreeBSD1 kernel: umass0:0:0:-1: Attached to scbus0 Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 31 15:06:31 FreeBSD1 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Jul 31 15:06:31 FreeBSD1 kernel: da0: Fixed Direct Access SCSI-2 device Jul 31 15:06:31 FreeBSD1 kernel: da0: 40.000MB/s transfers Jul 31 15:06:31 FreeBSD1 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) So apparently the FreeBSD server senses when this thing is connected but it cannot see the drive connected to it. BTW - The FreeBSD server only reports anything when I power up the drive on the device. So again I see there might be hope to access it. Of course I cannot mount anything as /dev/da0s1...etc are not there, only /dev/da0. The drive I'm attempting to mount was the main drive in another FreeBSD server I had working. The drive is ok and I can mount it using other methods. But this hot-swap USB method has some advantaged I'd like to use. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB Hard Drive Dock
On Mon, Aug 02, 2010 at 10:18:46AM -0700, Bill Tillman wrote: I just purchased a setup which will allow me to access IDE and/or SATA drives through a USB port. Of course I was hoping for it to work with FreeBSD and in spite of the reviews which said it needed no Windows drivers as soon as I opened it up there was a CD with the drivers for Windows on it. Take a look at the Windows driver, especially the .INF files that come with it. Sometimes this gives you interesting info. It may also help to add the ID of this particular chip to the list in the umass driver. Maybe it also needs some quirks, as some other chips do. So apparently the FreeBSD server senses when this thing is connected but it cannot see the drive connected to it. BTW - The FreeBSD server only reports anything when I power up the drive on the device. So again I see there might be hope to access it. With multi-card readers it sometimes helps to touch(1) the device node. Have you tried that? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpbpIhoo3YkS.pgp Description: PGP signature
Re: USB Hard Drive Dock
--- On Mon, 8/2/10, Roland Smith rsm...@xs4all.nl wrote: From: Roland Smith rsm...@xs4all.nl Subject: Re: USB Hard Drive Dock To: Bill Tillman btillma...@yahoo.com Cc: freebsd-questions@freebsd.org Date: Monday, August 2, 2010, 3:42 PM On Mon, Aug 02, 2010 at 10:18:46AM -0700, Bill Tillman wrote: I just purchased a setup which will allow me to access IDE and/or SATA drives through a USB port. Of course I was hoping for it to work with FreeBSD and in spite of the reviews which said it needed no Windows drivers as soon as I opened it up there was a CD with the drivers for Windows on it. Take a look at the Windows driver, especially the .INF files that come with it. Sometimes this gives you interesting info. It may also help to add the ID of this particular chip to the list in the umass driver. Maybe it also needs some quirks, as some other chips do. So apparently the FreeBSD server senses when this thing is connected but it cannot see the drive connected to it. BTW - The FreeBSD server only reports anything when I power up the drive on the device. So again I see there might be hope to access it. With multi-card readers it sometimes helps to touch(1) the device node. Have you tried that? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) I will give the drivers on the CD the once over as you suggest. I'm curious about the touch command you recommend. By that do you mean I should # touch /dev/da0s1 or # touch /dev/da0s1a...f I didn't know that the newer versions of FreeBSD would allow you to write in /dev folder. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: USB Hard Drive Dock
This went off-list, which was not my intention. -- ryan Begin forwarded message: From: Ryan Coleman ryan.cole...@cwis.biz Date: August 2, 2010 2:47:48 PM CDT To: Bill Tillman btillma...@yahoo.com Subject: Re: USB Hard Drive Dock Bill, I am not sure I follow what you're saying? FreeBSD will not discover a hard drive like this on a hot swap (just connecting the drive to the bridge while plugged in via USB -- in fact that could kill your USB bridge if you don't do it right - a risk in ANY hot swap attempt). If you disconnect the USB, then connect a drive, then reconnect the USB does it find your drive? If so, that's your route. I don't know if *anyone* on this list would recommend you do a traditional hot swap like what you've described. Unless the case if you have a lot of money to spend on replacing PCI USB bridges or motherboards. -- Ryan On Aug 2, 2010, at 12:18 PM, Bill Tillman wrote: I just purchased a setup which will allow me to access IDE and/or SATA drives through a USB port. Of course I was hoping for it to work with FreeBSD and in spite of the reviews which said it needed no Windows drivers as soon as I opened it up there was a CD with the drivers for Windows on it. When I hook this thing up to my FreeBSD server it shows up like this: Jul 31 15:06:29 FreeBSD1 root: Unknown USB device: vendor 0x152d product 0x2338 bus uhub1 Jul 31 15:06:29 FreeBSD1 kernel: usbd_set_config_index: could not read device status: USB_ERR_SHORT_XFER Jul 31 15:06:29 FreeBSD1 kernel: ugen1.2: JMicron at usbus1 Jul 31 15:06:29 FreeBSD1 kernel: umass0: MSC Bulk-Only Transfer on usbus1 Jul 31 15:06:29 FreeBSD1 kernel: umass0: SCSI over Bulk-Only; quirks = 0x4000 Jul 31 15:06:30 FreeBSD1 kernel: umass0:0:0:-1: Attached to scbus0 Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 31 15:06:31 FreeBSD1 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Jul 31 15:06:31 FreeBSD1 kernel: da0:Fixed Direct Access SCSI-2 device Jul 31 15:06:31 FreeBSD1 kernel: da0: 40.000MB/s transfers Jul 31 15:06:31 FreeBSD1 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 15:06:31 FreeBSD1 kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) So apparently the FreeBSD server senses when this thing is connected but it cannot see the drive connected to it. BTW - The FreeBSD server only reports anything when I power up the drive on the device. So again I see there might be hope to access it. Of course I cannot mount anything as /dev/da0s1...etc are not there, only /dev/da0. The drive I'm attempting to mount was the main drive in another FreeBSD server I had working. The drive is ok and I can mount it using other methods. But this hot-swap USB method has some advantaged I'd like to use. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
