On Wed, Nov 18, 2015 at 08:15:15AM -0800, Freddie Cash wrote:
> On Wed, Nov 18, 2015 at 2:25 AM, Slawa Olhovchenkov wrote:
>
> > On Mon, Nov 16, 2015 at 01:19:55PM -0800, Freddie Cash wrote:
> >
> > > On Mon, Nov 16, 2015 at 12:57 PM, Slawa Olhovchenkov
> >
On Wed, Nov 18, 2015 at 2:25 AM, Slawa Olhovchenkov wrote:
> On Mon, Nov 16, 2015 at 01:19:55PM -0800, Freddie Cash wrote:
>
> > On Mon, Nov 16, 2015 at 12:57 PM, Slawa Olhovchenkov
> wrote:
> > Did the original disk get labelled automatically? No, you had to
On Mon, Nov 16, 2015 at 01:19:55PM -0800, Freddie Cash wrote:
> On Mon, Nov 16, 2015 at 12:57 PM, Slawa Olhovchenkov wrote:
>
> > On Mon, Nov 16, 2015 at 11:40:12AM -0800, Freddie Cash wrote:
> >
> > > On Mon, Nov 16, 2015 at 11:36 AM, Kevin Oberman
> >
On Tue, Nov 17, 2015 at 12:08 AM, Patrick M. Hausen wrote:
> Hi, all,
>
> > Am 16.11.2015 um 22:19 schrieb Freddie Cash :
> >
> > You label the disks as they are added to the system the first time.
> That
> > way, you always know where each disk is located,
Hi, all,
> Am 16.11.2015 um 22:19 schrieb Freddie Cash :
>
> You label the disks as they are added to the system the first time. That
> way, you always know where each disk is located, and you only deal with the
> labels.
we do the same for obvious reasons. But I always
From what i remember its a control thing. If you have another layer below
zfs, be it software based or hardware based, zfs cant be sure what is going
on, therefore cant guarantee anything. This is quite a big thing when it
comes to data integrity which is a big reason to use zfs. I remember
I disagree, get the remote hands to copy the serial number to an easily
visible location on the drive when its in the enclosure. Then label the
drives with the serial number (or a compatible version of it). That way the
label is tied to the drive, and you dont have to rely on the remote hands
On Mon, Nov 16, 2015 at 11:40:12AM -0800, Freddie Cash wrote:
> On Mon, Nov 16, 2015 at 11:36 AM, Kevin Oberman wrote:
>
> > On Mon, Nov 16, 2015 at 1:00 AM, Borja Marcos wrote:
> >
> > >
> > > On Nov 14, 2015, at 3:31 PM, Gary Palmer wrote:
> > >
> > >
On Mon, Nov 16, 2015 at 1:00 AM, Borja Marcos wrote:
>
> On Nov 14, 2015, at 3:31 PM, Gary Palmer wrote:
>
> > You can do thinks in /boot/loader.conf to hard code bus and drive
> > assignments.
> >
> > e.g.
> >
> > hint.da.0.at="scbus0"
> > hint.da.0.target="19"
> >
On Mon, Nov 16, 2015 at 12:57 PM, Slawa Olhovchenkov wrote:
> On Mon, Nov 16, 2015 at 11:40:12AM -0800, Freddie Cash wrote:
>
> > On Mon, Nov 16, 2015 at 11:36 AM, Kevin Oberman
> wrote:
> > > As already mentioned, unless you are using zfs, use gpart to
On Mon, Nov 16, 2015 at 11:36 AM, Kevin Oberman wrote:
> On Mon, Nov 16, 2015 at 1:00 AM, Borja Marcos wrote:
>
> >
> > On Nov 14, 2015, at 3:31 PM, Gary Palmer wrote:
> >
> > > You can do thinks in /boot/loader.conf to hard code bus and drive
> > >
On Nov 14, 2015, at 3:31 PM, Gary Palmer wrote:
> You can do thinks in /boot/loader.conf to hard code bus and drive
> assignments.
>
> e.g.
>
> hint.da.0.at="scbus0"
> hint.da.0.target="19"
> hint.da.0.unit="0"
> hint.da.1.at="scbus0"
> hint.da.1.target="18"
> hint.da.1.unit="0"
Beware, the
On 12.11.2015 23:20 Royce Williams wrote:
> Firmware should match driver, e.g.:
>
> mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbs
>
>
> Some of this may help -- not yet updated for 10.2, but may still be useful:
>
>
On Sat, Nov 14, 2015 at 01:18:14PM +0100, Kai Gallasch wrote:
> On 12.11.2015 23:20 Royce Williams wrote:
> > Firmware should match driver, e.g.:
> >
> > mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbs
> >
> >
> > Some of this may help -- not yet updated for 10.2, but may still be useful:
> -Original Message-
> From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd-
> s...@freebsd.org] On Behalf Of Gary Palmer
> Sent: Saturday, November 14, 2015 7:31 AM
> To: Kai Gallasch
> Cc: freebsd-s...@freebsd.org; Royce Williams; freebsd-stable
> Subject
On Sat, Nov 14, 2015 at 01:18:14PM +0100, Kai Gallasch wrote:
> So now the drive stuck in the last drive bay is seen as da0 and the
> drive in the first drive bay as da11
>
> But: In the controller BIOS the scan order of the drives did not change
> at all with the new firmware! So the change is
Firmware should match driver, e.g.:
mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbs
Some of this may help -- not yet updated for 10.2, but may still be useful:
http://roycebits.blogspot.com/2015/01/freebsd-lsi-sas9211-8i-hba-firmware.html
Royce
On Thu, Nov 12, 2015 at 12:05 PM, Kai
> -Original Message-
> From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd-
> s...@freebsd.org] On Behalf Of Royce Williams
> Sent: Thursday, November 12, 2015 3:21 PM
> To: Kai Gallasch
> Cc: freebsd-s...@freebsd.org; freebsd-stable
> Subject: Re: LSI SAS2008
> -Original Message-
> From: Stephen Mcconnell [mailto:stephen.mcconn...@avagotech.com]
> Sent: Thursday, November 12, 2015 3:45 PM
> To: 'Royce Williams'; 'Kai Gallasch'
> Cc: 'freebsd-s...@freebsd.org'; 'freebsd-stable'
> Subject: RE: LSI SAS2008 mps driver preferre
19 matches
Mail list logo