Re: accidentally overwritten wrong drive with DD, please help
A word of warning: even multiple overwrites are not guaranteed to erase any kind of flash-based storage. This applies even to some spinning rust now that have intermediate flash storage caches on them (although those tend to be enterprise-level devices). SSD/NVME's made by a reputable manufacturer usually have a secure delete function, but there are cases where this doesn't work, or doesn't work entirely, etc.
Re: accidentally overwritten wrong drive with DD, please help
On 2024-06-24, Anon Loli wrote: > On Mon, Jun 24, 2024 at 07:36:57AM -0400, Steve Litt wrote: >> Anon Loli said on Sun, 23 Jun 2024 12:19:15 + >> >> >> >Okay, I've enabled the drive now, how do I approach this? >> >I want the drive that's receiving the data copy to be encrypted, and >> >> Encrypted? Man, you're getting too complicated for the situation. >> Priorities. Task 1 is to copy over the borked drive to a USB drive so >> you have a stable "go back to" point. Task 2 is to have a second drive >> to experiment on, safe in the knowledge that you can always restore >> from the copy from task 1. Encryption just makes it more likely you'll >> bork things again. >> >> >it'll have to be over ssh, so I'm assuming some combination of DD and >> >SCP? >> >> SSH and SCP? Say what? How bout a USB3 rotating drive? And NOT a >> Seagate. >> >> > >> >I've looked on the internet now, and it seems like dump/restore are >> >perfect for this (and even faster than dd?) >> >So maybe something like >> >`dump af /dev/sd3i | ssh receiving-computer "restore xf -"` >> >But where would the sd3i end up then and how? would it turn in a file, >> >or become a /dev/sd3i copy on the receiving computer? >> >If you don't respond, I'll search the internet and try to do it on my >> >own (for the 1st time) and possibly overwrite something again lol >> > >> >Would be great if I could find some great read about this >> > >> >> Personally, I think you're making this much harder than it has to be. >> If you care about those old photos, spend the money for enough USB hard >> drives, and don't get fancy until you have a copy of your files AND a >> backup of the copy of those files. Then you can treat the copy like a >> backup and copy them back. >> >> Seriously, priorities. Prioritize getting those files back, and don't >> let anything complicate that task. Don't skip steps. >> >> SteveT >> >> Steve Litt >> >> http://444domains.com >> > > I don't understand what's so complicated about DD, ssh/scp or encryption? > I'll have to find my USB adapter, this is going too slow over the network, > that > being said, I think that I mentioned the source drive being over 200GB in > size, > so why mention USB sticks? lol USB drive != "USB stick" (not that 200GB is much for a USB stick these days). (use bs=1m on the writing side to write in larger chunks if you're dd'ing to flash media or SMR HDD). > Encryption is a must, it's not just family photos, but even if it was, I'm > still not putting them on clear disk If you don't trust the machine you're attaching it to, you're screwed anyway. And some of the tools that might be able to help with recovery won't be much help with a softraid-encrypted disk. > I need to make a filesystem out of the backed-up copy if I understand > correctly, Turning it directly into a working filesystem is probably not going to happen. You need to try to extract what bits of data are still recoverable. Think more in terms of trying to find what valid files you can and copying them elsewhere. > Like what use is backing it up now and then making the filesystem on the same > drive and fucking up that entire drive? Yeah, you want to treat that copy as read-only, the same way you'd treat any drive you're trying to recover data from as read-only. If you're going to try and write anything to it, you'll then want _another_ copy to work on. -- Please keep replies on the mailing list.
Re: accidentally overwritten wrong drive with DD, please help
On Mon, 24 Jun 2024 19:29:52 +0100, Anon Loli wrote: > > Encryption is a must, it's not just family photos, but even if it was, I'm > still not putting them on clear disk > You may fill your disk, after you recover everything with random data. Couple of times. It removes everything. -- wbr, Kirill
Re: IPv6 ULA routing stops working after 20 hours or so
Am 23.06.2024 um 19:50 schrieb Thomas Bohl: The router doesn't have a valid NDP entry. It has a NDP entry for an address ifconfig says is deprecated. If I force the use of this deprecated address with "ping -I" the response are received. I have to verify if it always stops if pltime reaches zero. It doesn't always stop immediately if pltime reaches zero and a new temporary address is generated. Only sometimes. But in the long run it eventually will fail and never recover. It has to be a NDP problem. I'm not sure who is at fault. My guess would be the router, because its traces will start outputting a xx:xx:xx:xx:xx:xx mac address (that is not me anonymizing it): (fd00:172:17:174:d468:28ab:498e:5d0e is the new autoconf temporary address on the OpenBSD host.) [ND-CACHE] 2024/06/24 23:06:17,088 Devicetime: 2024/06/24 23:06:17,077[info] : ND state on interface HOST_O4 changed fe80::91:51ff:fe40:c93f iface HOST_O4 lladdr 02:91:51:40:c9:3f (BUNDLE-1,3) host DELAY src fe80::2a0:57ff:fe3a:ac77 [ND-CACHE] 2024/06/24 23:06:17,127 Devicetime: 2024/06/24 23:06:17,105[info] : outgoing packet on HOST_O4 target: fd00:172:17:174:d468:28ab:498e:5d0e, source: fe80::2a0:57ff:fe3a:ac77 fd00:172:17:174:d468:28ab:498e:5d0e iface HOST_O4 lladdr xx:xx:xx:xx:xx:xx host INIT src fe80::2a0:57ff:fe3a:ac77 [ND-CACHE] 2024/06/24 23:06:17,127 Devicetime: 2024/06/24 23:06:17,105[info] : ND state on interface HOST_O4 changed fd00:172:17:174:d468:28ab:498e:5d0e iface HOST_O4 lladdr xx:xx:xx:xx:xx:xx host INCOMPLETE src fe80::2a0:57ff:fe3a:ac77 [ND-CACHE] 2024/06/24 23:06:20,109 Devicetime: 2024/06/24 23:06:20,105[info] : ND state on interface HOST_O4 changed fd00:172:17:174:d468:28ab:498e:5d0e iface HOST_O4 lladdr xx:xx:xx:xx:xx:xx host UNREACHABLE src fe80::2a0:57ff:fe3a:ac77 I just don't get why Linux and Windows don't have the same problem. I try to collect more tcpdump and log-data.
route -n show blackhole routes
Folks, while reviewing nsh I was wondering how to improve show route commands... reviewing the man route man page, there doesnt seem to be a straight forward way of displaying blackhole routes without using route show |grep B for blackhole route show |grep R for Reject is there something Im missing, would I be better off improving route(8) rather than stringing commands together for NSH ? comment and feedback welcome -- Kindest regards, Tom Smyth.
Re: accidentally overwritten wrong drive with DD, please help
On Mon, Jun 24, 2024 at 12:34 PM Anon Loli wrote: > ... > Like what use is backing it up now and then making the filesystem on the > same > drive and fucking up that entire drive? > > backup now is so you can make different tests and still have somewhere to come back anything you do can further destroy the data
Re: accidentally overwritten wrong drive with DD, please help
On Mon, Jun 24, 2024 at 07:36:57AM -0400, Steve Litt wrote: > Anon Loli said on Sun, 23 Jun 2024 12:19:15 + > > > >Okay, I've enabled the drive now, how do I approach this? > >I want the drive that's receiving the data copy to be encrypted, and > > Encrypted? Man, you're getting too complicated for the situation. > Priorities. Task 1 is to copy over the borked drive to a USB drive so > you have a stable "go back to" point. Task 2 is to have a second drive > to experiment on, safe in the knowledge that you can always restore > from the copy from task 1. Encryption just makes it more likely you'll > bork things again. > > >it'll have to be over ssh, so I'm assuming some combination of DD and > >SCP? > > SSH and SCP? Say what? How bout a USB3 rotating drive? And NOT a > Seagate. > > > > >I've looked on the internet now, and it seems like dump/restore are > >perfect for this (and even faster than dd?) > >So maybe something like > >`dump af /dev/sd3i | ssh receiving-computer "restore xf -"` > >But where would the sd3i end up then and how? would it turn in a file, > >or become a /dev/sd3i copy on the receiving computer? > >If you don't respond, I'll search the internet and try to do it on my > >own (for the 1st time) and possibly overwrite something again lol > > > >Would be great if I could find some great read about this > > > > Personally, I think you're making this much harder than it has to be. > If you care about those old photos, spend the money for enough USB hard > drives, and don't get fancy until you have a copy of your files AND a > backup of the copy of those files. Then you can treat the copy like a > backup and copy them back. > > Seriously, priorities. Prioritize getting those files back, and don't > let anything complicate that task. Don't skip steps. > > SteveT > > Steve Litt > > http://444domains.com > I don't understand what's so complicated about DD, ssh/scp or encryption? I'll have to find my USB adapter, this is going too slow over the network, that being said, I think that I mentioned the source drive being over 200GB in size, so why mention USB sticks? lol Encryption is a must, it's not just family photos, but even if it was, I'm still not putting them on clear disk Now if you can't answer this that's fine, maybe someone else can.. if I they can't then I'll cry Question is: if I write to the raw crypto volume (the decrypted disk), everything should still be encrypted, right? I don't understand exactly how under the hood OpenBSD FDE works, but if I understand correctly, anything written to the crypto volume gets encrypted and what-not, and then stored to the drive encrypted, right? I need to make a filesystem out of the backed-up copy if I understand correctly, will it still work if 74M of it is overwritten? Because then I could maybe DD over the raw(/non-raw?) crypto volume and it should work? Like what use is backing it up now and then making the filesystem on the same drive and fucking up that entire drive?
OT: gnubook: a "social" dedicated to the opensource software
Hello, Just want to promote among this community too, gnubook https://gnubook.org an attempt for a social network dedicated to the opensource software. Gnubook will be base on Faceborg (like my own https://bsdload.com) for now and open to any fellow interested to talk and have a social presence about its opensource software. (Why the "gnubook" name? As an exemplification for a quick-to-type domain name, while just every software with its own license is very welcome...) Please don't mind to contact me to ask anything or to just manifest support. Kind regards, -Dan
Re: accidentally overwritten wrong drive with DD, please help
Anon Loli said on Sun, 23 Jun 2024 12:19:15 + >Okay, I've enabled the drive now, how do I approach this? >I want the drive that's receiving the data copy to be encrypted, and Encrypted? Man, you're getting too complicated for the situation. Priorities. Task 1 is to copy over the borked drive to a USB drive so you have a stable "go back to" point. Task 2 is to have a second drive to experiment on, safe in the knowledge that you can always restore from the copy from task 1. Encryption just makes it more likely you'll bork things again. >it'll have to be over ssh, so I'm assuming some combination of DD and >SCP? SSH and SCP? Say what? How bout a USB3 rotating drive? And NOT a Seagate. > >I've looked on the internet now, and it seems like dump/restore are >perfect for this (and even faster than dd?) >So maybe something like >`dump af /dev/sd3i | ssh receiving-computer "restore xf -"` >But where would the sd3i end up then and how? would it turn in a file, >or become a /dev/sd3i copy on the receiving computer? >If you don't respond, I'll search the internet and try to do it on my >own (for the 1st time) and possibly overwrite something again lol > >Would be great if I could find some great read about this > Personally, I think you're making this much harder than it has to be. If you care about those old photos, spend the money for enough USB hard drives, and don't get fancy until you have a copy of your files AND a backup of the copy of those files. Then you can treat the copy like a backup and copy them back. Seriously, priorities. Prioritize getting those files back, and don't let anything complicate that task. Don't skip steps. SteveT Steve Litt http://444domains.com
Re: 7.5 install crashes on "entry point at 0x1001000" HP Elitebook 840 G10
Hello, finally i'm still stuck on this problem. Are there any other tests I can do ? Thank you Comete 27 mai 2024 21:24 "Comète" a écrit: > Hi Aaron, > > thanks for the idea. Booting the regular kernel as suggested, has the same > result: > it freezes on "entry point at 0x1001000" too. > > Thanks a lot. > > Comete > > 27 mai 2024 04:48 "Aaron Mason" a écrit: > >> Hi >> >> Can you try booting the regular kernel? You should be able to do it this way: >> >> boot> /7.5/amd64/bsd >> >> If it makes it past the stage where the install kernel fails, it'll >> panic at the lack of root, which is expected. >> >> Might be a pointless move but it might help eliminate the install >> kernel as a variable. >> >> On Fri, May 24, 2024 at 10:30 PM Comète wrote: >> >>> Thanks Sven, >>> >>> I can't install OpenBDS because I get the error when trying to boot the >>> install image. >>> >>> Comete >>> >>> 24 mai 2024 07:48 "Sven Wolf" a écrit: >>> >>> Hi, >>> >>> I had a silimar issue on a Lenovo V130. >>> For this machine I needed to remove the amdgpu driver in the kernel. >>> >>> See also: >>> https://marc.info/?l=openbsd-misc&m=160232897421774&w=2 >>> https://marc.info/?l=openbsd-tech&m=160383074317608&w=2 >>> >>> Do you get the error "entry point at 0x1001000" also with the bsd.rd kernel >>> or only after you >>> installed the system with the bsd.mp/bsd.sp kernel? >>> >>> Best regards, >>> Sven >>> >>> On 5/23/24 22:40, Comète wrote: >>> >>> Hello, >>> I tried to install OpenBSD 7.5 on a new HP Elitebook 840 G10 (UEFI capable >>> only) without success. >>> It is stuck at boot on "entry point at 0x1001000". >>> Even retried after a BIOS upgrade but no luck either. >>> I tried with a snapshot install too with the same result. >>> I post here what lspci returns from a debian bookworm: >>> 00:00.0 Host bridge: Intel Corporation Device a706 >>> 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe >>> Graphics] (rev 04) >>> 00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic >>> Platform and Thermal >>> Framework Processor Participant >>> 00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port >>> 00:06.2 PCI bridge: Intel Corporation Device a73d >>> 00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI >>> Express Root Port >>> 00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI >>> Express Root Port >>> 00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module >>> 00:0a.0 Signal processing controller: Intel Corporation Raptor Lake >>> Crashlog and Telemetry (rev 01) >>> 00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB >>> Controller >>> 00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI >>> 00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI >>> 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host >>> Controller (rev 01) >>> 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) >>> 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi >>> (rev 01) >>> 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO >>> I2C Controller #0 (rev >>> 01) >>> 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI >>> Controller (rev 01) >>> 00:16.3 Serial controller: Intel Corporation Alder Lake AMT SOL Redirection >>> (rev 01) >>> 00:1c.0 PCI bridge: Intel Corporation Alder Lake PCH-P PCI Express Root >>> Port #9 (rev 01) >>> 00:1e.0 Communication controller: Intel Corporation Alder Lake PCH UART #0 >>> (rev 01) >>> 00:1e.2 Serial bus controller: Intel Corporation Alder Lake SPI Controller >>> (rev 01) >>> 00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev >>> 01) >>> 00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H >>> cAVS (rev 01) >>> 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller >>> (rev 01) >>> 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI >>> Controller (rev 01) >>> 02:00.0 Non-Volatile memory controller: SK hynix BC901 NVMe Solid State >>> Drive (DRAM-less) (rev 03) >>> 57:00.0 Wireless controller [0d40]: Intel Corporation XMM7560 LTE Advanced >>> Pro Modem (rev 01) >>> Thanks for your help. >>> Comete >> >> -- >> Aaron Mason - Programmer, open source addict >> I've taken my software vows - for beta or for worse
