Re: Mounting NetBSD partition on voidlinux

[Sagar Acharya <sagaracharya%tutanota.com@localhost>]

There is buffer overflow. I just don't get how recovery software like safecopy are victim to this issue. They should sanitize the data before taking an input right? After reading 7% of drive, buffer overflow is detected and safecopy terminates. How do I correct this?

They should treat the input data as untrusted. Something has been messed up bad!
I used the command

$safecopy /dev/sdc2 ~Desktop/foo -f 1* -r 1 -R 8 -Z 2*** buffer overflow detected ***: terminated
Aborted

I need something to repair this ufs2 partition.
Thanking you
Sagar Acharya
https://humaaraartha.in



22 Jun 2023, 13:58 by sagaracharya%tutanota.com@localhost:

> $ smartctl -a -T permissive /dev/sd0a
>
>> scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
>> >> Terminate command early due to bad response to IEC mode page
>>
> === START OF READ SMART DATA SECTION ===
> Current Drive Temperature: 0C
> Drive Trip Temperature: 0C
>
> Error Counter logging not supported
>
> Device does not support Self Test Logging
>
>
>
> Is there some program which can straight up fetch data from raw hex on disk like it appears in hexedit?
>
> Thanking you
> Sagar Acharya
> https://humaaraartha.in
>
>
>
> 22 Jun 2023, 01:32 by sagaracharya%tutanota.com@localhost:
>
>> 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 due to bad response to IEC mode page
>>> A mandatory SMART command failed: exiting.
>>>
>>
>> Thanking you
>> Sagar Acharya
>> https://humaaraartha.in
>>
>>
>>
>> 22 Jun 2023, 01:18 by martin%duskware.de@localhost:
>>
>>> On Wed, Jun 21, 2023 at 09:38:47PM +0200, Sagar Acharya wrote:
>>>
>>>> I did
>>>> dkctl sd0 addwedge testwedge 34 500 ffs
>>>>
>>>
>>> And what did it say? Usually it tells you what dkN device it created.
>>>
>>>> Now
>>>>
>>>> mount /dev/sd0a /mnt shows
>>>>
>>>> No match for 'sd0a': No such process
>>>>
>>>
>>> The wedge you created collides/overlaps with sd0a and you can not access
>>> the same sectors via two paths.
>>>
>>> But as I said, creating a wedge for a NetBSD disk in this case makes no
>>> sense. At best it will be identical to sd0a or some other partition, and
>>> give you the same results as using that partition.
>>>
>>> Martin
>>>
>
>