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 identifica

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 d

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 Arec

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(

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[1mm

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

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

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

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 i

[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/bi

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

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 BI