atacontrol reinit
Hi, How do I accomplish atacontrol reinit in 9.0 with ATA_CAM enabled? Plugged drives don't show up without a reboot and camcontrol reset or rescan does not help. Pete ___ 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
atacontrol spindown 0 does not work
Hello, I don't like to hear the spin down from my hard drive, it does it every 10 seconds approximately. I used ataidle -P 0 /dev/ad0 to disable it and it works. When I saw there was a atacontrol command for this, I tried it, so I removed ataidle and I tried : markand@Melon ~ $ sudo atacontrol spindown ad0 0 markand@Melon ~ $ sudo atacontrol spindown ad0 ad0: idle spin down disabled But I can still hear the noise every 10 seconds, I think atacontrol does not totally close the APM feature of the device. Do you have any clue? Cheers, -- David Demelier ___ 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: atacontrol spindown 0 does not work
On Tue, 2011-03-01 at 09:21 +0100, David Demelier wrote: But I can still hear the noise every 10 seconds, I think atacontrol does not totally close the APM feature of the device. atacontrol's spindown setting doesn't change anything in the disk itself: it just controls a timer in the ad(4) driver which sends a spindown command when it expires. You'll need to keep using ataidle to fix the APM value. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atacontrol spindown 0 does not work
El día Tuesday, March 01, 2011 a las 09:15:01AM +, Bruce Cran escribió: On Tue, 2011-03-01 at 09:21 +0100, David Demelier wrote: But I can still hear the noise every 10 seconds, I think atacontrol does not totally close the APM feature of the device. atacontrol's spindown setting doesn't change anything in the disk itself: it just controls a timer in the ad(4) driver which sends a spindown command when it expires. You'll need to keep using ataidle to fix the APM value. To the OP: I have to use ataidle as well on an Acer Aspire D250 laptop to switch-off the spindown of the disk... I'm wondering why you would prefere atacontrol? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ 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: atacontrol spindown 0 does not work
On Tue, 2011-03-01 at 11:47 +0100, Matthias Apitz wrote: I'm wondering why you would prefere atacontrol? I think everyone's been looking for an official solution. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
atacontrol spindown
Hi, With FreeBSD 7.1 I've started using atacontrol spindown for my secondary disks (i.e. disks that are accessed very infrequently). Everything seemed to work nice until I noticed in my daily security run output list of kernel messages that suggests that disks get awaken every night at 3 am. Could someone suggest what could trigger my disks to wake up? BTW, I am not running smartd daemon, so that cannot be an issue. Thanks in advance, Alexander. ___ 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: atacontrol spindown
On Wed, 29 Apr 2009 04:10:04 -0700 (PDT) Alexander Popov aopo...@yahoo.com wrote: Hi, With FreeBSD 7.1 I've started using atacontrol spindown for my secondary disks (i.e. disks that are accessed very infrequently). Everything seemed to work nice until I noticed in my daily security run output list of kernel messages that suggests that disks get awaken every night at 3 am. Could someone suggest what could trigger my disks to wake up? Hi Alexander, maybe it is cron when it runs the daily security checks so it checks for the disk? Or have a look at your cronjobs with best regards D. Dowse -- The only reality is virtual! ___ 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: atacontrol spindown
Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable=NO. With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? Thanks, Alexander. --- On Wed, 4/29/09, Daniel C. Dowse dcdo...@gmx.net wrote: From: Daniel C. Dowse dcdo...@gmx.net Subject: Re: atacontrol spindown To: freebsd-questions@freebsd.org Date: Wednesday, April 29, 2009, 1:50 PM On Wed, 29 Apr 2009 04:10:04 -0700 (PDT) Alexander Popov aopo...@yahoo.com wrote: Hi, With FreeBSD 7.1 I've started using atacontrol spindown for my secondary disks (i.e. disks that are accessed very infrequently). Everything seemed to work nice until I noticed in my daily security run output list of kernel messages that suggests that disks get awaken every night at 3 am. Could someone suggest what could trigger my disks to wake up? Hi Alexander, maybe it is cron when it runs the daily security checks so it checks for the disk? Or have a look at your cronjobs with best regards D. Dowse -- The only reality is virtual! ___ 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: atacontrol spindown
On 4/29/09, Alexander Popov aopo...@yahoo.com wrote: Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable=NO. With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? /etc/crontab -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atacontrol spindown
On Wed, 29 Apr 2009 05:44:51 -0700 (PDT) Alexander Popov aopo...@yahoo.com wrote: Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable=NO. With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? Thanks, Hi, Alexander, maybe post the part for the disk in your output of your daily security checks here, would be much easier to find out what the trigger may be. What file/directories are accessed, when it comes to that point? IMHO: i believe it is just because the hdd is there, so i think when the cron runs it just checks that the disk is still there. thx D.Dowse -- The only reality is virtual! ___ 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: atacontrol spindown
Hi, Paul, Below is my /etc/crontab. The only thing that is run at 3 am is periodic daily. # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: src/etc/crontab,v 1.32.32.1 2008/11/25 02:59:29 kensmith Exp $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a --- On Wed, 4/29/09, Paul B. Mahol one...@gmail.com wrote: From: Paul B. Mahol one...@gmail.com Subject: Re: atacontrol spindown To: aopo...@yahoo.com Cc: freebsd-questions@freebsd.org, Daniel C. Dowse dcdo...@gmx.net Date: Wednesday, April 29, 2009, 2:58 PM On 4/29/09, Alexander Popov aopo...@yahoo.com wrote: Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable=NO. With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? /etc/crontab -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atacontrol spindown
On 4/29/09, Alexander Popov aopo...@yahoo.com wrote: Hi, Paul, Below is my /etc/crontab. The only thing that is run at 3 am is periodic daily. If any of scripts from /etc/crontab needs access(just reading, not counting writing, considering it is not already cached) on spindowned hard disk your mission will fail. If you want to keep logging and logs (via another ways) you could make memory disk for root and var slice ... and transfer logs to another media ... or use another hard disk for that # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: src/etc/crontab,v 1.32.32.1 2008/11/25 02:59:29 kensmith Exp $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a --- On Wed, 4/29/09, Paul B. Mahol one...@gmail.com wrote: From: Paul B. Mahol one...@gmail.com Subject: Re: atacontrol spindown To: aopo...@yahoo.com Cc: freebsd-questions@freebsd.org, Daniel C. Dowse dcdo...@gmx.net Date: Wednesday, April 29, 2009, 2:58 PM On 4/29/09, Alexander Popov aopo...@yahoo.com wrote: Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable=NO. With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? /etc/crontab -- Paul -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atacontrol spindown
Hi, Daniel, This is the output: Checking setuid files and devices: Checking for uids of 0: root 0 toor 0 Checking for passwordless accounts: Checking login.conf permissions: ***.home kernel log messages: +++ /tmp/security.G4QuXmuU 2009-04-29 03:01:08.0 +0200 +ad4: Idle, spin down +ad4: drive spun down. +ad8: Idle, spin down +ad8: drive spun down. +ad4: request while spun down, starting. +ad8: request while spun down, starting. +ad8: Idle, spin down +ad8: drive spun down. +ad4: Idle, spin down +ad4: drive spun down. +ad4: request while spun down, starting. The timestamps in /var/log/messages suggested that +ad4: request while spun down, starting. happened at 3:01 am. It would not be very nice if it was due to cron start up; I don't have any system partitions on those drives, it shouldn't touch them... Regards, Alexander. --- On Wed, 4/29/09, Daniel C. Dowse dcdo...@gmx.net wrote: From: Daniel C. Dowse dcdo...@gmx.net Subject: Re: atacontrol spindown To: freebsd-questions@freebsd.org Date: Wednesday, April 29, 2009, 3:07 PM On Wed, 29 Apr 2009 05:44:51 -0700 (PDT) Alexander Popov aopo...@yahoo.com wrote: Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable=NO. With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? Thanks, Hi, Alexander, maybe post the part for the disk in your output of your daily security checks here, would be much easier to find out what the trigger may be. What file/directories are accessed, when it comes to that point? IMHO: i believe it is just because the hdd is there, so i think when the cron runs it just checks that the disk is still there. thx D.Dowse -- The only reality is virtual! ___ 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: atacontrol spindown
All FreeBSD system partitions are on a disk that I never try to spin down. It is weird that something in periodic daily tries to read from my data disks... Alexander. --- On Wed, 4/29/09, Paul B. Mahol one...@gmail.com wrote: From: Paul B. Mahol one...@gmail.com Subject: Re: atacontrol spindown To: aopo...@yahoo.com Cc: freebsd-questions@freebsd.org, Daniel C. Dowse dcdo...@gmx.net Date: Wednesday, April 29, 2009, 3:17 PM On 4/29/09, Alexander Popov aopo...@yahoo.com wrote: Hi, Paul, Below is my /etc/crontab. The only thing that is run at 3 am is periodic daily. If any of scripts from /etc/crontab needs access(just reading, not counting writing, considering it is not already cached) on spindowned hard disk your mission will fail. If you want to keep logging and logs (via another ways) you could make memory disk for root and var slice ... and transfer logs to another media ... or use another hard disk for that ___ 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: atacontrol spindown
On 4/29/09, Alexander Popov aopo...@yahoo.com wrote: All FreeBSD system partitions are on a disk that I never try to spin down. It is weird that something in periodic daily tries to read from my data disks... Than disable one by one until problem got fixed(easy to say than done), if not than it is ata bug. -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atacontrol spindown
On 29/4/09 14:18, Alexander Popov wrote: Hi, Daniel, This is the output: Checking setuid files and devices: Checking for uids of 0: root 0 toor 0 Checking for passwordless accounts: Checking login.conf permissions: ***.home kernel log messages: +++ /tmp/security.G4QuXmuU2009-04-29 03:01:08.0 +0200 +ad4: Idle, spin down +ad4: drive spun down. +ad8: Idle, spin down +ad8: drive spun down. +ad4: request while spun down, starting. +ad8: request while spun down, starting. +ad8: Idle, spin down +ad8: drive spun down. +ad4: Idle, spin down +ad4: drive spun down. +ad4: request while spun down, starting. The timestamps in /var/log/messages suggested that +ad4: request while spun down, starting. happened at 3:01 am. It would not be very nice if it was due to cron start up; I don't have any system partitions on those drives, it shouldn't touch them... Have a look through /etc/defaults/periodic.conf you will see things like daily_status_disks_enable=YES in there (does a df -l -h on all disks) and I think some of the security ones do checks for new setuid root files, these are all likely to spin up your disks. Vince Regards, Alexander. ___ 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: atacontrol + highpoint raid hot-swappable bays = reboot?
--- On Fri, 1/30/09, Gabe n...@att.net wrote: From: Gabe n...@att.net Subject: atacontrol + highpoint raid hot-swappable bays = reboot? To: freebsd-questions@freebsd.org Date: Friday, January 30, 2009, 2:40 AM Hello list, I've come upon a problem I've googled the daylights out of, further I've read atacontrol(8) up and down without success. My goal is simple, I have a supermicro 1U with hot-swappable drive bays which hold 2 SATA drives that are connected to a PCI highpoint rocket raid card. I need to be able to simulate a failure on HDD1 (drive bay 2) and I've been trying to do it by following the handbook here: [18.4.3] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/raid.html to no avail. atacontrol detach ata3 pull drive out wait some time put drive in atacontrol attach ata3 HDD is recognized and listed in 'list' command atacontrol addspare ar0 ata3 Now this is when I encounter a Device Busy error. In order to recover from this I've tried detaching and attaching to no avail, rebooting just makes atacontrol status ar0 only show disk 1 even though disk 2 (ata3) is listed in atacontrol list. See below for a transcript from the shell, hopefully someone can provide some insight before I flip out. :) Thanks, /gabe atap...@pci0:1:3:0: class=0x010400 card=0x00011103 chip=0x00051103 rev=0x02 hdr=0x00 vendor = 'Triones Technologies Inc. (HighPoint)' device = 'HPT372x UDMA/ATA133 RAID Controller' class = mass storage subclass = RAID Jan 30 02:19:00 amnesiac kernel: hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) Jan 30 02:19:00 amnesiac kernel: ar0: 76319MB HighPoint v2 RocketRAID RAID1 status: READY Script started on Fri Jan 30 02:21:01 2009 amnesiac# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: acd0 CD-224E/1.9A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol status ar0 ar0: ATA RAID1 status: READY subdisks: 0 ad6 ONLINE 1 ad4 ONLINE amnesiac# atacontrol detach ata2 amnesiac# tail -n5 /var/log/messages Jan 30 02:19:00 amnesiac savecore: no dumps found Jan 30 02:19:39 amnesiac login: ROOT LOGIN (root) ON ttyv0 Jan 30 02:21:38 amnesiac kernel: ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode Jan 30 02:21:38 amnesiac kernel: subdisk4: detached Jan 30 02:21:38 amnesiac kernel: ad4: detached amnesiac# atacontrol attach ata2 Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol status ar0 ar0: ATA RAID1 status: DEGRADED subdisks: 0 ad6 ONLINE 1 MISSING amnesiac# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: acd0 CD-224E/1.9A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol addspare ar0 ad4 atacontrol: ioctl(IOCATARAIDADDSPARE): Device busy amnesiac# ^Dexit Script done on Fri Jan 30 02:22:47 2009 ___ 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 Oh man, so we're all stumped? Any suggestions would be greatly appreciated. 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
atacontrol + highpoint raid hot-swappable bays = reboot?
Hello list, I've come upon a problem I've googled the daylights out of, further I've read atacontrol(8) up and down without success. My goal is simple, I have a supermicro 1U with hot-swappable drive bays which hold 2 SATA drives that are connected to a PCI highpoint rocket raid card. I need to be able to simulate a failure on HDD1 (drive bay 2) and I've been trying to do it by following the handbook here: [18.4.3] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/raid.html to no avail. atacontrol detach ata3 pull drive out wait some time put drive in atacontrol attach ata3 HDD is recognized and listed in 'list' command atacontrol addspare ar0 ata3 Now this is when I encounter a Device Busy error. In order to recover from this I've tried detaching and attaching to no avail, rebooting just makes atacontrol status ar0 only show disk 1 even though disk 2 (ata3) is listed in atacontrol list. See below for a transcript from the shell, hopefully someone can provide some insight before I flip out. :) Thanks, /gabe atap...@pci0:1:3:0: class=0x010400 card=0x00011103 chip=0x00051103 rev=0x02 hdr=0x00 vendor = 'Triones Technologies Inc. (HighPoint)' device = 'HPT372x UDMA/ATA133 RAID Controller' class = mass storage subclass = RAID Jan 30 02:19:00 amnesiac kernel: hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) Jan 30 02:19:00 amnesiac kernel: ar0: 76319MB HighPoint v2 RocketRAID RAID1 status: READY Script started on Fri Jan 30 02:21:01 2009 amnesiac# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: acd0 CD-224E/1.9A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol status ar0 ar0: ATA RAID1 status: READY subdisks: 0 ad6 ONLINE 1 ad4 ONLINE amnesiac# atacontrol detach ata2 amnesiac# tail -n5 /var/log/messages Jan 30 02:19:00 amnesiac savecore: no dumps found Jan 30 02:19:39 amnesiac login: ROOT LOGIN (root) ON ttyv0 Jan 30 02:21:38 amnesiac kernel: ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode Jan 30 02:21:38 amnesiac kernel: subdisk4: detached Jan 30 02:21:38 amnesiac kernel: ad4: detached amnesiac# atacontrol attach ata2 Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol status ar0 ar0: ATA RAID1 status: DEGRADED subdisks: 0 ad6 ONLINE 1 MISSING amnesiac# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: acd0 CD-224E/1.9A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol addspare ar0 ad4 atacontrol: ioctl(IOCATARAIDADDSPARE): Device busy amnesiac# ^Dexit Script done on Fri Jan 30 02:22:47 2009 ___ 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
atacontrol + highpoint raid hot-swappable bays = reboot?
Hello list, I've come upon a problem I've googled the daylights out of, further I've read atacontrol(8) up and down without success. My goal is simple, I have a supermicro 1U with hot-swappable drive bays which hold 2 SATA drives that are connected to a PCI highpoint rocket raid card. I need to be able to simulate a failure on HDD1 (drive bay 2) and I've been trying to do it by following the handbook here: [18.4.3] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/raid.html to no avail. atacontrol detach ata3 pull drive out wait some time put drive in atacontrol attach ata3 HDD is recognized and listed in 'list' command atacontrol addspare ar0 ata3 Now this is when I encounter a Device Busy error. In order to recover from this I've tried detaching and attaching to no avail, rebooting just makes atacontrol status ar0 only show disk 1 even though disk 2 (ata3) is listed in atacontrol list. See below for a transcript from the shell, hopefully someone can provide some insight before I flip out. :) Thanks, /gabe atap...@pci0:1:3:0: class=0x010400 card=0x00011103 chip=0x00051103 rev=0x02 hdr=0x00 vendor = 'Triones Technologies Inc. (HighPoint)' device = 'HPT372x UDMA/ATA133 RAID Controller' class = mass storage subclass = RAID Jan 30 02:19:00 amnesiac kernel: hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) Jan 30 02:19:00 amnesiac kernel: ar0: 76319MB HighPoint v2 RocketRAID RAID1 status: READY Script started on Fri Jan 30 02:21:01 2009 amnesiac# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: acd0 CD-224E/1.9A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol status ar0 ar0: ATA RAID1 status: READY subdisks: 0 ad6 ONLINE 1 ad4 ONLINE amnesiac# atacontrol detach ata2 amnesiac# tail -n5 /var/log/messages Jan 30 02:19:00 amnesiac savecore: no dumps found Jan 30 02:19:39 amnesiac login: ROOT LOGIN (root) ON ttyv0 Jan 30 02:21:38 amnesiac kernel: ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode Jan 30 02:21:38 amnesiac kernel: subdisk4: detached Jan 30 02:21:38 amnesiac kernel: ad4: detached amnesiac# atacontrol attach ata2 Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol status ar0 ar0: ATA RAID1 status: DEGRADED subdisks: 0 ad6 ONLINE 1 MISSING amnesiac# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: acd0 CD-224E/1.9A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 ST380817AS/3.42 Serial ATA v1.0 Slave: no device present amnesiac# atacontrol addspare ar0 ad4 atacontrol: ioctl(IOCATARAIDADDSPARE): Device busy amnesiac# ^Dexit Script done on Fri Jan 30 02:22:47 2009 ___ 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
atacontrol software or hardware raid
How can I detect if system has Software or hardware raid? Since in manual page: The atacontrol command can also be used to create purely software RAID arrays in systems that do NOT have a real hardware RAID card such as a Highpoint or Promise card. A common scenario is a 1U server such as the HP DL320 G4 or G5. These servers contain a SATA controller that has 2 channels that can contain 2 disks per channel, but the servers are wired to only place a single SATA drive on each channel. Or how can I find out if the hardware is real hardware RAID card? For example my system has following dmesg output: ad4: 152627MB Seagate ST3160815AS 4.AAB at ata2-master SATA300 ad6: 152627MB Seagate ST3160815AS 4.AAB at ata3-master SATA300 ar0: 152625MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad6 at ata3-master ar0: disk1 READY (mirror) using ad4 at ata2-master This system is an intel server with S3210SH server board in it. While installing system I see ad4,ad6 and ar0 as harddrives in sysinstall. I choose to install ar0. Additionally as far as I see ar0 is very susceptible to errors since a single CRC error can break the RAID consistency is that normal? I really appreciate those who uses such a kind of RAID1 Regards. ___ 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: atacontrol software or hardware raid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Omer Faruk Sen wrote: How can I detect if system has Software or hardware raid? Since in manual page: The atacontrol command can also be used to create purely software RAID arrays in systems that do NOT have a real hardware RAID card such as a Highpoint or Promise card. A common scenario is a 1U server such as the HP DL320 G4 or G5. These servers contain a SATA controller that has 2 channels that can contain 2 disks per channel, but the servers are wired to only place a single SATA drive on each channel. Or how can I find out if the hardware is real hardware RAID card? For example my system has following dmesg output: ad4: 152627MB Seagate ST3160815AS 4.AAB at ata2-master SATA300 ad6: 152627MB Seagate ST3160815AS 4.AAB at ata3-master SATA300 ar0: 152625MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad6 at ata3-master ar0: disk1 READY (mirror) using ad4 at ata2-master This system is an intel server with S3210SH server board in it. While installing system I see ad4,ad6 and ar0 as harddrives in sysinstall. I choose to install ar0. Additionally as far as I see ar0 is very susceptible to errors since a single CRC error can break the RAID consistency is that normal? I really appreciate those who uses such a kind of RAID1 Regards. ___ 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 ar RAID devices are almost always software/BIOS RAID. In this case intel matrix raid is software RAID provided by the system BIOS. The disadvantages of using it is your RAID array isn't portable to machines that don't have the same BIOS raid implimentation. One of the advantages of BIOS RAID is that you can boot from stripes, which you aren't doing anyways. You'll probably find that disabling the motherboard RAID and creating a gmirror device is a better option for software RAID 1. - -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5ABC 11B4 26F9 01F1 27AF AECB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkl81jYACgkQJvkB8Sevrsu1swCcCCq6/cG0WYajBvutibgvhIaA kn8An27y/SPbEKzRyaWntfZV95z/UJia =k2Gx -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
Re: atacontrol software or hardware raid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Omer Faruk Sen wrote: How can I detect if system has Software or hardware raid? Since in manual page: The atacontrol command can also be used to create purely software RAID arrays in systems that do NOT have a real hardware RAID card such as a Highpoint or Promise card. A common scenario is a 1U server such as the HP DL320 G4 or G5. These servers contain a SATA controller that has 2 channels that can contain 2 disks per channel, but the servers are wired to only place a single SATA drive on each channel. Or how can I find out if the hardware is real hardware RAID card? For example my system has following dmesg output: ad4: 152627MB Seagate ST3160815AS 4.AAB at ata2-master SATA300 ad6: 152627MB Seagate ST3160815AS 4.AAB at ata3-master SATA300 ar0: 152625MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad6 at ata3-master ar0: disk1 READY (mirror) using ad4 at ata2-master This system is an intel server with S3210SH server board in it. While installing system I see ad4,ad6 and ar0 as harddrives in sysinstall. I choose to install ar0. Additionally as far as I see ar0 is very susceptible to errors since a single CRC error can break the RAID consistency is that normal? I really appreciate those who uses such a kind of RAID1 Regards. ___ 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 ar RAID devices are almost always software/BIOS RAID. In this case intel matrix raid is software RAID provided by the system BIOS. The disadvantages of using it is your RAID array isn't portable to machines that don't have the same BIOS raid implimentation. One of the advantages of BIOS RAID is that you can boot from stripes, which you aren't doing anyways. You'll probably find that disabling the motherboard RAID and creating a gmirror device is a better option for software RAID 1. - -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5ABC 11B4 26F9 01F1 27AF AECB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkl81jYACgkQJvkB8Sevrsu1swCcCCq6/cG0WYajBvutibgvhIaA kn8An27y/SPbEKzRyaWntfZV95z/UJia =k2Gx -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
Re: atacontrol software or hardware raid
ar RAID devices are almost always software/BIOS RAID. In this case intel matrix raid is software RAID provided by the system BIOS. The it's always better to use gmirror. not mentioning more flexibility (you do not have to mirror whole 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
Help with: atacontrol create RAID1 ad4 ad6
I need help with this. I'm trying to create a software RAID1. I followed the instructions in man page http://www.freebsd.org/cgi/man.cgi?query=atacontrolsektion=8apropos=0manpath=FreeBSD+7.1-RELEASE atacontrol(8) atacontrol(8) wrote: [snip] A quick and dirty way to create such a mirrored array on a new system is to boot off the FreeBSD install CD, do a minimal scratch install, abort out of the post install questions, and at the command line issue the com- mand: atacontrol create RAID1 ad4 ad6 then immediately issue a reboot and boot from the installation CD again, and during the installation, you will now see ar0 listed as a disk to install on, and install on that instead of ad4, ad6, etc. [snip] I did the above exactly as stated, except when I reboot ar0 just disappears. What went wrong? Or, please point out what I missed. :confused: I've tried setting the SATA type in BIOS to either Native IDE or AHCI modes. If I set it to RAID mode, the installation says no disks found. When I boot up, either from the CD or from ad4, I see both disks, ad4 ad6. When I do the atacontrol create RAID1 ad4 ad6 command and then atacontrol status ar0, it reports that ar0 is READY, but when I reboot, it's gone. -- View this message in context: http://www.nabble.com/Help-with%3A--atacontrol-create-RAID1-ad4-ad6-tp21511186p21511186.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: atacontrol mode D PIO4 persist across reboots
On Monday 10 March 2008, Philip M. Gollucci wrote: This sets it for all controllers I only want to set it for ata1 which contains ad2. Thanks for the tip though. Globally disable it on boot, then write a script named /etc/rc.local that selectively re-enables it for certain drives. Here's mine: -- #!/bin/sh echo echo 'Setting controllers to DMA mode' atacontrol mode acd1 udma33 -- I had to do that because my DVD-ROM would autodetect UDMA66 or higher and hang. -- Kirk Strauser signature.asc Description: This is a digitally signed message part.
atacontrol mode D PIO4 persist across reboots
/var/run/dmesg.boot ad2: 28667MB SAMSUNG SV3002H PV100-11 at ata1-master UDMA33 ad2: FAILURE - READ_DMA timed out LBA=58711965 ad2: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad2: FAILURE - READ_DMA timed out LBA=58711951 ad2: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad2: FAILURE - READ_DMA timed out LBA=58711964 ad2: FAILURE - READ_DMA timed out LBA=0 10-30 minutes later, it finally gets through the boot. /etc/fstab: /dev/ad2s1 /X ufs rw 2 2 the problem here is the device needs to be PIO4 $ atacontrol mode ad2 PIO4 current mode = PIO4 My problem is how do I get this to persist across reboot ? -- Philip M. Gollucci ([EMAIL PROTECTED]) c:703.336.9354 Consultant / http://p6m7g8.net/Resume/resume.txt http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol mode D PIO4 persist across reboots
Philip M. Gollucci wrote: /var/run/dmesg.boot ad2: 28667MB SAMSUNG SV3002H PV100-11 at ata1-master UDMA33 ad2: FAILURE - READ_DMA timed out LBA=58711965 ad2: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad2: FAILURE - READ_DMA timed out LBA=58711951 ad2: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad2: FAILURE - READ_DMA timed out LBA=58711964 ad2: FAILURE - READ_DMA timed out LBA=0 10-30 minutes later, it finally gets through the boot. /etc/fstab: /dev/ad2s1 /X ufs rw 2 2 the problem here is the device needs to be PIO4 $ atacontrol mode ad2 PIO4 current mode = PIO4 My problem is how do I get this to persist across reboot ? Have a look at man 4 ata Your answer is probably: hw.ata.ata_dma=0 in /boot/loader.conf Are you sure it is not a faulty (or failing) disk though? This size / age drive should have no problem running in DMA mode. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol mode D PIO4 persist across reboots
Manolis Kiagias wrote: Have a look at man 4 ata Your answer is probably: hw.ata.ata_dma=0 This sets it for all controllers I only want to set it for ata1 which contains ad2. Thanks for the tip though. ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] ad0: 19092MB WDC WD200BB-60CJA0 16.06V16 at ata0-master UDMA33 ad1: 38166MB WDC WD400BB-53CLB0 95.04E95 at ata0-slave UDMA33 ad2: 28667MB SAMSUNG SV3002H PV100-11 at ata1-master UDMA33 -- Philip M. Gollucci ([EMAIL PROTECTED]) c:703.336.9354 Consultant / http://p6m7g8.net/Resume/resume.txt http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol mode D PIO4 persist across reboots
Hello Philip, Monday, March 10, 2008, 8:46:46 AM, you wrote: $ atacontrol mode ad2 PIO4 current mode = PIO4 My problem is how do I get this to persist across reboot ? putting it into /etc/rc.conf.local should work... -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: atacontrol rebuild on non-identical disks
I didn't see a response and this is an old one, you probably fixed it by now. You will need to dd the old disk to a new one then get an identical to the new one and raid them. Of course if the new one is larger you will still have the existing smaller partition table. If it was me I would build a new server and ship it UPS ground out there. Your existing disk is probably about ready to fail too, and both disks probably died due to overheating caused by one or more fan failures, and if your power supply fan gets choked with dust, it's a goner then the supply will burn up. I would guess the inside of that server is pretty filthy about now. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Justin Sullivan Sent: Friday, April 06, 2007 6:16 PM To: freebsd-questions@freebsd.org Subject: atacontrol rebuild on non-identical disks We have a (very) remote FreeBSD 5.5-RELEASE system running on Asus RS120 hardware and historically configured with 2 identical SATA drives using atacontrol RAID1 and the system installed on ar0. One of the drives has died, however no identical replacement drive could be easily sourced at the remote location. So, attempting to get things back to normal RAID1 operation as quickly as possible we have tried a same size but non-identical drive and attempted an atacontrol rebuild. However, this is stuck indefinitely at 0% rebuild progess. While I'm aware that some RAID1 mechanisms e.g. CCD seem to insist on identical disks, the documentation isn't so clear on ATA and I figured it was worth a try. Does anyone know if it is possible to overcome the non-identical disk issue and allow ata RAID1 to work again? I've also considered keeping the current ar0 setup on the single working disk and setting up a gmirror RAID1 copy on the second disk would work. Current config info is as follows: From atacontrol list: ATA channel 2: Master: ad4 WDC WD2000JD-00HBB0/08.02D08 Serial ATA v1.0 ATA channel 3: Master: ad6 HDT722525DLA380/V44OA9BA Serial ATA v1.0 From the permanently going nowhere rebuild output of atacontrol status: ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed The WDC WD2000JD on ad4 is the functional system drive and orignial member of the RAID1 array. ad6 is the new spare and presumably is completely blank still at this stage. I realise that sourcing an identical drive is probably the right (or at least easy) answer. The original drives (WDC WD2000JD on ad4) are still available for purchase, just not anywhere near where the machine lives - so getting a replacement drive would be a logistically difficult and time-consuming exercise. Thanks, JS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol rebuild on non-identical disks
We have a (very) remote FreeBSD 5.5-RELEASE system running on Asus RS120 hardware and historically configured with 2 identical SATA drives using atacontrol RAID1 and the system installed on ar0. One of the drives has died, however no identical replacement drive could be easily sourced at the remote location. So, attempting to get things back to normal RAID1 operation as quickly as possible we have tried a same size but non-identical drive and attempted an atacontrol rebuild. However, this is stuck indefinitely at 0% rebuild progess. While I'm aware that some RAID1 mechanisms e.g. CCD seem to insist on identical disks, the documentation isn't so clear on ATA and I figured it was worth a try. Does anyone know if it is possible to overcome the non-identical disk issue and allow ata RAID1 to work again? I've also considered keeping the current ar0 setup on the single working disk and setting up a gmirror RAID1 copy on the second disk would work. Current config info is as follows: From atacontrol list: ATA channel 2: Master: ad4 WDC WD2000JD-00HBB0/08.02D08 Serial ATA v1.0 ATA channel 3: Master: ad6 HDT722525DLA380/V44OA9BA Serial ATA v1.0 From the permanently going nowhere rebuild output of atacontrol status: ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed The WDC WD2000JD on ad4 is the functional system drive and orignial member of the RAID1 array. ad6 is the new spare and presumably is completely blank still at this stage. I realise that sourcing an identical drive is probably the right (or at least easy) answer. The original drives (WDC WD2000JD on ad4) are still available for purchase, just not anywhere near where the machine lives - so getting a replacement drive would be a logistically difficult and time-consuming exercise. Thanks, JS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
High disk load +mount/atacontrol/NFS/SMBFS crashes the system
Hello. I have experienced the following problem a couple of times in 2 different machines and FreeBSD versions (see below): when the disk is continuously reading/writing my system becomes unstable (it's not an everyday thing, but quite frustrating when it happens) and sometimes crashes. When copying from another machine by NFS/SMBFS more than one file at the same time (or when using the disk, like during a filesystem check in the background) often crashes (and the disk light indicator turns off). Running atacontrol ad0 mode UDMA100 when it was UDMA133 crashed the system (the disk activity indicator was always on) when I tried to solve the problem that way. Also when I was installing a port which installs many files on the second machine without using NFS/SMBFS, trying to mount a local NTFS filesystem (with kernel driver) crashed. The first machine is an Athlon XP 2400+ with FreeBSD 6.1-RELEASE and custom kernel (see below) and the second one a new Athlon64 X2 3500 with FreeBSD 6.2-RELEASE running in i386 mode, with generic SMP kernel. See the boot messages and kernel config here: http://people.freebsd.org/~alepulver/disk-crash.tar.bz2 Also I got (only twice, when checking the filesystem after one of these crashes) the following error on the first machine, that I don't know if it's related or not to the previous problems: fsync: giving up on dirty 0xc51d6990: tag devfs, type VCHR usecount 1, writecount 0, refcount 806 mountedhere 0xc51a4000 flags () v_object 0xc144cb58 ref 0 pages 3232 lock type devfs: EXCL (count 1) by thread 0xc54e2c00 (pid 837) dev ad2s1f I would appreciate any help. Thanks and Best Regards, Ale P.S.: does this problem belong to a more specific list like [EMAIL PROTECTED] signature.asc Description: PGP signature
Adaptec 1200A atacontrol
Hello, recently i have had a problem with one of the disks attached to an Adaptec 1200A RAID controller doing a 0+1 RAID. After replacing the disk and rebuilding the array FreeBSD says the array is degraded, marking the new disk and the other in the same channel as FREE. Is there anything needed to do with atacontrol to make FreeBSD recognize the array? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol status for 3ware?
Mike Tancsa writes: Sorry for the delay.. ever since my HD crashed last weekend.. have been having problems with my home courier-imap setup. :-( On Wed, 01 Mar 2006 22:40:32 -0500, in sentex.lists.freebsd.questions you wrote: How does one do atacontrol status for a 3ware card in FreeBSD 6? Why not use the cli tool that you can download from the 3ware website? That is the next step, but I was wondering if it was possible to get basic status info from atacontrol. I didnt think atacontrol ever worked with 3ware cards ? I guess I will have to ask on the 3ware support system what they meant when they once wrote to me saying that 3ware cards were fully intregrated into FreeBSD 6 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol status for 3ware?
At 05:57 PM 05/03/2006, Francisco Reyes wrote: How does one do atacontrol status for a 3ware card in FreeBSD 6? Why not use the cli tool that you can download from the 3ware website? That is the next step, but I was wondering if it was possible to get basic status info from atacontrol. Nope, the underlying twe and twa drivers are not part of the ata subsystem I didnt think atacontrol ever worked with 3ware cards ? I guess I will have to ask on the 3ware support system what they meant when they once wrote to me saying that 3ware cards were fully intregrated into FreeBSD 6 The drivers are certainly part of the base OS. Pop in the CD and you can install directly onto the 3ware array. The management tools to then manipulate the array can be either downloaded from 3ware or built from the ports. cd /usr/ports/sysutils/3dm/ make install or just download the cli. Also supported, are the smartmontools which are quite handy. ---Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: atacontrol status for 3ware?
what does 3ware tech support say? Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Francisco Reyes Sent: Wednesday, March 01, 2006 7:41 PM To: Free BSD Questions list Subject: atacontrol status for 3ware? How does one do atacontrol status for a 3ware card in FreeBSD 6? Tried atacontrol status 0 (like in previous versions) atacontrol status twe0 atacontrol status twed0 I rebuild an array and saw the controller display messages at the start of the rebuild and it showed twe0 as the name of the array. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 268.1.1/273 - Release Date: 3/2/2006 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol status for 3ware?
On Wed, 01 Mar 2006 22:40:32 -0500, in sentex.lists.freebsd.questions you wrote: How does one do atacontrol status for a 3ware card in FreeBSD 6? Tried atacontrol status 0 (like in previous versions) atacontrol status twe0 atacontrol status twed0 Hi, Why not use the cli tool that you can download from the 3ware website ? I didnt think atacontrol ever worked with 3ware cards ? ---Mike Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 [EMAIL PROTECTED], (http://www.tancsa.com) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol status for 3ware?
How does one do atacontrol status for a 3ware card in FreeBSD 6? Tried atacontrol status 0 (like in previous versions) atacontrol status twe0 atacontrol status twed0 I rebuild an array and saw the controller display messages at the start of the rebuild and it showed twe0 as the name of the array. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NCQ Re: Disk write caching, hw.ata.wc and atacontrol disagree)
So hw.ata.wc thinks that the disk write cache is off, but atacontrol cap thinks the disk write cache is on? I remember this is working but there was a reporting problem in atacontrol. Looks like atacontrol cap reports the state of the disk *before* hw.ata.wc took effect. It would be less confusing if atacontrol cap reported the state of the disk at the time atacontrol is run. You should easily be able to tell whether it is on or off by the write performance. It should plummet by a factor of 4 or so. I'm seeing only ~10% of the performance I get with the write cache on. Which leads to: Feature Support EnableValue Vendor Native Command Queuing (NCQ) yes - 31/0x1F Where is the knob to turn on NCQ? My controller and disks claim to support it, but grepping the 6.0 man pages finds nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk write caching, hw.ata.wc and atacontrol disagree
I'm trying to turn off the evil data corrupting on-disk write cache. I added hw.ata.wc=0 to /boot/loader.conf and rebooted. # sysctl hw.ata.wc hw.ata.wc: 0 So far so good. But! atacontrol cap ad4 says: Feature Support EnableValue Vendor write cacheyes yes So hw.ata.wc thinks that the disk write cache is off, but atacontrol cap thinks the disk write cache is on? If it matters: AMD64, nforce4, Seagate SATA 7200.8, FreeBSD 6.0 Beta3 So then I boot NetBSD and turn the write caches off with dkctl $disk setcache r and reboot FreeBSD and now I get Feature Support EnableValue Vendor write cacheyes no It appears that if hw.ata.wc = 1 then FreeBSD turns the write cache on, and if hw.ata.wc = 0 then FreeBSD leaves the write cache alone? Is there a way to have FreeBSD turn the write cache OFF? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk write caching, hw.ata.wc and atacontrol disagree
Dieter wrote on Wed, Dec 07, 2005 at 02:05:40PM +: I'm trying to turn off the evil data corrupting on-disk write cache. I added hw.ata.wc=0 to /boot/loader.conf and rebooted. # sysctl hw.ata.wc hw.ata.wc: 0 So far so good. But! atacontrol cap ad4 says: Feature Support EnableValue Vendor write cacheyes yes So hw.ata.wc thinks that the disk write cache is off, but atacontrol cap thinks the disk write cache is on? I remember this is working but there was a reporting problem in atacontrol. You should easily be able to tell whether it is on or off by the write performance. It should plummet by a factor of 4 or so. cstream -i- -o/mnt/wherever/tmpfile -v1 Martin -- %%% Martin Cracauer cracauer@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Atacontrol software RAID
Hi all, I've been trying to build a 2 disk mirror with atacontrol on a standard IDE controller (testing in vmware), from an already running 4.11 system. ad0 has the system, ad3 is the new drive. I thought I should be able to mimic the gmirror trick of making a 1 disk degraded mirror on ad3, move everything over to the raid, wipe ad0 and add it to the mirror. # atacontrol create RAID1 ad3 fails. needs @ least 2 disksso #atacontrol created RAID1 ad3 ad3 did the trick ;) - after a reboot it became : ar0: WARNING - mirror lost ar0: 6143MB ATA RAID1 array [783/255/63] status: DEGRADED subdisks: 0 DOWN 1 READY ad3: 6143MB VMware Virtual IDE Hard Drive [12483/16/63] at ata1-slave UDMA33 and I could use ar0 as i'd expect it to (could boot off it, moved all the data from ad0 to ar0, mounted all partitions from it,etc). The problem happened when I tried to add ad0 to the mirror...i couldn't find a way to do it. atacontrol addspare is not available in 4.x systems... Any suggestions on how to get ad0 to be part of ar0? Upgrading to 5.x may be an option, but then i'd be using gmirror anyway :-) thanks in advance, Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
On Thu, Sep 08, 2005 at 08:54:10PM +0200, G?ran Nilsson wrote: Hi. I have recently installed Freebsd 5.4 . I have also installed a cheap raidcontroller . On the controller i put on a 200+120gb disk. In the raidcontroller i create a JBOD raid, showing me that i now have 301gb of disk. That's a loss of 19gb, i can live with that. After login I do a atacontrol create JBOD ad5 ad6. It now creates ar0 device with 223gb of space. That's nearly a 100gb of disk loss! If and how can i prevent the huge 100gb of storage loss? I'd look at geom_ccd over atacontrol for this. man ccd /Regards dukka ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 pgpGmJmOGA5ii.pgp Description: PGP signature
atacontrol
Hi. I have recently installed Freebsd 5.4 . I have also installed a cheap raidcontroller . On the controller i put on a 200+120gb disk. In the raidcontroller i create a JBOD raid, showing me that i now have 301gb of disk. That's a loss of 19gb, i can live with that. After login I do a atacontrol create JBOD ad5 ad6. It now creates ar0 device with 223gb of space. That's nearly a 100gb of disk loss! If and how can i prevent the huge 100gb of storage loss? /Regards dukka ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
At 11:54 AM 9/8/2005, Göran Nilsson wrote: Hi. I have recently installed Freebsd 5.4 . I have also installed a cheap raidcontroller . On the controller i put on a 200+120gb disk. In the raidcontroller i create a JBOD raid, showing me that i now have 301gb of disk. That's a loss of 19gb, i can live with that. After login I do a atacontrol create JBOD ad5 ad6. It now creates ar0 device with 223gb of space. That's nearly a 100gb of disk loss! If and how can i prevent the huge 100gb of storage loss? If all you're going to do is use JBOD, why even have the raid controller in the first place? -Glenn /Regards dukka ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sv: Re: atacontrol
All other ide channels are taken, and it comes for a cheap amount of money. And i thought this would be the best way to combine different size of disk into just one large disk. I can add some extra info -- ad5: 194481MB Maxtor 6Y200P0/YAR41BW0 [395136/16/63] at ata2-slave UDMA133 ad6: 114440MB IC35L120AVVA07-0/VA6OA51A [232514/16/63] at ata3-master UDMA100 ar0: 228880MB ATA SPAN array [29178/255/63] status: READY subdisks: ---Originalmeddelande--- Från: Glenn Dawson Datum: 09/08/05 20:57:45 Till: Göran Nilsson ; freebsd-questions@freebsd.org Ämne: Re: atacontrol At 11:54 AM 9/8/2005, Göran Nilsson wrote: Hi. I have recently installed Freebsd 5.4 . I have also installed a cheap raidcontroller . On the controller i put on a 200+120gb disk. In the raidcontroller i create a JBOD raid, showing me that i now have 301gb of disk. That's a loss of 19gb, i can live with that. After login I do a atacontrol create JBOD ad5 ad6. It now creates ar0 device with 223gb of space. That's nearly a 100gb of disk loss! If and how can i prevent the huge 100gb of storage loss? If all you're going to do is use JBOD, why even have the raid controller in the first place? -Glenn /Regards dukka ___ gt;freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ NOD32 1.1212 (20050908) Information __ This message was checked by NOD32 antivirus system. http://www.nod32.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol
I have a simple question. Some time ago I was told always to use the same type of harddisk transfers. Now I have i.e.: Master = UDMA100 Slave = UDMA66 Does this mean the first disk really works on UDMA100 or is is delayed by the second one (as I was told some time ago). Or is the fbsd ata controller capable of setting each drive to its right speed? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
On 8/16/05, Dick Hoogendijk [EMAIL PROTECTED] wrote: I have a simple question. Some time ago I was told always to use the same type of harddisk transfers. Now I have i.e.: Master = UDMA100 Slave = UDMA66 Does this mean the first disk really works on UDMA100 or is is delayed by the second one (as I was told some time ago). Or is the fbsd ata controller capable of setting each drive to its right speed? AFAIK everything slows down. This is a hardware problem and FreeBSD can do nothing about it. This is why I only put one device on a controller/channel, I also do it because the controller can only talk to one device at a time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise TX2 Rebuild via atacontrol??
Am Montag, 4. April 2005 23:29 schrieb Edgar Martinez: All, I have a failed member in a RAID1 array and using atacontrol can see that the status is degraded. I am curious if I can use atacontrol to rebuild the array if the original array was built using the Promise BIOS utility. If I tell atacontrol to rebuild.will it corrupt my data or catch fire and explode?? You don't tell us what version you use, but promise is supported very well, even in atamkII in 6-current. If you replace the failed drive it sould be automatically rebuilt, the `atacontrol rebuild ar0` doesn't work as long as you (in 5.x) used addspare or the controller found a good spare drive. In 4.x you don't have the addspare option, you have to `atacontrol detach 3` and reattach it the same way to get recognized and inserted as spare in an existing array. -Harry Cheers! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgptKroYBBcXN.pgp Description: PGP signature
RE: Promise TX2 Rebuild via atacontrol??
I apologize...I usually am the one complaining to others about versioning...my bad... I do not think that the drive is at fault as much as the controller. I have had to deploy well over one hundred of the exact same configuration, and historically, it's always been the controller that just drops the drive for some reason. I usually end up re-mirroring the array on the old dead drive and the system will continue on its merry way (last one is over 1 year old since last resync)...hence you see why I am curious if I could just use atacontrol instead of taking the unit offline and spending 45min waiting for the resync TECHNOJARGON BELOW FBSD 5.3 STABLE Promise TX2 Orig BIOS ad4: 114473MB WDC WD1200JB-00DUA3/75.13B75 [232581/16/63] at ata2-master UDMA100 ad6: 114473MB WDC WD1200JB-00DUA3/75.13B75 [232581/16/63] at ata3-master UDMA100 ar0: 114440MB ATA RAID1 array [14589/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master Mounting root from ufs:/dev/ar0s1a ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=5861119 ad4: FAILURE - WRITE_DMA timed out ar0: WARNING - mirror lost -Original Message- From: Emanuel Strobl [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 05, 2005 4:15 AM To: freebsd-questions@freebsd.org; [EMAIL PROTECTED] Subject: Re: Promise TX2 Rebuild via atacontrol?? Am Montag, 4. April 2005 23:29 schrieb Edgar Martinez: All, I have a failed member in a RAID1 array and using atacontrol can see that the status is degraded. I am curious if I can use atacontrol to rebuild the array if the original array was built using the Promise BIOS utility. If I tell atacontrol to rebuild.will it corrupt my data or catch fire and explode?? You don't tell us what version you use, but promise is supported very well, even in atamkII in 6-current. If you replace the failed drive it sould be automatically rebuilt, the `atacontrol rebuild ar0` doesn't work as long as you (in 5.x) used addspare or the controller found a good spare drive. In 4.x you don't have the addspare option, you have to `atacontrol detach 3` and reattach it the same way to get recognized and inserted as spare in an existing array. -Harry Cheers! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Promise TX2 Rebuild via atacontrol??
All, I have a failed member in a RAID1 array and using atacontrol can see that the status is degraded. I am curious if I can use atacontrol to rebuild the array if the original array was built using the Promise BIOS utility. If I tell atacontrol to rebuild.will it corrupt my data or catch fire and explode?? Cheers! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with dump of an atacontrol-ed RAID1 array
I have an ICH6 SATA RAID controller that I have set up with atacontrol to behave as a RAID1 array. The array (ar0) consists of ad4 and ad6. Last night I started a dump like so: # dump -0Luaf /dev/da0s1 / to *hopefully* dump my root filesystem (ar0s1a) to a usb storage device. Now here is where things get a little fuzzy... The dump started just fine, and I was able to stick around until dump reported that it was about 10% done. At that point, I left for the night and then woke up to calls from users saying that they couldn't access services on that box. When I got to the terminal, I noticed that the last couple of dump's output messages on screen had to do with being unable to read from ar0s1a. I hit ^C to kill the dump and was asked if I wanted to abort. I said yes and that was the end of that terminal. I couldn't Alt+Fx or ssh in, so I had to power down the machine and bring it back up. When I did, ar0 was gone! So obviously the boot process told me it couldn't find its root filesystem and asked me for another one. I gave it ad4s1a and the machine came up just fine, albeit without RAID. So... has anyone had any experience with this? Does a rigged atacontrol software RAID not play well with a dump? I'm trying to figure out: a) why my dump failed b) why my ar0 RAID array was destroyed in the process I described above Lastly, if anyone with experience with atacontrol can tell me the best way to rebuild my array without losing any data. I *think* that I need to just create an array that only consists of one of my two drives (probably ad4 since its the one that's live right now), then add a hotspare (ad6), and rebuild. Is that right? The only real step I'm worried about is the atacontrol create statement, because I'm afraid it will wipe the drive right off the bat. Thanks a bunch, Jonathan Reeder ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol during boot ?
I need to change the mode of ata channel 1 to UDMA33. When the system is up I use atacontrol mode 1 UDMA33 UDMA33 for that. How can I do this during boot, before mounting HDDs (The reason for all this is, that one of my HDDs only likes UDMA33)? Thanks Hexren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol during boot ?
On 01/03/05 14:28:02, Hexren wrote: I need to change the mode of ata channel 1 to UDMA33. When the system is up I use atacontrol mode 1 UDMA33 UDMA33 for that. How can I do this during boot, before mounting HDDs (The reason for all this is, that one of my HDDs only likes UDMA33)? Thanks Hexren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] hw.ata.atapi_dma=1 in /boot/loader.conf activates udma, but I don't know about setting a certain speed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol and SATA RAID
Giovanni P. Tirloni wrote: Hi, I've a Intel SE7210TP1 motherboard with Adaptec HostRAID and I've created a RAID1 array with 2 SATA disks using the following command: atacontrol create RAID1 ad4 ad6 The system installed on /dev/ar0 just fine and I played a bit with atacontrol detaching and attaching the disks. Detaching ad6 worked without problems with the following commands: atacontrol detach 3 atacontrol attach 3 atacontrol rebuild 0 But when I tried to detach ad4 (after rebuilding array from previous detachment) I got an error saying the array was broken. Now when booting it shows this: ar0: 152627MB ATA RAID1 array [19457/255/63] status: DEGRADED subdisks: disk0 READY on ad4 at ata2-master disk1 DOWN no device found for this disk but atacontrol list shows ad6 there. So my question is: what's the proper way of doing de attach/detach operation ? I did a fresh install then turned the machine off and removed on disk. It booted again just fine. Then I turned it off again and inserted the disk I had removed. Now it will panic: panic: softdep_setup_inomapdep: found inode cpuid = 0 boot() called on cpu#0 Uptime: 2s If I removed the disk and boot again it will work and show the following message: ar0: 152627MB ATA RAID1 array [19457/255/63] status: DEGRADED subdisks: disk0 READY on ad4 at ata2-master disk1 DOWN no device found for this disk How can I replace a failed disk with this setup ? Given what I've read I'm not really using the controller's RAID support but only the RAID support present in the ata subsystem. Is that true ? In the BIOS I don't have any arrays. Thank you, -- Giovanni P. Tirloni ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: atacontrol and SATA RAID
atacontrol addspare ar0 ad6 should do the trick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Giovanni P. Tirloni Sent: Friday, October 29, 2004 3:24 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: atacontrol and SATA RAID Giovanni P. Tirloni wrote: Hi, I've a Intel SE7210TP1 motherboard with Adaptec HostRAID and I've created a RAID1 array with 2 SATA disks using the following command: atacontrol create RAID1 ad4 ad6 The system installed on /dev/ar0 just fine and I played a bit with atacontrol detaching and attaching the disks. Detaching ad6 worked without problems with the following commands: atacontrol detach 3 atacontrol attach 3 atacontrol rebuild 0 But when I tried to detach ad4 (after rebuilding array from previous detachment) I got an error saying the array was broken. Now when booting it shows this: ar0: 152627MB ATA RAID1 array [19457/255/63] status: DEGRADED subdisks: disk0 READY on ad4 at ata2-master disk1 DOWN no device found for this disk but atacontrol list shows ad6 there. So my question is: what's the proper way of doing de attach/detach operation ? I did a fresh install then turned the machine off and removed on disk. It booted again just fine. Then I turned it off again and inserted the disk I had removed. Now it will panic: panic: softdep_setup_inomapdep: found inode cpuid = 0 boot() called on cpu#0 Uptime: 2s If I removed the disk and boot again it will work and show the following message: ar0: 152627MB ATA RAID1 array [19457/255/63] status: DEGRADED subdisks: disk0 READY on ad4 at ata2-master disk1 DOWN no device found for this disk How can I replace a failed disk with this setup ? Given what I've read I'm not really using the controller's RAID support but only the RAID support present in the ata subsystem. Is that true ? In the BIOS I don't have any arrays. Thank you, -- Giovanni P. Tirloni ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol and SATA RAID
Hi, I've a Intel SE7210TP1 motherboard with Adaptec HostRAID and I've created a RAID1 array with 2 SATA disks using the following command: atacontrol create RAID1 ad4 ad6 The system installed on /dev/ar0 just fine and I played a bit with atacontrol detaching and attaching the disks. Detaching ad6 worked without problems with the following commands: atacontrol detach 3 atacontrol attach 3 atacontrol rebuild 0 But when I tried to detach ad4 (after rebuilding array from previous detachment) I got an error saying the array was broken. Now when booting it shows this: ar0: 152627MB ATA RAID1 array [19457/255/63] status: DEGRADED subdisks: disk0 READY on ad4 at ata2-master disk1 DOWN no device found for this disk but atacontrol list shows ad6 there. So my question is: what's the proper way of doing de attach/detach operation ? -- Giovanni P. Tirloni PS.: Please CC me any reply because I'm not subscribed to questions@ Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol addspare missing in -stable
Hi all, how do I rebuild a degraded RADI1 in -stable? I have a HighPoint 372 Controller and yesterday had one drive failed (wich it does regularly and comes back fine after reboot). atacontrol status ar0 reported only one disk (ad4) and degraded (of course). In -current with a SIL0680 I usually issue atacontrol detach $failedchannel atacontrol attach $failedchannel atacontrol addspare $faileddrive ar0 atacontrol rebuild ar0 Please give me an idea how things should work under -stable (from ~3 weeks ago). Thanks, -Harry pgp0.pgp Description: signature
Problems with atacontrol and Hightpoint 730 raid Hardware. 5.2 release.
Hi all, i'm experiencing some problems with FreeBsd 5.2 and an Highpoint raid controller (but it happens also with a promise Fasttrack TX2). I'm pretty sure it's my failure, but i can't understand what i miss. I'm doing this test on 5.x because i plan to migrate from 4.x to new release as soon as it'll released as a production platform, so i need as much informations as i can. I've done a lot of test: 1- the first test was done creating a RAID 1 array directly from HPT Bios. I've two devices ad4 and ad6 and a raid one ar0 as i expect. ATA channel 2: Master: ad4 Maxtor 6Y080L0/YAR41BW0 ATA/ATAPI rev 7 Slave: no device present ATA channel 3: Master: ad6 Maxtor 6Y080L0/YAR41BW0 ATA/ATAPI rev 7 Slave: no device present arc# atacontrol status ar0 ar0: ATA RAID1 subdisks: ad4 ad6 status: READY I've installed *BSD successfully without any flaws, rebooted, and all was working fine. Then i tried a failure problem on ad4, i've simulated it detaching the ata channel: atacontrol detach 2. And i've got a degraded array (that's fine). arc# atacontrol status ar0 ar0: ATA RAID1 subdisks: DOWN ad6 status: DEGRADED Then i detach physically the drive replacing it with a new one (supposed the procedure to substitute a failure HDD).Attached it to channel 2. arc# atacontrol attach 2 Master: ad4 Maxtor 6Y080L0/YAR41BW0 ATA/ATAPI rev 7 Slave: no device present and then looking at the raid status: arc# atacontrol status ar0 ar0: ATA RAID1 subdisks: DOWN ad6 status: DEGRADED All as it was planned. Now i've tried to rebuild the raid, and here we are with problems: arc# atacontrol rebuild ar0 arc# arc# arc# atacontrol status ar0 ar0: ATA RAID1 subdisks: DOWN ad6 status: DEGRADED The rebuild command quits immediatly rebuilding almost nothing. And the raid was still in degraded mode. Ok. Pherhaps i made a mistake attaching the drive and not attaching a spare drive. To avoid any problem i've reinstalled all from scrath and execute all the operations except the atacontrol attach. Then.. manpages for atacontrol reports: atacontrol addspare raid disk So, it was supposed to add the channel and then add disk to raid: new disk as master arc# atacontrol attach 2 Master: ad4 Maxtor 6Y080L0/YAR41BW0 ATA/ATAPI rev 7present Slave: no device arc# atacontrol addspare ar0 ad4 atacontrol: ioctl(ATARAIDADDSPARE): Device busy and as slave. arc# atacontrol attach 2 Master: no device present Slave: ad5 Maxtor 6Y080L0/YAR41BW0 ATA/ATAPI rev 7 arc# atacontrol addspare ar0 ad5 atacontrol: ioctl(ATARAIDADDSPARE): Device busy So... what the hell i've got to do to rebuild the array??? Obviously when i reboot, HPT Bios ask for replacing failure drive, and ask for rebuild... blocking the machine for more than 40 minutes... and this is not acceptable for me. The hardware is a KD7 RAID with Highpoint 730 controller, Duron 1600. Two 80 Gb Maxtor 7200 Rpm 8 Mb. Any Idea? Thanks in advance. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol weirdness: RAID 1 array is shown to be degraded but both disks are up
The 4.9 box has got onboard Promise RAID which so far has worked just fine. However, today I got a report about a degraded disk array so I went to check and found something rather odd: $ atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: ad6 WDC WD800BB-00CAA1/17.07W17 ATA/ATAPI rev 5 Slave: ad7 WDC WD800BB-00CAA1/17.07W17 ATA/ATAPI rev 5 $ atacontrol status 0 ar0: ATA RAID1 subdisks: ad6 ad7 status: DEGRADED How can a RAID array be degraded when both disks are still there? How do I figure out what disk holds the current set of data? And what do I need to do, anyway? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: atacontrol weirdness: RAID 1 array is shown to be degraded but bothdisks are
From: Gabriel Ambuehl [EMAIL PROTECTED] Reply-To: Gabriel Ambuehl [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: atacontrol weirdness: RAID 1 array is shown to be degraded but bothdisks are up Date: Fri, 6 Feb 2004 19:30:29 +0100 The 4.9 box has got onboard Promise RAID which so far has worked just fine. However, today I got a report about a degraded disk array so I went to check and found something rather odd: $ atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: ad6 WDC WD800BB-00CAA1/17.07W17 ATA/ATAPI rev 5 Slave: ad7 WDC WD800BB-00CAA1/17.07W17 ATA/ATAPI rev 5 $ atacontrol status 0 ar0: ATA RAID1 subdisks: ad6 ad7 status: DEGRADED How can a RAID array be degraded when both disks are still there? How do I figure out what disk holds the current set of data? And what do I need to do, anyway? The disk won't disappear from FreeBSD's device list unless it is removed intentionall. For Promise IDE based RAID systems, the best way to find out which one has failed is to boot into the RAID BIOS and look. It will tell you which one has failed. You can then replace that drive and rebuild the array. _ Let the advanced features services of MSN Internet Software maximize your online time. http://click.atdmt.com/AVE/go/onm00200363ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol software raid
Hello, Trying to help a friend set up a system for raid. He's got two 4 gb drives he'd like to mirror. And we were thinking atacontrol, googled for a site on this, and didn't find anything. Any help appreciated. Thanks. Dave. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
`atacontrol enclosure` does not work (ioctl(ATAENCSTAT): Device not configured)
Hello. It just does not seem to work. How do I fix that? cnst# whoami root cnst# atacontrol enclosure 0 0 atacontrol: ioctl(ATAENCSTAT): Device not configured cnst# uname -r 4.8-RELEASE Cheers, Constantine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol(8)
On Tuesday 14 October 2003 10:04 pm, Mike Maltese wrote: Why to this file and not to /etc/sysctl.conf? I have no monitor on that box, so I want to make sure it is more likely to work after the reboot. :-) I can't remember exactly why, but trust me, it will work. But why does it sets it to UDMA33, but not to UDMA66? Have you actually tried it yet? It should automatically set it to the drive's highest capability (controller allowing). Frankly, I've never seen a DVD drive, or any other optical drive for that matter, capable of DMA66, nor would it even need to be (33 is the highest I've seen). In any event, give it a try, I'm sure it will work. acd0: DVDROM ATAPI DVD-ROM 16X Maximum at ata1-master UDMA66 The controller is capable of ata-100. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol(8)
acd0: DVDROM ATAPI DVD-ROM 16X Maximum at ata1-master UDMA66 I stand corrected, although I maintain that no optical drive is capable of that kind of throughput. =) I was kinda wondering if he'd been duped on the specs of the drive. Thanks, Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol(8)
Hello, I have a few questions about atacontrol. First, why the option 'enclosure' does not seem to work? cnst# atacontrol enclosure 0 0 atacontrol: ioctl(ATAENCSTAT): Device not configured Second, where do I have to indicate that my DVD-ROM supports UDMA66? I assume that after saying atacontrol mode 1 udma66 udma66, the settings are going to be vanished the next reboot. Third, why it does not want to set the DVD-ROM to UDMA66 (the device supports it, as well as my 80-pin cable, and motherboard): cnst# atacontrol mode 1 udma66 udma66 Master = UDMA33 Slave = ??? cnst# atacontrol info 1 Master: acd0 AOPEN 16XDVD-ROM/AMH 20020328/R14 ATA/ATAPI rev 4 Slave: no device present The other question I have, is on how can I turn on the automatic acoustic management? cnst# atacontrol cap 0 0 ATA channel 0, Master, device ad0: ATA/ATAPI revision5 device model IC35L040AVER07-0 serial number censored firmware revision ER4OA44A cylinders 16383 heads 16 sectors/track 63 lba supported 80418240 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued yes yes 31/1F SMART yes yes microcode download no no security yes yes power management yes yes advanced power management yes no 0/00 automatic acoustic management yes no 254/FE 128/80 Cheers, Constantine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol(8)
Second, where do I have to indicate that my DVD-ROM supports UDMA66? I assume that after saying atacontrol mode 1 udma66 udma66, the settings are going to be vanished the next reboot. Add the following to /boot/loader.conf: hw.ata.atapi_dma=1 Reboot. Check dmesg. Third, why it does not want to set the DVD-ROM to UDMA66 (the device supports it, as well as my 80-pin cable, and motherboard): See above and try that first. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol(8)
On 2003-10-15 00:20, Mike Maltese wrote: Second, where do I have to indicate that my DVD-ROM supports UDMA66? I assume that after saying atacontrol mode 1 udma66 udma66, the settings are going to be vanished the next reboot. Add the following to /boot/loader.conf: hw.ata.atapi_dma=1 Reboot. Check dmesg. Why to this file and not to /etc/sysctl.conf? I have no monitor on that box, so I want to make sure it is more likely to work after the reboot. :-) Third, why it does not want to set the DVD-ROM to UDMA66 (the device supports it, as well as my 80-pin cable, and motherboard): See above and try that first. But why does it sets it to UDMA33, but not to UDMA66? Cheers, Constantine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol(8)
Why to this file and not to /etc/sysctl.conf? I have no monitor on that box, so I want to make sure it is more likely to work after the reboot. :-) I can't remember exactly why, but trust me, it will work. But why does it sets it to UDMA33, but not to UDMA66? Have you actually tried it yet? It should automatically set it to the drive's highest capability (controller allowing). Frankly, I've never seen a DVD drive, or any other optical drive for that matter, capable of DMA66, nor would it even need to be (33 is the highest I've seen). In any event, give it a try, I'm sure it will work. Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol(8)
Add the following to /boot/loader.conf: hw.ata.atapi_dma=1 Why to this file and not to /etc/sysctl.conf? I have no monitor on that box, so I want to make sure it is more likely to work after the reboot. loader.conf(5) is the system bootstrap configuration file (third step) and is read before all the system is start and even before the kernel is loaded. -- -jg. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol
Has anyone ever run across this error when trying to run atacontrol? $: atacontrol list atacontrol: control device not found: No such file or directory I can't locate much information on the command itself other than the man pages and they don't indicate which device the control device would be. Thanks. -- Micheal Patterson Network Administration Cancer Care Network 405-917-0600 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
On Sunday 21 September 2003 11:56 am, Micheal Patterson wrote: Has anyone ever run across this error when trying to run atacontrol? $: atacontrol list atacontrol: control device not found: No such file or directory atacontrol has to be run as root. -- Todd Stephens ICQ# 3150790 A witty saying proves nothing. -Voltaire ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
Todd Stephens [EMAIL PROTECTED] writes: On Sunday 21 September 2003 11:56 am, Micheal Patterson wrote: Has anyone ever run across this error when trying to run atacontrol? $: atacontrol list atacontrol: control device not found: No such file or directory atacontrol has to be run as root. Wrong error for that to be the problem. Maybe /dev/ata is missing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
-- Micheal Patterson Network Administration Cancer Care Network 405-917-0600 - Original Message - From: Todd Stephens [EMAIL PROTECTED] To: Micheal Patterson [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, September 21, 2003 10:57 AM Subject: Re: atacontrol On Sunday 21 September 2003 11:56 am, Micheal Patterson wrote: Has anyone ever run across this error when trying to run atacontrol? $: atacontrol list atacontrol: control device not found: No such file or directory atacontrol has to be run as root. -- Todd Stephens ICQ# 3150790 A witty saying proves nothing. -Voltaire I was running it as root. I've no idea what device it's looking for. -- Micheal Patterson Network Administration Cancer Care Network ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
On Sunday 21 September 2003 01:39 pm, Lowell Gilbert wrote: Wrong error for that to be the problem. Maybe /dev/ata is missing? Well, if run as a non-root user, I get the same error with permission denied appended on the very end of it. I assumed he merely did not copy the entire line. The OP has since said he was running as root, but the $ prompt he used in the example made me think he was not doing so. -- Todd Stephens ICQ# 3150790 A witty saying proves nothing. -Voltaire ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
cd /dev sh MAKEDEV ata then try atacontrol. ---Mike At 11:56 AM 21/09/2003, Micheal Patterson wrote: Has anyone ever run across this error when trying to run atacontrol? $: atacontrol list atacontrol: control device not found: No such file or directory I can't locate much information on the command itself other than the man pages and they don't indicate which device the control device would be. Thanks. -- Micheal Patterson Network Administration Cancer Care Network 405-917-0600 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
- Original Message - From: Mike Tancsa [EMAIL PROTECTED] To: Micheal Patterson [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, September 21, 2003 4:10 PM Subject: Re: atacontrol cd /dev sh MAKEDEV ata then try atacontrol. ---Mike Tried that as well.. It reports: ata - no such device name -- Micheal Patterson Network Administration Cancer Care Network 405-917-0600 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol
At 08:35 PM 21/09/2003, Micheal Patterson wrote: cd /dev sh MAKEDEV ata then try atacontrol. ---Mike Tried that as well.. It reports: ata - no such device name Do you have device ata in your kernel ? As well do you have ata) mknod ata c 159 0 root:operator ;; in /dev/MAKEDEV ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol raid0 interleave?
What is the suggested interleave numbers? how to calculate the best value? Evren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RAID with atacontrol
Hi Does anybody know if it's possible to create a RAID1 array on disks with data on them without destroying the data on them? My reason for doing this is that I have to disks that I run in an existing Promise Fasttrack100 RAID1 array, but I want to use the RAID controller in another machine. Then I heard that FreeBSD supports Promise RAID1 arrays in the kernel meaning that I can make RAID1 arrays without using a Promise RAID controller. Any help appriciated. -- Venlig hilsen / Best regards, Jacob Vennervald System Developer Proventum Solutions ApS Tuborg Boulevard 12 2900 Hellerup Denmark Phone: +45 36 94 41 66 Mobile: +45 61 68 58 51 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Questions about bootable raid 1 using atacontrol.
Hi, I have a server running 4.8 on a single disk. I'd like to set it up to mirror and be bootable. Killer performance isn't critical, but maximal flexibility to frankenstein it together from spare parts is. So, I'm shying away from hardware raids, and even the pseudo-hardware raids. I'd like to just stuff two ata drives in there and use atacontrol to set them up. I gather that I can't just cram a second disk into the existing system, rather I'll have to do dumps to somewhere, set up a raid, disklabel/newfs, then restore the dumps onto the raid. Is that an accurate summary. Once it's running, how do I recover if/when a disk pukes. It sounds like atacontrol's rebuild command only works w/ real controllers. Do I need to boot from a cd and then dd onto the new disk, or??? Do I need to add the new disk into the raid somehow? Thanks! g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions about bootable raid 1 using atacontrol.
On Wed, Jun 25, 2003 at 08:04:38PM -0700 or thereabouts, George Hartzell wrote: Hi, I have a server running 4.8 on a single disk. I'd like to set it up to mirror and be bootable. Killer performance isn't critical, but maximal flexibility to frankenstein it together from spare parts is. So, I'm shying away from hardware raids, and even the pseudo-hardware raids. I'd like to just stuff two ata drives in there and use atacontrol to set them up. I gather that I can't just cram a second disk into the existing system, rather I'll have to do dumps to somewhere, set up a raid, disklabel/newfs, then restore the dumps onto the raid. Is that an accurate summary. AFAIK, that is correct. Once it's running, how do I recover if/when a disk pukes. It sounds like atacontrol's rebuild command only works w/ real controllers. Do I need to boot from a cd and then dd onto the new disk, or??? Do I need to add the new disk into the raid somehow? I think Vinum or RAIDframe would be better if you want software RAID. Both support booting from the RAID. -- Josh Thanks! g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions about bootable raid 1 using atacontrol.
Joshua Oreman writes: On Wed, Jun 25, 2003 at 08:04:38PM -0700 or thereabouts, George Hartzell wrote: [...] Once it's running, how do I recover if/when a disk pukes. It sounds like atacontrol's rebuild command only works w/ real controllers. Do I need to boot from a cd and then dd onto the new disk, or??? Do I need to add the new disk into the raid somehow? I think Vinum or RAIDframe would be better if you want software RAID. Both support booting from the RAID. I don't think RAIDframe is supported in Stable, is it? Is there a particular advantage to Vinum over the atacontrol stuff? g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions about bootable raid 1 using atacontrol.
On Wed, Jun 25, 2003 at 09:02:22PM -0700 or thereabouts, George Hartzell wrote: Joshua Oreman writes: On Wed, Jun 25, 2003 at 08:04:38PM -0700 or thereabouts, George Hartzell wrote: [...] Once it's running, how do I recover if/when a disk pukes. It sounds like atacontrol's rebuild command only works w/ real controllers. Do I need to boot from a cd and then dd onto the new disk, or??? Do I need to add the new disk into the raid somehow? I think Vinum or RAIDframe would be better if you want software RAID. Both support booting from the RAID. I don't think RAIDframe is supported in Stable, is it? Is there a particular advantage to Vinum over the atacontrol stuff? It's more extensible, has loads more features, is better supported, will rebuild your RAID automatically if need be, you can boot from it, ... -- Josh g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PANIC: vinum / atacontrol (5.0-STABLE / 4.8-RC2)
Hi Greg
Thanks for your response!
#6 0xc0220332 in dsioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58 \001,
flags=0x2, sspp=0xc1328568)
at ../../kern/subr_diskslice.c:356
#7 0xc021fd5b in diskioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58 \001,
fflag=0x2, p=0xca10fee0)
at ../../kern/subr_disk.c:267
#8 0xc140b5af in ?? ()
#9 0xc140969b in ?? ()
#10 0xc140988e in ?? ()
#11 0xc140c461 in ?? ()
#12 0xc024efa2 in spec_ioctl (ap=0xcb307de4) at ../../miscfs/specfs/spec_vnops.c:306
This is different from the other crash. It looks like it happens in
Vinum. Take a look at vinum(4) or
http://www.vinumvm.org/vinum/how-to-debug.html for details of how to
bring life into them.
I have been looking at this page, and I'm not clear what else is needed, or what
you mean by bringing life into them. I followed the steps to analyse a kernel
panic, and provided the output... unfortunately I don't have the knowledge to
fix it myself.
The kenel is panicking in dsioctl(), kern/subr_diskslice.c:356. I've
had a look in there, but I really have no idea what it's trying to
do - I can't even work out what the ioctl is. I'm no kernel guy :(
The ioctl is the cmd parameter passed to diskioctl, 0x8004646d.
That's DIOCWLABEL. Finding them isn't easy, but basically:
0x8 - _IOW macro. We're writing.
004length to write
64 ioctl type ('d'). You'd go looking for a regular expression
_IOW.*'d'.
6d ioctl number (109). This one is in /sys/sys/disklabel.h:
#define DIOCWLABEL_IOW('d', 109, int) /* write en/disable label */
Thanks - that's helpful :)
It's not clear what's trying to write the label, but looking at the
locals of the dsioctl frame would help.
I provided this output in gdb.txt - the code and locals for frame 6 are:
(kgdb) f 6
#6 0xc0220332 in dsioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58
\001, flags=0x2, sspp=0xc1328568)
at ../../kern/subr_diskslice.c:356
356 sp = ssp-dss_slices[slice];
(kgdb) l
351 struct diskslices *ssp;
352 struct partition *pp;
353
354 slice = dkslice(dev);
355 ssp = *sspp;
356 sp = ssp-dss_slices[slice];
357 lp = sp-ds_label;
358 switch (cmd) {
359
360 case DIOCGDVIRGIN:
cmd = 0x0
data = 0xcb307d58 \001
flags = 0x2
error = 0xcb307d58
lp = (struct disklabel *) 0x
old_wlabel = 0x0
openmask = 0x4b
part = 0x2
slice = 0x2
sp = (struct diskslice *) 0x8c
ssp = (struct diskslices *) 0x0
I must admit, I was a little confused as to why cmd was suddenly 0x0 considering
that dsioctl was called with cmd = 0x8004646d, but as I'm no kernel hacker
there's probably a very good reason for it! Is it possible it's being
overwritten and that's why we panic?
I appreciate this may not be a bug in Vinum, but it certainly seems
like it's being triggered by vinum.
Yes, that's reasonable.
Greg
Cheers,
James
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PANIC: vinum / atacontrol (5.0-STABLE / 4.8-RC2)
On Saturday, 29 March 2003 at 10:45:43 +, james wrote:
Hi Greg
Thanks for your response!
#6 0xc0220332 in dsioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58 \001,
flags=0x2, sspp=0xc1328568)
at ../../kern/subr_diskslice.c:356
#7 0xc021fd5b in diskioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58
\001, fflag=0x2, p=0xca10fee0)
at ../../kern/subr_disk.c:267
#8 0xc140b5af in ?? ()
#9 0xc140969b in ?? ()
#10 0xc140988e in ?? ()
#11 0xc140c461 in ?? ()
#12 0xc024efa2 in spec_ioctl (ap=0xcb307de4) at ../../miscfs/specfs/spec_vnops.c:306
This is different from the other crash. It looks like it happens in
Vinum. Take a look at vinum(4) or
http://www.vinumvm.org/vinum/how-to-debug.html for details of how to
bring life into them.
I have been looking at this page, and I'm not clear what else is needed, or what
you mean by bringing life into them. I followed the steps to analyse a kernel
panic, and provided the output... unfortunately I don't have the knowledge to
fix it myself.
You need to load the symbols from the kld. Both pages tell you how to
do that.
It's not clear what's trying to write the label, but looking at the
locals of the dsioctl frame would help.
I provided this output in gdb.txt - the code and locals for frame 6 are:
(kgdb) f 6
#6 0xc0220332 in dsioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58
\001, flags=0x2, sspp=0xc1328568)
at ../../kern/subr_diskslice.c:356
356 sp = ssp-dss_slices[slice];
(kgdb) l
351 struct diskslices *ssp;
352 struct partition *pp;
353
354 slice = dkslice(dev);
355 ssp = *sspp;
356 sp = ssp-dss_slices[slice];
357 lp = sp-ds_label;
358 switch (cmd) {
359
360 case DIOCGDVIRGIN:
cmd = 0x0
data = 0xcb307d58 \001
flags = 0x2
error = 0xcb307d58
lp = (struct disklabel *) 0x
old_wlabel = 0x0
openmask = 0x4b
part = 0x2
slice = 0x2
sp = (struct diskslice *) 0x8c
ssp = (struct diskslices *) 0x0
I must admit, I was a little confused as to why cmd was suddenly 0x0
considering that dsioctl was called with cmd = 0x8004646d,
This is possibly a strangeness of gdb. It's not relevant, however.
but as I'm no kernel hacker there's probably a very good reason for
it! Is it possible it's being overwritten and that's why we panic?
No.
Look at the line where it happened:
356 sp = ssp-dss_slices[slice];
Now look at ssp:
ssp = (struct diskslices *) 0x0
ssp is taken indirectly from sspp:
355 ssp = *sspp;
So the caller is passing invalid data in sspp. That's potentially
Vinum; you need to get those symbols loaded and find out what Vinum is
doing.
To the rest of -questions: is this interesting? If not, I'll take it
offline. I need at least one yes please reply to continue beyond
the next exchange of messages.
Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PANIC: vinum / atacontrol (5.0-STABLE / 4.8-RC2)
Hi Greg
I will be able to analyse the 5.0-stable panic a little more when I get home.
In the meantime I've been doing simliar tests with 4.8-RC2. I get slightly more
progress, but still a panic at the end.
Sequence of events:
1, create volume, 2 plexes on 2 disks
2, vinum stop volume.p1
3, atacontrol detach 1 (drive b)
4, atacontrol attach 1 - this WORKS, doesn't panic like 5.0-STABLE
5, vinum start volume.p1
PANIC
As before, I have a debug kernel and core dump. I can't seem to configure my
mailer to not wrap lines, so I've posted all relevant information to
http://web.hisser.org/vinum/4.8-crash/ . They are plain text files.
The kenel is panicking in dsioctl(), kern/subr_diskslice.c:356. I've had a look
in there, but I really have no idea what it's trying to do - I can't even work
out what the ioctl is. I'm no kernel guy :(
I appreciate this may not be a bug in Vinum, but it certainly seems like it's
being triggered by vinum. I can access the drive, query the disklabel, and
format the partition after the attach - it's only when I restart the plex does
it panic.
If I detach the plex before removing it, I get the same panic in dsioctl() when
I re-attach the plex, without even getting the opportunity to start the plex.
I would love to be able to help get this working, as I'm unable to hotswap at
all in Linux, which is what has made me move to FreeBSD.
Thanks
James
On Fri, 28 Mar 2003, Greg 'groggy' Lehey wrote:
[Format recovered--see http://www.lemis.com/email/email-format.html]
Computer output wrapped.
On Thursday, 27 March 2003 at 14:18:43 +, james wrote:
Hi
I am trying to configure hotswap-raid and vinum on my machine, and have found I
can cause the kernel to panic at will.
Ideally I would like to be able to stop a plex, use atacontrol attach/detach to
replace the disk, and rebuild the plex. Would this work in theory?
Apparently. There was a time when people claimed that ATA drives
couldn't be hot swapped, but that seems to be incorrect nowadays.
Now I stop and unload vinum, and try to run atacontrol:
eddie# vinum stop
vinum unloaded
eddie# kldstat | grep vinum
eddie#
eddie# atacontrol detach 3
PANIC
I have built a debug kernel, and have a core. The backtrace is below.
If you need any more info please let me know!
James
Now follows the gdb-output:
(kgdb) bt
#9 0xc01a9223 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#10 0xc02e311e in trap_fatal (frame=0xc0b94e00, eva=0x0) at
/usr/src/sys/i386/i386/trap.c:844
#11 0xc02e2e32 in trap_pfault (frame=0xc873fa74, usermode=0x0, eva=0x24) at
/usr/src/sys/i386/i386/trap.c:758
#12 0xc02e2a1d in trap (frame=
{tf_fs = 0xc0380018, tf_es = 0xc0b90010, tf_ds = 0x10, tf_edi = 0x0,
tf_esi = 0xc1857530, tf_ebp = 0xc873fab4, tf_isp = 0xc873faa0, tf_
ebx = 0xc19a6c00, tf_edx = 0xe7, tf_ecx = 0xc032a340, tf_eax = 0x0, tf_trapno =
0xc, tf_err = 0x0, tf_eip = 0xc01c6de6, tf_cs = 0x8, tf_eflag
s = 0x10292, tf_esp = 0xc873faf0, tf_ss = 0xc01296ae})
at /usr/src/sys/i386/i386/trap.c:445
#13 0xc02d44f8 in calltrap () at {standard input}:98
#14 0xc01296ae in ata_command (atadev=0xc1857530, command=0xe7, lba=0x0,
count=0x0, feature=0x0, flags=0x4)
at bus_at386.h:526
#15 0xc01396df in adclose (dev=0x0, flags=0x3, fmt=0x0, td=0x0) at
/usr/src/sys/dev/ata/ata-disk.c:292
(etc)
The trap occurred between frames 12 and 13 at address 0xc873faa0, in
the ATA code. Depending on your prowess with kernel code, you may be
able to find out what has gone wrong. I'd be inclined to look at
frame 13:
(gdb) f 13 select frame
(gdb) l list the code
(gdb) i loc show local variables
My guess is that something has not been initialized. It's probably
worth submitting a bug report.
Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PANIC: vinum / atacontrol (5.0-STABLE / 4.8-RC2)
On Friday, 28 March 2003 at 11:32:48 +, james wrote:
On Fri, 28 Mar 2003, Greg 'groggy' Lehey wrote:
[Format recovered--see http://www.lemis.com/email/email-format.html]
Computer output wrapped.
On Thursday, 27 March 2003 at 14:18:43 +, james wrote:
Hi
I am trying to configure hotswap-raid and vinum on my machine, and have found I
can cause the kernel to panic at will.
Ideally I would like to be able to stop a plex, use atacontrol attach/detach to
replace the disk, and rebuild the plex. Would this work in theory?
Apparently. There was a time when people claimed that ATA drives
couldn't be hot swapped, but that seems to be incorrect nowadays.
Now I stop and unload vinum, and try to run atacontrol:
eddie# vinum stop
vinum unloaded
eddie# kldstat | grep vinum
eddie#
eddie# atacontrol detach 3
PANIC
I have built a debug kernel, and have a core. The backtrace is below.
If you need any more info please let me know!
James
Now follows the gdb-output:
(kgdb) bt
#9 0xc01a9223 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#10 0xc02e311e in trap_fatal (frame=0xc0b94e00, eva=0x0) at
/usr/src/sys/i386/i386/trap.c:844
#11 0xc02e2e32 in trap_pfault (frame=0xc873fa74, usermode=0x0, eva=0x24) at
/usr/src/sys/i386/i386/trap.c:758
#12 0xc02e2a1d in trap (frame=
{tf_fs = 0xc0380018, tf_es = 0xc0b90010, tf_ds = 0x10, tf_edi = 0x0,
tf_esi = 0xc1857530, tf_ebp = 0xc873fab4, tf_isp = 0xc873faa0, tf_
ebx = 0xc19a6c00, tf_edx = 0xe7, tf_ecx = 0xc032a340, tf_eax = 0x0, tf_trapno =
0xc, tf_err = 0x0, tf_eip = 0xc01c6de6, tf_cs = 0x8, tf_eflag
s = 0x10292, tf_esp = 0xc873faf0, tf_ss = 0xc01296ae})
at /usr/src/sys/i386/i386/trap.c:445
#13 0xc02d44f8 in calltrap () at {standard input}:98
#14 0xc01296ae in ata_command (atadev=0xc1857530, command=0xe7, lba=0x0,
count=0x0, feature=0x0, flags=0x4)
at bus_at386.h:526
#15 0xc01396df in adclose (dev=0x0, flags=0x3, fmt=0x0, td=0x0) at
/usr/src/sys/dev/ata/ata-disk.c:292
(etc)
The trap occurred between frames 12 and 13 at address 0xc873faa0, in
the ATA code. Depending on your prowess with kernel code, you may be
able to find out what has gone wrong. I'd be inclined to look at
frame 13:
(gdb) f 13 select frame
(gdb) l list the code
(gdb) i loc show local variables
My guess is that something has not been initialized. It's probably
worth submitting a bug report.
I will be able to analyse the 5.0-stable panic a little more when I get home.
In the meantime I've been doing simliar tests with 4.8-RC2. I get slightly more
progress, but still a panic at the end.
Sequence of events:
1, create volume, 2 plexes on 2 disks
2, vinum stop volume.p1
3, atacontrol detach 1 (drive b)
4, atacontrol attach 1 - this WORKS, doesn't panic like 5.0-STABLE
5, vinum start volume.p1
PANIC
OK, that's good background information, but first we need to look at
the dump.
As before, I have a debug kernel and core dump. I can't seem to
configure my mailer to not wrap lines, so I've posted all relevant
information to http://web.hisser.org/vinum/4.8-crash/ . They are
plain text files.
You should consider getting a different MUA.
#6 0xc0220332 in dsioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58 \001,
flags=0x2, sspp=0xc1328568)
at ../../kern/subr_diskslice.c:356
#7 0xc021fd5b in diskioctl (dev=0xc1383200, cmd=0x8004646d, data=0xcb307d58 \001,
fflag=0x2, p=0xca10fee0)
at ../../kern/subr_disk.c:267
#8 0xc140b5af in ?? ()
#9 0xc140969b in ?? ()
#10 0xc140988e in ?? ()
#11 0xc140c461 in ?? ()
#12 0xc024efa2 in spec_ioctl (ap=0xcb307de4) at ../../miscfs/specfs/spec_vnops.c:306
This is different from the other crash. It looks like it happens in
Vinum. Take a look at vinum(4) or
http://www.vinumvm.org/vinum/how-to-debug.html for details of how to
bring life into them.
The kenel is panicking in dsioctl(), kern/subr_diskslice.c:356. I've
had a look in there, but I really have no idea what it's trying to
do - I can't even work out what the ioctl is. I'm no kernel guy :(
The ioctl is the cmd parameter passed to diskioctl, 0x8004646d.
That's DIOCWLABEL. Finding them isn't easy, but basically:
0x8 - _IOW macro. We're writing.
004length to write
64 ioctl type ('d'). You'd go looking for a regular expression
_IOW.*'d'.
6d ioctl number (109). This one is in /sys/sys/disklabel.h:
#define DIOCWLABEL _IOW('d', 109, int) /* write en/disable label */
It's not clear what's trying to write the label, but looking at the
locals of the dsioctl frame would help.
I appreciate this may not be a bug in Vinum, but it certainly seems
like it's being triggered by vinum.
Yes, that's reasonable.
Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete
PANIC: vinum / atacontrol (5.0-STABLE)
Hi
I am trying to configure hotswap-raid and vinum on my machine, and have found I
can cause the kernel to panic at will.
Ideally I would like to be able to stop a plex, use atacontrol attach/detach to
replace the disk, and rebuild the plex. Would this work in theory?
I am using atacontrol to allow me to hot-swap drives. On a freshly rebooted
system, where I haven't yet loaded vinum, this works:
eddie# mount /dev/ad6s1a /mnt
eddie# touch /mnt/SOME_DATA
eddie# umount /mnt
eddie# atacontrol detach 3
ad6: removed from configuration
eddie# atacontrol attach 3
Master: ad6 IC35L120AVV207-0/V24OA63A ATA/ATAPI rev 6
Slave: no device present
eddie# mount /dev/ad6s1a /mnt
eddie# cd /mnt
eddie# ls
SOME_DATA
eddie#
And now, I create a vinum volume that's mirrored across 2 drives, the second of
which is ad6:
eddie# cat config1
drive a device /dev/ad4s1a
drive b device /dev/ad6s1a
volume mirror setupstate
plex org concat
sd length 1000m drive a
plex org concat
sd length 1000m drive b
eddie# vinum create config1
2 drives:
D a State: up /dev/ad4s1a A: 116796/117796 MB
D b State: up /dev/ad6s1a A: 116796/117796 MB
1 volumes:
V mirrorState: up Plexes: 2 Size: 1000 MB
2 plexes:
P mirror.p0 C State: up Subdisks: 1 Size: 1000 MB
P mirror.p1 C State: up Subdisks: 1 Size: 1000 MB
2 subdisks:
S mirror.p0.s0 State: up D: aSize: 1000 MB
S mirror.p1.s0 State: up D: bSize: 1000 MB
Now I stop and unload vinum, and try to run atacontrol:
eddie# vinum stop
vinum unloaded
eddie# kldstat | grep vinum
eddie#
eddie# atacontrol detach 3
PANIC
I have built a debug kernel, and have a core. The backtrace is below.
If you need any more info please let me know!
James
Now follows the gdb-output:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01c6de6
stack pointer = 0x10:0xc873fab4
frame pointer = 0x10:0xc873fab4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 2 (g_event)
trap number = 12
panic: page fault
syncing disks, buffers remaining... panic: bdwrite: buffer is not busy
Uptime: 22m39s
Dumping 126 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112
---
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:232
232 dumping++;
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:232
#1 0xc01a9011 in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:364
#2 0xc01a9223 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#3 0xc01e78ed in bdwrite (bp=0xc0b94e00) at /usr/src/sys/kern/vfs_bio.c:950
#4 0xc027e46b in ffs_update (vp=0xc1ae68e0, waitfor=0x0) at
/usr/src/sys/ufs/ffs/ffs_inode.c:125
#5 0xc02924df in ffs_fsync (ap=0xc873f8ec) at
/usr/src/sys/ufs/ffs/ffs_vnops.c:315
#6 0xc02915ee in ffs_sync (mp=0xc1906a00, waitfor=0x2, cred=0xc0b86e00,
td=0xc0325e40) at vnode_if.h:612
#7 0xc01fa24b in sync (td=0xc0325e40, uap=0x0) at
/usr/src/sys/kern/vfs_syscalls.c:138
#8 0xc01a8c82 in boot (howto=0x100) at /usr/src/sys/kern/kern_shutdown.c:273
#9 0xc01a9223 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#10 0xc02e311e in trap_fatal (frame=0xc0b94e00, eva=0x0) at
/usr/src/sys/i386/i386/trap.c:844
#11 0xc02e2e32 in trap_pfault (frame=0xc873fa74, usermode=0x0, eva=0x24) at
/usr/src/sys/i386/i386/trap.c:758
#12 0xc02e2a1d in trap (frame=
{tf_fs = 0xc0380018, tf_es = 0xc0b90010, tf_ds = 0x10, tf_edi = 0x0,
tf_esi = 0xc1857530, tf_ebp = 0xc873fab4, tf_isp = 0xc873faa0, tf_
ebx = 0xc19a6c00, tf_edx = 0xe7, tf_ecx = 0xc032a340, tf_eax = 0x0, tf_trapno =
0xc, tf_err = 0x0, tf_eip = 0xc01c6de6, tf_cs = 0x8, tf_eflag
s = 0x10292, tf_esp = 0xc873faf0, tf_ss = 0xc01296ae})
at /usr/src/sys/i386/i386/trap.c:445
#13 0xc02d44f8 in calltrap () at {standard input}:98
#14 0xc01296ae in ata_command (atadev=0xc1857530, command=0xe7, lba=0x0,
count=0x0, feature=0x0, flags=0x4)
at bus_at386.h:526
#15 0xc01396df in adclose (dev=0x0, flags=0x3, fmt=0x0, td=0x0) at
/usr/src/sys/dev/ata/ata-disk.c:292
#16 0xc0177593 in g_disk_access (pp=0xc1919380, r=0x0, w=0x0, e=0x0) at
/usr/src/sys/geom/geom_disk.c:96
#17 0xc017b634 in g_access_rel (cp=0xc1913800, dcr=0x, dcw=0x,
dce=0xfffe)
at /usr/src/sys/geom/geom_subr.c:437
#18 0xc017a0b0 in g_slice_access (pp=0xc1911680, dr=0x, dw=0x,
de=0xfffe)
at /usr/src/sys/geom/geom_slice.c:121
#19 0xc017b634 in g_access_rel (cp=0xc213a000, dcr=0x, dcw=0x,
dce=0x)
at /usr/src/sys/geom/geom_subr.c:437
#20 0xc017a0b0 in g_slice_access (pp=0xc1d4cd80, dr
Re: PANIC: vinum / atacontrol (5.0-STABLE)
[Format recovered--see http://www.lemis.com/email/email-format.html]
Computer output wrapped.
On Thursday, 27 March 2003 at 14:18:43 +, james wrote:
Hi
I am trying to configure hotswap-raid and vinum on my machine, and have found I
can cause the kernel to panic at will.
Ideally I would like to be able to stop a plex, use atacontrol attach/detach to
replace the disk, and rebuild the plex. Would this work in theory?
Apparently. There was a time when people claimed that ATA drives
couldn't be hot swapped, but that seems to be incorrect nowadays.
Now I stop and unload vinum, and try to run atacontrol:
eddie# vinum stop
vinum unloaded
eddie# kldstat | grep vinum
eddie#
eddie# atacontrol detach 3
PANIC
I have built a debug kernel, and have a core. The backtrace is below.
If you need any more info please let me know!
James
Now follows the gdb-output:
(kgdb) bt
#9 0xc01a9223 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#10 0xc02e311e in trap_fatal (frame=0xc0b94e00, eva=0x0) at
/usr/src/sys/i386/i386/trap.c:844
#11 0xc02e2e32 in trap_pfault (frame=0xc873fa74, usermode=0x0, eva=0x24) at
/usr/src/sys/i386/i386/trap.c:758
#12 0xc02e2a1d in trap (frame=
{tf_fs = 0xc0380018, tf_es = 0xc0b90010, tf_ds = 0x10, tf_edi = 0x0,
tf_esi = 0xc1857530, tf_ebp = 0xc873fab4, tf_isp = 0xc873faa0, tf_
ebx = 0xc19a6c00, tf_edx = 0xe7, tf_ecx = 0xc032a340, tf_eax = 0x0, tf_trapno =
0xc, tf_err = 0x0, tf_eip = 0xc01c6de6, tf_cs = 0x8, tf_eflag
s = 0x10292, tf_esp = 0xc873faf0, tf_ss = 0xc01296ae})
at /usr/src/sys/i386/i386/trap.c:445
#13 0xc02d44f8 in calltrap () at {standard input}:98
#14 0xc01296ae in ata_command (atadev=0xc1857530, command=0xe7, lba=0x0, count=0x0,
feature=0x0, flags=0x4)
at bus_at386.h:526
#15 0xc01396df in adclose (dev=0x0, flags=0x3, fmt=0x0, td=0x0) at
/usr/src/sys/dev/ata/ata-disk.c:292
(etc)
The trap occurred between frames 12 and 13 at address 0xc873faa0, in
the ATA code. Depending on your prowess with kernel code, you may be
able to find out what has gone wrong. I'd be inclined to look at
frame 13:
(gdb) f 13 select frame
(gdb) llist the code
(gdb) i locshow local variables
My guess is that something has not been initialized. It's probably
worth submitting a bug report.
Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Difference between Vinum and atacontrol RAID?
Pete wrote: [ ... ] The RAID-1 volume I'm using right now is with two drives attached to a non-RAID card with a Promise chipset. Does it work if you move the two drives to another machine without a Promise, Highpoint, or other RAID controller card or MB chipset...? Hardware based RAID is likely to be faster, particularly in the case of parity calculations for RAID-5. (Not that many IDE controllers can do RAID-5, but...) It would be, but the RAID on the Promise and Highpoint devices is not true hardware RAID. It's just software RAID with the drivers moved over to an EPROM on the card. When you write to a RAID-1 mirror on such a device, does the CPU and PCI bus see two copies of the data? Or does the Promise or HPT deal with distributing the data across the right devices itself? I know from my own experience and that of other people that the Linux software RAID outperforms the hardware RAID of these devices. I'm willing to bet that the FreeBSD RAID at least comes close, if not betters the Linux performance. Software-based RAID can do fine for things like -0 -1; but without numbers, subjective discussion of performance can be misleading -Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Vinum root file systems (was: Difference between Vinum and atacontrol RAID?)
On Sunday, 9 March 2003 at 20:15:32 -0500, Chuck Swiger wrote: Pete wrote: Generally, one cannot boot from a vinum based-device, unless you are only doing RAID-1 mirroring. You can have a Vinum root file system as long as at least one plex is concatenated from a single subdisk. I'm familar with something called encapsulating the root partition under Solaris and Veritas; it's not for the faint-of-heart. :-) I suspect this is the same thing. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Difference between Vinum and atacontrol RAID?
On Sun, 09 Mar 2003, Chuck Swiger wrote: The ATA RAID support via atacontrol apparently requires hardware RAID controllers like the Promise or Highpoint devices. I don't think this is right. The RAID-1 volume I'm using right now is with two drives attached to a non-RAID card with a Promise chipset. I also get the impression -- though can't test it right now -- that the atacrontrol-based RAID will work across cards. Anyone know for sure about this? Hardware based RAID is likely to be faster, particularly in the case of parity calculations for RAID-5. (Not that many IDE controllers can do RAID-5, but...) It would be, but the RAID on the Promise and Highpoint devices is not true hardware RAID. It's just software RAID with the drivers moved over to an EPROM on the card. I know from my own experience and that of other people that the Linux software RAID outperforms the hardware RAID of these devices. I'm willing to bet that the FreeBSD RAID at least comes close, if not betters the Linux performance. Thanks, pete To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Difference between Vinum and atacontrol RAID?
A couple days ago, I asked on the -hackers list about a problem I was having with Vinum and my Promise-based controllers. Søren replied with how to do this by using atacontrol to build the volume. No Vinum seems to be required. I thought Vinum was FreeBSD's RAID system. If you wanted to do software RAID with FreeBSD, you needed to use Vinum. Now I find this out. Does that ATA subsystem have RAID support built in? (Since atacontrol just seems to control the ATA devices...) If this is so, what's the use of Vinum? When should I use one vs the other? How do Vinum and the ATA subsystem's RAID relate? Thanks, pete To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Difference between Vinum and atacontrol RAID?
Pete wrote: [ ... ] I thought Vinum was FreeBSD's RAID system. If you wanted to do software RAID with FreeBSD, you needed to use Vinum. Now I find this out. Does that ATA subsystem have RAID support built in? (Since atacontrol just seems to control the ATA devices...) If this is so, what's the use of Vinum? When should I use one vs the other? How do Vinum and the ATA subsystem's RAID relate? Vinum resembles a popular commercial RAID product called Veritas LVM; vinum does software-based RAID. The ATA RAID support via atacontrol apparently requires hardware RAID controllers like the Promise or Highpoint devices. Hardware based RAID is likely to be faster, particularly in the case of parity calculations for RAID-5. (Not that many IDE controllers can do RAID-5, but...) The RAID volumes created with vinum are accessible only under FreeBSD, whereas the ATA-based RAID solutions create a logical volume accessible via the normal BIOS interfaces, so the RAID device looks like a single, bigger physical disk drive. Thus you can use an ATA-based hardware RAID volume as a boot device, install multiple operating systems, etc. Generally, one cannot boot from a vinum based-device, unless you are only doing RAID-1 mirroring. I'm familar with something called encapsulating the root partition under Solaris and Veritas; it's not for the faint-of-heart. :-) -Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Fixing degraded atacontrol based software RAID?
Hello, I have a machine running atacontrol based software RAID in which one of the disks recently failed (Maxtor, not IBM for those who want to know). Now I'm wondering how I should go about fixing this. atacontrol seems to lack a command to fix broken software only arrays. I suppose I could use dd -if workingdisk -of newdisk but atacontrol seems to block the disks during multi user (and since the box has got work to do, I can't just take it down for a few hours). Other option would be to just install a hardware RAID controller I suppose. I still have a 3ware one laying around somewhere (this one features background rebuilding, albeit very slowly) but I'd be interested to hear whether I can do background rebuilding triggered from atacontrol with Highpoint 370 or Promise Fasttrak controllers. Any comments would greatly be appreciated (as would be CCs to myself as the traffic on this list makes it sometimes hard to find the answers ;-). TIA regards, Gabriel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
