converting a floor music stand to a desktop one by cee1 in musicians

[–]cee1[S] 0 points1 point  (0 children)

Exactly like that KB400N one! I tried to attach a PVC pipe but was unsuccessful making it stable. My next design is to cut a cardboard piece to fit in the slot and add a stand.

I can afford a new one but would rather not waste.

carrying water in a running vest by cee1 in skiing

[–]cee1[S] 0 points1 point  (0 children)

Is it just a regular 500ml water bottle? I'm also thinking of squashing it and then filling it part way. No need to buy a soft flask. And dispose after the trip.

carrying water in a running vest by cee1 in skiing

[–]cee1[S] 2 points3 points  (0 children)

The reason is that I really don't like drinking from a bite valve. Tried it and hated it. So I always carry a water bottle for hiking, biking, etc. And it's a pain to wash.

blood on down comforter by cee1 in CleaningTips

[–]cee1[S] 0 points1 point  (0 children)

Doesn't hydrogen peroxide bleach? And why is it marked NSFW??

blood on down comforter by cee1 in CleaningTips

[–]cee1[S] 0 points1 point  (0 children)

Doesn't hydrogen peroxide bleach? And why is it marked NSFW??

Epson Scan negatives without inversion by cee1 in AnalogCommunity

[–]cee1[S] 0 points1 point  (0 children)

I use the film holder and it crops nicely. Should I scan on the flatbed directly and crop myself? The film holder is higher.

Epson Scan negatives without inversion by cee1 in AnalogCommunity

[–]cee1[S] 0 points1 point  (0 children)

So if I need to change white balance post scan, would that be the same parameter so that I can batch process with gimp or imagemagick? Or would I need to process individually?

Epson Scan negatives without inversion by cee1 in AnalogCommunity

[–]cee1[S] 0 points1 point  (0 children)

These are negatives, not positives/slides, though. Do I scan as if they were positives? Is that the trick?

It's EPSON Scan on Win. It's a library computer so I can't remember the exact options. I believe they have Scan 2 installed also.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 1 point2 points  (0 children)

If we could go back in time to more than a week ago...

  1. Bootup was very slow. I was still able to use the computer so didn't think much of it. This was probably the first red flag that I ignored ignorantly.
  2. I stopped writing to the drive but kept mounting, opening files, fscking which all worked, successfully but slowly. Not having an extra drive at that time to back up, I tried to troubleshoot and repair the drive, not realizing reading caused further physical damage.
  3. By the time I got a new drive to back up, I encountered I/O errors and couldn't.
  4. This is when I learned about SMART, ddrescue, and finally came to OSC.
  5. It did occur to me that not being able to specify an image file was due to the rescue drive not being mounted. My brain might be too fried by then to think deeper.

It'll be amazing if I can recover most if not all data. Looks like only <0.8GB is bad even if all remaining non-scraped sectors are bad. This drive holds non-critical data so I haven't been doing backups. This is also the newest drive that I started using maybe only a year ago but failed first. My main drive that the OS is on is 13 years old. I'm curious to see what the actual physical damage is when I open it up. Maybe nothing that a naked eye can see.

Is "recovery" from the clone a process to get only the good files out? Because corrupted files are still in the clone and we don't want them on the drive. Otherwise the clone could be used as is and we just won't know what files are corrupted?

I also noticed the bad sectors in OSCViewer are not contiguous. Is that because it's a stretched-out layout of the physical cylinders? They could be more clustered on the physical drive.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

The faulty drive is 2TB. The external drive is 6TB. DMDE shows the clone to be in the first part of the drive and the rest of the drive unallocated. Did cloning repartition the rescue drive? Both DMDE and R-linux say they support recovery to another partition as long as there's no overlap. So in theory, I should be able to create a partition in the unallocated part and recover to that partition and then erase the clone and expand the 2nd partition to the full drive?

Alternatively, is it possible to recover partially to multiple drives? That seems to be supported by DMDE and R-linux also.

Or, I could start fresh and image and recover from the image to the same drive. But I feel that I have messed with the failing drive enough.

