On 22.06.23 07:52, Matthias Petermann wrote:
On 21.06.23 19:54, Matthias Petermann wrote:
2>log.txt ssh user@srv-net -vvv doas /sbin/dump -X -h 0 -b 64 -0auf -
/data/119455aa-6ef8-49e0-b71a-9c87e84014cb > /mnt/test.dump
...just noticed another variation, this time client_loop: send
On 21.06.23 19:54, Matthias Petermann wrote:
2>log.txt ssh user@srv-net -vvv doas /sbin/dump -X -h 0 -b 64 -0auf -
/data/119455aa-6ef8-49e0-b71a-9c87e84014cb > /mnt/test.dump
...just noticed another variation, this time client_loop: send
disconnect occured:
Updating src tree:
P src/doc/3RDPARTY
P src/lib/libedit/libedit.pc
P src/usr.bin/make/cond.c
P src/usr.bin/make/parse.c
P src/usr.bin/make/unit-tests/dep-wildcards.mk
P src/usr.bin/make/unit-tests/directive-include-guard.exp
P src/usr.bin/make/unit-tests/directive-include-guard.mk
P
Date: 22 Jun 2023, 01:32
From: sagaracha...@tutanota.com
To: mar...@duskware.de
Subject: Re: Mounting NetBSD partition on voidlinux
> As Sir Dice said, I used smartctl -a and I got this
>
> scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
> >> Terminate command early
https://forums.freebsd.org/threads/fsck-floating-point-exception.80552/
This looks exactly like my current issue. Except that my sd card is 16GB in
size!
It is scary to see that unresolved even when the greatest of the great pros
'Sir Dice' is involved!
Thanking you
Sagar Acharya
On Wed, Jun 21, 2023 at 02:17:37PM +0200, Sagar Acharya wrote:
> I have no clue on the wedges thing.
>
> dmesg shows these errors while mounting.
>
> ufs: ufs_fill_super(): fragment size 0 is not a power of 2
> ufs: ufs_fill_super(): fragment size 8192 is too large
Linux's ufs driver is
On Wed, Jun 21, 2023 at 08:43:45PM +0200, Sagar Acharya wrote:
> $ dkctl sd0 listwedges
> /dev/rsd0: no wedges configured
>
> What are wedges? I get sectors which are 512 bytes long on physical disk.
With "dkctl sd0 addwedge " you can use arbitrary "partitions" on disk sd0
without modifying
On Wed, Jun 21, 2023 at 08:39:45PM +0200, Sagar Acharya wrote:
> I am on a NetBSD 10 install now after sabotaging my fully good alpine due to
> constraints of sd card. The memory card from which I want to retrieve data is
> mounted at sd0
>
> $ fsck_ffs /dev/sd0a
> /dev/rsd0a[1] Floating point
$ dkctl sd0 listwedges
/dev/rsd0: no wedges configured
What are wedges? I get sectors which are 512 bytes long on physical disk.
Thanking you
Sagar Acharya
https://humaaraartha.in
21 Jun 2023, 18:24 by mar...@duskware.de:
> On Wed, Jun 21, 2023 at 02:20:25PM +0200, Sagar Acharya wrote:
>
>>
I am on a NetBSD 10 install now after sabotaging my fully good alpine due to
constraints of sd card. The memory card from which I want to retrieve data is
mounted at sd0
$ fsck_ffs /dev/sd0a
/dev/rsd0a[1] Floating point exception (core dumped) fsck_ffs /dev/sd0a
$ mount /dev/sd0a /mnt
Hello,
On 21.06.23 11:22, RVP wrote:
On Wed, 21 Jun 2023, RVP wrote:
A `Broken pipe' from ssh means the RHS of the pipeline exited
prematurely.
Is what I said, but, I see that ssh ignores SIGPIPE (network I/O--duh!),
so that error message is even odder.
Do a `2>log.txt ssh -vvv ...' and
On Wed, Jun 21, 2023 at 02:20:25PM +0200, Sagar Acharya wrote:
> Also, linux doesn't have fsck_ffs and debian had support for ufs in ufsutils
> a long time ago.
>
> I highly recommend that for such cases you have a small standalone source
> which can be built for correcting such errors which
Hi,
On 21.06.23 14:20, Sagar Acharya wrote:
Also, linux doesn't have fsck_ffs and debian had support for ufs in ufsutils a
long time ago.
I highly recommend that for such cases you have a small standalone source which
can be built for correcting such errors which can perhaps have disklabel,
Also, linux doesn't have fsck_ffs and debian had support for ufs in ufsutils a
long time ago.
I highly recommend that for such cases you have a small standalone source which
can be built for correcting such errors which can perhaps have disklabel,
fsck_ffs, etc. A user can use it locally!
I have no clue on the wedges thing.
dmesg shows these errors while mounting.
ufs: ufs_fill_super(): fragment size 0 is not a power of 2
ufs: ufs_fill_super(): fragment size 8192 is too large
Thanking you
Sagar Acharya
https://humaaraartha.in
21 Jun 2023, 16:58 by m...@petermann-it.de:
> Hi,
Kindly cc,
I am not subscribed to mailing list.
Thanking you
Sagar Acharya
https://humaaraartha.in
21 Jun 2023, 15:42 by sagaracha...@tutanota.com:
> My NetBSD system has gotten corrupted. How do I mount my NetBSD partition on
> voidlinux?
>
> Is it UFS or FFS?
>
> Thanking you
> Sagar
Hi,
On 21.06.23 12:16, Martin Husemann wrote:
On Wed, Jun 21, 2023 at 12:12:35PM +0200, Sagar Acharya wrote:
My NetBSD system has gotten corrupted. How do I mount my NetBSD partition on
voidlinux?
The typical recovery doesn't involve any other OS. If your kernel
works and finds the /
r...@sdf.org (RVP) writes:
>I don't get that: there's no pipe there when you do `> file'. So how come
>a Broken pipe still?
It's the communication between ssh and sshd where ssh can no longer write
to a network connection closed by sshd. The problem is to find out why
the connection got closed.
On Wed, Jun 21, 2023 at 12:12:35PM +0200, Sagar Acharya wrote:
> My NetBSD system has gotten corrupted. How do I mount my NetBSD partition on
> voidlinux?
The typical recovery doesn't involve any other OS. If your kernel
works and finds the / partition you can "boot -sa" and select
/rescue/init
My NetBSD system has gotten corrupted. How do I mount my NetBSD partition on
voidlinux?
Is it UFS or FFS?
Thanking you
Sagar Acharya
https://humaaraartha.in
On Wed, 21 Jun 2023, RVP wrote:
A `Broken pipe' from ssh means the RHS of the pipeline exited prematurely.
Is what I said, but, I see that ssh ignores SIGPIPE (network I/O--duh!),
so that error message is even odder.
Do a `2>log.txt ssh -vvv ...' and post the `log.txt' file when you send
On Wed, 21 Jun 2023, Matthias Petermann wrote:
My mistake... the error message probably was slighty different but still
related to the ssh_client_loop.
Aah! ssh is stuffing errno in _many_ places, so it's definitely possible.
See, for example:
On Wed, 21 Jun 2023, Matthias Petermann wrote:
Before I had dd in place, I used a redirection > $dumpname which results in
the same kind of broken pipe issues. I just did verify this by repeating this
as an isolated test case.
I don't get that: there's no pipe there when you do `> file'.
On 21.06.23 10:22, RVP wrote:
On Wed, 21 Jun 2023, Matthias Petermann wrote:
Before I had dd in place, I used a redirection > $dumpname which
results in the same kind of broken pipe issues. I just did verify this
by repeating this as an isolated test case.
I don't get that: there's no
Hello,
On 21.06.23 09:31, RVP wrote:
On Tue, 20 Jun 2023, Matthias Petermann wrote:
problems. Since there is a bit more steam on the system, I get
irregular but predictable SSH connection disconnects (ssh client loop
send disconnect: Broken pipe). I have already tried all possible
On Tue, 20 Jun 2023, Matthias Petermann wrote:
problems. Since there is a bit more steam on the system, I get irregular but
predictable SSH connection disconnects (ssh client loop send disconnect:
Broken pipe). I have already tried all possible combinations of
ClientAliveInterval and
26 matches
Mail list logo
