On your quest for data integrity using OpenZFS is unavoidable. In fact, it would be quite unfortunate if you are using anything but ZFS for storing your valuable data. However, a lot of people are reluctant to try it out. Reason being that an enterprise-grade filesystem with a wide range of features built into it, ZFS must be difficult to use and administer. Nothing can be further from truth. Using ZFS is as easy as it gets. With a handful of terminologies, and even fewer commands you are ready to use ZFS anywhere – From the enterprise to your home/office NAS.

In the words of the creators of ZFS: “We want to make adding storage to your system as easy as adding new RAM sticks.”

Beck also spoke with Sen. Tom Cotten (R-AR) who indicated that he’d heard similar unbelievable reports of the State Department trying to stop flights, even a British flight with Brits trying to get out their Afghan allies.

Glenn Beck
@glennbeck
I've heard reports that OUR State Department told Macedonia to stop taking Afghan refugees. @SenTomCotton tells me he's heard similar reports. If our govt won't save these people, WE WILL. But the State Dept. must stop standing in the way. //

I previously reported about how the State Department booted 500 Afghan interpreters and other Special Immigrant Visa holders after they had made it into the airport. This, even as some planes were going out with largely empty seats. It’s not clear if any of those people got out.

So this isn’t just a problem of Joe Biden being derelict in his duty here and not doing enough, there is actual active blocking of people trying to save people here. There needs to be answers as to why they would do such a horrible thing immediately because the time is running out and every action like this costs lives.

Joe Biden has presided over one of the bloodiest days of our war in Afghanistan. That day was made possible solely by his incompetence and, sad to say, the spinelessness and/or incompetence of the chain of command of the US military. Young men were put needlessly at risk to do a hazardous mission that did not need to have been done. We didn’t need to operate from a single airfield. We didn’t need to let the Taliban occupy half of that airfield. We didn’t need to put our security in the hands of the Taliban. We didn’t need to evacuate US and allied nationals and our Afghan allies under these circumstances. This situation didn’t just develop organically. These were all of these choices made by the Biden White House and its commissars in the Defense and State Departments.

It didn’t have to be this way, but it is, and Joe Biden owns all of this.

RNC Research
@RNCResearch
Nancy Pelosi jokes around for 6 minutes while completely ignoring the 12 U.S. service members killed by terrorists in Afghanistan. Unacceptable

Independent Women's Voice
@IWV
How can @SpeakerPelosi give this self- righteous speech about women’s rights while supporting the man who just abandoned Afghan women to the Taliban?

#Afghanistan

Donald Trump did a deal with the Taliban last year when they were only wannabe rulers in which all U.S. troops would be out of Afghanistan by May 1, before the annual Afghan fighting season got underway in that godforsaken land.

In exchange, the Taliban agreed to reduce violent attacks, mainly on Americans, forbid terrorists to set up shop there again, and to negotiate in good faith with the elected central government in Kabul.

The withdrawal commitment was political cover for the United States, so the exit wasn’t an ignominious admission of defeat, like the Soviets in 1989 and every other attempted occupier for the last 33 centuries.

No one except perhaps some kindergarteners in Arkansas expected the Taliban to live up to much of that agreement. And only those toddlers were disappointed.

For some inexplicable reason, Biden delayed the withdrawal first to the anniversary of 9/11 that started this whole mess and then to Aug. 31, which is the prime-time combat season in a land that has no NFL to follow. Taliban forces were well on the move by then.

Taking the flag down at Bagram weeks early with no contingency plan for adversity was the signal for insurgents to step on the gas. So, they did. //

During the Taliban’s swift march to victory in the Afghan mountains, Biden was AWOL on vacation in the Maryland mountains.

No one heard anything and when we finally did, Biden was not confident and decisive. He was confused, defensive, looked lost. A healthy president, asked a challenging media question, would not turn and stride away.

In the end, it took less than 25 days. In a 6-3 ruling, the CDC’s order was blocked. Even Chief Justice John Roberts joined the majority this time, with Justice Brett Kavanaugh keeping his word that he could flip sides if this issue came up again.

Steven Mazie
@stevenmazie
BREAKING: Supreme Court blocks Biden’s moratorium on tenant evictions by 6-3 vote.

Conservative majority says it "strains credulity to believe" that the statute under which the moratorium was imposed "grants the CDC the sweeping authority that it asserts".
9:23 PM · Aug 26, 2021 from San Diego, CA //

Meanwhile, the liberals on the court did what they always do, which is dissent based on things that have nothing to do with the law.

Arguing that taking illegal action is fine because it might be less forceful than other (probably illegal) actions is nonsensical on its face. The question was always whether the eviction moratorium itself passed muster. It clearly does not. Yet, the liberals continue to act as if the Supreme Court is a place for social experimentation and not interpreting the law.

