I did the second backup again and reattached the disk to my system, the
result was like that:
https://5md.at/l/obcons2 (disk attached but CRC error follows)
But I can mount it correctly.
So I decide to try changing drive enclosure, from as a simple
as not powered Orico 2.5'' to a powered Orico
Stuart Henderson :
> the duid is in the disklabel. if you clone a disk to another, you will clone
> the duid too.
> (it can be edited with disklabel -e).
Beside the useful clarification more than one is elaborating
why we should live with clonable uids?
However, clonable uids come really in h
On 2023-03-25, Jan Stary wrote:
>> and there is a problem in OpenBSD caused by the same UID of the two disks.
>
> 1. Guess what the letters U I D stand for.
> 2. Don't use two disk with the same uid.
the duid is in the disklabel. if you clone a disk to another, you will clone
the duid too.
(it c
>
>> a slight different console output:
>> https://5md.at/l/obcons1
>
> Don't do this. Console output is text - put it into the email,
> don't make people go to a web page to read console output.
Sincerely, I need an hack for copy text from xfce console...
>> and there is a problem in OpenBSD
On Mar 24 17:47:28, my2...@aol.com wrote:
> a slight different console output:
> https://5md.at/l/obcons1
Don't do this. Console output is text - put it into the email,
don't make people go to a web page to read console output.
> I expect there is problem on that disk.
Obviously.
> and there is
Beyond the reporting problem of the disk in OpenBSD I'm going ahead with my
analysis.
I'm performing an H3 test and H5 test on the CRC disk (backup #2) by a copy
machine.
H3 test result is successful. I'm waiting for H5 test result and I am enough
curious.
It shouldnt be a problem of disk cap
Hi Jan,
Sorry for the missing clarifications on my settings.
>> Why would another disk have the same UID and how is that obvious?
I use hardware copy machines for all my storage devices, since 2012.
>> Your problem is a HW failure, not a clash of names.
What I mean is when I try to insert the
On Mar 24 04:34:42, my2...@aol.com wrote:
> sd1(umass0:1:0) Check Condition (error 0x70) on opcode 0x2a
>SENSE KEY: Aborted Command
> ASC/ASCQ: information Unit iuCRC Error Detected
>
> sd1 was the original disk which the second backup disk was copy from.
> And obviously the faulty sd3
Hello,
I just come from the following situation on 7.2, patched till
two days ago.
Lost some files I attached my second backup external disk to recover
them. And I couldn't see the disk, no error message, no advice from the
terminal. This disk should appear to me like sd3.
I then decided to e
9 matches
Mail list logo
