>>> On Sun, Nov 14, 2021 at 10:40:28PM +0100, na...@poczta.fm wrote:
>>> Hi misc@,
>>>
>>> While testing the U-blox MPCI-L210 LTE modem on OpenBSD -current
>>> (the modem is attached as a cdce(4) device, the router mode is enabled;
>>> other modes are also available), I noticed that the
Hey Georg,
The configs look ok to me. The error message and your description
sound like you might have forgotten to copy the certificate private
keys to /etc/iked/private/local.key
On Wed, Dec 01, 2021 at 08:50:58PM +0100, Georg Pfuetzenreuter wrote:
> Hello,
>
> I try to connect two OpenBSD
On Tue, Nov 30, 2021 at 11:11:03PM -0700, Theo de Raadt wrote:
> I am dissapointed to see "long answers" to "short spurious claims".
>
> Nick, your long mail didn't help anything.
>
> Chris, your report sucks. Use sendbug and file a bug report with no
> details missing. Not one user has
On Wed, Dec 01, 2021 at 01:39:39PM +0530, Sandeep Gupta wrote:
> Hello,
> All partitions except for /dev/rsd1c and /dev/rsd1i are clean.
> For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG".
> For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY".
If that's the case, you are probably
Sandeep, go ahead reformat your disk. Do keep in mind the structure of
a BSD disk though
a partition - is usually /
b partition - is usually swap
c partition - is always the entire disk including a, and b,
and it goes on.../var, /usr, /usr/local, /home etc etc
Best Regards,
-peter
On
On Wed, Dec 01, 2021 at 05:49:06PM +0530, Sandeep Gupta wrote:
> Not sure why not. It seems the rsd1c is where the superblock is. Also
Each filesystem has it's own superblock, residing at the start of
its partition.
c partitions are a way to refer to the whole disk and do not have a
Not sure why not. It seems the rsd1c is where the superblock is. Also
there is no other
mechanism to refer to the whole disk. I guess it's time to format the disk.
On Wed, Dec 1, 2021 at 4:20 PM Janne Johansson wrote:
>
> Den ons 1 dec. 2021 kl 11:09 skrev Sandeep Gupta :
> > @Peter, @Janne:
Den ons 1 dec. 2021 kl 11:09 skrev Sandeep Gupta :
> @Peter, @Janne: Thanks for the infos. Newfs seemed promising but it
> seems like the disk is beyond repair :(.
> I did newfs -N and got quite a few location of superblocks:
> Then I tried
> fsck_ffs -b #blockid /dev/rsd1c
You should *NOT* newfs
@Peter, @Janne: Thanks for the infos. Newfs seemed promising but it
seems like the disk is beyond repair :(.
I did newfs -N and got quite a few location of superblocks:
Then I tried
fsck_ffs -b #blockid /dev/rsd1c
No matter which blockid i tried, it always gave the same BAD SUPER
BLOCK: MAGIC
On Wed, Dec 1, 2021 at 4:56 AM Nick Holland wrote:
> And yeah, he really wants you to UNDERSTAND what you are doing.
> Total jerk, I know.
I got confused by the MAKEDEV, thinking I have to create a required disk.
In fact, using one of the disks in hw.disknames worked as expected.
> The obvious
Den ons 1 dec. 2021 kl 09:12 skrev Sandeep Gupta :
> I am running OpenBSD 7.0 on RPi4. I accidentally removed the usb
> cable connecting the sata ssd to the RPi4.
> Well OpenBSD froze and upon reboot I got the very comforting
> Synchronous Exception message.
> Thankfully, I have another RPi4
On 2021/12/01 02:05, Alexander wrote:
> On 2021/11/30 8:14, Stuart Henderson wrote:
> > On 2021-11-29, Amit Kulkarni wrote:
> > > On Sun, Nov 28, 2021 at 5:17 PM Alexander wrote:
> > >> Just to gauge what to expect from this and whether I did this wrong:
> > >> After configuring
Hello,
I am running OpenBSD 7.0 on RPi4. I accidentally removed the usb
cable connecting the sata ssd to the RPi4.
Well OpenBSD froze and upon reboot I got the very comforting
Synchronous Exception message.
Thankfully, I have another RPi4 running OpenBSD. I can mount the
corrupted disk ( did
13 matches
Mail list logo