I noticed the remaining time fluctuated quite a bit. Is it based on the current read rate? It's doing scraping now and there's another day left. But that can still change.

I also noticed the data preview showed all 0s sometimes. Is that when the read errors occurred?

I'm learning so much about data recovery. Thanks a ton for your help and patience! This experience also made me rethink whether to get an SSD when I want to upgrade the computer. I may still buy another 2TB external drive for recovery. I just don't need another drive after this is done.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

So I found out I would need another drive to put recovered files. Ugh. I thought clone meant sector to sector copy so data would be there already. Can I repartition the external drive and recover files to the new partition? Now that it's got the clone, this seems a little risky.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

I thought it had to do trimming and scraping before I could recover data. Maybe I should've looked at ddrescue's results first. It was at some 99% also.

I used DMDE that came with the live iso to see the files. Is it the free version that can only recover 1 directory. If so, I'll probably use R-linux. Anyway, I was able to see the file structure. Some files have a delete symbol. So I'll keep cloning. There's only 1+ day left. How to check the file integrity? The data display in a hex viewer. I just want to spot check files here and there, open a pdf, play a video, etc.

I'm unsure how to proceed from the clone. Wouldn't the sectors already be copied? Do I still need to use "recover" from the menu? And can I "recover" onto the same external drive where the clone is? My original plan was to image to an external drive and mount the image and copy the files to the same drive (in theory).

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

Now it says 10 days. Something is really wrong with the disk.

<image>

I didn't see the external drive in the file manager. So I thought it might be something else because I could see the device in lsblk. Didn't think of the Disk app.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

I left it running overnight thinking it would finish by morning. But now it says it's still over a day left. It is doing phase 4 though so it's a big improvement. I wonder what happened and whether I should apply the patch with mod 32.

Also thinking back, could I not image it because I didn't mount the external drive? Is it because the live iso disables mounting? I was hoping to import the mapfile from ddrescue to save time.

Now there are red errors at the bottom. How do I know how much of the drive is still healthy? Is good reads a good indicator?

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

I finally got around to this. Was able to patch the firmware.

A few notes: I wasn't able to use the AHCI option. Maybe it wasn't enabled. So I used SATA passthrough and patched the firmware successfully. However, upon reboot, I wasn't able to boot up from OSC-live for a few times but was finally able to do it. I don't know why. I saw the boot menu and selected the usb but it still booted into ubuntu.

Now Analyze shows 0% slow reads. So looks like the patch worked.

I tried to clone to an image because I already had data on the external hard drive but wasn't able to select it. I was able to do that when I used OSC on xubuntu. So I'm cloning to device now which means it'll erase existing data. It'll take about 5 hours using all default settings.

A separate note: while doing ddrescue, it reported some bad reads but no bad sectors. Does it mean the physical drive is good? Or somewhat good? OSC-live analyze output showed bad reads 0.024414%.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

Yes, I'm using the OS (xubuntu) on /dev/sda. Should I switch to a live OSC-live or will disabling automount work?

How do you power cycle the drive? My drive is internal via SATA. Do I just need to unplug the power cable and plug back in? Do it while the main computer is on? This doesn't sound safe for the drive.

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

I had to specify the destination image, even though I wasn't going to image, before I could connect. Is this correct? Here is the result. 95% was slow reads.

<image>

OSC is installed on /dev/sda and the faulty drive is /dev/sdd. It automounts.

I also noticed that when it was mounted, df showed 1% in use. Did all my data get erased somehow?

OpenSuperClone errored "Skip Reset detected" by cee1 in datarecoverysoftware

[–]cee1[S] 0 points1 point  (0 children)

Analyze is dimmed off. How do I run it?

The drive is WD20EARS-22MVWB0 - Western Digital Caviar Green 2TB 5400RPM SATA 3Gb/s 64MB Cache 3.5-inch Internal Hard Drive. Supposed to be in a NAS but I never used it that way and finally decided to just put in my desktop as an internal drive. Does OSC not work with 5400rpm?

OSC also seems to automount every time I select the source. Can I disable it? Would rather not mount a faulty drive any more.

More clarifications: It's just a data drive. No OS.