Today was one of the darkest days the United States has suffered in the last two decades. It opened with suicide bombings disrupting the already bungled evacuation attempt in Afghanistan. The latest count is that at least 13 American soldiers have perished, with at least 90 Afghans, including many women and children.

For nearly eight hours, the President of the United States remained silent. Shockingly, even as the death toll rose, we heard nothing. No written statement offering condolences for their deaths ever came. The White House couldn’t even muster a quick show of empathy via Joe Biden’s Twitter account. Once again, it became patently obvious that we simply don’t have a president. //

So, what now? Unfortunately, there are no easy answers. But for Republicans, they are answers nonetheless. Without control of the House, the GOP cannot start hearings and investigations to figure out what went into the series of incompetent, inexcusable decisions that led us to this moment of national disgrace.

But what they can do is call for impeachment. They can call for Biden’s resignation. They can start finally talking about his clear mental and physical decline. Will any of that lead to his removal? I have no idea, but what I do know is that this is no time to sit on the sidelines and hide behind norms and decorum. Rather, this is the time to take a strong position and take no prisoners in the process.

The GOP does not need a majority to file articles of impeachment. They certainly don’t need a majority to get in front of a camera and point out that Biden is suffering from some combination of senility and dementia.

Tesla aims to eventually become a massive distributed electric utility, and we’ve now learned of a new product, Autobidder, which appears to be the next step in that direction.

“Basically, they just put all those Afghans on a kill list,” said one defense official. //

U.S. officials in Kabul gave the Taliban a list of names of American citizens, green card holders and Afghan allies to grant entry into the militant-controlled outer perimeter of the city’s airport, a choice that's prompted outrage behind the scenes from lawmakers and military officials.

The move, detailed to POLITICO by three U.S. and congressional officials, was designed to expedite the evacuation of tens of thousands of people from Afghanistan as chaos erupted in Afghanistan’s capital city last week after the Taliban seized control of the country. It also came as the Biden administration has been relying on the Taliban for security outside the airport.

Are you looking to convert bootable USB to an ISO Image file in Windows 10?

If yes then this post is definitely for you.

In the previous post, I have already talked about how to create bootable ISO from windows files.

And which is similar to this post only.

The idea of this post came to my mind when I was writing one of my posts on how to create a bootable USB from an ISO file.

At that time I thought is it possible to create an ISO file from bootable USB that I have created.

So then I started searching on the internet and I found my answer.

And the answer is Yes.

So in this post, I will show you how to create an ISO file from a bootable USB drive & easily create a backup of it.

As you can see, the drive's power-on hours are 520 (which is accurate, as I've had it for under a month), but the two errors say they occurred at 10610 hours and 16878 hours — obviously impossible.

What's happening here? Are the errors real? Worrisome? Could there be some kind of "odometer tampering" going on here by my vendor? //

I think that your suspicion of "odometer tampering" is correct, and it is possible. The recorded errors are likely real and definitely worrisome because they indicate bad sectors upon reading. The disk was likely wiped before making its way to you, so those bad sectors have probably been remapped.

Whoever sold you the hard drive reset the S.M.A.R.T. attributes to make it look like a new hard drive.
Anecdote

On 25 July 2015, I purchased six very similar hard drives from goHardDrive.com. When I checked all the disks, I experienced almost the exact same symptoms:

The point of current / worst attributes like temperature is exactly this: to tell you if the drive has ever been outside its max operating temperature, and thus might have suffered permanent damage.

That's why it says "failed in the past", not "failing now": you did just barely touch the max-temp threshold. Note the attribute display shows "normalized: 50, threshold: 45, worst: 45". (These are 0..200 normalized values like for any other attribute, not raw Celsius temps.)

You also have some bad sectors (uncorrectable sector errors), so whether the brief high temperature caused that or not, it's probably time to ditch that drive.

A better SMART software UI would show you the current and max-ever temp. e.g.
smartctl -a /dev/sda or smartctl -x /dev/sda (-x prints all available SMART and non-SMART data it can get from the drive, including a temperature history log if the drive has one, with an ASCII bar graph.)

smartctl -x includes this for an old WD Green 1TB (WD10EADS) hard drive:

TestDisk is OpenSource software and is licensed under the terms of the GNU General Public License (GPL v2+).

TestDisk is powerful free data recovery software! It was primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software: certain types of viruses or human error (such as accidentally deleting a Partition Table). Partition table recovery using TestDisk is really easy.

This document explains how to create under Linux a LiveCD running FreeDOS that automatically start TestDisk.

