Re: Hot Swapping SATA drive?
1) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I insert a drive into this thing while the system is running? Assuming your board supports sata hotswap (too lazy to check) it'll be just fine. I've done this many times with the machine I'm messing with zfs on. Will I be able to mount partitions contained on the drive in question after I do so? y 2) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I remove a drive from this thing while the system is running, assuming that I have already properly umounted all relevant partitions first? No. On my test machine I've been yoinking drives without even any unmounting and it's just fine (up until I pull that last drive in my array and zfs shits the bed). Honestly, the only thing you have to worry about is if you're in there messing with cable ends that you don't accidentally touch the cable clip to something else on the board and short it out. 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? You need the sata ports running in straight up pure ahci mode (as opposed to IDE mode or compatible or something that emulates old style parallel-ata). Be aware that Windows up through XP doesn't support ahci, so if you're dual booting an old system you'll have problems. You'll also almost certainly want to disable any motherboard-based raid options too, as they tend to be complete crap. sata vs esata esata is pin-identical to normal sata. The only difference is that esata has a more robust plug design meant to handle frequent [dis]connections and tighter electrical requirements in the cable for longer distances. As far as your board/OS is concerned, it's just another sata port. __ it has a certain smooth-brained appeal ___ 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: Hot Swapping SATA drive?
On Sat, 18 May 2013 10:49:13 -0400 Quartz articulated: You need the sata ports running in straight up pure ahci mode (as opposed to IDE mode or compatible or something that emulates old style parallel-ata). Be aware that Windows up through XP doesn't support ahci, so if you're dual booting an old system you'll have problems. You'll also almost certainly want to disable any motherboard-based raid options too, as they tend to be complete crap. There is a huge amount of information via a quick Google search that would seem to contradict your statements regarding WinXP and AHCI. http://expertester.wordpress.com/2008/07/27/how-to-enable-ahci-windows-xp/ http://answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/how-do-i-change-windows-xp-to-use-ahci-disk-mode/7819a905-cfd9-4966-b2aa-67afc80a31d8 -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Hot Swapping SATA drive?
In message 519794e9.6080...@sneakertech.com, Quartz qua...@sneakertech.com wrote: 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? You need the sata ports running in straight up pure ahci mode (as opposed to IDE mode or compatible or something that emulates old style parallel-ata). OK. Thanks Quartz,. I'll make it a point to check for that. Be aware that Windows up through XP doesn't support ... No worries. The system in question is only running FreeBSD. Someday soon it may be running debian, but *never* will it be running windoze. You'll also almost certainly want to disable any motherboard-based raid options too, as they tend to be complete crap. OK. I never use RAID in any form anyway, so it probably is already disabled, but I'll make a point to double check. Thanks! ___ 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: Hot Swapping SATA drive?
You need the sata ports running in straight up pure ahci mode (as opposed to IDE mode or compatible or something that emulates old style parallel-ata). OK. Thanks Quartz,. I'll make it a point to check for that. The wording on different bios' can often be confusing. I've seen ahci mode referred to on one board as native mode but on a different system it's referred to as enhanced (where normal is emulation), and other oddisims. Double check your mobo manual and find the chapter that talks about it. You'll also almost certainly want to disable any motherboard-based raid options too, as they tend to be complete crap. OK. I never use RAID in any form anyway, so it probably is already disabled, but I'll make a point to double check. A word of warning: Not all boards do things *right*, so it pays to test. I've encountered systems where you get gpt checksum errors and stuff when ahci is on because the board masks part of the drive for its fake-raid stuff even if you have fake-raid supposedly turned off. __ it has a certain smooth-brained appeal ___ 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: Hot Swapping SATA drive?
Be aware that Windows up through XP doesn't support ahci, There is a huge amount of information via a quick Google search that would seem to contradict your statements regarding WinXP and AHCI. Sorry, poor choice of wording. I meant earlier versions of Windows don't support achi *natively*. As your links suggest, you can sometimes find that your manufacturer will provide a driver that lets you fake out WinXP into being ok with your board's implementation of ahci (usually by emulating SCSI), but it's not a universal solution. __ it has a certain smooth-brained appeal ___ 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: Hot Swapping SATA drive?
On Tue, 14 May 2013, RW wrote: On Tue, 14 May 2013 07:45:21 -0400 Robert Huff wrote: Ronald F. Guilmette writes: 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? I am unable to check the BIOS settings on that MB (which may be ASrock as well), but I don't believe I had to do anything other hand make sure eSATA was enabled. I don't there there is any difference between SATA and eSATA above the physical layer. I'm not sure what that setting would do. At a guess, it could connect one of the internal SATA ports to the eSATA connector. ___ 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: Hot Swapping SATA drive?
Warren Block writes: I don't there there is any difference between SATA and eSATA above the physical layer. I'm not sure what that setting would do. At a guess, it could connect one of the internal SATA ports to the eSATA connector. That's the way mine works; on the other hand, it's specially marked internal connector. Robert Huff ___ 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
Hot Swapping SATA drive?
Ronald F. Guilmette writes: I bought one of these things awhile ago: http://www.amazon.com/gp/product/B004LXJXSW/ref=oh_details_o00_s00_i00?ie=UTF8psc=1 I believe I have a similar object, only a) external (eSATA), b) from a different manufacturer, and c) connected to a -CURRENT system. I use it as a backup device. I just now tried to read up a little bit on all of this ACPI stuff, but my eyes are starting to glaze over. So if someone would answer these simple and obvious questions, I'd appreciate it: 1) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I insert a drive into this thing while the system is running? Will I be able to mount partitions contained on the drive in question after I do so? That works for me. I need to re-scan the ata channel using atacontrol but once that happens it's fine. 2) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I remove a drive from this thing while the system is running, assuming that I have already properly umounted all relevant partitions first? Nothing bad happened to me. 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? I am unable to check the BIOS settings on that MB (which may be ASrock as well), but I don't believe I had to do anything other hand make sure eSATA was enabled. Please excuse my ignorance, but I've never done this stuff before. I remember the nerves when I tried this. You should be fine, Robert Huff ___ 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: Hot Swapping SATA drive?
On Tue, 14 May 2013 07:45:21 -0400, Robert Huff wrote: Ronald F. Guilmette writes: 1) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I insert a drive into this thing while the system is running? Will I be able to mount partitions contained on the drive in question after I do so? That works for me. I need to re-scan the ata channel using atacontrol but once that happens it's fine. Isn't that supposed to be camcontrol today? I've been using SCSI hot swap devices for many years, and they usually required a re-scan of the bus. The same often works for USB-connected devices which also use CAM, and maybe SATA and eSATA also support it today? 2) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I remove a drive from this thing while the system is running, assuming that I have already properly umounted all relevant partitions first? Nothing bad happened to me. Again, it may be nice (to the system) to detach the ATA device from the bus; see man atacontrol (and man camcontrol in comparison) for the proper command to do this. From the electrical point of view, there should be no problem. 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? I am unable to check the BIOS settings on that MB (which may be ASrock as well), but I don't believe I had to do anything other hand make sure eSATA was enabled. The only thing that might be worth looking at in the CMOS setup would be the method of the driver, making the device come up as da0 (for example) or ada0, depending if EHCI or XHCI can be selected. But I assume this only applies to USB devices (and maybe Firewire). SATA should work fine with the default settings. -- 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: Hot Swapping SATA drive?
On Tue, 14 May 2013 07:45:21 -0400 Robert Huff wrote: Ronald F. Guilmette writes: 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? I am unable to check the BIOS settings on that MB (which may be ASrock as well), but I don't believe I had to do anything other hand make sure eSATA was enabled. I don't there there is any difference between SATA and eSATA above the physical layer. I'm not sure what that setting would do. You do need to set the SATA channel to AHCI. Note that this may require Windows to be updated if it's on a the same drive or if it's on a a group of channels that's switched collectively. ___ 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: Hot Swapping SATA drive?
In message 20882.9169.697806.928...@jerusalem.litteratus.org, Robert Huff roberth...@rcn.com wrote: Ronald F. Guilmette writes: I bought one of these things awhile ago: http://www.amazon.com/gp/product/B004LXJXSW/ref=oh_details_o00_s00_i00?ie=U TF8psc=1 I believe I have a similar object, only a) external (eSATA), b) from a different manufacturer, and c) connected to a -CURRENT system. I use it as a backup device. Yea, mine is internal, and real SATA. I wonder if that will make a difference. 1) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I insert a drive into this thing while the system is running? Will I be able to mount partitions contained on the drive in question after I do so? That works for me. I need to re-scan the ata channel using atacontrol but once that happens it's fine. Hummm... I tried atacontrol info and I got this: atacontrol: ATA_CAM option is enabled in kernel. Please use camcontrol instead. So I guess I need to use camcontrol instead. But what command? What were you using with atacontrol to re-scan? Was that atacontrol attach? I wonder what the camcontrol equivalent to that is. Nothing obvious is jumping out at me from the man page. I am unable to check the BIOS settings on that MB (which may be ASrock as well), but I don't believe I had to do anything other hand make sure eSATA was enabled. OK. Thanks. I'm determined to try this, and to make it work. Now I just need to know what camcontrol command I should be using. 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: Hot Swapping SATA drive?
In message 20130514144721.aa321c25.free...@edvax.de, Polytropon free...@edvax.de wrote: I've been using SCSI hot swap devices for many years, and they usually required a re-scan of the bus. The same often works for USB-connected devices which also use CAM, and maybe SATA and eSATA also support it today? OK, so what command should I use when I plug a drive in? Would that be camcontrol rescan foo where foo is something like /dev/ada0? I'm guessing that that can't be correct, because ada0 is an actual drive. So what is the device id for the bus itself? Again, it may be nice (to the system) to detach the ATA device from the bus; see man atacontrol (and man camcontrol in comparison) for the proper command to do this. From the electrical point of view, there should be no problem. I am a firm believer in being nice. I just need to know the proper command. Would that be camcontrol stop foo ? The only thing that might be worth looking at in the CMOS setup would be the method of the driver, making the device come up as da0 (for example) or ada0, depending if EHCI or XHCI can be selected. Ummm... my new little SATA plug-in bay is strictly SATA... not eSATA, and *definitely* not USB, so I think that EHCI and/or XHCI are probably irrelevant. Those are strictly USB things, no? 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: Hot Swapping SATA drive?
Ronald F. Guilmette writes: That works for me. I need to re-scan the ata channel using atacontrol but once that happens it's fine. Hummm... I tried atacontrol info and I got this: atacontrol: ATA_CAM option is enabled in kernel. Please use camcontrol instead. So I guess I need to use camcontrol instead. But what command? What were you using with atacontrol to re-scan? Was that atacontrol attach? Yeah - # atacontrol detach ata0 # atacontrol attach ata0 did it. Robert Huff ___ 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: Hot Swapping SATA drive?
On Tue, 14 May 2013 16:34:11 -0700, Ronald F. Guilmette wrote: In message 20130514144721.aa321c25.free...@edvax.de, Polytropon free...@edvax.de wrote: I've been using SCSI hot swap devices for many years, and they usually required a re-scan of the bus. The same often works for USB-connected devices which also use CAM, and maybe SATA and eSATA also support it today? OK, so what command should I use when I plug a drive in? Would that be camcontrol rescan foo where foo is something like /dev/ada0? No. You use the typical SCSI-like device notation, bus:unit:lun, for example 0:1:0, or all for all buses and devices. I'm guessing that that can't be correct, because ada0 is an actual drive. So what is the device id for the bus itself? With camcontrol devlist, you can get a list that will show you what devices have been recognized and how the bus:unit:lun corresponds to the device files. Example: $ camcontrol devlist HL-DT-ST DVDRAM GSA-H42N RL00at scbus0 target 0 lun 0 (pass0,cd0) HL-DT-ST DVD-ROM GDR8163B 0L30 at scbus0 target 1 lun 0 (pass1,cd1) Generic Flash HS-CF 4.55 at scbus3 target 0 lun 0 (pass2,da0) Generic Flash HS-MS/SD 4.55 at scbus3 target 0 lun 1 (pass3,da1) Generic Flash HS-SM 4.55 at scbus3 target 0 lun 2 (pass4,da2) WDC WD15 EARS-00MVWB0at scbus4 target 0 lun 0 (pass5,da3) The disk you're attaching will probably be something like the entries for the USB disk (last line). Again, it may be nice (to the system) to detach the ATA device from the bus; see man atacontrol (and man camcontrol in comparison) for the proper command to do this. From the electrical point of view, there should be no problem. I am a firm believer in being nice. I just need to know the proper command. Would that be camcontrol stop foo ? Yes. You can use the start and stop commands like the attach and detach commands for atacontrol. Additionally, you can use tur for test (if) unit (is) ready, and readcap to print the capabilities. Also reset and rescan are helpful. See man camcontrol for details about what those commands do, and how to properly call them. In most cases, # camcontrol command bus:unit:lun | all will be the correct form. The only thing that might be worth looking at in the CMOS setup would be the method of the driver, making the device come up as da0 (for example) or ada0, depending if EHCI or XHCI can be selected. Ummm... my new little SATA plug-in bay is strictly SATA... not eSATA, and *definitely* not USB, so I think that EHCI and/or XHCI are probably irrelevant. Those are strictly USB things, no? I'm not fully sure about that, but I assume you're right, if the manufacturer has properly glued the SATA ports onto the mainboard instead of creating some strange abomination of a SATA through USB something. :-) -- 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
Hot Swapping SATA drive?
I bought one of these things awhile ago: http://www.amazon.com/gp/product/B004LXJXSW/ref=oh_details_o00_s00_i00?ie=UTF8psc=1 So far, it seems to be working just peachy, but I have yet to do anything the least bit adventurous with it, such as trying to either insert a drive into it or remove a drive from it while the system is powered on (and running FreeBSD). I just now tried to read up a little bit on all of this ACPI stuff, but my eyes are starting to glaze over. So if someone would answer these simple and obvious questions, I'd appreciate it: 1) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I insert a drive into this thing while the system is running? Will I be able to mount partitions contained on the drive in question after I do so? 2) Given a system running FreeBSD 9.1-RELEASE, is anything bad gonna happen if I remove a drive from this thing while the system is running, assuming that I have already properly umounted all relevant partitions first? 3) Assuming that I want to do this stuff, what BIOS options should I be setting or unsetting on the motherboard? Please excuse my ignorance, but I've never done this stuff before. P.S. I am _not_ using ZFS. P.P.S. Motherboard is ASRock N68C-GS FX. ___ 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: sata/ata device permission for user
On 2013-04-15 07:49, Beeblebrox wrote: EDIT: I had already placed in /etc/devfs.conf this entry some time ago: # Allow members of group operator to mount cdrom own /dev/cd0 root:operator perm/dev/cd0 0660 Not allowing mount despite all of these adjustments (being tested with data cd and NOT audio cd), which is what I am unable to figure out. The user also needs access to the corresponding pass device which is shown by camcontrol devlist. He also needs access to /dev/xpt0 I think. signature.asc Description: OpenPGP digital signature
sata/ata device permission for user
The user also needs access to the corresponding pass device which is shown by camcontrol devlist. He also needs access to /dev/xpt0 I think. HL-DT-ST DVDRAM GSA-4165B DL05 at scbus6 target 0 lun 0 (cd0,pass3) crw--- 1 root operator 0x48 Apr 18 07:08 pass0 crw--- 1 root operator 0x49 Apr 18 07:08 pass1 crw--- 1 root operator 0x4a Apr 18 07:08 pass2 crw--- 1 root operator 0x4b Apr 18 07:08 pass3 crw--- 1 root operator 0x42 Apr 18 07:08 xpt0 User is member of operator group. However, I agree with your idea because just now I was working with cdrtools and got this error, but when I ran as root no error: % cdda2wav summary --device /dev/cd0 cdda2wav: Permission denied. Open of /dev/xpt0 failed. Cannot open or use SCSI driver. cdda2wav: For possible targets try 'cdda2wav -scanbus'. Make sure you are root. Probably you did not define your SCSI device. Set the CDDA_DEVICE environment variable or use the -D option. Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5804740.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: sata/ata device permission for user
On Thu, 18 Apr 2013 00:32:09 -0700 (PDT), Beeblebrox wrote: The user also needs access to the corresponding pass device which is shown by camcontrol devlist. He also needs access to /dev/xpt0 I think. Correct, that matches my settings. :-) HL-DT-ST DVDRAM GSA-4165B DL05 at scbus6 target 0 lun 0 (cd0,pass3) crw--- 1 root operator 0x48 Apr 18 07:08 pass0 crw--- 1 root operator 0x49 Apr 18 07:08 pass1 crw--- 1 root operator 0x4a Apr 18 07:08 pass2 crw--- 1 root operator 0x4b Apr 18 07:08 pass3 crw--- 1 root operator 0x42 Apr 18 07:08 xpt0 User is member of operator group. But the group permissions are --- (none). However, I agree with your idea because just now I was working with cdrtools and got this error, but when I ran as root no error: % cdda2wav summary --device /dev/cd0 cdda2wav: Permission denied. Open of /dev/xpt0 failed. Cannot open or use SCSI driver. cdda2wav: For possible targets try 'cdda2wav -scanbus'. Make sure you are root. Probably you did not define your SCSI device. Set the CDDA_DEVICE environment variable or use the -D option. You should be able to see something like this: % cdda2wav summary --device /dev/cd0 No target specified, trying to find one... cdda2wav: Too many CD/DVD/BD-Recorder targets found. scsibus0: 0,0,0 0) 'HL-DT-ST' 'DVDRAM GSA-H42N ' 'RL00' Removable CD-ROM 0,1,0 1) 'HL-DT-ST' 'DVD-ROM GDR8163B' '0L30' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * cdda2wav: Select a target from the list above and use 'cdda2wav dev=b,t,l'. As it has been mentioned, access to xpt is also required. It should be fine to set this via group permissions. This is an example of possible settings: linkcd0 dvd own cd0 root:operator permcd0 0660 own cd1 root:operator permcd1 0660 own pass0 root:operator permpass0 0660 own pass1 root:operator permpass1 0660 own xpt0root:operator permxpt00660 See man xpt for details. -- 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
sata/ata device permission for user
But the group permissions are --- (none). D'oh! Well, that made a difference and I can query the cd0 device with cdda2wav as my user now. I still can't mount a data CD however. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5804757.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: sata/ata device permission for user
On Thu, Apr 18, 2013 at 03:41:11AM -0700, Beeblebrox typed: But the group permissions are --- (none). D'oh! Well, that made a difference and I can query the cd0 device with cdda2wav as my user now. I still can't mount a data CD however. What's the output of: sysctl vfs.usermount ?? -- Ruben ___ 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: sata/ata device permission for user
What's the output of: sysctl vfs.usermount vfs.usermount: 1 I can mount USB devices... - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5804802.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: sata/ata device permission for user
On Thu, 18 Apr 2013 03:41:11 -0700 (PDT), Beeblebrox wrote: But the group permissions are --- (none). D'oh! Well, that made a difference and I can query the cd0 device with cdda2wav as my user now. I still can't mount a data CD however. You need write access to the cd, pass and xpt devices. You also need to _own_ the mount target directory. If you try something temporary within your home directory, it should always work: % cd % mkdir mnttest % mount -o ro -t cd9660 /dev/cd0 mnttest If you intend to mount below /media or into /cdrom or /dvd, you need to set the proper owner. If you are using X with the GiveConsole and TakeConsole script. Then you can do things like this: % mount /media/dvd given that all the over information is preprogrammed in /etc/fstab. -- 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
sata/ata device permission for user
My user is unable to mount cdrom and cannot use qemu for the HDD devices. Why is access to these devices being refused for my user? 1. % mount_cd9660 /dev/cd0 /cdrom mount_cd9660: /dev/cd0: Operation not permitted 2. % qemu-system-x86_64 -hda /dev/ada2 qemu-system-x86_64: -hda /dev/ada2: could not open disk image /dev/ada2: Operation not permitted *SETTINGS:* % id = uid=1001(xyz) gid=0(wheel) groups=0(wheel),5(operator),1001(xyz) /etc/devfs.rules has: [localrules=10] add path 'ada[0-9]*' mode 0660 group operator add path 'da[0-9]*' mode 0660 group operator add path 'cd[0-9]*' mode 0660 group operator /etc/rc.conf has: devfs_system_ruleset=localrules Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691.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: sata/ata device permission for user
On Sun, 14 Apr 2013 01:11:38 -0700 (PDT), Beeblebrox wrote: My user is unable to mount cdrom and cannot use qemu for the HDD devices. Why is access to these devices being refused for my user? Because there have to be certain permissions in order to allow a non-root user perform such tasks: 1. The setting vfs.usermount=1 has to be present in /etc/sysctl.conf . 2. The user must have write access to the device file. 3. The user has to own the mount directory. It helps if the user is in the wheel group. 1. % mount_cd9660 /dev/cd0 /cdrom mount_cd9660: /dev/cd0: Operation not permitted Check permissions of /dev/cd0 and /cdrom. 2. % qemu-system-x86_64 -hda /dev/ada2 qemu-system-x86_64: -hda /dev/ada2: could not open disk image /dev/ada2: Operation not permitted Check permissions of /dev/ada2, maybe write permission is needed? *SETTINGS:* % id = uid=1001(xyz) gid=0(wheel) groups=0(wheel),5(operator),1001(xyz) /etc/devfs.rules has: [localrules=10] add path 'ada[0-9]*' mode 0660 group operator add path 'da[0-9]*' mode 0660 group operator add path 'cd[0-9]*' mode 0660 group operator /etc/rc.conf has: devfs_system_ruleset=localrules Looks correct, but doesn't seem to be sufficient. But take into mind that /etc/devfs.rules is used for dynamically allocated devices, and /etc/devfs.conf for those present at boot time (usually cd, maybe also da and ada depending on your setup). Also see: http://forums.freebsd.org/showthread.php?t=5796 Compare to Handbook 19.5.2: http://www.freebsd.org/doc/en/books/handbook/usb-disks.html Maybe also helpful: http://www.cyberciti.biz/faq/freebsd-allow-ordinary-users-mount-cd-rom-dvds-usb-removabledevice/ -- 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
sata/ata device permission for user
Hello, 1. Neglected to specify that vfs.usermount=1 is set in /etc/sysctl.conf. My user can mount USB drives. 2. Settings in /etc/devfs.rules is being passed to system correctly because ownership is correct: crw-rw 1 root operator 0x57 Apr 15 09:46 /dev/cd0 3. File permissions for /cdrom is root operator 2 Mar 3 2011 cdrom/ I had also tried mounting on a folder with 1777 permission before posting. Otherwise, * I had solved the qemu problem, it was a small oversight. It helps if the user is in the wheel group. Membership in operator should be sufficient... Looks correct, but doesn't seem to be sufficient. /etc/devfs.rules is used for dynamically allocated devices and /etc/devfs.conf for those present at boot time. As far as I understand, you can set rules for any device in devfs.rules, but not vice-versa. But I should also try with devfs.conf just to make sure... Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5803879.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
sata/ata device permission for user
EDIT: I had already placed in /etc/devfs.conf this entry some time ago: # Allow members of group operator to mount cdrom own /dev/cd0 root:operator perm/dev/cd0 0660 Not allowing mount despite all of these adjustments (being tested with data cd and NOT audio cd), which is what I am unable to figure out. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5803900.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
rescan of sata channels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, is there a way to detach and attach a device on a sata channel in FreeBSD 9 on FreeBSD 8 I used atacontrol detach to detach a sata HD bevor removing it from a hotswap bay and atacontroll attach to rescan the channel after inserting a new Harddrive in die Bay. In camcontroll there is no such command. an rescan or reinit doesn't reveal the new hdd. Is there a way to force the sata channel to rescan an detect the Harddisk without reboot. Regards Estartu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (FreeBSD) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQCVAwUBUMb3KAzx22nOTJQRAQJhygP/c4VUBQTpTko66ZuNuV06tryPf5T9gxIE j0ViE9hzzjcuazo0tBlqwO/RGNIn5z0K8JWYj9SLWLdLBLI5fsk98Q3ApUvdr0bA 4/rq53wxvehJeqTfqywTs6ECIrpnHE0R49PKkf1CqNkHBntEtUDQXvfmBT0gh2vV wRZbky9sa9U= =xxsH -END PGP SIGNATURE- ___ 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
supermicro sat2-mv8 sata raid card driver
Hello, are there any plans to provide a driver for the supermicro sat2-mv8 (8-port) sata raid card ? Kind regards, Dirk ___ 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
ahcich Timeouts SATA SSD
My configuration is as follows: FreeBSD 8.2-RELEASE Supermicro X8DTi-LN4F (Intel Tylersburg 5520 chipset) motherboard 24 GB system memory 32 x Hitachi Deskstar 5K3000 disks connected to 4 x Intel SASUC8I (LSI 3081E-R) in IT mode 2 x Crucial M4 64 Gb SATA SSD for FreeBSD OS (zroot) 2 x Intel 320 MLC 80 Gb SATA SSD for L2ARC and swap SSD are connected to on-board SATA port on motherboard This system was commissioned in February of 2012 and ran without issue as a ZFS backup system on our network until about 3 weeks ago. At that time I started getting kernel panics due to timeouts to the on-board SATA devices. The only change to the system since it was built was to add an SSD for swap (32 Gb swap device) and this issue did not happen until several months after this was added. My initial thought was that I might have a bad SSD drive so I swapped out one of the Crucial SSD drives and the problem happened again a few days later. I then moved to systematically replacing items such as SATA cables, memory, motherboard, etc and the problem continued. For example, I swapped out the 4 SATA cables with brand new SATA cables and waited to see if the problem happened again. Once it did I moved on to replacing the motherboard with an identical motherboard, waited, etc. I could not find an obvious hardware related explanation for this behavior so about a week and a half ago I did a fresh install of FreeBSD 9.0-RELEASE to move from the ATA driver to the AHCI driver as I found some evidence that this was helpful. The problem continued with something like this: ahcich0: Timeout on slot 29 port 0 ahcich0: is 0 cs ss e000 rs e000 tfd 40 serr cmd 0004df17 ahcich0: AHCI reset: device not ready after 31000ms (tfd = 0080) ahcich0: Timeout on slot 31 port 0 ahcich0: is cs 8000 ss rs 8000 tfd 80 serr cmd 0004df17 (ada0:ahcich0:0:0:0): lost device ahcich0: AHCI reset: device not ready after 3100ms (tfd = 0080) ahcich0: Timeout on slot 31 port 0 ahcich0: is cs 8003 ss 80003 rs 8003 tfd 80 serr 000 cmd 0004df17 (ada0:ahcich0:0:0:0): removing device entry ahcich0: AHCI reset: device not ready after 31000ms (tfd = 0080) ahcich0: Poll timeout on slot 1 port 0 ahcich0: is cs 0002 ss 0 rs 002 tfd 80 serr cmd 004c117 When this happens the only way to recover the system is to hard boot via IPMI (yanking the power vs hitting reset). I cannot say that every time this happens a hard reset is necessary but more often than not a hard reset is necessary as the on-board AHCI portion of the BIOS does not always see the disks after the event without a hard system power reset. I have done a bunch of Google work on this and have seen the issue appear in FreeNAS and FreeBSD but no clear cut resolution in terms of how to address it or what causes it. Some people had a bad SSD, others had to disable NCQ or power management on their SSD, particular brands of SSD (Samsung), etc. Nothing conclusive so far. At the present time the issue happens every 1-2 hours unless I have the following in my /boot/loader.conf after the ahci_load statement: ahci_load=YES # See ahci(4) hint.ahcich.0.sata_rev=1 hint.ahcich.1.sata_rev=1 hint.ahcich.2.sata_rev=1 hint.ahcich.3.sata_rev=1 hint.ahcich.0.pm_level=1 hint.ahcich.1.pm_level=1 hint.ahcich.2.pm_level=1 hint.ahcich.3.pm_level=1 I have a script in /usr/local/etc/rc.d which disables NCQ on these drives: #!/bin/sh CAMCONTROL=/sbin/camcontrol $CAMCONTROL tags ada0 -N 1 /dev/null $CAMCONTROL tags ada1 -N 1 /dev/null $CAMCONTROL tags ada2 -N 1 /dev/null $CAMCONTROL tags ada3 -N 1 /dev/null exit 0 I went ahead and pulled the Intel SSDs as they were showing ASR and hardware resets which incremented. Removing both of these disks from the system did not change the situation. The combination of /boot/loader.conf and this script gets me 6 days or so of operation before the issue pops up again. If I remove these two items I get maybe 2 hours before the issue happens again. Right now I'm down to one OS disk and one swap disk and that is it for SSD disks on the system. At the last reboot (yesterday) I disabled APM on the disks (ada0 and ada1 at this point) to see if that makes a difference as I found a reference to this being a potential problem. I'm looking for insight/help on this as I'm about out of options. If there is a way to gather more information when this happens, post up information, etc I'm open to trying it. What is driving me crazy is that I can't seem to come up with a concrete explanation as to why now and not back when the system was built. The issue only seems to happen when the system is idle and the SSD drives do not see much action other than to host OS, scripts, etc while the Intel/LSI based drives is where the actual I/O is at. The system logs do not show anything prior to event happening and the OS
SATA Controllers
Looking through the list of SATA Controllers available at Best Buy, I don't find any of them listed on the 9.0 hardware page. I need a couple cheap ones (for non-production systems). Does anyone have recommendations? ___ 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 9.0 LSI MegaRAID SATA problem
On 07/10/2012 12:00 PM, Bosko Radivojevic wrote: Hi, i just forgot to add following output from FreeBSD 8.3: # atacontrol status ar0 ar0: ATA RAID1 status: READY subdisks: 0 ad4 ONLINE 1 ad6 ONLINE Thanks, Bosko Hi Bosko, For FreeBSD 9.0-RELEASE see the release notes http://www.freebsd.org/releases/9.0R/relnotes.html especially Thegraid(8) http://www.freebsd.org/cgi/man.cgi?query=graidsektion=8manpath=FreeBSD+9.0-RELEASEGEOM class has been added. This is a replacement of theataraid(4) http://www.freebsd.org/cgi/man.cgi?query=ataraidsektion=4manpath=FreeBSD+9.0-RELEASEdriver supporting various BIOS-based software RAID.[r219974 http://svn.freebsd.org/viewvc/base?view=revisionrevision=219974] Disclaimer: http://www.ose.nl/email ___ 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 9.0 LSI MegaRAID SATA problem
# gmirror list gmirror: Command 'list' not available. # gmirror status gmirror: Command 'status' not available. gmirror load It is probably soft-RAID, but I prefer to use it though appropriate driver instead of classical software RAID configured through OS. i would recommend otherwise. Actually it is already strange FreeBSD have drivers to nonexistent hardware, duplicating mostly gmirrorgstripe functionality flaky 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: FreeBSD 9.0 LSI MegaRAID SATA problem
On 07/10/2012 12:11 PM, Wojciech Puchar wrote: It is always better to use gmirror instead of hardware RAID. One have full control over what is going on mmh not always. Nothing replaces a good hardware RAID card with a BBU for real reason i used parantheses for word hardware. That's clear to me. These hardware raid controllers are not very reliable because they are indeed not real hardware raid controllers, but software based. Maybe for desktop usage it's ok/ good enough? It is better to use the operating systems raid capability linke gmirror instead. Of course real hardware raid controllers with cache and battery backed are a different thing and very reliable. Disclaimer: http://www.ose.nl/email ___ 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 9.0 LSI MegaRAID SATA problem
Hi Bas, thank you for response. 'geom disk list' gives me list of disks, but 'geom raid load;geom raid list' doesn't give anything. I've tried 'geom load mirror', but 'geom mirror list' is also empty. What next? :) Thanks! ___ 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 9.0 LSI MegaRAID SATA problem
That's clear to me. These hardware raid controllers are not very reliable because they are indeed not real hardware raid controllers, but software based. Maybe for desktop usage it's ok/ good enough? precise what is desktop usage is. i don't see a reason for doing mirroring for home use. It is better to use the operating systems raid capability linke gmirror instead. always. Of course real hardware raid controllers with cache and battery backed are a different thing and very reliable. if you have workload where battery backed cache will actually improve things (heavy fsync usage) then yes. otherwise no. i've seen many of them, older, newer, and with same disks i always got at least same performance with FreeBSD software solution. Not talking about RAID5 of which i am not interested at all - there is no reason trading performance for available space nowadays with 2-3TB disks. ___ 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 9.0 LSI MegaRAID SATA problem
'geom raid load;geom raid list' doesn't give anything. I've tried 'geom load mirror', but 'geom mirror list' is also empty. what other do you expect with no mirrors created yet? ___ 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 9.0 LSI MegaRAID SATA problem
On 07/10/2012 12:20 PM, Bosko Radivojevic wrote: Hi Bas, thank you for response. 'geom disk list' gives me list of disks, but 'geom raid load;geom raid list' doesn't give anything. I've tried 'geom load mirror', but 'geom mirror list' is also empty. What next? :) Thanks! Hi Bosko, I do not have any experience with these kind of controllers, so I could just guess. What does pciconf -lv produce, looking at the lines for you disk/softraid controller? Look for the device with class = mass storage Maybe it's not fully supported by graid, which would surprise me because graid this is a replacement for ataraid. Disclaimer: http://www.ose.nl/email ___ 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 9.0 LSI MegaRAID SATA problem
On Tue, Jul 10, 2012 at 12:26 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: what other do you expect with no mirrors created yet? But mirror (raid10) array is created through LSI MegaRAID BIOS. I'm trying to replicate behaviour from FreeBSD 8.3 (array created through RAID BIOS, seen as a device in OS). ___ 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 9.0 LSI MegaRAID SATA problem
I proceeded with: graid label Intel raid RAID1 ada0 ada1. Hope this works what I want :) On Tue, Jul 10, 2012 at 12:31 PM, Bosko Radivojevic bosko.radivoje...@gmail.com wrote: On Tue, Jul 10, 2012 at 12:26 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: what other do you expect with no mirrors created yet? But mirror (raid10) array is created through LSI MegaRAID BIOS. I'm trying to replicate behaviour from FreeBSD 8.3 (array created through RAID BIOS, seen as a device in OS). ___ 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 9.0 LSI MegaRAID SATA problem
On 07/10/2012 12:26 PM, Wojciech Puchar wrote: That's clear to me. These hardware raid controllers are not very reliable because they are indeed not real hardware raid controllers, but software based. Maybe for desktop usage it's ok/ good enough? precise what is desktop usage is. Here at work we just use non raided disks for workstations which run linux. The home directories are on nfs, so when a disk fails it's replaced very fast by doing a basic install on a new disk or just replacing the disk by a preinstalled disk laying on the shelf here. i don't see a reason for doing mirroring for home use. Me neither, just keep back-ups of important data on a different place/device It is better to use the operating systems raid capability linke gmirror instead. always. Of course real hardware raid controllers with cache and battery backed are a different thing and very reliable. if you have workload where battery backed cache will actually improve things (heavy fsync usage) then yes. otherwise no. i've seen many of them, older, newer, and with same disks i always got at least same performance with FreeBSD software solution. Not talking about RAID5 of which i am not interested at all - there is no reason trading performance for available space nowadays with 2-3TB disks. I have never tries the FreeBSD raid solution as we always have servers with from past to now acc, amr and mfi controllers with raid1 and raid5 in the past mostly used for databases and perl cgi based web applications. Disclaimer: http://www.ose.nl/email ___ 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 9.0 LSI MegaRAID SATA problem
On Tue, 10 Jul 2012, Bosko Radivojevic wrote: On Tue, Jul 10, 2012 at 12:26 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: what other do you expect with no mirrors created yet? But mirror (raid10) array is created through LSI MegaRAID BIOS. I'm if it is RAID10 i assume you have 4 disks. trying to replicate behaviour from FreeBSD 8.3 (array created through RAID BIOS, seen as a device in OS). BIOS raid is not compatible with gmirror RAID. backup and restore. Actually i would recommend creating it as two RAID1 (gmirror) devices and spreading data. it is safer and..if you can spread data well... faster. BIOS RAID usually use far too small block sizes, to be better on windows benchmarks that shows linear read speed. except specialized uses it is no improvement under unix. What you need is to spread DIFFERENT I/O operations from different task to different heads. ___ 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 9.0 LSI MegaRAID SATA problem
Hi Bosko, I do not have any experience with these kind of controllers, so I could just guess. I have a lot ;) but the only thing i always do is to disable RAID in BIOS just after receiving new machine. whole experience. ___ 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 9.0 LSI MegaRAID SATA problem
Hi all! I have a problem installing FreeBSD 9.0 on Fujitsu Primergy RX200 S5 server with LSI MegaRAID SATA controller (two SATA HDDs in RAID1 array). When booted from a CD, FreeBSD doesn't recognize RAID Array, it recognizes HDDs only (ad4 ad6). On the same server, FreeBSD 8.3 installation recognizes RAID Array (ar0). pciconf -vl on FreeBSD 9.0: ahci0@pci0:0:31:2: class=0x010400 card=0x11501734 chip=0x3a258086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82801JIR (ICH10R) SATA RAID Controller' class = mass storage subclass = RAID pciconf -vl on FreeBSD 8.3: atapci0@pci0:0:31:2:class=0x010400 card=0x11501734 chip=0x3a258086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'SATA RAID Controller' class = mass storage subclass = RAID dmesg output on FreeBSD 8.3: # dmesg|grep ar0 ar0: writing of DDF metadata is NOT supported yet ar0: 952720MB DDF RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master As far as I understand (while I don't have that much FreeBSD experience), amr is the appropriate driver for this controller. Tried to load it manually (kldload /boot/kernel/amr.ko) but it seems the driver is already present in kernel. What am I missing here? Thanks! ___ 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: Many SATA disks
On 3/31/2012 6:28 PM, Daniel Feenberg wrote: We would like to build a FreeBSD machine ourselves with many (~15) SATA drives, but NOT use a RAID controller. We want to be able to remove any drive and connect it to an ordinary motherboard SATA port and mount the filesystem using only the OS provided drivers and tools. I have built many FreeBSD systems, but never used port multipliers and don't know which controllers advertised as RAID controllers will support a plain pass-thru mode. Would anyone like to make a suggestion from actual experience? The system will be used solely for archiving, so performance is not critical, but portability of the partitions to other systems is necessary. We use this controller http://www.addonics.com/products/adsa3gpx8-4e.php connected to 3 external drive cages. It works via the siis driver # camcontrol devlist | egrep ada|ulti WDC WD2001FASS-00U0B0 01.00101 at scbus0 target 0 lun 0 (ada0,pass0) WDC WD2001FASS-00U0B0 01.00101 at scbus0 target 1 lun 0 (ada1,pass1) WDC WD2001FASS-00U0B0 01.00101 at scbus0 target 2 lun 0 (ada2,pass2) WDC WD2001FASS-00U0B0 01.00101 at scbus0 target 3 lun 0 (ada3,pass3) Port Multiplier 47261095 1f06at scbus0 target 15 lun 0 (pass4,pmp2) WDC WD2002FAEX-007BA0 05.01D05 at scbus2 target 0 lun 0 (ada4,pass5) WDC WD2002FAEX-007BA0 05.01D05 at scbus2 target 1 lun 0 (ada5,pass6) WDC WD2002FAEX-007BA0 05.01D05 at scbus2 target 2 lun 0 (ada6,pass7) WDC WD2002FAEX-007BA0 05.01D05 at scbus2 target 3 lun 0 (ada7,pass8) WDC WD2002FAEX-007BA0 05.01D05 at scbus2 target 4 lun 0 (ada8,pass9) Port Multiplier 37261095 1706at scbus2 target 15 lun 0 (pass10,pmp0) WDC WD2002FAEX-007BA0 05.01D05 at scbus3 target 0 lun 0 (ada9,pass11) WDC WD2002FAEX-007BA0 05.01D05 at scbus3 target 1 lun 0 (ada10,pass12) WDC WD2002FAEX-007BA0 05.01D05 at scbus3 target 2 lun 0 (ada11,pass13) WDC WD2002FAEX-007BA0 05.01D05 at scbus3 target 3 lun 0 (ada12,pass14) Port Multiplier 37261095 1706at scbus3 target 15 lun 0 (pass15,pmp1) ST31000333AS SD35at scbus6 target 0 lun 0 (ada13,pass20) ST31000528AS CC35at scbus7 target 0 lun 0 (ada14,pass21) ST31000340AS SD1Aat scbus8 target 0 lun 0 (ada15,pass22) WDC WD1002FAEX-00Z3A0 05.01D05 at scbus11 target 0 lun 0 (ada16,pass23) They are part of a zfs pool, but you could use them as individual drives. If they are not part of some raid system, you will have of course no redundancy should a disk fail, unless you have some other plan for that. For us, the pool is not usable if one of the drive cages fails, so its not the most reliable setup for high availability. But its a backup server, so temporary down time should a PM fail is acceptable. Individual disks of course can be swapped out as needed. Also, using ZFS allows us to easily add to the storage capacity for more backups or for longer snapshot retention. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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
Many SATA disks
We would like to build a FreeBSD machine ourselves with many (~15) SATA drives, but NOT use a RAID controller. We want to be able to remove any drive and connect it to an ordinary motherboard SATA port and mount the filesystem using only the OS provided drivers and tools. I have built many FreeBSD systems, but never used port multipliers and don't know which controllers advertised as RAID controllers will support a plain pass-thru mode. Would anyone like to make a suggestion from actual experience? The system will be used solely for archiving, so performance is not critical, but portability of the partitions to other systems is necessary. Daniel Feenberg NBER ___ 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: Burning CDs or DVDs with SATA drive?
from my previous message: Does growisofs work on CDRs or only DVDs? If 'cdrecord -scanbus' doesn't work at all, how do I get the SCSI device n:n:n? Use camcontrol? I see both FreeBSD and NetBSD have makefs (which can make a UFS/FFS or iso file system, taking the place of mkisofs in cdrtools. But NetBSD has no CD or DVD burner in the base system. I could also try to build cdrkit and see if that works. At that stage I hadn't looked in the Makefile to see that cdrkit was not an option on FreeBSD 9.0 . So far, I tried cdrecord and readcd only as root, so permissions ought not yet to be an issue. amelia2# camcontrol devlist WDC WD30EZRS-11J99B0 80.00A80at scbus1 target 0 lun 0 (pass0,ada0) PLEXTOR DVDR PX-L890SA 1.05at scbus5 target 0 lun 0 (pass1,cd0) WD My Book 1130 1012 at scbus7 target 0 lun 0 (pass2,da0) WD SES Device 1012 at scbus7 target 0 lun 1 (pass3,ses0) UFD USB Flash Drive 1100 at scbus8 target 0 lun 0 (da1,pass4) Kingston DataTraveler 2.0 PMAP at scbus9 target 0 lun 0 (da2,pass5) amelia2# readcd dev=5,0,0 sectors=0-0 - readcd: Device not ready. I got same results after running kldload atapicam. Also, cdrecord -scanbus didn't work at all. In Linux, beginning with kernel 2.6, cdrtools work with ATA or IDE CD or DVD burners without inserting a SCSI layer. Maybe I need to build and install growisofs (sysutils/dvd+rw-tools)? I have /dev/xpt0 even without kldload atapicam, also /dev/pass*. cdrtools use dev=n1,n2,n3, which don't have to be all zero. I had intended, and still intend, to build a Linux installation, may or may not bother with NetBSD. I want to see what Linux can do that FreeBSD can't, how and if the device drivers are superior. NetBSD has no USB 3.0 support now or in the foreseeable future, and otherwise doesn't like my hardware; I tried before installing FreeBSD. Tom ___ 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: Burning CDs or DVDs with SATA drive?
I built and installed sysutils/cdrtools when there was a thread on burncd and SATA, but cdrecord can't see anything (running cdrecord -scanbus): cdrecord: Inappropriate ioctl for device. CAMIOCOMMAND ioctl failed. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd9.0) Copyright (C) 1995-2010 J?rg Schilling Running cdrecord dev=help or cdrecord dev=HELP: did no better. Do you have permissions set properly? Maybe it still tries to access per ATAPICAM, which may be non-working just like acd - just a wild guess, I'm not using 9-RC here so I can't be more specific. I had a similar problem on the older computer (i386 with ATA, not SATA) in NetBSD, but cdrecord ran well in Linux. CD-RW drive there is ATAPI. I've been using cdrecord and cdrdao now since burncd stopped working for me somewhere in v5. For DVDs, growisofs should work. While cdrecord and cdrdao address th SCSI device by n:n:n, growisofs uses /dev/cdN. -- Polytropon After I failed to burn a CD in NetBSD (5.1_STABLE) on the older computer (i386) with cdrecord, I booted into FreeBSD 8.2 RELEASE and was successful with burncd. That drive was CD-RW, ATAPI, that computer has ATA but no SATA. Does growisofs work on CDRs or only DVDs? If 'cdrecord -scanbus' doesn't work at all, how do I get the SCSI device n:n:n? Use camcontrol? I see both FreeBSD and NetBSD have makefs (which can make a UFS/FFS or iso file system, taking the place of mkisofs in cdrtools. But NetBSD has no CD or DVD burner in the base system. I could also try to build cdrkit and see if that works. Tom ___ 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: Burning CDs or DVDs with SATA drive?
On Fri, 4 Nov 2011 09:23:13 + (GMT), Thomas Mueller wrote: After I failed to burn a CD in NetBSD (5.1_STABLE) on the older computer (i386) with cdrecord, I booted into FreeBSD 8.2 RELEASE and was successful with burncd. That drive was CD-RW, ATAPI, that computer has ATA but no SATA. Good to see that it's still supposed to work in 8.2. :-) Does growisofs work on CDRs or only DVDs? Haven't tested that, but it should also work for CD media instead of DVD, just the size of the ISO data is limited to the size of a CD. If 'cdrecord -scanbus' doesn't work at all, how do I get the SCSI device n:n:n? Use camcontrol? Yes. You need to have the device ATAPICAM option in your kernel (or the module for that functionality), then you can do: # camcontrol devlist HL-DT-ST DVDRAM GSA-H42N RL00at scbus0 target 0 lun 0 (pass0,cd0) HL-DT-ST DVD-ROM GDR8163B 0L30 at scbus0 target 1 lun 0 (pass1,cd1) Generic Flash HS-CF 4.55 at scbus3 target 0 lun 0 (pass2,da0) Generic Flash HS-MS/SD 4.55 at scbus3 target 0 lun 1 (pass3,da1) Generic Flash HS-SM 4.55 at scbus3 target 0 lun 2 (pass4,da2) The first two entries are optical drives, the first one has recording capability. Device ID is 0:0:0, the corresponding device files are /dev/pass0 and /dev/cd0, _those_ are provided by ATAPICAM. Programs like cdreord and cdrdao require the 0:0:0 device, growisofs uses /dev/cd0. Note that you need to set the _permissions_ for those device files in order to use non-root access to them! You also need access to /dev/xpt0 which belongs to the artificial SCSI subsystem. :-) You could, for example, make them owned root:operator, permission 0660, and add your user to the operator group. I see both FreeBSD and NetBSD have makefs (which can make a UFS/FFS or iso file system, taking the place of mkisofs in cdrtools. But NetBSD has no CD or DVD burner in the base system. I did always use mkisofs for preparing the ISO for a CD, but you can include that step by piping. The growisofs does this step implicitely, e. g. % growisofs -Z /dev/dvd -r -J /path/to/files This will run mkisofs - the flags -r and -J are explained in man mkisofs. For a pre-mastered ISO file, % growisofs -dvd-compat -Z /dev/dvd=image.iso would do the job. This ISO file could have been created by mkisofs, by k9copy, or even by dd. You can also use this with VCD images, created by mkvcdfs, as far as I remember. By the way, I have symlinked /dev/dvd to /dev/cd0 so I can access this more easily. :-) I could also try to build cdrkit and see if that works. Haven't tested this one yet, but it seems to conflict with cdrtools, and according to the Makefile, it does not run on v9. Sounds like it's work trying. -- 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
Burning CDs or DVDs with SATA drive?
What software, base or ports, is used to burn a CD or DVD on a SATA drive, /dev/cd0 ? Would burncd be appropriate, or do I need cdrtools? Or cdrkit? This is on FreeBSD 9.0-RC1 amd64. I built and installed sysutils/cdrtools when there was a thread on burncd and SATA, but cdrecord can't see anything (running cdrecord -scanbus): cdrecord: Inappropriate ioctl for device. CAMIOCOMMAND ioctl failed. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd9.0) Copyright (C) 1995-2010 Jörg Schilling Running cdrecord dev=help or cdrecord dev=HELP: did no better. I had a similar problem on the older computer (i386 with ATA, not SATA) in NetBSD, but cdrecord ran well in Linux. CD-RW drive there is ATAPI. Tom ___ 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: Burning CDs or DVDs with SATA drive?
On Thu, 3 Nov 2011 10:32:16 + (GMT), Thomas Mueller wrote: What software, base or ports, is used to burn a CD or DVD on a SATA drive, /dev/cd0 ? Would burncd be appropriate, or do I need cdrtools? Or cdrkit? This is on FreeBSD 9.0-RC1 amd64. I can imagine that in 9.0 where acd is obsoleted by cd, burncd will either be rewritten, or be useless. In that case, using tools that work with old-fashioned and now modern cd should work fine. I built and installed sysutils/cdrtools when there was a thread on burncd and SATA, but cdrecord can't see anything (running cdrecord -scanbus): cdrecord: Inappropriate ioctl for device. CAMIOCOMMAND ioctl failed. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd9.0) Copyright (C) 1995-2010 Jörg Schilling Running cdrecord dev=help or cdrecord dev=HELP: did no better. Do you have permissions set properly? Maybe it still tries to access per ATAPICAM, which may be non-working just like acd - just a wild guess, I'm not using 9-RC here so I can't be more specific. I had a similar problem on the older computer (i386 with ATA, not SATA) in NetBSD, but cdrecord ran well in Linux. CD-RW drive there is ATAPI. I've been using cdrecord and cdrdao now since burncd stopped working for me somewhere in v5. For DVDs, growisofs should work. While cdrecord and cdrdao address th SCSI device by n:n:n, growisofs uses /dev/cdN. -- 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
SATA SDD cards
Has anyone tried using an SATA SSD card (SATA add-on card that is a SSD drive) in FreeBSD? I was looking at an OCZ RevoDrive and was wondering if anyone had tried using one of those specifically, or any SATA SSD card in general. Rob ___ 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: SATA SDD cards
On Wed, Jun 15, 2011 at 11:00 AM, Rob li...@midsummerdream.org wrote: Has anyone tried using an SATA SSD card (SATA add-on card that is a SSD drive) in FreeBSD? I was looking at an OCZ RevoDrive and was wondering if anyone had tried using one of those specifically, or any SATA SSD card in general. I have not used a SATA SSD card, however, I might steer you away from OCZ. I have a regular SSD drive made by them. When I was partitioning the drive, I wanted to make sure that the partitions were aligned with the NAND cell size to maximize the performance of the drive. As you may know already the NAND cell size roughly translates to the sector size in HDDs. On many HDDs the sector size is 512 bytes, but on some newer drives it is 4K, so partitions need to start on 4K boundaries to be aligned properly. So, the same sort of thing is needed with SSD drives, but they are not all 4K, some are 1K, some are 8K etc. So, I delved deep into OCZs information about my drive online and I was not able to find information about the NAND cell size. I eventually called OCZ, and after a bit of back and forth the tech I was talked to went and asked his manager then came back and told me that he is not allowed to give out that information. He did tell me that he was told starting the partition at LBA 64 will make sure that the drive is aligned. This information helps in one sense, but since there are new options in gpart(8) in CURRENT that allow you to set the sector size to automatically align partitions properly this information does not help in the long run. Buy from a company that doesn't keep their drive specs a mystery. ___ 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: SATA Host Adapter Recommendation
--As of May 21, 2011 7:26:22 PM -0700, Jason C. Wells is alleged to have said: I am looking to get 2 sata host adapters. The mandatory requirements are good freebsd support and hot swap capability. I plan to use gmirror. I have discovered that my onboard chipsets don't support hot swap. --As for the rest, it is mine. While I will be reading this thread with interest, as I'm looking to buy a SATA adaptor sometime in the moderate future, I do have one other thought: Before you assume your onboard chipsets don't support hot swap, check your BIOS settings. Many boards still ship with their BIOS set to run everything in 'legacy' mode, which doesn't support hot swap. Make sure there isn't a switch for a AHCI mode that needs to be flipped. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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
SATA Host Adapter Recommendation
I am looking to get 2 sata host adapters. The mandatory requirements are good freebsd support and hot swap capability. I plan to use gmirror. I have discovered that my onboard chipsets don't support hot swap. The highpoint cards are rated highly on newegg. Are these good with freebsd? Thanks, Jason C. Wells ___ 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: SATA Host Adapter Recommendation
I have a Highpoint 4-port PCI-E 4x card in a server that has worked well for a few years. It's a bit pricey, but I've had no problems with it. Recently, I've gotten 3 Rosewill RC-218 cards because they're much cheaper and I don't need the RAID functionality on other cards. I'm building servers with them now, but FreeBSD recognizes the disks attached to them fine (so long as your on = 8.2 and you add hw.hptrr.attach_generic=0 in /boot/loader.conf). I haven't tried hot-swapping any drives yet, but I'm assuming since it's SATA it should work fine. I should probably verify that soon. Rob On 5/21/11 9:26 PM, Jason C. Wells wrote: I am looking to get 2 sata host adapters. The mandatory requirements are good freebsd support and hot swap capability. I plan to use gmirror. I have discovered that my onboard chipsets don't support hot swap. The highpoint cards are rated highly on newegg. Are these good with freebsd? Thanks, Jason C. Wells ___ 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
Best SATA/SAS controller for ZFS on FreeBSD 8.2 RELEASE?
My hardware: Dell 1950 with dual quad-core X5450 processors, 16GB RAM, boot drive connected to a SAS 6/iR controller (mpt0), pair of external ACARD 9010 RAMDisks (da3 da4) connected to an LSI SAS3801E controller (mpt1). The RAMdisks are configured in a ZFS mirror (Backbone) in hopes of both high IOPS and data integrity. Main purpose of the database is to run a small (4GB) PostgreSQL database. My problem: Twice in the last 3 weeks I see more and more errors from the mpt1 driver until it decides that it's lost the drives and Postgres hangs. I try a shutdown-h, which it can't complete, and eventually hold down the power button to shut the machine off. When I boot it it comes up fine, scrubs complete in seconds with zero errors found, and all is grand... Until the next time. I'm hesitant to blame the RAMdisks, because (1) I've got some of them working fine for me with other OSes and (2) zpool scrub consistently shows no errors. I've read some suggestions on the Net suggesting that the MPT driver in FreeBSD is sub-optimal, so that's one area I want to check-- is there another controller that would be better? Most of my ZFS experience has been in OpenSolaris, where LSI cards are pretty much the standard, but FreeBSD is not OpenSolaris Logfiles below: May 11 17:58:46 backbone kernel: mpt1: attempting to abort req 0xff800068b790:25990 function 0 May 11 17:58:46 backbone kernel: mpt1: mpt_cam_event: 0x16 May 11 17:58:46 backbone kernel: mpt1: mpt_cam_event: 0x16 May 11 17:58:47 backbone kernel: mpt1: abort of req 0xff800068b790:25990 completed May 11 17:58:47 backbone kernel: mpt1: attempting to abort req 0xff800068b790:25990 function 0 May 11 17:58:47 backbone kernel: mpt1: mpt_cam_event: 0x16 May 11 17:58:47 backbone kernel: mpt1: mpt_cam_event: 0x16 May 11 17:58:47 backbone kernel: mpt1: abort of req 0xff800068b790:25990 completed May 11 17:58:47 backbone kernel: mpt1: attempting to abort req 0xff800068b790:25990 function 0 May 11 17:58:48 backbone kernel: mpt1: abort of req 0xff800068b790:25990 completed May 11 17:58:48 backbone kernel: mpt1: attempting to abort req 0xff800068b790:25990 function 0 May 11 17:58:48 backbone kernel: mpt1: abort of req 0xff800068b790:25990 completed Eventually it tires of those entries and segues into: May 11 17:59:24 backbone kernel: mpt1: mpt_cam_event: 0x16 May 11 17:59:24 backbone last message repeated 2 times May 11 17:59:24 backbone kernel: (da3:mpt1:0:2:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 11 17:59:24 backbone kernel: (da3:mpt1:0:2:0): CAM status: SCSI Status Error May 11 17:59:24 backbone kernel: (da3:mpt1:0:2:0): SCSI status: Check Condition May 11 17:59:24 backbone kernel: (da3:mpt1:0:2:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) May 11 17:59:24 backbone kernel: (da4:mpt1:0:4:0): WRITE(10). CDB: 2a 0 0 40 53 39 0 0 18 0 May 11 17:59:24 backbone kernel: (da4:mpt1:0:4:0): CAM status: SCSI Status Error May 11 17:59:24 backbone kernel: (da4:mpt1:0:4:0): SCSI status: Check Condition May 11 17:59:24 backbone kernel: (da4:mpt1:0:4:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) And then it starts complaining about vdev I/O failures: May 11 17:59:58 backbone root: ZFS: vdev I/O failure, zpool=Backbone path=/dev/da3 offset=270336 size=8192 error=6 May 11 17:59:58 backbone kernel: (da3:mpt1:0:2:0): lost device May 11 17:59:58 backbone kernel: (da3:mpt1:0:2:0): Invalidating pack May 11 17:59:58 backbone last message repeated 3 times May 11 17:59:58 backbone kernel: (da4:mpt1:0:4:0): lost device May 11 17:59:58 backbone kernel: (da4:mpt1:0:4:0): Invalidating pack May 11 17:59:58 backbone last message repeated 3 times May 11 17:59:58 backbone kernel: (da3:mpt1:0:2:0): Synchronize cache failed, status == 0xa, scsi status == 0x0 May 11 17:59:58 backbone kernel: (da3:mpt1:0:2:0): removing device entry May 11 17:59:58 backbone kernel: (da4:mpt1:0:4:0): Synchronize cache failed, status == 0xa, scsi status == 0x0 May 11 17:59:58 backbone kernel: May 11 17:59:58 backbone kernel: (da4:mpt1:0:4:0): removing device entry May 11 17:59:58 backbone root: ZFS: vdev I/O failure, zpool=Backbone path=/dev/da3 offset=8589156352 size=8192 error=6 May 11 17:59:58 backbone root: ZFS: vdev I/O failure, zpool=Backbone path=/dev/da3 offset=8589418496 size=8192 error=6 May 11 17:59:58 backbone root: ZFS: vdev I/O failure, zpool=Backbone path=/dev/da4 offset=270336 size=8192 error=6 May 11 17:59:58 backbone root: ZFS: vdev I/O failure, zpool=Backbone path=/dev/da4 offset=8589156352 size=8192 error=6 May 11 17:59:58 backbone root: ZFS: vdev I/O failure, zpool=Backbone path=/dev/da4 offset=8589418496 size=8192 error=6 May 11 17:59:58 backbone root: ZFS: zpool I/O failure, zpool=Backbone error=6 May 11 17:59:58 backbone last message repeated 15 times May 11 17:59:58 backbone root: ZFS: zpool I/O failure, zpool=Backbone error=28 May 11 17:59:58 backbone last
Re: how to enable NCQ on Intel ESB2 AHCI SATA?controller/ST31000340NS
On Wed, 23 Mar 2011 16:37:11 -0500, Dan Nelson wrote: DN If you do a verbose boot, you should get a couple more lines printed: DN DN ahci0: Caps: 64bit NCQ SNTF AL CLO 3Gbps PM PMD SSC PSC 32cmd CCC EM 6ports DN ahci0: Caps2: DN ahci0: EM Caps: ALHD XMT SMB LED DN DN If you see NCQ in your Caps line, then queueing should be supported by the DN controller. Looking at the ahci.c source, there is a quirk AHCI_Q_NONCQ DN that disables NCQ, but it it only used for VIA VT8251 chips. It seems to be NCQ not supported by this controller: ahci0: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported ahci0: Caps: 64bit ALP AL 3Gbps PM SSC PSC 32cmd 6ports ahci0: Caps2: -- WBR, Anton Yuzhaninov ___ 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: how to enable NCQ on Intel ESB2 AHCI SATA controller/ST31000340NS
In the last episode (Mar 22), Anton Yuzhaninov said: How to enable NCQ on this controller: ahci0@pci0:0:31:2: class=0x010601 card=0x808015d9 chip=0x26818086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'LSI LOGIC, 62089A2, LSISAS1068 B0, T 0620, WE 119200.1 (62089A2)' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0x18a0, size 8, enabled bar [14] = type I/O Port, range 32, base 0x1874, size 4, enabled bar [18] = type I/O Port, range 32, base 0x1878, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x1870, size 4, enabled bar [20] = type I/O Port, range 32, base 0x1880, size 32, enabled bar [24] = type Memory, range 32, base 0xd8700400, size 1024, enabled cap 01[70] = powerspec 2 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair dmesg: ahci0: Intel ESB2 AHCI SATA controller port 0x18a0-0x18a7,0x1874-0x1877,0x1878-0x187f,0x1870-0x1873,0x1880-0x189f mem 0xd8700400-0xd87007ff irq 19 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported If you do a verbose boot, you should get a couple more lines printed: ahci0: Caps: 64bit NCQ SNTF AL CLO 3Gbps PM PMD SSC PSC 32cmd CCC EM 6ports ahci0: Caps2: ahci0: EM Caps: ALHD XMT SMB LED If you see NCQ in your Caps line, then queueing should be supported by the controller. Looking at the ahci.c source, there is a quirk AHCI_Q_NONCQ that disables NCQ, but it it only used for VIA VT8251 chips. -- Dan Nelson dnel...@allantgroup.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
how to enable NCQ on Intel ESB2 AHCI SATA controller/ST31000340NS
How to enable NCQ on this controller: ahci0@pci0:0:31:2: class=0x010601 card=0x808015d9 chip=0x26818086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'LSI LOGIC, 62089A2, LSISAS1068 B0, T 0620, WE 119200.1 (62089A2)' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0x18a0, size 8, enabled bar [14] = type I/O Port, range 32, base 0x1874, size 4, enabled bar [18] = type I/O Port, range 32, base 0x1878, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x1870, size 4, enabled bar [20] = type I/O Port, range 32, base 0x1880, size 32, enabled bar [24] = type Memory, range 32, base 0xd8700400, size 1024, enabled cap 01[70] = powerspec 2 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair dmesg: ahci0: Intel ESB2 AHCI SATA controller port 0x18a0-0x18a7,0x1874-0x1877,0x1878-0x187f,0x1870-0x1873,0x1880-0x189f mem 0xd8700400-0xd87007ff irq 19 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported ... ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ST31000340NS SN05 ATA-8acd0: DVDROM DVD-ROM UJDA780/1.50 at ata0-slave UDMA33 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ST31000340NS SN05 ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) There is no lines Command Queueing enabled # camcontrol tags ada0 (pass0:ahcich0:0:0:0): device openings: 2 camcontrol identify ada0 pass0: ST31000340NS SN05 ATA-8 SATA 2.x device pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 2.x device model ST31000340NS firmware revision SN05 serial number 9QJ1L67B WWN 5000c500d902ea3 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 1953525168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 7200 Feature Support Enabled Value Vendor read ahead yes yes write cacheyes yes flush cacheyes yes overlapno Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags # uname -srp FreeBSD 8.2-STABLE-20110315 amd64 -- WBR, Anton Yuzhaninov ___ 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: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1)
Bahman Kahinpour bahman.li...@gmail.com wrote: Is AHCI mode the best mode for SATA controller? (highest speed, utilizing all fancy features, ...) In general, probably yes, provided the combination of hardware and driver actually works properly _all_ the time :) AHCI is new enough that the occasional hardware erratum or driver bug might be more likely than with an older technology such as IDE or ATA. ___ 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
Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1)
Hello FreeBSD people all over the world, There is an onboard Intel SATA controller on Intel DH55HC motherboard. I have tried FreeBSD version 7.3 and 8.1 on this motherboard, it recognizes the SATA controller but recognizes the hard disk as IDE devices. How can this happen? $ uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Jan 23 19:28:28 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/CUSTOM i386 $ dmesg | grep SATA atapci1: Intel PCH SATA300 controller port 0xf090-0xf097,0xf080-0xf083,0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 0xfe725000-0xfe7257ff irq 19 at device 31.2 on pci0 ad8: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata4-master UDMA100 SATA 3Gb/s ad10: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata5-master UDMA100 SATA 3Gb/s ad12: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata6-master UDMA100 SATA 3Gb/s acd0: DVDR SONY DVD RW DRU-870S/1.61 at ata7-master UDMA100 SATA 1.5Gb/s $ I did everything to prevent the FreeBSD kernel from recognizing the hard drives as IDE. I turned off all IDE emulation options in the BIOS. How can I fix that? Thanks Bahman Kahinpour ___ 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: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1)
Do you mean that both traditional IDE drives and these new SATA drives both begin with ad in FreeBSD? I am new to FreeBSD, I have just migrated from Linux. In Linux, traditional IDE drives used to begin with hd and these new SATA drives began with sd and recognized as SCSI devices. I expected this new SATA drives to begin with da in FreeBSD. Do you mean I am wrong and both IDE and SATA devices begin with ad? On 1/24/11, Robert Bonomi bon...@mail.r-bonomi.com wrote: From owner-freebsd-questi...@freebsd.org Mon Jan 24 05:48:21 2011 Date: Mon, 24 Jan 2011 15:10:07 +0330 From: Bahman Kahinpour bahman.li...@gmail.com To: freebsd-questions@freebsd.org Subject: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1) Hello FreeBSD people all over the world, There is an onboard Intel SATA controller on Intel DH55HC motherboard. I have tried FreeBSD version 7.3 and 8.1 on this motherboard, it recognizes the SATA controller but recognizes the hard disk as IDE devices. How can this happen? $ uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Jan 23 19:28:28 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/CUSTOM i386 $ dmesg | grep SATA atapci1: Intel PCH SATA300 controller port 0xf090-0xf097,0xf080-0xf083,0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 0xfe725000-0xfe7257ff irq 19 at device 31.2 on pci0 ad8: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata4-master UDMA100 SATA 3Gb/s ad10: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata5-master UDMA100 SATA 3Gb/s ad12: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata6-master UDMA100 SATA 3Gb/s acd0: DVDR SONY DVD RW DRU-870S/1.61 at ata7-master UDMA100 SATA 1.5Gb/s $ I did everything to prevent the FreeBSD kernel from recognizing the hard drives as IDE. I turned off all IDE emulation options in the BIOS. How can I fix that? what are you -expecting- to see? ATA drives, either PATA or SATA _are_ IDE interface. the boot messages show they're being regocnises as SATA, at 3 gigabit/sec. Everything looks right to 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: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1)
On 01/25/11 00:01, Bahman Kahinpour wrote: Do you mean that both traditional IDE drives and these new SATA drives both begin with ad in FreeBSD? I am new to FreeBSD, I have just migrated from Linux. In Linux, traditional IDE drives used to begin with hd and these new SATA drives began with sd and recognized as SCSI devices. I expected this new SATA drives to begin with da in FreeBSD. Do you mean I am wrong and both IDE and SATA devices begin with ad? I believe so, yes. I have several SATA systems running FreeBSD, as well as some ATA. Only difference is the numerical start- ad0 as opposed to ad4, but I believe that is mainboard bios dependent. On 1/24/11, Robert Bonomibon...@mail.r-bonomi.com wrote: From owner-freebsd-questi...@freebsd.org Mon Jan 24 05:48:21 2011 Date: Mon, 24 Jan 2011 15:10:07 +0330 From: Bahman Kahinpourbahman.li...@gmail.com To: freebsd-questions@freebsd.org Subject: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1) Hello FreeBSD people all over the world, There is an onboard Intel SATA controller on Intel DH55HC motherboard. I have tried FreeBSD version 7.3 and 8.1 on this motherboard, it recognizes the SATA controller but recognizes the hard disk as IDE devices. How can this happen? $ uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Jan 23 19:28:28 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/CUSTOM i386 $ dmesg | grep SATA atapci1:Intel PCH SATA300 controller port 0xf090-0xf097,0xf080-0xf083,0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 0xfe725000-0xfe7257ff irq 19 at device 31.2 on pci0 ad8: 476940MBWDC WD5000AADS-00S9B0 01.00A01 at ata4-master UDMA100 SATA 3Gb/s ad10: 476940MBWDC WD5000AADS-00S9B0 01.00A01 at ata5-master UDMA100 SATA 3Gb/s ad12: 476940MBWDC WD5000AADS-00S9B0 01.00A01 at ata6-master UDMA100 SATA 3Gb/s acd0: DVDRSONY DVD RW DRU-870S/1.61 at ata7-master UDMA100 SATA 1.5Gb/s $ I did everything to prevent the FreeBSD kernel from recognizing the hard drives as IDE. I turned off all IDE emulation options in the BIOS. How can I fix that? what are you -expecting- to see? ATA drives, either PATA or SATA _are_ IDE interface. the boot messages show they're being regocnises as SATA, at 3 gigabit/sec. Everything looks right to 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 ___ 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: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1)
-Original Message- From: Bahman Kahinpour [mailto:bahman.li...@gmail.com] Sent: 24 January 2011 11:40 To: freebsd-questions@freebsd.org Subject: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1) Hello FreeBSD people all over the world, There is an onboard Intel SATA controller on Intel DH55HC motherboard. I have tried FreeBSD version 7.3 and 8.1 on this motherboard, it recognizes the SATA controller but recognizes the hard disk as IDE devices. How can this happen? $ uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Jan 23 19:28:28 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/CUSTOM i386 $ dmesg | grep SATA atapci1: Intel PCH SATA300 controller port 0xf090-0xf097,0xf080-0xf083,0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 0xfe725000-0xfe7257ff irq 19 at device 31.2 on pci0 ad8: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata4-master UDMA100 SATA 3Gb/s ad10: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata5-master UDMA100 SATA 3Gb/s ad12: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata6-master UDMA100 SATA 3Gb/s acd0: DVDR SONY DVD RW DRU-870S/1.61 at ata7-master UDMA100 SATA 1.5Gb/s $ I did everything to prevent the FreeBSD kernel from recognizing the hard drives as IDE. I turned off all IDE emulation options in the BIOS. How can I fix that? Thanks Bahman Kahinpour ___ 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 This is very motherboard dependent, if your board supports AHCI, putting the sata controller in to that mode will result in the drives starting as ada rather than ad. You will also need to load the AHCI driver in /etc/loader.conf ahci_load=YES ada0 at ahcich0 bus 0 target 0 lun 0 ada0: SAMSUNG HD154UI 1AG01118 ATA/ATAPI-7 SATA 2.x device ada0: 300.000MB/s transfers ada0: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C) ada0: Native Command Queueing enabled I pulled that from one of my systems, the data drives are sata the boot disk is IDE so for me changing to AHCI had no effect on the system booting, if you boot from a SATA drive I suspect you might need to tweak fstab to allow the system to boot correctly. Regards Graeme ___ 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: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1)
Oh man, I really liked your answer, thanks so much. I disabled all legacy options in the BIOS (SATA controller is in AHCI mode which I do not know what it is) and added this little ahci_load=YES thing to /boot/loader.conf and now my hard drives are recognized as: (and changed fstab and of course after a few little errors in the boot process): ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: WDC WD5000AADS-00S9B0 01.00A01 ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: WDC WD5000AADS-00S9B0 01.00A01 ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: WDC WD5000AADS-00S9B0 01.00A01 ATA-8 SATA 2.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) Trying to mount root from ufs:/dev/ada0s1a I think it's good now. And the order of recognition of drives is the same as Linux (I mean ada0=sda ada1=sdb ada2=sdc). Is AHCI mode the best mode for SATA controller? (highest speed, utilizing all fancy features, ...) Good luck On 1/24/11, Graeme Dargie a...@tangerine-army.co.uk wrote: -Original Message- From: Bahman Kahinpour [mailto:bahman.li...@gmail.com] Sent: 24 January 2011 11:40 To: freebsd-questions@freebsd.org Subject: Onboard SATA Controller of Intel DH55HC Motherboard (FreeBSD 7.3 FreeBSD 8.1) Hello FreeBSD people all over the world, There is an onboard Intel SATA controller on Intel DH55HC motherboard. I have tried FreeBSD version 7.3 and 8.1 on this motherboard, it recognizes the SATA controller but recognizes the hard disk as IDE devices. How can this happen? $ uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Jan 23 19:28:28 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/CUSTOM i386 $ dmesg | grep SATA atapci1: Intel PCH SATA300 controller port 0xf090-0xf097,0xf080-0xf083,0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 0xfe725000-0xfe7257ff irq 19 at device 31.2 on pci0 ad8: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata4-master UDMA100 SATA 3Gb/s ad10: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata5-master UDMA100 SATA 3Gb/s ad12: 476940MB WDC WD5000AADS-00S9B0 01.00A01 at ata6-master UDMA100 SATA 3Gb/s acd0: DVDR SONY DVD RW DRU-870S/1.61 at ata7-master UDMA100 SATA 1.5Gb/s $ I did everything to prevent the FreeBSD kernel from recognizing the hard drives as IDE. I turned off all IDE emulation options in the BIOS. How can I fix that? Thanks Bahman Kahinpour ___ 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 This is very motherboard dependent, if your board supports AHCI, putting the sata controller in to that mode will result in the drives starting as ada rather than ad. You will also need to load the AHCI driver in /etc/loader.confahci_load=YES ada0 at ahcich0 bus 0 target 0 lun 0 ada0: SAMSUNG HD154UI 1AG01118 ATA/ATAPI-7 SATA 2.x device ada0: 300.000MB/s transfers ada0: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C) ada0: Native Command Queueing enabled I pulled that from one of my systems, the data drives are sata the boot disk is IDE so for me changing to AHCI had no effect on the system booting, if you boot from a SATA drive I suspect you might need to tweak fstab to allow the system to boot correctly. Regards Graeme ___ 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: ZFS + GPT with root on memory stick and mirrored SATA drives
On 10 January 2011 21:46, Carl Chave c...@chave.us wrote: snip echo -en \n\nNow run these two commands to make the changes live, and reboot zfs set mountpoint=legacy $zpool/be/$nroot zpool set bootfs=$zpool/be/$nroot $zpool\n\n Thanks for the input krad. It would be nice to easily switch back and forth but aren't you still stuck if everything blows up on that first reboot? In order to switch back to the known working dataset you've got to get to a fixit prompt to set the correct bootfs property right? unfortunatly at the moment yes, but all you have to do is reset the bootfs property. It would be nice id you could do something from within the boot loader similar to variables you can pass in grub with opensolaris ___ 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: ZFS + GPT with root on memory stick and mirrored SATA drives
On 11 January 2011 09:09, krad kra...@gmail.com wrote: On 10 January 2011 21:46, Carl Chave c...@chave.us wrote: snip echo -en \n\nNow run these two commands to make the changes live, and reboot zfs set mountpoint=legacy $zpool/be/$nroot zpool set bootfs=$zpool/be/$nroot $zpool\n\n Thanks for the input krad. It would be nice to easily switch back and forth but aren't you still stuck if everything blows up on that first reboot? In order to switch back to the known working dataset you've got to get to a fixit prompt to set the correct bootfs property right? unfortunatly at the moment yes, but all you have to do is reset the bootfs property. It would be nice id you could do something from within the boot loader similar to variables you can pass in grub with opensolaris having said that as long as the loader works you should be able to reset the rootfs variable ___ 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: ZFS + GPT with root on memory stick and mirrored SATA drives
On 11 January 2011 09:19, krad kra...@gmail.com wrote: On 11 January 2011 09:09, krad kra...@gmail.com wrote: On 10 January 2011 21:46, Carl Chave c...@chave.us wrote: snip echo -en \n\nNow run these two commands to make the changes live, and reboot zfs set mountpoint=legacy $zpool/be/$nroot zpool set bootfs=$zpool/be/$nroot $zpool\n\n Thanks for the input krad. It would be nice to easily switch back and forth but aren't you still stuck if everything blows up on that first reboot? In order to switch back to the known working dataset you've got to get to a fixit prompt to set the correct bootfs property right? unfortunatly at the moment yes, but all you have to do is reset the bootfs property. It would be nice id you could do something from within the boot loader similar to variables you can pass in grub with opensolaris having said that as long as the loader works you should be able to reset the rootfs variable some similar stuff here. http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE ___ 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: ZFS + GPT with root on memory stick and mirrored SATA drives
On 10 January 2011 04:58, Carl Chave c...@chave.us wrote: Posting the below for input. The bulk of this is from a guide that Morgan Wesström posted to this list. Some of it is taken from the root on ZFS wiki entries on freebsd.org. Some from a pjd post here: http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ And then there's this that Svein Skogen posted to the list: I usually (today) set up something similar. I sysinstall FreeBSD onto a CF card with the one-big-root method, then create a zpool (on spinning-metal-storage) where I create the usr, tmp, var fs'es, tar|tar the originals over and fix the mountpoint info on the zfs'es. Then I add swap on a zvol (since I don't know how to properly use a kernel dump, I don't need swap to store it). I'm setting up a new home server and I always agonize over partitioning. So the steps below install the base system with zfs root on a usb stick and /tmp /usr /var and swap on mirrored sata drives. I've tested these steps and everything works but before I press on with actually configuring and using the server, does anybody have any input on whether I should or shouldn't do it this way? ZFS best practices suggests that having elements of the root filesystem on different pools is a bad idea. So that might be strike 1. Memory Stick / /bin /boot /dev /etc /lib /libexec /media /mnt /proc /rescue /root /sbin /sys -- /usr/src/sys Hard disk zpool --- /tmp /usr /var swap on zvol Separate zfs datasets - /tmp /usr /usr/home /usr/local /usr/obj /usr/ports /usr/ports/distfiles /usr/ports/packages /usr/src /var /var/log /var/audit /var/tmp Install Procedure (Mostly by Morgan Wesström) - Select your country and keyboard layout. Enter the Fixit environment and use the live filesystem on your DVD. Your usb memory stick will most likely be da0 but you can (and should) check it with camcontrol devlist before you continue. Create a new GPT partitioning scheme: # gpart create -s gpt da0 Create a 64KiB partition for the zfs bootcode starting at LBA 1920: # gpart add -b 1920 -s 128 -t freebsd-boot da0 Create a zfs partition spanning the remainder of the usb memory stick and give it a label we can refer to: # gpart add -t freebsd-zfs -l FreeBSDonUSB da0 (The starting LBA for the first partition is there to align the partitions to the flash memory's erase block size. This is particularly important for the main zfs partition. The main partition above will start at exactly 1MiB (LBA 2048) which will align it to any erase block size used today. This alignment is also of great importance if you use this guide to install FreeBSD to one of the newer harddrives using 4096 byte sectors.) Install the protective MBR to LBA 0 and the zfs bootcode to the first partition: # gpart bootcode -b /dist/boot/pmbr -p /dist/boot/gptzfsboot -i 1 da0 Create /boot/zfs (for zpool.cache) and load the zfs kernel modules: # mkdir /boot/zfs # kldload /dist/boot/kernel/opensolaris.ko # kldload /dist/boot/kernel/zfs.ko Create a zfs pool and set its bootfs property: # zpool create zrootusb /dev/gpt/FreeBSDonUSB # zpool set bootfs=zrootusb zrootusb Switch to fletcher4 checksums and turn off access time modifications: # zfs set checksum=fletcher4 zrootusb # zfs set atime=off zrootusb Create zfs mirrored data pool on SATA disks # zpool create zdata mirror /dev/ad4 /dev/ad6 # zfs set canmount=off zdata # zfs set mountpoint=/zrootusb zdata # zfs set checksum=fletcher4 zdata # zfs create zdata/tmp # zfs create zdata/usr # zfs create zdata/usr/home # zfs create zdata/usr/local # zfs create zdata/usr/obj # zfs create zdata/usr/ports # zfs create zdata/usr/ports/distfiles # zfs create zdata/usr/ports/packages # zfs create zdata/usr/src # zfs create zdata/var # zfs create zdata/var/log # zfs create zdata/var/audit # zfs create zdata/var/tmp Create swap zvol on zdata pool # zfs create -V 5G zdata/swap # zfs set org.freebsd:swap=on zdata/swap # zfs set checksum=off zdata/swap Extract at a minimum, base and the generic kernel: # cd /dist/8.1-RELEASE/base # DESTDIR=/zrootusb ./install.sh # cd ../kernels # DESTDIR=/zrootusb ./install.sh generic Delete the empty, default kernel directory and move the generic kernel into its place: # rmdir /zrootusb/boot/kernel # mv /zrootusb/boot/GENERIC /zrootusb/boot/kernel Make sure the zfs modules are loaded at boot: # cat /zrootusb/boot/loader.conf zfs_load=YES vfs.root.mountfrom=zfs:zrootusb kern.cam.boot_delay=1 ^d Create /etc/rc.conf. Adjust and add to your own needs: # cat /zrootusb/etc/rc.conf hostname=sodserve sshd_enable=YES zfs_enable=YES ^d Setup your time zone: # cp /zrootusb/usr/share/zoneinfo/EST5EDT /zrootusb/etc
Re: ZFS + GPT with root on memory stick and mirrored SATA drives
snip echo -en \n\nNow run these two commands to make the changes live, and reboot zfs set mountpoint=legacy $zpool/be/$nroot zpool set bootfs=$zpool/be/$nroot $zpool\n\n Thanks for the input krad. It would be nice to easily switch back and forth but aren't you still stuck if everything blows up on that first reboot? In order to switch back to the known working dataset you've got to get to a fixit prompt to set the correct bootfs property right? ___ 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
ZFS + GPT with root on memory stick and mirrored SATA drives
Posting the below for input. The bulk of this is from a guide that Morgan Wesström posted to this list. Some of it is taken from the root on ZFS wiki entries on freebsd.org. Some from a pjd post here: http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ And then there's this that Svein Skogen posted to the list: I usually (today) set up something similar. I sysinstall FreeBSD onto a CF card with the one-big-root method, then create a zpool (on spinning-metal-storage) where I create the usr, tmp, var fs'es, tar|tar the originals over and fix the mountpoint info on the zfs'es. Then I add swap on a zvol (since I don't know how to properly use a kernel dump, I don't need swap to store it). I'm setting up a new home server and I always agonize over partitioning. So the steps below install the base system with zfs root on a usb stick and /tmp /usr /var and swap on mirrored sata drives. I've tested these steps and everything works but before I press on with actually configuring and using the server, does anybody have any input on whether I should or shouldn't do it this way? ZFS best practices suggests that having elements of the root filesystem on different pools is a bad idea. So that might be strike 1. Memory Stick / /bin /boot /dev /etc /lib /libexec /media /mnt /proc /rescue /root /sbin /sys -- /usr/src/sys Hard disk zpool --- /tmp /usr /var swap on zvol Separate zfs datasets - /tmp /usr /usr/home /usr/local /usr/obj /usr/ports /usr/ports/distfiles /usr/ports/packages /usr/src /var /var/log /var/audit /var/tmp Install Procedure (Mostly by Morgan Wesström) - Select your country and keyboard layout. Enter the Fixit environment and use the live filesystem on your DVD. Your usb memory stick will most likely be da0 but you can (and should) check it with camcontrol devlist before you continue. Create a new GPT partitioning scheme: # gpart create -s gpt da0 Create a 64KiB partition for the zfs bootcode starting at LBA 1920: # gpart add -b 1920 -s 128 -t freebsd-boot da0 Create a zfs partition spanning the remainder of the usb memory stick and give it a label we can refer to: # gpart add -t freebsd-zfs -l FreeBSDonUSB da0 (The starting LBA for the first partition is there to align the partitions to the flash memory's erase block size. This is particularly important for the main zfs partition. The main partition above will start at exactly 1MiB (LBA 2048) which will align it to any erase block size used today. This alignment is also of great importance if you use this guide to install FreeBSD to one of the newer harddrives using 4096 byte sectors.) Install the protective MBR to LBA 0 and the zfs bootcode to the first partition: # gpart bootcode -b /dist/boot/pmbr -p /dist/boot/gptzfsboot -i 1 da0 Create /boot/zfs (for zpool.cache) and load the zfs kernel modules: # mkdir /boot/zfs # kldload /dist/boot/kernel/opensolaris.ko # kldload /dist/boot/kernel/zfs.ko Create a zfs pool and set its bootfs property: # zpool create zrootusb /dev/gpt/FreeBSDonUSB # zpool set bootfs=zrootusb zrootusb Switch to fletcher4 checksums and turn off access time modifications: # zfs set checksum=fletcher4 zrootusb # zfs set atime=off zrootusb Create zfs mirrored data pool on SATA disks # zpool create zdata mirror /dev/ad4 /dev/ad6 # zfs set canmount=off zdata # zfs set mountpoint=/zrootusb zdata # zfs set checksum=fletcher4 zdata # zfs create zdata/tmp # zfs create zdata/usr # zfs create zdata/usr/home # zfs create zdata/usr/local # zfs create zdata/usr/obj # zfs create zdata/usr/ports # zfs create zdata/usr/ports/distfiles # zfs create zdata/usr/ports/packages # zfs create zdata/usr/src # zfs create zdata/var # zfs create zdata/var/log # zfs create zdata/var/audit # zfs create zdata/var/tmp Create swap zvol on zdata pool # zfs create -V 5G zdata/swap # zfs set org.freebsd:swap=on zdata/swap # zfs set checksum=off zdata/swap Extract at a minimum, base and the generic kernel: # cd /dist/8.1-RELEASE/base # DESTDIR=/zrootusb ./install.sh # cd ../kernels # DESTDIR=/zrootusb ./install.sh generic Delete the empty, default kernel directory and move the generic kernel into its place: # rmdir /zrootusb/boot/kernel # mv /zrootusb/boot/GENERIC /zrootusb/boot/kernel Make sure the zfs modules are loaded at boot: # cat /zrootusb/boot/loader.conf zfs_load=YES vfs.root.mountfrom=zfs:zrootusb kern.cam.boot_delay=1 ^d Create /etc/rc.conf. Adjust and add to your own needs: # cat /zrootusb/etc/rc.conf hostname=sodserve sshd_enable=YES zfs_enable=YES ^d Setup your time zone: # cp /zrootusb/usr/share/zoneinfo/EST5EDT /zrootusb/etc/localtime Create an empty fstab to avoid startup warnings: # touch /zrootusb/etc/fstab Set the root password in the new environment: # cd / # chroot /zrootusb /bin/sh # passwd root
Re: Troubles on SATA drives ZFS
On 10/11/10 21:22, Alejandro Imass wrote: 1) Would damage to the 2 disks cause damae on the other 2? Not likely but in your situation it might damage the controller, in which nothing you do to the drives will help. In the worst case, the controller then might in turn damage the drives. ___ 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: Troubles on SATA drives ZFS
On Tue, Oct 12, 2010 at 5:59 AM, Ivan Voras ivo...@freebsd.org wrote: On 10/11/10 21:22, Alejandro Imass wrote: 1) Would damage to the 2 disks cause damae on the other 2? Not likely but in your situation it might damage the controller, in which nothing you do to the drives will help. In the worst case, the controller then might in turn damage the drives. I was under the impression that SATA was not that sensible to hot unplugging, in fact I thought that SATA supports hot pluging, so by yanking the wires out it should not have damaged the disks or the controller IMO. But you might be correct because I use only cheap HW ;-) ___ 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: Troubles on SATA drives ZFS
On 12 October 2010 15:30, Alejandro Imass a...@p2ee.org wrote: On Tue, Oct 12, 2010 at 5:59 AM, Ivan Voras ivo...@freebsd.org wrote: On 10/11/10 21:22, Alejandro Imass wrote: 1) Would damage to the 2 disks cause damae on the other 2? Not likely but in your situation it might damage the controller, in which nothing you do to the drives will help. In the worst case, the controller then might in turn damage the drives. I was under the impression that SATA was not that sensible to hot unplugging, in fact I thought that SATA supports hot pluging, so by yanking the wires out it should not have damaged the disks or the controller IMO. But you might be correct because I use only cheap HW ;-) The SATA standard does support hot-plugging but it's optional if the hardware (controllers and the drives) support it or not. ___ 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
Troubles on SATA drives ZFS
Hello, I have a 4drive zfs pool with raidz on FBSD 8 and I accidentally tripped and yanked the sata wires off 2 drives while it was running. I immediately shutdown the server, fixed the wiring and re-started the server. Incredibly I ran zpool status and zpool scrub and only 8 files were damaged. I removed them and recovered from backup. I cleared the errors on the pool but I keep getting errors on the 4 drives. I am by no means a ZFS expert so all I have tried is: - zpool status - zpool scrub - dlete and restore files - zpool scrub - zpool clear Everything Ok and then I get ZFS-80008A again :-( My questions: 1) Would damage to the 2 disks cause damae on the other 2? 2) Is there a utility in FBSD to check the physical drive itself and mark any bad sectors as such? 3) Can all this be doen directly from ZFS commands, etc? Fortunatelly my FBSD system lives in a start-up IDE drive so I can un-mount the pool and run any utilities over the drives. Thanks in advance for any help! Alex ___ 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: Troubles on SATA drives ZFS
On Mon, 11 Oct 2010 15:22:41 -0400, Alejandro Imass a...@p2ee.org wrote: 2) Is there a utility in FBSD to check the physical drive itself and mark any bad sectors as such? There is smartctl in port smartmontools, and badsect provided by the system. -- 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: Troubles on SATA drives ZFS
On Mon, Oct 11, 2010 at 4:06 PM, Polytropon free...@edvax.de wrote: On Mon, 11 Oct 2010 15:22:41 -0400, Alejandro Imass a...@p2ee.org wrote: 2) Is there a utility in FBSD to check the physical drive itself and mark any bad sectors as such? There is smartctl in port smartmontools, and badsect provided by the system. Thanks! Let me RTFM and post my results! Alex -- 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: Problem adding 1TB SATA disk to system
On Sun, Sep 19, 2010 at 6:13 PM, freebsd-questions freebsd-questions@freebsd.org wrote: Dear Sir/Madam, Your email was unable reach the intended person that you were sending it to. For more information on our business please click on the following link: Click here for our website http://www.xpbargains.net We look forward to your continued business in the future. Regards, Webmaster ___ 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: Problem adding 1TB SATA disk to system
On Thu, Sep 16, 2010 at 6:17 PM, Michael Powell nightre...@hotmail.comwrote: Andy Wodfer wrote: I'm running FreeBSD 8.0 release (will upgrade to 8.1 STABLE tonight). However, I'm having big problems adding a new harddrive to the system. I want a separate 1TB SATA installed to recover backup files on, but when I add it I only get error messages: dmesg: ad2: 953869MB WDC WD1000FYPS-01ZKB0 02.01B01 at ata1-master SATA300 GEOM: ad2: corrupt or invalid GPT detected. GEOM: ad2: GPT rejected -- may not be recoverable. GEOM: ufsid/4c80e66f50f43e15: corrupt or invalid GPT detected. GEOM: ufsid/4c80e66f50f43e15: GPT rejected -- may not be recoverable. I've tried label and fdisk, but I can't get it to work. [snip] I do not believe you can utilize fdisk and label for this. Since it appears there may be a possibility of a garbage MBR present this will wipe it: 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. You will need to set this up with gpart instead of fdisk. More details in man gpart and possibly glabel. The devil is in the details, but this may be enough to get you pointed down the road. I couldn't get it to work. My solution was to remove the 1TB drive and install 2x500GB drives in a small RAID instead. Made life so much easier. :-) Cheers, Andy ___ 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
Problem adding 1TB SATA disk to system
Hi all, I'm running FreeBSD 8.0 release (will upgrade to 8.1 STABLE tonight). However, I'm having big problems adding a new harddrive to the system. I want a separate 1TB SATA installed to recover backup files on, but when I add it I only get error messages: dmesg: ad2: 953869MB WDC WD1000FYPS-01ZKB0 02.01B01 at ata1-master SATA300 GEOM: ad2: corrupt or invalid GPT detected. GEOM: ad2: GPT rejected -- may not be recoverable. GEOM: ufsid/4c80e66f50f43e15: corrupt or invalid GPT detected. GEOM: ufsid/4c80e66f50f43e15: GPT rejected -- may not be recoverable. I've tried label and fdisk, but I can't get it to work. Fdisk: WARNING: It is safe to use a geometry of 1938021/16/63 for ad2 on │ │ computers with modern BIOS versions. If this disk is to be used │ │ on an old machine it is recommended that it does not have more │ │ than 65535 cylinders, more than 255 heads, or more than│ │ 63 sectors per track. │ ││ │ Would you like to keep using the current geometry? Yes ... but it doesn't work. The computer hardware was bought new about 7 months ago and the mainboard is an intel server board. Can someone help me get this disk up and running (if possible?)? Thanks! Best regards, Andy ___ 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: Problem adding 1TB SATA disk to system
Andy Wodfer wrote: Hi all, I'm running FreeBSD 8.0 release (will upgrade to 8.1 STABLE tonight). However, I'm having big problems adding a new harddrive to the system. I want a separate 1TB SATA installed to recover backup files on, but when I add it I only get error messages: dmesg: ad2: 953869MB WDC WD1000FYPS-01ZKB0 02.01B01 at ata1-master SATA300 GEOM: ad2: corrupt or invalid GPT detected. GEOM: ad2: GPT rejected -- may not be recoverable. GEOM: ufsid/4c80e66f50f43e15: corrupt or invalid GPT detected. GEOM: ufsid/4c80e66f50f43e15: GPT rejected -- may not be recoverable. I've tried label and fdisk, but I can't get it to work. [snip] I do not believe you can utilize fdisk and label for this. Since it appears there may be a possibility of a garbage MBR present this will wipe it: 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. You will need to set this up with gpart instead of fdisk. More details in man gpart and possibly glabel. The devil is in the details, but this may be enough to get you pointed down the road. -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: Sata Tape Drives
Il 07/16/10 00:24, Dan Nelson ha scritto: In the last episode (Jul 15), Michael Anderson said: Or, more clearly: Are SATA tape drives supported? I see they are on some other BSD flavors, but I haven't found any mention in the FreeBSD hardware compatibility documents. I see an atapist device in /sys/conf/NOTES: device atapist # ATAPI tape drives , which might work. The atapicam or ahci device may also make sata tapes show up as if they were scsi devices. Try ahci first. http://www.freebsd.org/cgi/man.cgi?query=ahci http://www.freebsd.org/cgi/man.cgi?query=atapicam And please, in case you try, let us know the results... I know I'm not helping you, but I've tried many times to find out whether SATA *and SAS* tape drives are expected to work. bye Thanks av. ___ 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: Sata Tape Drives
Or, more clearly: Are SATA tape drives supported? I see they are on some other BSD flavors, but I haven't found any mention in the FreeBSD hardware compatibility documents. Will the OS just see a tape drive on a SATA controller as a sequential-access SCSI device the way it sees SATA disks as SCSI block devices? Quoting Michael Anderson michael.ander...@elego.de: Hello, I'm looking to replace a busted tape drive with a Quantum DLT SATA drive. Is this supported? Thanks! -- Michael Anderson IT Services Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Building 12.3 (BIG) room 227 13355 Berlin, Germany phone +49 30 23 45 86 96 michael.anderson at elegosoft.com fax +49 30 23 45 86 95 http://www.elegosoft.com Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 ___ 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 -- Michael Anderson IT Services Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Building 12.3 (BIG) room 227 13355 Berlin, Germany phone +49 30 23 45 86 96 michael.anderson at elegosoft.com fax +49 30 23 45 86 95 http://www.elegosoft.com Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 ___ 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: Sata Tape Drives
In the last episode (Jul 15), Michael Anderson said: Or, more clearly: Are SATA tape drives supported? I see they are on some other BSD flavors, but I haven't found any mention in the FreeBSD hardware compatibility documents. I see an atapist device in /sys/conf/NOTES: device atapist # ATAPI tape drives , which might work. The atapicam or ahci device may also make sata tapes show up as if they were scsi devices. Try ahci first. http://www.freebsd.org/cgi/man.cgi?query=ahci http://www.freebsd.org/cgi/man.cgi?query=atapicam -- Dan Nelson dnel...@allantgroup.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
Quantum DLT SATA tape drive
Hello, I'm looking to replace a busted tape ATA DAT drive with a Quantum DLT SATA drive. Is this supported? Thanks! ___ 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
Sata Tape Drives
Hello, I'm looking to replace a busted tape drive with a Quantum DLT SATA drive. Is this supported? Thanks! -- Michael Anderson IT Services Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Building 12.3 (BIG) room 227 13355 Berlin, Germany phone +49 30 23 45 86 96 michael.anderson at elegosoft.com fax +49 30 23 45 86 95 http://www.elegosoft.com Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 ___ 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: Recommended supported SATA Cards?
On 06/30/2010 04:45 PM, Diego Arias wrote: On Wed, Jun 30, 2010 at 4:33 PM, Robli...@midsummerdream.org wrote: I've seen the SYBA SY-PEX40008, but would prefer to have a PCI-e 4x connector for the bandwidth and avoid a port multiplier if possible. Since this will be in a ZFS pool, I'd prefer not to have 1 bad port take out more than 1 disk. :) I have seen the Sil3124 chipset mentioned before in my searches and wasn't sure of its level of support either so it's nice to know that chipset is well supported. Does the siis driver support offlining and swapping hard disks without rebooting? The Adaptec 1430SA seems to use a Marvell chipset according to some searching of the freebsd archives: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2005-10/0389.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-11/0441.html http://old.nabble.com/Adaptec-1405-on-FreeBSD-td26337538.html But Adaptec's own site/documentation doesn't want to confirm it for me. The best I've come up with is: http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=12177p_created=1098385883p_sid=1tiW_K3kp_accessibility=0p_redirect=p_lva=438p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQ6MSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MjE5LDIxOSZwX3Byb2RzPTQ1JnBfY2F0cz0mcF9wdj0xLjQ1JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTE*p_li=p_topview=1 I've found a commit that mentions support for the 1430SA: http://lists.freebsd.org/pipermail/svn-src-stable-8/2009-November/000565.html But I'm not sure what the state of the support is or how stable it is with that driver (looks to be ata?) If the 1430SA uses the Marvell chipset (as it appears to), then I guess the question comes down to the level of support for the Marvell 88SX6541 and 88SX7042 chipsets. Anyone know the current state of functionality for the above Marvell chipsets? Rob On 06/30/2010 09:07 AM, Steve Polyack wrote: On 06/29/10 16:58, Rob wrote: I've been trying to find a PCI-e SATA II (300MB/s) controller card for a FreeBSD 8.0 system, but am having problems determining if FreeBSD 8.0 will support them. Ideally I'd like to find one that is not a HW Raid controller, as I don't need that functionality since I place to use ZFS and the HW Raid on the card just gets in the way. I know that a HighPoint RocketRAID 23x0 (2310, 2320) will work with the htprr driver, but those are HW RAID cards. I've found 'Adaptec 2241000-R 1430SA' and 'Rosewill RC-218' cards, and those are the ones I'm having a hard time telling if FreeBSD supports. Searching of the e-mail archives has given me mixed results and nothing definitive to say that they work. I'm not sure what chipset the Adaptec 2241000-R 1430SA uses, but the Rosewill uses the Marvell 88SX7042 chipset. I'd prefer to use Adaptec if possible as in the past they produced good SCSI boards and used to be well supported (in Linux anyway), but I'll use the Rosewill if it's well supported in FreeBSD. It's also possible Adaptec has taken a hit in support/quality since I last used one of their boards. :) I think the Marvell SATA chipset work is still a work-in-progress. It may still be supported by the ata(4) driver, but that driver typically does not support any SATA-specific features, such as NCQ. Does anyone know if the above boards are supported in FreeBSD? Anyone have any recommendations for PCI-e 4x SATA controllers with a minimum of 4 internal connectors? We use a handful of the SYBA SY-PEX40008 cards (http://www.newegg.com/Product/Product.aspx?Item=N82E16816124027) to manage a handful of drives with ZFS. The cards have some RAID features, but you can simply plug disks in and use them without involving the RAID layer. If your motherboard supports it, you can even disable the Option ROM from showing up on boot. Overall, the performance has been pretty good. The siis(4) driver has full support for the Sil3124 chipset that these use and supports all of the bells whistles like NCQ and FIS-based switching for port multipliers. They have also been very stable. The only gripe for me is that it's only 1x PCI-E, instead of 4x, so you won't get full performance out of it once you have 4 fast drives attached. Rob ___ 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 ___ 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 Actually 3ware seems to have very good FreeBSD support is that beyond your budget? 3ware
Re: Recommended supported SATA Cards?
On Thu, 01 Jul 2010, Rob wrote: On 06/30/2010 04:45 PM, Diego Arias wrote: On Wed, Jun 30, 2010 at 4:33 PM, Robli...@midsummerdream.org wrote: I've seen the SYBA SY-PEX40008, but would prefer to have a PCI-e 4x connector for the bandwidth and avoid a port multiplier if possible. Since this will be in a ZFS pool, I'd prefer not to have 1 bad port take out more than 1 disk. :) I have seen the Sil3124 chipset mentioned before in my searches and wasn't sure of its level of support either so it's nice to know that chipset is well supported. Does the siis driver support offlining and swapping hard disks without rebooting? The Adaptec 1430SA seems to use a Marvell chipset according to some searching of the freebsd archives: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2005-10/0389.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-11/0441.html http://old.nabble.com/Adaptec-1405-on-FreeBSD-td26337538.html But Adaptec's own site/documentation doesn't want to confirm it for me. The best I've come up with is: http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=12177p_created=1098385883p_sid=1tiW_K3kp_accessibility=0p_redirect=p_lva=438p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQ6MSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MjE5LDIxOSZwX3Byb2RzPTQ1JnBfY2F0cz0mcF9wdj0xLjQ1JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTE*p_li=p_topview=1 I've found a commit that mentions support for the 1430SA: http://lists.freebsd.org/pipermail/svn-src-stable-8/2009-November/000565.html But I'm not sure what the state of the support is or how stable it is with that driver (looks to be ata?) If the 1430SA uses the Marvell chipset (as it appears to), then I guess the question comes down to the level of support for the Marvell 88SX6541 and 88SX7042 chipsets. Anyone know the current state of functionality for the above Marvell chipsets? Rob On 06/30/2010 09:07 AM, Steve Polyack wrote: On 06/29/10 16:58, Rob wrote: I've been trying to find a PCI-e SATA II (300MB/s) controller card for a FreeBSD 8.0 system, but am having problems determining if FreeBSD 8.0 will support them. Ideally I'd like to find one that is not a HW Raid controller, as I don't need that functionality since I place to use ZFS and the HW Raid on the card just gets in the way. I know that a HighPoint RocketRAID 23x0 (2310, 2320) will work with the htprr driver, but those are HW RAID cards. I've found 'Adaptec 2241000-R 1430SA' and 'Rosewill RC-218' cards, and those are the ones I'm having a hard time telling if FreeBSD supports. Searching of the e-mail archives has given me mixed results and nothing definitive to say that they work. I'm not sure what chipset the Adaptec 2241000-R 1430SA uses, but the Rosewill uses the Marvell 88SX7042 chipset. I'd prefer to use Adaptec if possible as in the past they produced good SCSI boards and used to be well supported (in Linux anyway), but I'll use the Rosewill if it's well supported in FreeBSD. It's also possible Adaptec has taken a hit in support/quality since I last used one of their boards. :) I think the Marvell SATA chipset work is still a work-in-progress. It may still be supported by the ata(4) driver, but that driver typically does not support any SATA-specific features, such as NCQ. Does anyone know if the above boards are supported in FreeBSD? Anyone have any recommendations for PCI-e 4x SATA controllers with a minimum of 4 internal connectors? We use a handful of the SYBA SY-PEX40008 cards (http://www.newegg.com/Product/Product.aspx?Item=N82E16816124027) to manage a handful of drives with ZFS. The cards have some RAID features, but you can simply plug disks in and use them without involving the RAID layer. If your motherboard supports it, you can even disable the Option ROM from showing up on boot. Overall, the performance has been pretty good. The siis(4) driver has full support for the Sil3124 chipset that these use and supports all of the bells whistles like NCQ and FIS-based switching for port multipliers. They have also been very stable. The only gripe for me is that it's only 1x PCI-E, instead of 4x, so you won't get full performance out of it once you have 4 fast drives attached. Rob ___ 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org
Re: Recommended supported SATA Cards?
On 06/29/10 16:58, Rob wrote: I've been trying to find a PCI-e SATA II (300MB/s) controller card for a FreeBSD 8.0 system, but am having problems determining if FreeBSD 8.0 will support them. Ideally I'd like to find one that is not a HW Raid controller, as I don't need that functionality since I place to use ZFS and the HW Raid on the card just gets in the way. I know that a HighPoint RocketRAID 23x0 (2310, 2320) will work with the htprr driver, but those are HW RAID cards. I've found 'Adaptec 2241000-R 1430SA' and 'Rosewill RC-218' cards, and those are the ones I'm having a hard time telling if FreeBSD supports. Searching of the e-mail archives has given me mixed results and nothing definitive to say that they work. I'm not sure what chipset the Adaptec 2241000-R 1430SA uses, but the Rosewill uses the Marvell 88SX7042 chipset. I'd prefer to use Adaptec if possible as in the past they produced good SCSI boards and used to be well supported (in Linux anyway), but I'll use the Rosewill if it's well supported in FreeBSD. It's also possible Adaptec has taken a hit in support/quality since I last used one of their boards. :) I think the Marvell SATA chipset work is still a work-in-progress. It may still be supported by the ata(4) driver, but that driver typically does not support any SATA-specific features, such as NCQ. Does anyone know if the above boards are supported in FreeBSD? Anyone have any recommendations for PCI-e 4x SATA controllers with a minimum of 4 internal connectors? We use a handful of the SYBA SY-PEX40008 cards (http://www.newegg.com/Product/Product.aspx?Item=N82E16816124027) to manage a handful of drives with ZFS. The cards have some RAID features, but you can simply plug disks in and use them without involving the RAID layer. If your motherboard supports it, you can even disable the Option ROM from showing up on boot. Overall, the performance has been pretty good. The siis(4) driver has full support for the Sil3124 chipset that these use and supports all of the bells whistles like NCQ and FIS-based switching for port multipliers. They have also been very stable. The only gripe for me is that it's only 1x PCI-E, instead of 4x, so you won't get full performance out of it once you have 4 fast drives attached. Rob ___ 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: Recommended supported SATA Cards?
I've seen the SYBA SY-PEX40008, but would prefer to have a PCI-e 4x connector for the bandwidth and avoid a port multiplier if possible. Since this will be in a ZFS pool, I'd prefer not to have 1 bad port take out more than 1 disk. :) I have seen the Sil3124 chipset mentioned before in my searches and wasn't sure of its level of support either so it's nice to know that chipset is well supported. Does the siis driver support offlining and swapping hard disks without rebooting? The Adaptec 1430SA seems to use a Marvell chipset according to some searching of the freebsd archives: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2005-10/0389.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-11/0441.html http://old.nabble.com/Adaptec-1405-on-FreeBSD-td26337538.html But Adaptec's own site/documentation doesn't want to confirm it for me. The best I've come up with is: http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=12177p_created=1098385883p_sid=1tiW_K3kp_accessibility=0p_redirect=p_lva=438p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQ6MSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MjE5LDIxOSZwX3Byb2RzPTQ1JnBfY2F0cz0mcF9wdj0xLjQ1JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTE*p_li=p_topview=1 I've found a commit that mentions support for the 1430SA: http://lists.freebsd.org/pipermail/svn-src-stable-8/2009-November/000565.html But I'm not sure what the state of the support is or how stable it is with that driver (looks to be ata?) If the 1430SA uses the Marvell chipset (as it appears to), then I guess the question comes down to the level of support for the Marvell 88SX6541 and 88SX7042 chipsets. Anyone know the current state of functionality for the above Marvell chipsets? Rob On 06/30/2010 09:07 AM, Steve Polyack wrote: On 06/29/10 16:58, Rob wrote: I've been trying to find a PCI-e SATA II (300MB/s) controller card for a FreeBSD 8.0 system, but am having problems determining if FreeBSD 8.0 will support them. Ideally I'd like to find one that is not a HW Raid controller, as I don't need that functionality since I place to use ZFS and the HW Raid on the card just gets in the way. I know that a HighPoint RocketRAID 23x0 (2310, 2320) will work with the htprr driver, but those are HW RAID cards. I've found 'Adaptec 2241000-R 1430SA' and 'Rosewill RC-218' cards, and those are the ones I'm having a hard time telling if FreeBSD supports. Searching of the e-mail archives has given me mixed results and nothing definitive to say that they work. I'm not sure what chipset the Adaptec 2241000-R 1430SA uses, but the Rosewill uses the Marvell 88SX7042 chipset. I'd prefer to use Adaptec if possible as in the past they produced good SCSI boards and used to be well supported (in Linux anyway), but I'll use the Rosewill if it's well supported in FreeBSD. It's also possible Adaptec has taken a hit in support/quality since I last used one of their boards. :) I think the Marvell SATA chipset work is still a work-in-progress. It may still be supported by the ata(4) driver, but that driver typically does not support any SATA-specific features, such as NCQ. Does anyone know if the above boards are supported in FreeBSD? Anyone have any recommendations for PCI-e 4x SATA controllers with a minimum of 4 internal connectors? We use a handful of the SYBA SY-PEX40008 cards (http://www.newegg.com/Product/Product.aspx?Item=N82E16816124027) to manage a handful of drives with ZFS. The cards have some RAID features, but you can simply plug disks in and use them without involving the RAID layer. If your motherboard supports it, you can even disable the Option ROM from showing up on boot. Overall, the performance has been pretty good. The siis(4) driver has full support for the Sil3124 chipset that these use and supports all of the bells whistles like NCQ and FIS-based switching for port multipliers. They have also been very stable. The only gripe for me is that it's only 1x PCI-E, instead of 4x, so you won't get full performance out of it once you have 4 fast drives attached. Rob ___ 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 ___ 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: Recommended supported SATA Cards?
On Wed, Jun 30, 2010 at 4:33 PM, Rob li...@midsummerdream.org wrote: I've seen the SYBA SY-PEX40008, but would prefer to have a PCI-e 4x connector for the bandwidth and avoid a port multiplier if possible. Since this will be in a ZFS pool, I'd prefer not to have 1 bad port take out more than 1 disk. :) I have seen the Sil3124 chipset mentioned before in my searches and wasn't sure of its level of support either so it's nice to know that chipset is well supported. Does the siis driver support offlining and swapping hard disks without rebooting? The Adaptec 1430SA seems to use a Marvell chipset according to some searching of the freebsd archives: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2005-10/0389.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-11/0441.html http://old.nabble.com/Adaptec-1405-on-FreeBSD-td26337538.html But Adaptec's own site/documentation doesn't want to confirm it for me. The best I've come up with is: http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=12177p_created=1098385883p_sid=1tiW_K3kp_accessibility=0p_redirect=p_lva=438p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQ6MSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MjE5LDIxOSZwX3Byb2RzPTQ1JnBfY2F0cz0mcF9wdj0xLjQ1JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTE*p_li=p_topview=1 I've found a commit that mentions support for the 1430SA: http://lists.freebsd.org/pipermail/svn-src-stable-8/2009-November/000565.html But I'm not sure what the state of the support is or how stable it is with that driver (looks to be ata?) If the 1430SA uses the Marvell chipset (as it appears to), then I guess the question comes down to the level of support for the Marvell 88SX6541 and 88SX7042 chipsets. Anyone know the current state of functionality for the above Marvell chipsets? Rob On 06/30/2010 09:07 AM, Steve Polyack wrote: On 06/29/10 16:58, Rob wrote: I've been trying to find a PCI-e SATA II (300MB/s) controller card for a FreeBSD 8.0 system, but am having problems determining if FreeBSD 8.0 will support them. Ideally I'd like to find one that is not a HW Raid controller, as I don't need that functionality since I place to use ZFS and the HW Raid on the card just gets in the way. I know that a HighPoint RocketRAID 23x0 (2310, 2320) will work with the htprr driver, but those are HW RAID cards. I've found 'Adaptec 2241000-R 1430SA' and 'Rosewill RC-218' cards, and those are the ones I'm having a hard time telling if FreeBSD supports. Searching of the e-mail archives has given me mixed results and nothing definitive to say that they work. I'm not sure what chipset the Adaptec 2241000-R 1430SA uses, but the Rosewill uses the Marvell 88SX7042 chipset. I'd prefer to use Adaptec if possible as in the past they produced good SCSI boards and used to be well supported (in Linux anyway), but I'll use the Rosewill if it's well supported in FreeBSD. It's also possible Adaptec has taken a hit in support/quality since I last used one of their boards. :) I think the Marvell SATA chipset work is still a work-in-progress. It may still be supported by the ata(4) driver, but that driver typically does not support any SATA-specific features, such as NCQ. Does anyone know if the above boards are supported in FreeBSD? Anyone have any recommendations for PCI-e 4x SATA controllers with a minimum of 4 internal connectors? We use a handful of the SYBA SY-PEX40008 cards (http://www.newegg.com/Product/Product.aspx?Item=N82E16816124027) to manage a handful of drives with ZFS. The cards have some RAID features, but you can simply plug disks in and use them without involving the RAID layer. If your motherboard supports it, you can even disable the Option ROM from showing up on boot. Overall, the performance has been pretty good. The siis(4) driver has full support for the Sil3124 chipset that these use and supports all of the bells whistles like NCQ and FIS-based switching for port multipliers. They have also been very stable. The only gripe for me is that it's only 1x PCI-E, instead of 4x, so you won't get full performance out of it once you have 4 fast drives attached. Rob ___ 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 ___ 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 Actually 3ware seems to have very good FreeBSD support is that beyond your
Recommended supported SATA Cards?
I've been trying to find a PCI-e SATA II (300MB/s) controller card for a FreeBSD 8.0 system, but am having problems determining if FreeBSD 8.0 will support them. Ideally I'd like to find one that is not a HW Raid controller, as I don't need that functionality since I place to use ZFS and the HW Raid on the card just gets in the way. I know that a HighPoint RocketRAID 23x0 (2310, 2320) will work with the htprr driver, but those are HW RAID cards. I've found 'Adaptec 2241000-R 1430SA' and 'Rosewill RC-218' cards, and those are the ones I'm having a hard time telling if FreeBSD supports. Searching of the e-mail archives has given me mixed results and nothing definitive to say that they work. I'm not sure what chipset the Adaptec 2241000-R 1430SA uses, but the Rosewill uses the Marvell 88SX7042 chipset. I'd prefer to use Adaptec if possible as in the past they produced good SCSI boards and used to be well supported (in Linux anyway), but I'll use the Rosewill if it's well supported in FreeBSD. It's also possible Adaptec has taken a hit in support/quality since I last used one of their boards. :) Does anyone know if the above boards are supported in FreeBSD? Anyone have any recommendations for PCI-e 4x SATA controllers with a minimum of 4 internal connectors? Rob ___ 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
Problem with system install with Toshiba MK2565GSX SATA disk
Hello, I am trying to install a toshiba HD on an appliance, the Toshiba is a MK2565GSX of 250GB described here:http://www3.toshiba.co.jp/storage/english/spec/hdd25/65.htm#spec02 The system I am trying to install is pfSense (FBSD 7.2). I am not a 100% sure about the disk geometry… as It is not quite clear. What is sure is that disk has 488 397 168 sectors… Normally It should have 484 521 cylinder 16 heads and 63 sectors, but I am not certain this setting is ok… If I have a look at the BIOS setting after install, It tells me that disk has 65535 cylinder, 16 head, 255 sector which is not quite the same as the above… If I use a simple install I generally end up with an error on my HD after boot, once he tries to mount the disk… Kernel is loaded ok, up until he reaches the disk da0 then there is an error: ad1: FAILURE - READ_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=18446744073709551553 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a […] Then I do not have access to the device using manual system mounting… What would be your advise? Any idea what is precisely going wrong? Thank you very much. G.B. Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz ___ 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: Problem with system install with Toshiba MK2565GSX SATA disk
Looks like the problem was related to BIOS setting. I have changed the setting of disk detection from AUTO to LBA and this has allowed me to boot on the disk. One more question: With the disk I am using FBSD seems to have two possibility for the partition table size (or at least depending on different boot, It is offering me sometimes the 1st option and other time the second one): 1. 30401 cylinders | 255 heads | 63 sectors 2. 484521 cylinders | 16 heads | 63 sectors Global dis size is 250GB (LBA 488397168) Le 24 juin 2010 à 20:37, bsd a écrit : Hello, I am trying to install a toshiba HD on an appliance, the Toshiba is a MK2565GSX of 250GB described here:http://www3.toshiba.co.jp/storage/english/spec/hdd25/65.htm#spec02 The system I am trying to install is pfSense (FBSD 7.2). I am not a 100% sure about the disk geometry… as It is not quite clear. What is sure is that disk has 488 397 168 sectors… Normally It should have 484 521 cylinder 16 heads and 63 sectors, but I am not certain this setting is ok… If I have a look at the BIOS setting after install, It tells me that disk has 65535 cylinder, 16 head, 255 sector which is not quite the same as the above… If I use a simple install I generally end up with an error on my HD after boot, once he tries to mount the disk… Kernel is loaded ok, up until he reaches the disk da0 then there is an error: ad1: FAILURE - READ_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=18446744073709551553 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a […] Then I do not have access to the device using manual system mounting… What would be your advise? Any idea what is precisely going wrong? Thank you very much. G.B. Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz ___ 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 Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz ___ 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: Need help with SATA disk timing out in 8.1 Beta
-Original Message- From: Jerry Bell [mailto:je...@nrdx.com] Sent: 18 June 2010 06:11 To: freebsd-questions@freebsd.org Subject: Need help with SATA disk timing out in 8.1 Beta I am having all sorts of problems with drives in a new server. I have a 450G sata drive that hold my root partition, works great, no issues. I have a second, 1TB drive that has been all sorts of trouble. When writing to this disk, I occasionally see errors like this: Jun 17 07:40:36 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1564898207 Jun 17 07:40:36 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1564898207 Jun 17 07:57:12 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1565052351 Jun 17 07:57:12 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1565052351 Jun 17 09:45:12 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1565983775 Jun 17 09:45:12 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1565983775 Jun 17 09:50:24 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1566082719 Jun 17 09:50:24 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1566082719 Jun 17 10:01:25 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1566358623 Jun 17 10:01:25 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1566358623 Jun 17 10:02:59 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1566387807 Jun 17 10:02:59 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1566387807 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=43231 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=57567 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=773471 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=786271 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=810079 Jun 17 10:19:00 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=76767 Jun 17 10:19:00 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=784479 Last week, I asked the datacenter to provide me with a new 1TB drive, and they did. It formatted fine, no errors. I copied files to it, ran bonnie, etc, and no signs of any DMA issues. Until this morning when I started having the errors again. If I run a tool like bonnie, I am very easily reproduce the errors. After some research, I find that these errors are often indicative of SATA cable problems. The datacenter replaced the cable, and the problem continues. The datacenter moved the sata cable to a new SATA port, and the problem continues The datacenter adds a BRAND NEW 1TB drive (now the system has 3 drive), and I am unable to format the drive because of these errors: ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=168172351 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=602334847 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=602334847 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=427014463 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=427014463 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=15425407 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=471408895 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=471408895 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=91422655 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=203161183 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1211817727 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1211817727 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=37998847 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=309632575 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=309632575 ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=24831007 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=59067391 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=497744575 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=497744575 ad10: FAILURE - WRITE_MUL status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=1128895 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=13920511 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=547029919 ad10: FAILURE - WRITE_DMA48 status
Re: Need help with SATA disk timing out in 8.1 Beta
On Fri, Jun 18, 2010 at 12:11 AM, Jerry Bell je...@nrdx.com wrote: I am having all sorts of problems with drives in a new server. I have a 450G sata drive that hold my root partition, works great, no issues. I have a second, 1TB drive that has been all sorts of trouble. When writing to this disk, I occasionally see errors like this: Jun 17 07:40:36 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1564898207 snip I am at the end of my ability to troubleshoot this. Could this be a problem with FreeBSD 8.1 beta and not the drives after all? I have seen a reference to a patch for previous versions that increase the DMA timeout time to 10 or 15 seconds, which fixes problems, but I am not certain that would fix my particular issue. You could use ahci which might workaround the issue and give you better performance. load it from /boot/loader.conf beware it will change names of detected devices, you may want to consider using glabel. -- 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: Need help with SATA disk timing out in 8.1 Beta
Have you changed the cable? ___ 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: Need help with SATA disk timing out in 8.1 Beta
Yes, twice. On 6/18/2010 4:52 AM, Matthias Gamsjager wrote: Have you changed the cable? ___ 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
Need help with SATA disk timing out in 8.1 Beta
I am having all sorts of problems with drives in a new server. I have a 450G sata drive that hold my root partition, works great, no issues. I have a second, 1TB drive that has been all sorts of trouble. When writing to this disk, I occasionally see errors like this: Jun 17 07:40:36 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1564898207 Jun 17 07:40:36 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1564898207 Jun 17 07:57:12 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1565052351 Jun 17 07:57:12 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1565052351 Jun 17 09:45:12 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1565983775 Jun 17 09:45:12 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1565983775 Jun 17 09:50:24 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1566082719 Jun 17 09:50:24 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1566082719 Jun 17 10:01:25 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1566358623 Jun 17 10:01:25 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1566358623 Jun 17 10:02:59 www3 kernel: ad8: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1566387807 Jun 17 10:02:59 www3 kernel: ad8: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1566387807 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=43231 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=57567 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=773471 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=786271 Jun 17 10:18:59 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=810079 Jun 17 10:19:00 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=76767 Jun 17 10:19:00 www3 kernel: ad8: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=784479 Last week, I asked the datacenter to provide me with a new 1TB drive, and they did. It formatted fine, no errors. I copied files to it, ran bonnie, etc, and no signs of any DMA issues. Until this morning when I started having the errors again. If I run a tool like bonnie, I am very easily reproduce the errors. After some research, I find that these errors are often indicative of SATA cable problems. The datacenter replaced the cable, and the problem continues. The datacenter moved the sata cable to a new SATA port, and the problem continues The datacenter adds a BRAND NEW 1TB drive (now the system has 3 drive), and I am unable to format the drive because of these errors: ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=168172351 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=602334847 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=602334847 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=427014463 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=427014463 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=15425407 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=471408895 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=471408895 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=91422655 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=203161183 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=1211817727 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=1211817727 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=37998847 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=309632575 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=309632575 ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=24831007 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=59067391 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=497744575 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=497744575 ad10: FAILURE - WRITE_MUL status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=1128895 ad10: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=13920511 ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=547029919 ad10: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=547029919 So, the problem has occurred on 3 different drives. SATA ports and cables do not appear to impact the problem
Re: SATA time outs
I'd appreciate it if someone could lend some assistance with this issue. The machine in question is pretty much unusable atm! Regards, Casey - Casey Scott ca...@phantombsd.org wrote: Since upgrading to 8.0 RELEASE, I continually get these errors: ... Jun 11 15:24:08 kernel: ad6: 953869MB Seagate ST31000340AS SD1A at ata3-master SATA150 Jun 11 15:24:08 kernel: (probe6:ahc0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jun 11 15:24:08 kernel: (probe6:ahc0:0:6:0): CAM Status: SCSI Status Error Jun 11 15:24:08 kernel: (probe6:ahc0:0:6:0): SCSI Status: Check Condition Jun 11 15:24:08 kernel: (probe6:ahc0:0:6:0): UNIT ATTENTION asc:29,2 Jun 11 15:24:08 kernel: (probe6:ahc0:0:6:0): SCSI bus reset occurred Jun 11 15:24:08 kernel: (probe6:ahc0:0:6:0): Retrying Command (per Sense Data) ... I've tried 3 different drives w/ 2 different disk controllers. Anything I use as the second drive generates this message on boot, and will eventually fail with timeout errors after a couple hours. The other drive on the system, ad4, never displays these symptoms. This isn't new hardware, and worked flawlessly until now. Any suggestions? Has a bug been introduced into the ata driver? Regards, Casey ___ 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
