a bit late, but fwiw -
I have 7.5 on an optiplex 990 on SSD, no issues. Not quite a 980, but I
honestly doubt that this matters given my experience on these boxes. (I also
have 7.5 on a 960, and have had it on a 955 and 945. There’s nothing special
about the Dells that I have and booting
On 2024-04-25, Chris Petrik wrote:
> Remember softraid isn't the same as hw raid and I will always chose hw over
> soft this includes zfs.
There are advantages and disadvantages for both. e.g. a software
setup with multiple disk controllers can, if there's support for data
error detec
> Hello,
>
> Remember softraid isn't the same as hw raid and I will always chose hw over
> soft this includes zfs.
>
> Chris
I am sorry, but what relevance does your personal preferences have
to anything regarding this issue?
FWIW, I have seen more than one example of
Hello,
Remember softraid isn't the same as hw raid and I will always chose hw over
soft this includes zfs.
Chris
Sent from Proton Mail Android
Original Message
On 4/25/24 3:14 PM, Martin wrote:
> > On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling
> On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote:
>
> > I checked, the softraid manual page already has an example installboot
> > invocation in EXAMPLES, which should be clear enough.
>
>
> Regardless, I've tweaked the wording a bit. Hopefully more
On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote:
> I checked, the softraid manual page already has an example installboot
> invocation in EXAMPLES, which should be clear enough.
Regardless, I've tweaked the wording a bit. Hopefully more clear now.
On Thu, Apr 25, 2024 at 03:27:29AM +, Martin wrote:
> I eventually found out what was going on.
>
> The FreeBSD boot problem was not related at all.
>
> Long story short and for future reference, installboot needs
> to be run on the softraid volume, NOT on the physical di
I eventually found out what was going on.
The FreeBSD boot problem was not related at all.
Long story short and for future reference, installboot needs
to be run on the softraid volume, NOT on the physical disk. And this
has to be repeated after a softraid volume rebuild in order for the new
> That seems... unusual. Do you have an (old) IDE compatibility option turned
> on in
> the BIOS? I would have expected it to attach via AHCI:
> sd0 at scsibus1 targ 2 lun 0:
On Tue, Apr 23, 2024 at 08:26:40PM -0500, Brian Conway wrote:
> > wd0 at pciide0 channel 0 drive 0:
>
> That seems... unusual. Do you have an (old) IDE compatibility option turned
> on in the BIOS? I would have expected it to attach via AHCI:
>
> sd0 at scsibus1 targ 2 lun 0:
>
On 2024-04-24, Brian Conway wrote:
>> wd0 at pciide0 channel 0 drive 0:
>
> That seems... unusual. Do you have an (old) IDE compatibility option turned
> on in the BIOS? I would have expected it to attach via AHCI:
Optiplex 980 is from ~2010, similar age to the HP N54L microserver etc.
Disks
> RAID replicates the data in the RAIDed area, yes?
>
> Do you have some reason to believe that the boot information (MBR, etc) is
> _inside_ the RAID area, because I do not believe that. Really feels like
> installboot needs to be run on this drive to, uh, install the proper boot
> info.
>
>
> wd0 at pciide0 channel 0 drive 0:
That seems... unusual. Do you have an (old) IDE compatibility option turned on
in the BIOS? I would have expected it to attach via AHCI:
sd0 at scsibus1 targ 2 lun 0: naa.5002538e304456ac
Brian Conway
On Tue, Apr 23, 2024 at 8:19 AM wrote:
> Also, if I boot from a USB stick, with only the new SSD attached, the
> softraid is registered as degraded (as the other old disk is missing), so
> it has been populated, and the partition is also marked with an asterisk
> for boot, but I
C.MP#82 amd64
>
> Don't know if your OptiPlex 980 is newer than mine.
I find it strange that this isn't working, but I have tried just going for a
standard OpenBSD install and also tested a standard FreeBSD install on two
different SSDs - ignoring my original softraid setup, but no matter wh
On Tue, Apr 23, 2024 at 09:08:26PM +, Martin wrote:
> Turns out this machine, for some reason, simply cannot boot of SSDs with
> neither OpenBSD or FreeBSD on the box. Only spinning drives work.
>
> It's an old Dell Inc. OptiPlex 980.
>
> I suspect there is some issue with the BIOS of the
Turns out this machine, for some reason, simply cannot boot of SSDs with
neither OpenBSD or FreeBSD on the box. Only spinning drives work.
It's an old Dell Inc. OptiPlex 980.
I suspect there is some issue with the BIOS of the machine and the BSD
bootloaders as Linux with GRUB works on SSDs.
Also, if I boot from a USB stick, with only the new SSD attached, the softraid
is registered as degraded (as the other old disk is missing), so it has been
populated, and the partition is also marked with an asterisk for boot, but I
still cannot boot from that drive.
> I suspect this error comes from your BIOS/UEFI rather than the OpenBSD
> boot loader. Did you check how boot drives are configured in firmware?
I already tested that by moving the new disk to another box and boot it from
that, unfortunately I get the same error.
On Tue, Apr 23, 2024 at 12:51:41AM +, i...@protonmail.com wrote:
> I have a softraid mirror setup with two old spinning disks. I have detached
> one of the disks from the mirror and attached a new SSD. I then wanted to
> rebuild the mirror, using one old spinning drive and th
I have a softraid mirror setup with two old spinning disks. I have detached one
of the disks from the mirror and attached a new SSD. I then wanted to rebuild
the mirror, using one old spinning drive and the new SSD, and then afterwards,
remove the old spinning drive and replace with yet another
I am practicing setting up RAID5 inside a virtual machine running
OpenBSD 7.5 in VMM on OpenBSD 7.4.
I created 3 disks sd0, sd1, sd2, and sd3, and 4 disk devices (the fourth to
represent the RAID array itself):
Welcome to the OpenBSD/amd64 7.5 installation program.
(I)nstall, (U)pgrade,
Please ignore, sibiria on IRC clarified to me that boot support is
limited to only RAID1, crypto, and RAID1c disciplines.
--
jrmu
IRCNow (https://ircnow.org)
On Tue, Apr 09, 2024 at 03:50:19PM -0700, jrmu wrote:
> I am practicing setting up RAID5 inside a virtual machine running
> OpenBSD 7.5
Hi misc,
I'm practicing data recovery scenarios with a RAID 1 array on softraid0.
optiplex# bioctl -i softraid0
Volume Status Size Device
softraid0 0 Online64022953984 sd0 RAID1
0 Online64022953984 0:0.0 noencl
1 Online
Hi,
On Friday, November 17th, 2023 at 08:26, D.A. wrote:
> What encryption algorithm does softraid?
According to the presentation titled "softraid(4) boot" by Stefan Sperling
at EuroBSDCon 2015, AES with 256-bit key(s) in XTS mode.
(You can check sys/dev/softraid_crypto.c
What encryption algorithm does softraid?
--
>
>> If you are on
>> sticks copy machine by three slots are also a solution.
>
> Running an OpenBSD system entirely from USB sticks, and using a copy machine
> to make backups is not a good suggestion for general usage.
Indeed, and also depends on their size.
> P.S. Daniele, please fix your
On Mon, Nov 13, 2023 at 10:15:30AM +0100, Daniele B. wrote:
> In few words, when the matter is saving the data of one 1 disk the best
> solution is adopt a backup strategy for that purpose.
Yes, this is true.
I answered the OPs direct question about how to create the raid mirror, but
that was
by three slots are also a solution.
Involving 1 more disk in raid 1 is never a good solution for different
reasons the most important one: against a disk failure you put at risk the
full raid set; then softraid is never running properly and never good for
your disk life beside slowing down your system
On Mon, Nov 13, 2023 at 02:05:34AM +0100, i...@tutanota.com wrote:
> Is that possible or does the first disk needs to be reformattet and
> repartitioned before adding a second disk?
You will need to copy your data elsewhere, then re-partition and
create the raid mirror, then copy your data back.
I have an OpenBSD box running with a single drive. I wanted to add a
second drive and then run the two in a softraid mirror in order for the
first disk to not be a single point of failure in the box.
Is that possible or does the first disk needs to be reformattet and
repartitioned before adding
Just a follow up on this for general interest.
I got boards made in Hong Kong from the design done by Tobias Schramm
generously made available on github. I received the board a few days
ago, I ordered then the nvme 2230 to test and received it today and here
we are.
The following tests are
On Mon, Jun 5, 2023 at 3:07 AM Nick Holland wrote:
>
> =-
> PREVIOUS=(find previous backup)
> TODAY=(today's date)
> OLDEST=(find oldest backup in the set)
> REMOTE=(machine we are backing up)
>
> # remove oldest backup
> rm -r $OLDEST &
>
> mkdir $TODAY
>
> # make new
Hiya.
tl;dr version: multiple machines with softraid RAID1 & softdep have
file systems freeze when doing lots of I/O, possibly involving
adding and removing links from the same files at the same time.
Workaround found.
Need help finding better diagnostic information.
long ver
ulations, part of data must be encrypted;
>> regulations also dictate that I have to be able to destroy the encryption
>> keys.
[...]
>> To "destroy" the keys I think it could be sufficient to use dd and overwrite
>> the first megabyte of the softraid chunk with random
I have to be able to destroy the encryption
> keys.
>
> So, I want to split data into multiple partitions, mounted read-only (it's
> "cold" data, there's no point in mounting rw); one of them, of about 50GB,
> will be a chunk dedicated to softraid. The volume will be assemble
, mounted read-only (it's
"cold" data, there's no point in mounting rw); one of them, of about 50GB, will
be a chunk dedicated to softraid. The volume will be assembled by hand and the
on-disk encryption key will be encrypted with a user supplied password (right,
regulations).
If I
.2 drives in this small box.
>
> https://github.com/pcengines/apu2-documentation/blob/master/docs/APU_mPCIe_capabilities.md
>
> Then may be I can run softraid on my OpenBSD APU2.
>
> I would very much appreciated if anyone happen to know the model that
> they us
Then may be I can run softraid on my OpenBSD APU2.
I would very much appreciated if anyone happen to know the model that
they use or know that is working.
Amazon have a very long list, but the description isn't to useful and
describe for use with USB, or wireless card and there is so many
Thanks man. Will use it.
On 2023-05-01 11:39, Thomas Bohl wrote:
Hi
In a server with an encrypted root - server boots with key in USB
stick, not passphrase.
Can I remove the USB stick with the key, after the server is up and
running?
Yes
Will I have any problems doing that?
No.
Hi
In a server with an encrypted root - server boots with key in USB stick,
not passphrase.
Can I remove the USB stick with the key, after the server is up and
running?
Yes
Will I have any problems doing that?
No. Though not at the moment, I used such a setup for years. Only
Hi misc,
In a server with an encrypted root - server boots with key in USB stick,
not passphrase.
Can I remove the USB stick with the key, after the server is up and
running? Will I have any problems doing that?
I know that in the case of a reboot, it will be necessary to go and
re-insert
then this very
>possibility helps at least to understand the point the OP was trying
>to make when starting this thread.
>
>Regards,
>Wolfgang
I wasn't going to say anything more, but after reading this I figured
I ought to at least suggest an update to the documentation. Since I'm
defin
On Sat, Jan 07, 2023 at 02:33:31PM +, Nathan Carruth wrote:
The way I see it, this depends on one's use case.
There certainly are cases where it is important to be able
to irrevocably destroy all data in an instant. But there are
also use cases where one is only interested in making sure
The way I see it, this depends on one's use case.
There certainly are cases where it is important to be able
to irrevocably destroy all data in an instant. But there are
also use cases where one is only interested in making sure
that the average person couldn’t access one’s data if one lost
one’s
Nathan Carruth writes:
> permanently and irrevocably destroy all data on your entire disk”.
This is a feature. More so, it's the very point in an encrypted
filesystem. If you haven't planned for this failure scenario then
what are you doing using a device which *by design* can irrevocably
trash
) at the start of the original partition. See [relevant source
> file] for details. If this information should become corrupted, the
> softraid(4)
> volume will become unusable.”
>
> Thanks!
> Nathan
>
> PS I have been using OpenBSD since 2010. I like it very much in many
&
this would be useful:
>
> “Note: bioctl(8) writes header information (such as salt values for
> crypto volumes) at the start of the original partition. See [relevant source
> file] for details. If this information should become corrupted, the
> softraid(4)
> volume will become unusable
he partition, it's stored 16 blocks (8k) into the partition
>and for the current version of softraid it's 64 blocks (32k) long.
>
>But it's useless without the data so unless you are doing unsupported things
>like poking at the softraid partition size, etc, and want to make a backup
&
Namaste Stuart, Tobias,
> Sent: Thursday, January 05, 2023 at 4:58 PM
> From: "Tobias Fiebig"
> To: misc@openbsd.org
> Subject: Re: Probable error in softraid(4) documentation
>
> Heho,
>
> On Wed, 2023-01-04 at 00:04 +, Stuart Henderson wrote:
> &
Heho,
On Wed, 2023-01-04 at 00:04 +, Stuart Henderson wrote:
> stacking would refer to creating one softraid (say a raid1 mirror)
> and then creating a separate softraid device (say a crypto volume)
> using the first softraid disk as a component.
Incidentally, if you happen to hav
d 16 blocks (8k) into the partition
and for the current version of softraid it's 64 blocks (32k) long.
But it's useless without the data so unless you are doing unsupported things
like poking at the softraid partition size, etc, and want to make a backup
before doing that then I don't see how it helps y
am curious what you mean by this:
>
> ??? Backing up, restoring or
> otherwise messing with the softraid metadata without using the standard tools
> is an advanced subject???
>
> as far as I know there aren???t any standard tools for doing any
> of this? If there is, it i
Thank you for your response (apologies that I just saw this).
I will have a look at the file you mentioned.
I am curious what you mean by this:
“ Backing up, restoring or
otherwise messing with the softraid metadata without using the standard tools
is an advanced subject”
as far as I know
tores if
needed, restoring individual files, etc. You can also use e.g. dump
or tar, piping the output through an encryption tool before storing.
- backup the whole disk partition/s e.g. with dd.
This might be a bit impractical as to keep things consistent I think
you'll want to unmount, detach the
/s e.g. with dd.
This might be a bit impractical as to keep things consistent I think
you'll want to unmount, detach the softraid device, backup, reattach,
remount. Restoration is much more fiddly too. Additionally this isn't
designed as an archival format; it would seem that it will be much more
fragile.
On Thu, Jan 05, 2023 at 05:13:05AM +, Nathan Carruth wrote:
> Perhaps I should have clarified my use case. I have data which
> is potentially legally privileged and which I also cannot afford
> to lose. Thus an unencrypted backup is out of the question, and
> my first thought was to use
On Thu, Jan 05, 2023 at 05:13:05AM +, Nathan Carruth wrote:
> I presume that OpenBSD also writes on-disk metadata of the
> same sort somewhere. Where?
Look at /usr/src/sys/dev/softraidvar.h.
The structures that contain the softraid metadata are defined there. There is
general so
this out of
the source code but I don’t have time right now.
As it stands, the documentation gives no hint that softraid
crypto gives any additional risk of data loss. If there are in
fact e.g. salt values written in an unknown location on the
disk, whose loss renders THE ENTIRE DISK cryptographically
g drives...and I'm not sure why, I suspect there's a
good reason. But fdisk output is NOT there, and I'd rather
prefer it be there too on fdisk platforms).
Nick.
Thanks!
Nathan
Does a softraid(4) crypto volume require metadata backup? (I am
running amd64 OpenBSD 6.9 if it is relevant, will proba
On 2023-01-03, Puru Shartha wrote:
> Namaste misc,
>
> The softraid(4) documentation states the following in the CAVEAT
> section [1]:
>
> "Stacking disciplines (CRYPTO on top of RAID 1, for example) is not
> supported at this time."
>
> Based on my limited
Namaste misc,
The softraid(4) documentation states the following in the CAVEAT
section [1]:
"Stacking disciplines (CRYPTO on top of RAID 1, for example) is not
supported at this time."
Based on my limited understanding, RAID 1C seems to allow the above.
Also, Dhanyavaad Stefan f
.
Thanks!
Nathan
> Does a softraid(4) crypto volume require metadata backup? (I am
> running amd64 OpenBSD 6.9 if it is relevant, will probably
> upgrade in the next few months.)
>
> I understand FreeBSD GELI (e.g.) requires such a backup to protect
> against crypto-related metadata co
On 1/2/23 22:22, Nathan Carruth wrote:
Does a softraid(4) crypto volume require metadata backup? (I am
running amd64 OpenBSD 6.9 if it is relevant, will probably
upgrade in the next few months.)
I understand FreeBSD GELI (e.g.) requires such a backup to protect
against crypto-related metadata
Does a softraid(4) crypto volume require metadata backup? (I am
running amd64 OpenBSD 6.9 if it is relevant, will probably
upgrade in the next few months.)
I understand FreeBSD GELI (e.g.) requires such a backup to protect
against crypto-related metadata corruption rendering the encrypted
volume
of the entire disk (rsd3c), rather than trying to read just the one
sector. Remember, there's an offset between the sectors of sd5 (the
softraid drive) and sd2 & sd3 where sd5 lives. So I'd kinda expect your
sd3 check to pass because you missed the bad spot, and I'd expect your
sd5 check to pass bec
I have raid1 volume (one of two on PC) with 2 disks.
# disklabel sd5
# /dev/rsd5c:
type: SCSI
disk: SCSI disk
label: SR RAID 1
duid: 7a03a84165b3d165
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 243201
total sectors: 3907028640
boundstart: 0
On 9/7/22 09:05, Erling Westenvik wrote:
Hello,
...
My question is: Should I let swap be outside RAID altogether? Like
"directly" on the physical disks as in sd0b and sd1b? I mean, why have
softraid waste CPU cycles making swap content (if any) redundant? What
do you people do?
> (Follow up question as for swap sizing: In the age of 32+ GB RAM, do
> you people really follow the recommendations on having swap at least
> twice the amount of RAM? I'm hoping for 72GB RAM and that would steal
> 144GB of my 525GB disks, something that seems ridiculous.)
That advice is
Hello,
I'm making the transition from SATA to SSD. A late bloomer.. My setup
for years have been a semi-FDE softraid on two physical disks, sd0 and
sd1, where the sd0a and sd1a chunks make up a RAID 1 volume sd2. sd2
contains an unencrypted root partition, sd2a, and the remainder
On 5/6/22 9:03 AM, Proton wrote:
Hi,
I'm using softraid 1C on my remote dedicated server, built on two NVMe disks.
It works really well from performance perspective and provide some data
protection,
but there is no way to check device health status because SMART doesn’t work.
I guess bioctl
On 2022-04-03, Nick Holland wrote:
> If you are going to find your data, you need to recreate the disklabel
> partitions exactly as they were on the encrypted FFS from OpenBSD.
> scan_ffs(8) may help.
OoenBSD's scan_ffs only supports FFS1, the OS defaults to FFS2.
Am 02.04.22 18:56 schrieb harold:
> Hello,
>
> Today I take a little breath to try to get some help about a little problem
> I have since weeks.
> I lost data due to misunderstanding of formatting rdsc1 softraid partition
> on openbsd.
>
> I tell you my little story i
Well, I am very surprised to see an email going into OpenBSD vs all on
the list, and even more surprised to see it's author it a good veteran
of OpenBSD.
But I guess things change with time ...
Yes, trying multiboot without backups is a real problem calling. Most
of the email is pure hype. Not a
rt openbsd and mount back my
softraid partition. It asks for my
password, recognize it. Slice looks empty. Df shows only few kb files.
Data is gone. No backup.
Two points :
*looks like it’s not possible to reinsall openbsd without formatting
everything. A bit sad, where it’s
not said, and I car
Den sön 3 apr. 2022 kl 15:58 skrev harold :
For anyone else that wants to experiment with dual/triple-booting:
> I lost data due to misunderstanding
> I tell you more :
> a/ I had windows and linux mint 18 (gpt/efi)
> b/ I add openbsd to these double systems. Now three. Grub2 manages it.
[
Hello,
Today I take a little breath to try to get some help about a little
problem I have since weeks.
I lost data due to misunderstanding of formatting rdsc1 softraid
partition on openbsd.
I tell you my little story in the attached document, because I lost
data and would really like
On 4/2/22 12:56 PM, harold wrote:
...
I tell you my little story in the attached document,
Just a thought, but you might want to reconsider your means of telling
your story.
For example, I am not in the habit of opening unsolicited PDF documents...
Nick.
Hello,
Today I take a little breath to try to get some help about a little
problem I have since weeks.
I lost data due to misunderstanding of formatting rdsc1 softraid
partition on openbsd.
I tell you my little story in the attached document, because I lost
data and would really like
rypt disk before the installation of OpenBSD 7.0
> > according to the instructions here
> > https://www.openbsd.org/faq/faq14.html#softraid and managed to mess it.
> >
> > I have performed
> >
> > # cd /dev && sh MAKEDEV sd0
> > # fdisk -iy -g -
art over from scratch (which I agree with others, this
would be a good starting point), I'd just suggest zeroing the first 1MB
of the physical disk. That will clear all OpenBSD structures from the
physical disk, the softraid encrypted disk, and any (important) evidence
there was a softraid disk t
On Fri, Mar 25, 2022 at 10:28:55AM +0100, soko.tica wrote:
> Hello list,
>
> I have tried to encrypt disk before the installation of OpenBSD 7.0
> according to the instructions here
> https://www.openbsd.org/faq/faq14.html#softraid and managed to mess it.
First of all, if
Hello list,
I have tried to encrypt disk before the installation of OpenBSD 7.0
according to the instructions here
https://www.openbsd.org/faq/faq14.html#softraid and managed to mess it.
I have performed
# cd /dev && sh MAKEDEV sd0
# fdisk -iy -g -b 960 sd0
# disklabel -E sd0
Labe
ase the header gets corrupted somehow.
Neither the manpages softraid(4), bioctl(8) nor a google search mention
anything like that. Is there a reason why this wouldn't be necessary on
OpenBSD or did I just not read the documentation thoroughly enough?
Thanks in advance.
Best regards,
Alexander
one left.
So, I can attach only one of this 4 tb drives at the same time.
I think, maybe I can attach new 4 tb drive to old raid as a third
volume, wait for it "repair",
Unfortunately, unless something changed when I wasn't looking, you can't
change the number of drives in a softraid R
of this 4 tb drives at the same time.
I think, maybe I can attach new 4 tb drive to old raid as a third
volume, wait for it "repair",
Unfortunately, unless something changed when I wasn't looking, you can't
change the number of drives in a softraid RAID1 after creation. I really
wish
27.10.2021 20:41, cho...@jtan.com пишет:
It's easier by far not to muck about trying to resize partitions.
If you can mount each drive (old and new) in an operating system
that isn't using them then that's your best bet and that's not so
hard to arrange. Mount the old partition structure in
It's easier by far not to muck about trying to resize partitions.
If you can mount each drive (old and new) in an operating system
that isn't using them then that's your best bet and that's not so
hard to arrange. Mount the old partition structure in /old, create
new larger partitions on the new
Hello misc!
I want to replace my two 2TB hdd, joined in raid1.
I have two 4TB drives, and I want to replace smaller drives with them.
it wouldn't be a problem, if i had some spare sata ports, but in my pc i
have only one left.
So, I can attach only one of this 4 tb drives at the same time.
200, xavie...@mailoo.org wrote:
> Hello, There's a strange write speed bounce behavior on my SATA
> softraid
> RAID1 SSD (Crucial BX500 480GB 3D NAND). Sequential writes starts
> high
> (~450MB/s with dd and a bs of 1M) then after about 30s to 1:30 minute
> it
> falls to a low ~7MB/s f
d
> > Device has enabled the following command sets/features:
> > NOP command
> > READ BUFFER command
> > WRITE BUFFER command
> > Host Protected Area feature set
> > Read look-ahead
> > Write cache
> >
All right, thanks for pointing out the details and the procedure, seems
legit secfreeze is issued by default.
On Thu, 2021-06-10 at 07:08 -0700, Bryan Linton wrote:
> On 2021-06-10 11:49:59, Xavier Sanchez wrote:
> >
> > Read somewhere that issuing a security erase could also help. So I
> >
>> The Crucial BX500 SSD uses SMR technology, which is best used for
>> infrequent-write applications.
>> For general-purpose, and especially NAS, applications, CMR technology should
>> be used.
>
> hmm, does SMR stand for something other than "shingled magnetic recording"
> related to
On 2021-06-10, Kent Watsen wrote:
> The Crucial BX500 SSD uses SMR technology, which is best used for
> infrequent-write applications.
> For general-purpose, and especially NAS, applications, CMR technology should
> be used.
hmm, does SMR stand for something other than "shingled magnetic
On 2021-06-10 11:49:59, Xavier Sanchez wrote:
>
> Read somewhere that issuing a security erase could also help. So I
> tried issuing the following:
>
> # atactl sd0c secsetpass user high
> User password:
> Retype user password:
>
t;Flush Cache Ext command
>Flush Cache command
>48bit address feature set
>DOWNLOAD MICROCODE command
>
>
>> On Wed, 2021-06-09 at 03:45 +0200, xavie...@mailoo.org wrote:
>> Hello, There's a strange write speed bounce behavior on my SA
feature set
Flush Cache Ext command
Flush Cache command
48bit address feature set
DOWNLOAD MICROCODE command
On Wed, 2021-06-09 at 03:45 +0200, xavie...@mailoo.org wrote:
> Hello, There's a strange write speed bounce behavior on my SATA
> softraid
> RAID1 SSD
Hello, There's a strange write speed bounce behavior on my SATA softraid
RAID1 SSD (Crucial BX500 480GB 3D NAND). Sequential writes starts high
(~450MB/s with dd and a bs of 1M) then after about 30s to 1:30 minute it
falls to a low ~7MB/s for one minute, then bounce back to the high speed
of 450MB
On Wed, Apr 28, 2021 at 04:38:35PM +0800, Fung wrote:
> OpenBSD 6.9 RAID 1C (encrypted raid1) softraid discipline can't boot
>
> OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT 2021
>
> one disk, shell create RAID CRYPTO, install system ok, boot ok
> two disk, s
OpenBSD 6.9 RAID 1C (encrypted raid1) softraid discipline can't boot
OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT 2021
one disk, shell create RAID CRYPTO, install system ok, boot ok
two disk, shell create RAID 1, install system ok, boot ok
two disk, shell create RAID 1C ok, install
1 - 100 of 1184 matches
Mail list logo
