Tag: failed

storage – Why is mdadm unable to deal with an “almost failed” disk?

Multiple times in my career now I’ve come across mdadm RAID sets (RAID1+0, 5, 6 etc) in various environments (e.g. CentOS/Debian boxes, Synology/QNAP NASes) which appear to be simply unable to handle failing disk. That is a disk that is not totally dead, but has tens of thousands of bad sectors and is simply unable to handle I/O. But, it isnt totally dead, it’s still kind of working. The kernel log is typically full of UNC errors.

Sometimes, SMART will identify the disk as failing, other times there are no other symptoms other than slow I/O.

The slow I/O actually causes the entire system to freeze up. Connecting via ssh takes forever, the webGUI (if it is a NAS) stops working usually. Running commands over ssh takes forever as well. That is until I disconnect / purposely “fail” the disk out of the array, then things go back to “normal” – that is as normal as they can be with a degraded array.

I’m just wondering, if a disk is taking so long to read/write from, why not just knock it out of the array, drop a message in the log and keep going? It seems making the whole system grind to a halt because one disk is kinda screwy totally nullifies one of the main benefits of using RAID (fault tolerance – the ability to keep running if a disk fails). I can understand that in a single-disk scenario (e.g. your system has as single SATA disk connected and it is unable to execute read/writes properly) this is catastrophic, but in a RAID set (especially the fault tolerant “personalities”) it seems not only annoying but also contrary to common sense.

Is there a very good reason the default behavior of mdadm is to basically cripple the box until someone remotes in and fixes it manually?

Kubernetes manual certificate renewal – apiserver ceritificate update failed

We have a baremetal k8 cluster deployed using Kubespray, its certificates are expiring soon.

openssl x509 -in /etc/kubernetes/pki/apiserver.crt -noout -text |grep ' Not '

To update certificates, followed given instructions in official guide.

kubeadm certs renew all

Then removed manifest files in /etc/kubernetes/manifests/ one by one, but api-server did not restart after moving its manifest back to /etc/kubernetes/manifests, had to manually restart the node.

Here, suggest to restart docker container.

My questions are

  1. What is the most secure way to update certificates. (node restart or docker restart)
  2. How is the performance impact during this certificate update process?
  3. Is there a way to define certificate life time in kubespray installation?

Kubernetes version : 1.18.8
Kubeadm : v1.18.8
OS : Ubuntu 18.04

18.04 – Deja Dup Restore Failed – unexpected end of data | Restoring from Live Session to fresh install

I’m trying to restore my system to before a borked upgrade. There is a fresh install of 18.04 Desktop on the drive now, and I’m trying to restore my settings and such using Deja Dup from a live session.

After a short while of it seemingly being stuc in Preparing… it gave this error:

    Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1393, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1476, in do_backup
    list_current(col_stats)
  File "/usr/bin/duplicity", line 704, in list_current
    for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 354, in combine_path_iters
    refresh_triple_list(triple_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 341, in refresh_triple_list
    new_triple = get_triple(old_triple(1))
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 327, in get_triple
    path = path_iter_list(iter_index).next()
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 239, in sigtar2path_iter
    for tarinfo in tf:
  File "/usr/lib/python2.7/tarfile.py", line 2512, in next
    tarinfo = self.tarfile.next()
  File "/usr/lib/python2.7/tarfile.py", line 2360, in next
    tarinfo = self.tarinfo.fromtarfile(self)
  File "/usr/lib/python2.7/tarfile.py", line 1254, in fromtarfile
    return obj._proc_member(tarfile)
  File "/usr/lib/python2.7/tarfile.py", line 1276, in _proc_member
    return self._proc_pax(tarfile)
  File "/usr/lib/python2.7/tarfile.py", line 1408, in _proc_pax
    value = value.decode("utf8")
  File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
    return codecs.utf_8_decode(input, errors, True)
 UnicodeDecodeError: 'utf8' codec can't decode byte 0xe0 in position 21: unexpected end of data

What happened, and what can I do to fix it? Would it be better at this point to just manually setup the fresh install to what it was before without the restore?

partitioning – Windows 10 Mirror volume showing up as “Failed” in diskpart but both disks are showing as healthy

I recently had a pretty big system crash a few weeks ago which caused several of my drives to disappear from windows. I booted into a linux drive and all of them show up perfectly with no errors whatsoever. My question is why I can’t access my mirror drive despite both drives showing up as healthy in diskpart.

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0                             Mirror      1863 GB  Failed
  Volume 1         System Rese  NTFS   Partition     50 MB  Healthy    System
  Volume 2     C                NTFS   Partition    148 GB  Healthy    Boot
  Volume 3                      NTFS   Partition    508 MB  Healthy    Hidden
  Volume 4     D                NTFS   Partition    118 GB  Healthy
  Volume 5     E   Backup       NTFS   Partition    812 GB  Healthy
  Volume 6         Recovery     NTFS   Partition    499 MB  Healthy    Hidden
  Volume 7                      FAT32  Partition    100 MB  Healthy    Hidden
  Volume 8     F   2TB          NTFS   Partition   1863 GB  Healthy
  Volume 9     H   utapc        NTFS   Partition      9 MB  Healthy
  Volume 10        NO_LABEL     FAT32  Partition    300 MB  Healthy    Hidden
  Volume 11    G                NTFS   Partition    118 GB  Healthy
  Volume 12                     NTFS   Partition    537 MB  Healthy    Hidden

DISKPART> select volume 0

Volume 0 is the selected volume.

DISKPART> detail volume

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 3    Online         1863 GB      0 B   *
  Disk 5    Online         1863 GB      0 B   *

Read-only              : No
Hidden                 : No
No Default Drive Letter: No
Shadow Copy            : No
Offline                : No
BitLocker Encrypted    : No
Installable            : No

Virtual Disk Service error:
The object is in failed status.

and the disk status:

DISKPART> select disk 3

Disk 3 is now the selected disk.

DISKPART> detail disk

ST2000LM007-1R8174
Disk ID: FE8DA338
Type   : SATA
Status : Online
Path   : 3
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0103)#PCI(0001)#ATA(C03T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0                             Mirror      1863 GB  Failed

