Re: problem: bsdlabel
On 28.03.2012 20:41, Nenhum_de_Nos wrote: > hail, > > I partitioned the disk this way: > > fdisk da0 > *** Working on device /dev/da0 *** > parameters extracted from in-core disklabel are: > cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 166 (0xa6),(OpenBSD) > start 126, size 20964699 (10236 Meg), flag 0 > beg: cyl 0/ head 2/ sector 1; > end: cyl 280/ head 254/ sector 63 > The data for partition 2 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 20971629, size 8379126 (4091 Meg), flag 0 > beg: cyl 281/ head 108/ sector 1; > end: cyl 802/ head 254/ sector 63 > The data for partition 3 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 29350755, size 41929650 (20473 Meg), flag 0 > beg: cyl 803/ head 0/ sector 1; > end: cyl 340/ head 254/ sector 63 > The data for partition 4 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 71280405, size 124086060 (60588 Meg), flag 80 (active) > beg: cyl 341/ head 0/ sector 1; > end: cyl 896/ head 254/ sector 63 > > > but when was time to label it, I did it wrong: > > bsdlabel -w da0 > > should have aimed slice 2 > > now, I just get da0 on /dev and sysinstall only sees da0 also. but fdisk sees > it all (as showed > above) > > how can I erase all label info from da0 (not da0s1 or da0s2). > I tried to rewrite fdisk and all mbr info, but label info is still there. > I'd like not to have to reinstall OpenBSD, if possible. First of in the future you should use gpart(8) utility to manage partitions and slices. bsdlabel keeps metadata in the second sector. Therefore you should rewrite it to destroy label. But to be sure please show output of this command: # gpart show -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
RE: problem: bsdlabel
Hi Matheus, You have two options. Option 1. Resync the in-memory and on-disk view of the world Identify the device from # usbconfig list Then power it off and then power on. If this doesn't work then you'll need to dd the device. For example: # usbconfig list ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE # usbconfig -d 4.2 power_off # usbconfig -d 4.2 power_on Option 2. Clear the boot blocks # dd if=/dev/zero of=/dev/da0 bs=1M count=1 If this doesn't help then zero the whole device, omit the bs and count arguments. I'd also suggest that you assign 0xa5 to the device, by # fdisk -p da0 > /tmp/fdisk.cf Use a text editor to change the 0xa6 to 0xa5; then write it back to fdisk # fdisk -f /tmp/fdisk.cf /dev/da0 Of course, the excessive option is to reboot... Regards, Dewayne. PS I think this question would be better placed in the FreeBSD Questions mailing list :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_9 tinderbox] failure on ia64/ia64
TB --- 2012-03-28 21:43:24 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-03-28 21:43:24 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2012-03-28 21:43:24 - cleaning the object tree TB --- 2012-03-28 21:43:24 - cvsupping the source tree TB --- 2012-03-28 21:43:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_9/ia64/ia64/supfile TB --- 2012-03-28 21:44:29 - building world TB --- 2012-03-28 21:44:29 - CROSS_BUILD_TESTING=YES TB --- 2012-03-28 21:44:29 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-28 21:44:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-28 21:44:29 - SRCCONF=/dev/null TB --- 2012-03-28 21:44:29 - TARGET=ia64 TB --- 2012-03-28 21:44:29 - TARGET_ARCH=ia64 TB --- 2012-03-28 21:44:29 - TZ=UTC TB --- 2012-03-28 21:44:29 - __MAKE_CONF=/dev/null TB --- 2012-03-28 21:44:29 - cd /src TB --- 2012-03-28 21:44:29 - /usr/bin/make -B buildworld >>> World build started on Wed Mar 28 21:44:30 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Mar 28 23:32:24 UTC 2012 TB --- 2012-03-28 23:32:24 - generating LINT kernel config TB --- 2012-03-28 23:32:24 - cd /src/sys/ia64/conf TB --- 2012-03-28 23:32:24 - /usr/bin/make -B LINT TB --- 2012-03-28 23:32:24 - cd /src/sys/ia64/conf TB --- 2012-03-28 23:32:24 - /usr/sbin/config -m LINT TB --- 2012-03-28 23:32:24 - building LINT kernel TB --- 2012-03-28 23:32:24 - CROSS_BUILD_TESTING=YES TB --- 2012-03-28 23:32:24 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-28 23:32:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-28 23:32:24 - SRCCONF=/dev/null TB --- 2012-03-28 23:32:24 - TARGET=ia64 TB --- 2012-03-28 23:32:24 - TARGET_ARCH=ia64 TB --- 2012-03-28 23:32:24 - TZ=UTC TB --- 2012-03-28 23:32:24 - __MAKE_CONF=/dev/null TB --- 2012-03-28 23:32:24 - cd /src TB --- 2012-03-28 23:32:24 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Mar 28 23:32:24 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/ufs/ffs/ffs_inode.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/ufs/ffs/ffs_snapshot.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/ufs/ffs/ffs_softdep.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffi
Re: 9.0 Install and serial terminal
On Wed, March 28, 2012 17:28, Nenhum_de_Nos wrote: > hail, > > I have some problems trying to install 9.0-BETA3 using a serial terminal. I > edited to have it boot > using serial console, that was fine, but I can't get it to create the slices > the size I want. I > say 1g to create a swap, and it puts there -56GB as size. Next I try to set > 4GB to /var, using 4g > or 4GB, and it sets 1.5GB. > > FreeBSD Installer > > ── > > > > ┌──Partition > Editor┐ > │ Create partitions for FreeBSD. No changes will be > │ > │ made until you select Finish. > │ > > │┌^(-)┐│ > ││ ada0s4 59 GB BSD > ││ > ││ada0s4a 2.0 GBfreebsd-ufs/ > ││ > ││ada0s4b -56 GBfreebsd-swap none > ││ > ││ada0s4d 1.5 GBfreebsd-ufs/var > ││ > ││da0 3.8 GBGPT > ││ > ││ da0p1 64 kB freebsd-boot > ││ > ││ da0p2 535 MBfreebsd-ufs > ││ > ││ > ││ > > │└┘│ > > ├──┤ > │< Auto > > │ > > └──┘ > > > > Add a new partition > > to add to this, I couldn't find where to say that I'd like that or this > partition to be formatted, > and how to create labels to it. > > is this supposed to happen this way ? Am I doing something wrong ? > > thanks, > > matheus as an update, when I deleted the slice and tried again, it worked fine. The partition table was created using sysinstall from the same installation. matheus -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.0 Install and serial terminal
hail, I have some problems trying to install 9.0-BETA3 using a serial terminal. I edited to have it boot using serial console, that was fine, but I can't get it to create the slices the size I want. I say 1g to create a swap, and it puts there -56GB as size. Next I try to set 4GB to /var, using 4g or 4GB, and it sets 1.5GB. FreeBSD Installer ── ┌──Partition Editor┐ │ Create partitions for FreeBSD. No changes will be│ │ made until you select Finish.│ │┌^(-)┐│ ││ ada0s4 59 GB BSD ││ ││ada0s4a 2.0 GBfreebsd-ufs/ ││ ││ada0s4b -56 GBfreebsd-swap none ││ ││ada0s4d 1.5 GBfreebsd-ufs/var ││ ││da0 3.8 GBGPT ││ ││ da0p1 64 kB freebsd-boot ││ ││ da0p2 535 MBfreebsd-ufs ││ ││ ││ │└┘│ ├──┤ │< Auto > │ └──┘ Add a new partition to add to this, I couldn't find where to say that I'd like that or this partition to be formatted, and how to create labels to it. is this supposed to happen this way ? Am I doing something wrong ? thanks, matheus -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
problem: bsdlabel
hail, I partitioned the disk this way: fdisk da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 166 (0xa6),(OpenBSD) start 126, size 20964699 (10236 Meg), flag 0 beg: cyl 0/ head 2/ sector 1; end: cyl 280/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 20971629, size 8379126 (4091 Meg), flag 0 beg: cyl 281/ head 108/ sector 1; end: cyl 802/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 29350755, size 41929650 (20473 Meg), flag 0 beg: cyl 803/ head 0/ sector 1; end: cyl 340/ head 254/ sector 63 The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 71280405, size 124086060 (60588 Meg), flag 80 (active) beg: cyl 341/ head 0/ sector 1; end: cyl 896/ head 254/ sector 63 but when was time to label it, I did it wrong: bsdlabel -w da0 should have aimed slice 2 now, I just get da0 on /dev and sysinstall only sees da0 also. but fdisk sees it all (as showed above) how can I erase all label info from da0 (not da0s1 or da0s2). I tried to rewrite fdisk and all mbr info, but label info is still there. I'd like not to have to reinstall OpenBSD, if possible. thanks, matheus -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Floppy disks don't work with FreeBSD 9.0
> Hi. > > I'm a bit short on free machines, so the closest I can get right now > is my everyday machine running from sources cvsupped from > RELENG_8 3.rd of March: > I 'csuped' to FreeBSD 9.0-STABLE today and still had the same problem. This computer has normal floppy disk operation when using FreeBSD 8.3-RC1 and doesn't have any fd functionality with FreeBSD 9.0-STABLE. I entered a Problem Report in the system today. Thanks for all of the help, we'll let the development team take if from here. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ESCape codes displayed instead of processed in pager
Ever since I have upgraded to 9-stable, I have noticed that the manpages seem to be munged up with displayed instead of processed ESCape codes. an example: 1:41:05pm argus(8): man man MAN(1) FreeBSD General Commands Manual MAN(1) ESC[1mNAMEESC[0m ESC[1mman ESC[22m-- display online manual documentation pages ESC[1mSYNOPSISESC[0m ESC[1mman ESC[22m[ESC[1m-adhoESC[22m] [ESC[1m-t ESC[22m| ESC[1m-wESC[22m] [ESC[1m-M ESC[4mESC[22mmanpathESC[24m] [ESC[1m-P ESC[4mESC[22mpagerESC[24m] [ESC[1m-S ESC[4mESC[22mmansectESC[24m] [ESC[1m-m ESC[4mESC[22marchESC[24m[:ESC[4mmachineESC[24m]] [ESC[1m-p ESC[22m[ESC[4meprtvESC[24m]] [ESC[4mmansectESC[24m] ESC[4mpageESC[24m ESC[4m...ESC[0m ESC[1mman -f ESC[4mESC[22mkeywordESC[24m ESC[4m...ESC[0m ESC[1mman -k ESC[4mESC[22mkeywordESC[24m ESC[4m...ESC[0m ESC[1mDESCRIPTIONESC[0m The ESC[1mman ESC[22mutility finds and displays online manual documentation pages. If ESC[4mmansectESC[24m is provided, ESC[1mman ESC[22mrestricts the search to the specific section of the manual. I have actually ruled out nroff -man, and have determined that this has to do with /usr/bin/more and /usr/bin/less. example: 1:44:45pm argus(9): man man | cat MAN(1) FreeBSD General Commands Manual MAN(1) NAME man -- display online manual documentation pages SYNOPSIS man [-adho] [-t | -w] [-M manpath] [-P pager] [-S mansect] [-m arch[:machine]] [-p [eprtv]] [mansect] page ... man -f keyword ... man -k keyword ... DESCRIPTION The man utility finds and displays online manual documentation pages. If mansect is provided, man restricts the search to the specific section of the manual. So far as I can tell, it is in both more and less. if it relies on termcap, then the issue is bigger, because it does the same thing in syscons as it does an xterm. My bottom line question is what changed, and how do I change my end to make things work as expected again? Honestly, this is a real pain in the ass when I need a manual page. jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Too many open files
1:23:14pm argus(50): lsof -n | awk '{print $2 "\t" $1}' | sort | uniq
-c | sort
lsof: Command not found.
1:35:12pm argus(51): man lsof | cat
No manual entry for lsof
1:35:38pm argus(52): find /usr/src -iname \*lsof\*
1:36:42pm argus(53): find /usr/src -type f -iname \*lsof\*
1:36:50pm argus(54):
huh??? 9-stable here. is this a -port?
Aha!
1:39:07pm argus(1): cd /usr/ports
1:39:11pm argus(2): make search name=lsof
Port: lsof-4.86A,6
Path: /usr/ports/sysutils/lsof
Info: Lists information about open files (similar to fstat(1))
Maint: l...@lerctr.org
B-deps:
R-deps:
WWW:http://people.freebsd.org/~abe/
Port: p5-Unix-Lsof-0.0.5_1
Path: /usr/ports/sysutils/p5-Unix-Lsof
Info: Unix::Lsof -- a wrapper to the Unix lsof utility
Maint: g...@gjvc.com
B-deps: p5-IPC-Run3-0.044 perl-5.12.4_3
R-deps: p5-IPC-Run3-0.044 perl-5.12.4_3
WWW:http://search.cpan.org/dist/Unix-Lsof/
Next time, please state that it is a port and not a builtin.
Thanks
jim
Shane Ambler wrote:
On 26/03/2012 02:19, C. P. Ghost wrote:
On Sun, Mar 25, 2012 at 6:46 PM, Prabhpal S. Mavi
wrote:
Greetings Friends,
have anyone has come across this warning / error? This occurs when i
ssh
to my FreeBSD 9.0 System. any help would be greatly appreciated.
Warning:
/usr/share/games/fortune/freebsd-tips.dat: Too many open files in
system
[mavi@titan ~]$ su
su: pam_start: system error
Thanks / Regards
Prabhpal
What does this command say on your system?
% sysctl kern.maxfiles kern.maxfilesperproc kern.openfiles
You may have exceeded the maximum number of open files
in the system. Maybe some ill-conceived program that doesn't
close non-needed connections, files, etc is at fault? It's easy
to open more and more files, and to gradually fill the open
files descriptor table in the kernel this way.
-cpghost.
From knowing that you have too many files open you can increase the
maxfile numbers - but if you want to know what uses them try this -
lsof -n | awk '{print $2 "\t" $1}' | sort | uniq -c | sort
lsof outputs open file info, awk then gives us the PID and proc name
which gets sorted and uniq gives a count of each which we sort to have
the largest file count at the bottom of the list. What you end up with
is a list of two numbers and a name - count of files open followed by
the PID and proc name that has them open.
The catch is that it also includes network connections (I know how to
list only network but not sure how to exclude them)
ps ax | grep PID
will show you the full program name if it has been shortened.
lsof -p PID
will show all the open files for PID
Not sure if this is the best way but it works for me.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SAS Drive identification LEDs
On 03/28/12 12:40, Fred Liu wrote: >> Shouldn't imagine so... I'm using a set of 4x four-bay Chenbro >> 80H10321513C0 jobbies in a 4U box for a total of 16 disks. >> >> My original post showed me lighting up an identification LED by poking >> values at the backplane via the ses device, but the Areca utility seems >> to >> do it by poking the drives themselves - which is a much better solution >> and >> *should* be backplane-agnostic. > > Sounds very good! But what if the drive is thoroughly damaged? How would you identify such a drive on any other system? -- Sorry for the disclaimer... The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Critical Software Ltd. reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. Critical Software Ltd. registered in England, 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. This message has been scanned for security threats by iCritical. For further information, please visit www.icritical.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Floppy disks don't work with FreeBSD 9.0
On 28/03/2012 09:03, Mark Felder wrote: On Tue, 27 Mar 2012 16:48:26 -0500, Thomas Laus wrote: Could this be related to CAM system issues that shipped with FreeBSD 9.0 and were fixed in -STABLE? Like the CDROM issues? I'd probably test in -STABLE first. Unfortunately I don't have any floppy drives to test this with or I'd lend a hand. I can confirm that the floppy does work on my FreeBSD-9-Stable machine (csup'd about a week ago). Graham ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SAS Drive identification LEDs
On 03/28/12 06:11, Fred Liu wrote: > Does ARC-1320 card need specific backplane to work with to identify > HDD's position? Shouldn't imagine so... I'm using a set of 4x four-bay Chenbro 80H10321513C0 jobbies in a 4U box for a total of 16 disks. My original post showed me lighting up an identification LED by poking values at the backplane via the ses device, but the Areca utility seems to do it by poking the drives themselves - which is a much better solution and *should* be backplane-agnostic. -- Sorry for the below disclaimer The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Critical Software Ltd. reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. Critical Software Ltd. registered in England, 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. This message has been scanned for security threats by iCritical. For further information, please visit www.icritical.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
