drive – Repair corrupt GPT table for hardware RAID

After a system reboot on my Odroid XU4, I have unfortunately lost the ability to mount my hardware RAID 0 array. I'm a bit lost on how to fix the problem (and hopefully fix it). The drive is backed up every month, but data recovery is preferred if possible.

System information:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.4 LTS
Release:    18.04
Codename:   bionic

fdisk gives the following result for unity:

sudo fdisk /dev/sda

The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/sda: 7.3 TiB, 8001456963584 bytes, 15627845632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FF0E1EB3-7607-42A4-9D17-B24199DB2EC7

Device           Start         End     Sectors  Size Type
/dev/sda1         2048 15607421876 15607419829  7.3T Linux filesystem
/dev/sda2  15607422976 15627845598    20422623  9.8G Linux filesystem

I don't recall seeing a warning about the partition table before all this mess. I have found similar posts related to GPT partition table in this forum (eg Correct a corrupted backup GPT table?), And most seem to suggest using gdisk to repair the partition table. I took a look at the disk using gdisk /dev/sda.

GPT fdisk (gdisk) version 1.0.3

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: damaged

Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.

Am I on the right track here trying to get my disk up and running? If so, it would repair the partition table using gdisk be destructive and lead to data loss?

antminer s9 controller board repair

Antminer S9 does not display the kernel page and cannot access settings to change group details. firmware updated through Bitmain. The controller card flashed with the SD card and the miner started but was unable to save the new group settings. when the miner rebooted it went back to mining settings in antpool when prior to flashing it should have had details of slushpool where it had been the last to mine. Can someone help with this problem please?

repair: is it possible / practical to adjust the Gost scale light meter on a Kiev 4M to work at ASA values?

I just received a Kiev 4M (a Contax II or Contax III variant built in Ukraine made with repatriated equipment from the Zeiss factory). This is the version with a selenium (or silicon?) Photometer at the top of the camera, just below the accessory shoe. It is a type of "central needle", where the exposure is set on a dial around the rewind knob, with film speed scale in the old Soviet Gost system (the Gost value is 90% ASA, so the Gost 100 film would be ASA 90), and measure by turning the exposure dial until the gauge needle is at the diamond mark, then read the exposure (shutter and aperture values) off the scale and enter them into the lens and shutter speed dial.

It's a fairly simple meter to use and more convenient than carrying a separate meter, though its limited sensitivity makes it less useful indoors (a very common problem with selenium meters).

What interests me is whether it is reasonably easy to set this meter to read 10% lower, so that you can set the ISO / ASA linear scale film speed on the measurement scale directly.

There is a small screw inside a protective collar on the back of the camera's top cover, below / behind the meter. Is this screw to adjust the meter or rangefinder? If first, is it practical to apply a 10% change in reading with this screw?

bootcamp – Repair bluetooth drivers with windows 10 in MBP

In the bootcamp of my macbook pro, bluetooth does not work and in an attempt to fix it by following the steps: which are based on windows that use their own bluetooth drivers instead of the ones that apple provides.

I did not get it working (code 10) and removed the drivers for the broadcom 802.11ac network adapter which I am now unable to install again.

Can anyone show me where to find / download the Apple certificate or any Broadcom 802.11ac network adapter driver and try to fix the Bluetooth issues?

How to repair DIY rubber grips on Nikon cameras?

I recommend the Loctite Plastics Bonding system for this type of & # 39; gummy & # 39; plastics. I haven't specifically used it on a Nikon grip, but it works great in similar applications.

The problem with regular "5 min" epoxy and Gorilla Glue is that they are stiff and not flexible, so for rubber items the glue cannot stick. Gorilla Glue has an additional problem as it is for porous surfaces, it requires activation with water (not plastics) and it expands when curing so it is unlikely to look original if you use Gorilla Glue.

What is different from these things is that you have something to give, so in applications where you need something that is not stiff like normal epoxy, this is what you should get:

laptop repair – MacBook Air Early 2015 Black Screen Repetit Chime, boot key combination not working, can this MacBook be recovered?

Halo everyone.

First of all, sorry for my bad English.

So my MacBook air A1465 suddenly falls into a deep coma.

MacBook now cannot be turned on. Just a blank black screen with a ringing bell.

I did the SMC reboot, the PRAM reboot etc. nothing works. I can't even use any combination of boot keys (except SMC and PRAM Reset).

What happened?

When I was doing some work, the Mac shut down when the battery level was around 20%.

I thought it could just be that the battery was too low.

I grabbed the MagSafe, plugged it in. The charger light comes on. and I leave it for a few minutes

Then I opened the cover and pressed the power button.

Nothing, black screen. Thinking that maybe it just takes time to boot, I leave it alone. a few minutes later I come back and the screen is still black and the fan spins so% # * @ strong. Then I pressed the power button to force it to shut down.

Then I try to boot into safe mode, sometimes it works (I can enter the operating system in safe mode) but sometimes it just doesn't work, like the switch button doesn't even respond when I pressed it while the Mac is starting