DISKPART> select disk 5

Disk 5 is now the selected disk.

DISKPART> detail disk

ST2000LM003 HN-M201RAD
Disk ID: 3759FFC0
Type   : SATA
Status : Online
Path   : 7
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0103)#PCI(0001)#ATA(C07T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0                             Mirror      1863 GB  Failed

DISKPART>

firebase – Flutter FIRESTORE INTERNAL ASSERTION FAILED: threads > 1

I’m having a problem with my flutter app on iOS.

When I try to make a call to get data from a collection, the application ends with the error:

FIRESTORE INTERNAL ASSERTION FAILED: threads > 1

Basically this is the snippet that is causing the error:

await FirebaseFirestore.instance.collection("myCollection").get();

These are my dependencies:

firebase_auth: ^2.0.0
cloud_firestore: ^2.5.0

Sorry if there is already a topic for this subject, but the only one I found was not resolved.

Any suggestions please?

Magento 2: Failed to set PHP CodeSniffer installed_paths Config on upgrade to 2.4.3 from 2.3.0

I am getting this error after running: composer update command:

Failed to set PHP CodeSniffer installed_paths Config

I tried composer global require "squizlabs/php_codesniffer=*" but still getting the same error. Please help.

why my viber sticker download failed?

I can’t download my viber stickers. It shows download failed.

I tried many times & I uninstalled it and reinstalled it again.
But this trouble not correct.

What I have to do for this?

2010 – “Failed to cache field with id” unexpected error on list item edit

Some of our users are receiving “Unexpected errors” when modifying list items. They are third party, but have access to our internal SharePoint site. Our site admin sees “Failed to cache field with id” errors when checking logs.

I am not able to recreate error when doing same change on the list items. This problem is reoccurring for ~5 third party users.

How can I troubleshoot this?

A MS employee mentioned content database size/transaction log space… would this transaction log space change based on end-user saving changes?
https://social.technet.microsoft.com/Forums/sharepoint/en-US/72cfe4c1-ff23-455a-b562-8cfcc2ee45db/sp-log-failed-to-cache-field-with-id?forum=sharepointgeneralprevious

Failed to cache field with id “{…}”, overwrite=0

System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.WebControls.LookupField.Validate() at System.Web.UI.Page.Validate() at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Thank you for your time,

postgresql – Non-fatal error and failed db cluster initalisation failed

So I’m new to PG and installing via (enterpriseDB site)(1) for Mac running Big Sur.

I noticed when I install in default Library location I run into the below error.

enter image description here

I no longer get the error when I change the directory. But, I want to understand why it doesn’t like the directory to be default “Library”.

Additionally, when I set the directory to be the application folder I run into the below issue.

enter image description here

Overall this prevents the default server from showing up in pgadmin tool. I really want to learn Postgres but this issue is fustrating me.

intended outcome

  • Install PG in default directory (Library)
  • For DB cluster initalisation to be successful