• Download FreeDOS OEM CD-ROM disc builder assistant

  wget -N http://www.fdos.org/bootdisks/ISO/FDOEMCD.builder.zip

• Download the DOS version of TestDisk & PhotoRec

  wget -N https://www.cgsecurity.org/testdisk-6.12.dos.zip

• Cleanup the work directory if it already exists

  rm -rf FDOEMCD

• Uncompress the archive

  unzip FDOEMCD.builder.zip

• Uncompress latest version of TestDisk & PhotoRec

  cd FDOEMCD/CDROOT
  unzip ../../testdisk-6.12.dos.zip
  mv testdisk-6.12 testdisk

  Create an autorun script

  echo "@ECHO OFF" > AUTORUN.BAT
  echo "CLS" >> AUTORUN.BAT
  echo "CD TESTDISK" >> AUTORUN.BAT
  echo "TESTDISK.EXE" >> AUTORUN.BAT

• This script must use DOS newlines, not Unix ones

  unix2dos AUTORUN.BAT

• Create the iso image using mkisofs

  cd ..
  mkisofs -o testdisk.iso -p "Christophe Grenier" -publisher "www.cgsecurity.org" -V "TestDisk CD" \
  -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -N -J -r \
  -c boot.catalog -hide boot.catalog -hide-joliet boot.catalog CDROOT

• Boot from this iso image in qemu emulator

qemu -localtime -boot d -cdrom testdisk.iso -hda disk.dd

• If everything is ok, burn the iso

Label Aria Music Fnac Music / 592273

Année de production 1993

Giacomo Puccini
Messa di Gloria. Messe pour ténor, baryton, choeur et orchestre

2. 2. Gloria

Naxos / 8.557638

Année de production 2005

Ferdinand Ries
Concerto pour piano et orchestre No 8, en la bémol majeur. Salut au Rhin (Op.151)

The following sections describe how to identify the type of data corruption and how to repair the data, if possible.

• Identifying the Type of Data Corruption

• Repairing a Corrupted File or Directory

• Repairing ZFS Storage Pool-Wide Damage

Checksum errors can occur transiently on individual disks or across multiple disks. The most likely culprits are bit rot or transient storage subsystem errors - oddities like signal loss due to solar flares and so on.

With ZFS, they are not of much concern, but some degree of preventative maintenance is necessary to prevent a failure from accumulation.

From time to time you may see zpool status output similar to this:

    NAME        STATE            READ  WRITE CKSUM
    zones       ONLINE             0     0     0
      mirror-0        ONLINE       0     0     0
        c1t0d0        ONLINE       0     0     23
        c1t1d0        ONLINE       0     0     0

Note the "23" in the CKSUM column.

If this number is significantly large or growing rapidly, the drive is likely in a "pre-failure" state and will fail soon, and is otherwise (in this case) potentially compromising the redundancy of the VDEV.

One thing to make note of is that checksum errors on individual drives, from time to time, is normal and expected behavior (if not optimal). So are many errors on single drives which are about to fail. Many checksum failures across multiple drives can be indicative of a significant storage subsystem problem: a damaged cable, a faulty HBA, or even power problems. If this is noticed, consider contacting Support for assistance with identification.

This document is written for administrators and those who have familiarity with computing hardware platforms and storage concepts such as RAID. If you're already versed in the general failure process, you can skip ahead to how to replace a drive and repairing the pool.
Degrees of verbosity

When a drive fails or has errors, a great degree of logging data is available on SmartOS. We can drill down in more detail to help us find the underlying cause of disk failure. In descending order, these commands will present the disk failure cause in increasing verbosity:

• zpool status
• iostat -en
• iostat -En
• fmadm faulty
• fmdump -et {n}days
• fmdump -eVt {n}days

The zpool status command will present us with a high level view of pool health.

iostat will present us with high level error counts and specifics as to the devices in question.

fmadm faulty will tell us more specifically which event led to the disk failure. (fmadm can also be used to clear transitory faults; this, however, is outside the scope of this document. Refer to the fmadm man page for more information.) fmdump is much more specific still, presenting us of a log of the last {n} days of fault events. This information is often extraneous to replacing faulted disks, but if the problem is more complex than a simple single disk failure, it is extremely useful in isolating a root cause.

There's a nice lengthy post of the zfs-discuss mailing list that covers how scrub works on a raidz vdev. The gist of it is:

• read data block, compute checksum
• read checksum from disk, compare to computed checksum
• compute parity for block, compute checksum for parity block
• read checksum for parity block from disk, compare to computed checksum

If compute checksums don't match the checksums on disk, then data block is rebuilt from parity, checksums are compared, and data written overtop of the bad data block.