I tried SMC reboot, stroller reboot, but nothing has any noticeable effect. Still black screen and ringing doorbell

When I was finally able to boot into macOS, the first thing I did was upgrade the operating system from macOS Sierra to High Sierra (thinking that maybe only the operating system is too old and needs some updating).

But no, the problem is still there, when I close the cover and open it again, the black screen is back.

So I thought, maybe I should clean install the thing. So I did it. I took a USB device and made a boot.

Using the disk utility tools, I formatted the SSD and proceeded to install High Sierra.

When it first restarts, I can see the Apple logo and progress bar, but nothing else. progress bar does not move, Apple logo remains there for hours. Then I press the power button again to turn it off.

In short, now the mac is completely dead, I can no longer start the USB installer, I cannot enter diagnostics, CMD + R does not work, nothing.

All start key combos do not work. I tried every tingling combination and every way to press it, nothing.

What is the possible status of this MacBook?

Is it the EFI chip that is damaged? or is it RAM? Processor? GPU? Hardware problem or just the EFI firmware is broken.

Soon? Can I get this MacBook back? At this point, I'm willing to even try soldering the new EFI chip, but before doing so I just want to shrink it.

Can anyone help guide me in the right direction without involving the Apple Store, because in my place there is no way I can find an Apple store or genius bar?

keyboard – Repair repeated keystrokes in Windows

My keyboard has this problem that sometimes it registers two keystrokes, duplicating a key. So I am trying to fix it using software.

I solved it by going to the Ease of Access Center and enabling Filter Keys> Bounce Keys, and set the delay to 50 milliseconds (lowest setting is 0.5s or 500ms, but changed to 50 using registry and it worked).

This solved my problem, but now when I press a key, it no longer repeats.

I tried to solve this using Repeat Keys / Slow Keys, but it didn't work.

Could anyone help?

vmware: when trying to repair Windows Explorer in VDI with an additional spacer, above the ribbon bar and below the title bar, making the title bar not clickable

Our VDI environment uses horizons with instant clones. Application volumes for applications and EMU to redirect profiles.

In my master image, I can log in as the administrator account and I don't see the problem, however, when I log in to any domain account, the problem is present. I reviewed and deleted all profiles that are not "administrator" and "default", making sure they are also deleted from the registry, then deleted the profile of our network share for our redirected UEM profiles.

Log in with new profiles and multiple accounts, everyone has the same problem. The only solution I have found is to restart explorer.exe, which alleviates the problem of the current session, but then comes back when we close the session and start it again.

The group that is using this master image is not in production, since we are looking to migrate to EMU. The current production group does not have this problem, but it has a different master image (one that a user created a while ago that is no longer in the company, so we wanted to start over with a new image win10 1909).

AppVolumes write volumes do not have a profile either, since it is configured to only give applications to the users we are testing in the new group.

Below is the screenshot I made of Windows Explorer with excess space (inside the yellow box)

enter the description of the image here

Repair Windows boot before uninstalling dual boot

Hello everyone, I am trying to uninstall my ubuntu, and I found a way to repair the Windows boot before removing the ubuntu partition through the cmd on system 32 with the bootrec / fixmbr command, but my system cannot find the File, is there another way to repair Windows boot before removing Ubuntu partition?

terminal: repair a damaged partition after an action (disk partition) in recovery mode, macOS?

There is a backstory of this, so naked with me for a moment.

In an attempt to create a free space partition for Ubuntu without using the disk utility application, I started in recovery mode and tried

diskutil partitionDisk /dev/disk0 GPT free Linux 100G

just to see if I could create a free space partition to install Ubuntu.

First, I'm not even sure if that was the right syntax to use, although the command seemed to work, but when I tried to restart in macos, I got the folder with a question mark image.

I returned to recovery mode and discovered that the volume /dev/disk0s2 I was giving a mistake.

so I deleted the volume / dev / disk0s2.

gpt remove -i 2 disk0

then used gpt -r show disk0

I stayed with

# gpt -r show disk0

start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 1953115495
1953115495 32 Sec GPT table
1953115167 1 Sec GPT header

(there is no C&P in recovery mode)

Then I tried to add the partition again, since I'm sure of the file system I've been using.

gpt add -i 2 -b 409640 -s 195311549 -t 7C3457EF-0000-11AA-AA11-00306543ECAC disk0

It is an Apple APFS partition.

but even with that, when I try to verify the volume

diskutil verifyVolume disk0s2

I get the error

starting file system verification for disk0s2: Unrecognized file system (-69846)

Any help to repair my volume and the proper syntax to partition the free space would help.


diskutil list

  /dev/disk0 (internal, physical):
 #:                    TYPE NAME                  SIZE        IDENTIFIER
 0:  GUID_paritition_scheme                      *1.0 TB      disk0
 1:                     EFI EFI                   209.7 MB    disk0s1
 2: 7C3457EF-0000-11AA-AA11-00306543ECAC          1000.0 GB   disk0s2

but I still can't start in macOS without seeing the question mark folder.