Date: Fri, 28 Feb 2020 11:14:00 -0300 From: Mario Olofo <mario.olofo@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Running FreeBSD on M.2 SSD Message-ID: <CAP4Gn9CVRmWuo4VNOikEoyfRcVurjEMPj63DWjMY1ezrAgt_EQ@mail.gmail.com> In-Reply-To: <5127f890-3e97-4982-1e09-3f9e53ecf6aa@nomadlogic.org> References: <CAP4Gn9DbdzSMbj=xn3E4TMRWzs-WY%2Bun2Rzd9Dt3PUeDL%2BYtpA@mail.gmail.com> <20200224144602.GA64065@phouka1.phouka.net> <CAP4Gn9DYui-x_wsDN3TUMd7cDPB%2BTSfRX3TL5DAa=8a1=eRGxQ@mail.gmail.com> <437a5eae-03c8-737d-48bf-39e2e9163d6d@nomadlogic.org> <CAP4Gn9Cy1w=ftw5QrdCFhWOQ_TaOOK=Wj2NGDC6R81fGPPAB6w@mail.gmail.com> <81ef514d-2575-e9e2-136b-dc79d1c62d74@nomadlogic.org> <CAP4Gn9AqK0BEmWhJ%2BqPqHcqN__GYf6tyonW6dwnvRqf-a2_www@mail.gmail.com> <5127f890-3e97-4982-1e09-3f9e53ecf6aa@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks! The only thing that I didn't checked was the questions of Theron, about misaligned data. The layout of the disk is as follows: Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores Unidades: setor de 1 * 512 =3D 512 bytes Tamanho de setor (l=C3=B3gico/f=C3=ADsico): 512 bytes / 512 bytes Tamanho E/S (m=C3=ADnimo/=C3=B3timo): 512 bytes / 512 bytes Tipo de r=C3=B3tulo do disco: gpt Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A Dispositivo In=C3=ADcio Fim Setores Tamanho Tipo /dev/sdb1 2048 1023999 1021952 499M Windows ambiente de recupera=C3=A7=C3=A3o /dev/sdb2 1024000 1228799 204800 100M Sistema EFI /dev/sdb3 1228800 1261567 32768 16M Microsoft reservado /dev/sdb4 1261568 532482047 531220480 253,3G Microsoft dados b=C3=A1si= co /dev/sdb5 532482048 549257215 16775168 8G FreeBSD ZFS /dev/sdb6 549257216 937719807 388462592 185,2G Linux sistema de arquivos The zfsroot was configured automatically by the installer, so I think that it align the volume automaticaly right? Mario Em sex., 28 de fev. de 2020 =C3=A0s 03:04, Pete Wright <pete@nomadlogic.org= > escreveu: > > > On 2020-02-27 20:44, Mario Olofo wrote: > > Thanks for the update. > > > > May you share what quirks was detected for your card and firmware to > > see if it matches mine? > > The only way I was able to run FreeBSD 12-STABLE on the SSD was using > > the suggested sysctl vfs.zfs.trim.enabled=3D0 > > Maybe the problem really is a combination of factors, for the person > > that filed a bug on bugzilla the fix was setting the quirks 4k and > > broken_trim, but for me the real block size is 512bytes and only > > setting the flag broken_trim didn't help... > > > This is a default install off of the latest 12.1-STABLE snapshot, no > special loader or sysctl knobs used. dmesg doesn't show anything > interesting: > > $ dmesg|grep ada > ses0: pass0,ada0 in 'Slot 00', SATA Slot: scbus0 target 0 > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: <WDC WDS480G2G0B-00EPW0 UK450000> ACS-2 ATA SATA 3.x device > ada0: Serial Number 185243800880 > ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada0: Command Queueing enabled > ada0: 457872MB (937721856 512 byte sectors) > GEOM_ELI: Device ada0p4.eli created. > > here's the output of sysctl: > $ sysctl kern.cam.ada > kern.cam.ada.0.sort_io_queue: 0 > kern.cam.ada.0.max_seq_zones: 0 > kern.cam.ada.0.optimal_nonseq_zones: 0 > kern.cam.ada.0.optimal_seq_zones: 0 > kern.cam.ada.0.zone_support: None > kern.cam.ada.0.zone_mode: Not Zoned > kern.cam.ada.0.rotating: 0 > kern.cam.ada.0.unmapped_io: 1 > kern.cam.ada.0.write_cache: -1 > kern.cam.ada.0.read_ahead: -1 > kern.cam.ada.0.delete_method: DSM_TRIM > kern.cam.ada.write_cache: 1 > kern.cam.ada.read_ahead: 1 > kern.cam.ada.spindown_suspend: 1 > kern.cam.ada.spindown_shutdown: 1 > kern.cam.ada.send_ordered: 1 > kern.cam.ada.default_timeout: 30 > kern.cam.ada.retry_count: 4 > > cheers, > -pete > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP4Gn9CVRmWuo4VNOikEoyfRcVurjEMPj63DWjMY1ezrAgt_EQ>