minor

backupNAS.md

@@ -1,6 +1,7 @@
 ---
 keywords:
   - IT
+  - 
 ---
 ## Backup odroid NAS
 

filesystems.md

@@ -2,6 +2,9 @@
 ## btrfs
 ### btrfs scrub
 As a copy-on-write (COW) filesystem btrfs can compensate some errors from the underlying storage
+- check checksum on READ
+- fix logical block if valid copy is available (RAID1, RADI5/&, DUP)
+- 07.2022 no force WRITE-VERIFY possible -> look downwards
 ##### btrfs resize
 ```
 btrfs filesystem show -d
@@ -25,7 +28,8 @@ the manual way of creating is eating the correct escape.
 
 ### ATA/SMART
 #### hdparm
-with hdparm you can activate the write-verify `-R1` handling, if the drive has got this feature. Most consumer devices do not have this. Otherwise hdparm is more for the temporary set of AAM or APM, ATAsecurity, DCO, e.g.
+##### write-verify
+with hdparm you can activate the write-verify `-R1` handling, if the drive has got this feature. Most consumer devices do not have this. Otherwise hdparm is more for the temporary set of AAM or APM, ATAsecurity, DCO, e.g. To disable use `-R0`
 ```
 /dev/sdb: [SSD]
  multcount     =  0 (off)
@@ -41,5 +45,6 @@ with hdparm you can activate the write-verify `-R1` handling, if the drive has g
  readahead     = 256 (on)
  geometry      = 60801/255/63, sectors = 976773168, start = 0
 ```
+If it tells you `write-read-verify = 2` then the feature is enabled
 #### smartmontools
 the smartmontools contains mainly two features: the smart daemon and the smartctl tool. `smartctl` controls the SMART features of a drive, `smartd` usually surveille and run tests as a daemon with it. 

hardware-list.md

@@ -29,7 +29,7 @@ mSATA USB3  enclousure
 USB3 Toshiba 2.5" HDD
 - 1 x 2,5" HDD 1TB CMR [2014?]
 ### USB SATA enclosure
-firmware not updatable due missing SPI flash --broken
+firmware not updatable due missing SPI flash --broken!
 ```
 Inateck 2,5" Gehäuse (ASMT 2115 USB)
 ASMedia 1153 - B1PU73D7A0 1809

lenovo_L13YOGA_G2_AMD.md

@@ -14,4 +14,5 @@ My own system: https://linux-hardware.org/?probe=6dfbd97685
 ### broken under archlinux
 1. keyboard backlight https://wiki.archlinux.org/title/Keyboard_backlight#On_GNOME
 2. keyboard FN keys
-3. bluetooth daemon disabled by default
+3. bluetooth daemon disabled by default
+4. touchscreen not detected

linux_hardening.md

@@ -37,6 +37,8 @@ So it should be more or less equal to use integrity with or without encryption:
  - RAID1 preferred
  - heavily perfomance issues caused by the journal ( none or bitmap as dangerous alternative)
 https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/device-mapper/dm-crypt.rst
+and maybe this gets into production
+ - T13/ATA External Path Protection
 
 the used strcuture to get this done:
 block device -> dm-integrity -> mdadm/lvm2 (RAID1) -> btrfs
@@ -46,9 +48,13 @@ block device -> dm-integrity -> cryptsetup(mdadm/lvm2 (RAID1)) -> btrfs
 - [ ] GPT formatted block devices to get recognized properly under windows
 - [ ] complete header backup
 - [ ] block device sector size 
-- [ ] blcok device support for SCT/ERC
-
+- [ ] block device support for SCT/ERC `smartctl -l scterc /dev/sdX`
+- [ ] Block device support for write-verify  `smartctl -R1 /dev/sdX`
+- [ ] blcok device support ``hdparm --dco-identify /dev/sdX`
 
+Western Digital Time Limited Error Recovery (TLER)
+Seagate  Error Recovery Control (ERC)
+Samsung/Hitachi Command Completion Time Limit (CCTL)
 
 
 Odroid HC1 HDD
@@ -188,9 +194,15 @@ SCT capabilities:              (0x303d) SCT Status supported.
 ERC settings: `smartctl -l scterc /dev/sda` or setting `smartctl -l scterc,150,150 /dev/sda`
 
 #### related issues
+- https://cateee.net/lkddb/web-lkddb/BLK_DEV_INTEGRITY.html
+##### cryptsetup
  - https://gitlab.com/cryptsetup/cryptsetup/-/issues/632 xxHASH64 support, needs separate `--tag-size 8`
  - https://gitlab.com/cryptsetup/cryptsetup/-/issues/668 dm-integrity documentation with setting recommendation
  - https://gitlab.com/cryptsetup/cryptsetup/-/issues/620 systemd LUKS key mgmnt integration
  - https://gitlab.com/cryptsetup/cryptsetup/-/issues/573 issues with caching the flag "recalculating"
+###### ATA background
  - https://raid.wiki.kernel.org/index.php/Drive_Data_Sheets#Non-Raid_drives 
  - https://www.smartmontools.org/wiki/FAQ#WhatiserrorrecoverycontrolERCandwhyitisimportanttoenableitfortheSATAdisksinRAID
+##### dm-integrity
+ - https://www.kernel.org/doc/html/latest/admin-guide/device-mapper/dm-integrity.html
+ - https://man7.org/linux/man-pages/man8/integritysetup.8.html

virtualbox.md

@@ -30,7 +30,13 @@ libguestfs
 virt-list-partitions FILE_NAME.vhdx
 guestmount -a srv-kirikas-storage.vhdx -m DEVICE --ro MOUNT_POINT
 ```
-
+### vmdk
+```
+sudo apt install libguestfs-tools
+    sudo guestmount -a xyz.vmdk -m /dev/sda3 --ro /mnt/vmdk
+OR    sudo guestmount -a xyz.vmdk -i --ro /mnt/vmdk
+sudo -i (you need to be root to access the folder)
+```
 ### virtual bridge inside
 as soon as you have a bridge inside the VM all the networking traffic is broken.
 Maybe it is the copy of the MAC, which breaks it. However, after doing things, it is working now.