August 25, 20196 yr Nach dem Update Versuch von Version 6.6.6 auf 6.7.2 ist der Cache Speicher SAMSUNG_MZVPV128HDGM-00000_S1XVNYAG909211 (nvme0n1) nicht mehr lesbar. (Cache Devices nvme0n1 Unmountable disk present:) Dieses Laufwerk war Bestandteil eines Cache Pools aus 3 SSD-Platten (Cache SAMSUNG_MZVPV128HDGM-00000_S1XVNYAG909211 - 128 GB (nvme0n1); Cache2 WDC_WDS120G1G0B-00RC30_174105A040E7 - 120 GB (sdh); Cache3 WDC_WDS120G1G0B-00RC30_174105A04476 - 120 GB) Nach dem Update auf 6.7.2 wurde nur noch das erste Laufwerk erkannt, was aber nicht gemountet wurde. Ich habe deshalb einen Downgrade auf 6.6.6 durchgeführt. Die vermissten Laufwerke werden jetzt wieder angezeigt, aber das Problem mit dem ersten Laufwerk besteht weiterhin. Docker und VM zeigen keinen Inhalt (Keine Apps und VMs). Wie kann ich mein System wieder herstellen? Werden alle Daten die im Cache stehen auch auf den anderen Laufwerken gespeichert? (Ich vermisse die Systemfestplatte von der VM die auf der Cache-SSD gespeichert war) Wird der Cache wenn er jetzt neu angelegt wird aus dem Inhalt der anderen Laufwerke (Cache Pool) wieder automatisch aufgebaut? Was ist zu tun, damit die SSDs (Cache2 und 3) auch in Version 6.7.2 benutzbar sind? Können da Treiber nachinstalliert werden? Das Mainboard ist ein Gigabyte Technology Co., Ltd. - H170N-WIFI-CF mit Intel® Core™ i7-6700T CPU @ 2.80GHz und 32GB Speicher.
August 25, 20196 yr Author After the update attempt from version 6.6.6 to 6.7.2, the cache memory SAMSUNG_MZVPV128HDGM-00000_S1XVNYAG909211 (nvme0n1) is no longer readable. (Cache Devices nvme0n1 Unmountable disk present This drive was part of a cache pool of 3 SSD disks (Cache SAMSUNG_MZVPV128HDGM-00000_S1XVNYAG909211 - 128 GB (nvme0n1); Cache2 WDC_WDS120G1G0B-00RC30_174105A040E7 - 120 GB (sdh); Cache3 WDC_WDS120G1G0B-00RC30_174105A04476 - 120 GB) After the update to 6.7.2 Only the first drive was detected, but it was not mounted. That's why I downgraded to 6.6.6. The missing drives are now displayed again, but the problem with the first drive persists. Docker and VM show no content (no apps and VMs). How can I restore my system? Will all data stored in the cache be stored on the other drives as well? (I miss the system disk from the VM that was stored on the cache SSD) If the cache is newly created from the content of the other drives (cache pool) is the cache automatically rebuilt? What should be done so that the SSDs (Cache2 and 3) can also be used in version 6.7.2? Can the drivers be installed afterwards? The motherboard is a Gigabyte Technology Co., Ltd. - H170N-WIFI-CF with Intel® Core ™ i7-6700T CPU @ 2.80GHz and 32GB memory. Edited August 25, 20196 yr by ungross
August 26, 20196 yr Community Expert Post diags after array start, WD drivers are likely not being detected on v6.7 because of the Marvell controller, this might help.
August 30, 20196 yr Author I tried the first three commands with the first device from the pool, which consists of three devices. Pool = nvme0n1 + sdh + sdi root@unRAID:~# mount -o usebackuproot,ro /dev/nvme0n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. root@unRAID:~# mount -o degraded,usebackuproot,ro /dev/nvme0n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. root@unRAID:~# mount -o ro,notreelog,nologreplay /dev/nvme0n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error.
August 30, 20196 yr Author Did I understand correctly that the mount command for a pool per device in my case three times for nvme0n1, sdh1 and sdi1 must be performed?
August 30, 20196 yr Community Expert 4 minutes ago, ungross said: Did I understand correctly that the mount command for a pool per device in my case three times for nvme0n1, sdh1 and sdi1 must be performed? You just need to mount one device to mount the pool, and you always need to specify the partition, for the NVMe device it would be /dev/nvme0n1p1
August 30, 20196 yr Community Expert If you're following the FAQ recovery instructions it's created before, with mkdir
September 5, 20196 yr Author I have secured my remaining data via FTP. ddrescue is installed. Now the question is what needs to be cloned, so that the cache pool (Cache nvme0n1 128GB, Cache2 sdh 120GB, Cache3 sdi 120GB) is again accessible. The array devices are Parity sde (8TB) Disk 1 sdd, 2 sdg, 3 sdb, 5 sdf (4TB) and Disk4 sdc (8TB).
September 5, 20196 yr Community Expert Not sure what you're asking, ddrescue isn't used for cache pool recovery, and by secured your data, do you mean cache data? Some options for cache recovery are in the FAQ.
September 6, 20196 yr Author I have backed up the data from Disk4. ddrescue needs a hard disk (Y) to write to. For this purpose, one of the hard disks in the array should be used. ddrescue -f /dev/nvme0n1 /dev/sdd /boot/ddrescue.log Where is the link to the manual now? What does "2 or 3 posts above the linked one" mean? Edited September 6, 20196 yr by ungross
September 6, 20196 yr Community Expert I'm sorry, still not understanding what you're trying to do, ddrescue is used to recover a failing HDD, e.g. with some bad sectors, not to recover cache pool. 1 hour ago, ungross said: What does "2 or 3 posts above the linked one" mean? That was about this: On 8/26/2019 at 10:47 AM, ungross said: Where exactly does the change have to be made? Where can I find the file? That was about the Marvell controller and that change is done on the syslunux boot setting, as explained here.
September 6, 20196 yr Author Presumably, I expressed myself incomprehensibly. I have a UNRAID server whose operating system I have updated. After the upgrade, the cache pool was no longer detected. The cache pool consists of 3 SSDs. Two of them are located on a controller whose drivers are not included in the current version of UNRAID. That's why I undone the update. Now all SSDs are recognized, but the cache pool can not be mounted. What do I have to do to get to the files stored on the cache pool.
September 6, 20196 yr Community Expert On 9/5/2019 at 9:16 AM, johnnie.black said: Some options for cache recovery are in the FAQ.
September 7, 20196 yr Author Thank you for the detailed support. I have one more question about the recommended article. 2) BTRFS restore (non-destructive) If mounting read-only fails try btrfs restore, it will try to copy all data to another disk, you need to create the destination folder before, e.g., create a folder named restore on disk2 and then: How is the destination folder created on one of the other disks?
September 7, 20196 yr Author I found out. I created the folder /sicherung on Disk1 and tried the option v and vi. But now comes this message: btrfs restore -vi /dev/nvme0n1 /mnt/disk1/sicherung No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super ERROR: superblock bytenr 274877906944 is larger than device size 128035676160 Could not open root, trying backup super
September 7, 20196 yr Author I tried it with the 2 and 3 SSD from the cache array. Something was copied but then the message comes: Restoring /mnt/disk1/sicherung2/appdata/nextcloud/log/nginx/error.log Done searching /appdata/nextcloud/log/nginx Restoring /mnt/disk1/sicherung2/appdata/nextcloud/log/php Restoring /mnt/disk1/sicherung2/appdata/nextcloud/log/php/error.log Done searching /appdata/nextcloud/log/php Done searching /appdata/nextcloud/log Restoring /mnt/disk1/sicherung2/appdata/nextcloud/keys Restoring /mnt/disk1/sicherung2/appdata/nextcloud/keys/cert.key Restoring /mnt/disk1/sicherung2/appdata/nextcloud/keys/cert.crt Done searching /appdata/nextcloud/keys Restoring /mnt/disk1/sicherung2/appdata/nextcloud/php Restoring /mnt/disk1/sicherung2/appdata/nextcloud/php/php-local.ini Done searching /appdata/nextcloud/php Done searching /appdata/nextcloud Done searching /appdata Restoring /mnt/disk1/sicherung2/System-Cache Restoring /mnt/disk1/sicherung2/System-Cache/HSSV113201 Restoring /mnt/disk1/sicherung2/System-Cache/HSSV113201/vdisk1.img offset is 40960 offset is 217088 offset is 253952 offset is 106496 offset is 4952064 offset is 8192 offset is 4984832 offset is 106496 offset is 5373952 offset is 6197248 offset is 8511488 offset is 9699328 offset is 8192 offset is 4096 offset is 4096 offset is 20480 offset is 24576 offset is 23347200 Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror offset is 1011712 offset is 52654080 offset is 52875264 offset is 53395456 Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror Trying another mirror offset is 929792 offset is 798720 offset is 56266752 offset is 57098240 offset is 167936 offset is 368640 offset is 770048 Trying another mirror Trying another mirror How do I get the content of the first SSD? (NVME0N)
September 8, 20196 yr Community Expert 12 hours ago, ungross said: btrfs restore -vi /dev/nvme0n1 /mnt/disk1/sicherung You need to specify the partition: btrfs restore -vi /dev/nvme0n1p1
September 8, 20196 yr Author the crucial file I really need is under system cache / HSSV113201 / vdisk1.img I get this message: Error copying data for /mnt/disk1/security4/system-cache/HSSV113201/vdisk1.img Done searching / system cache / HSSV113201 Error searching /mnt/disk1/security4/system-cache/HSSV113201/vdisk1.img Done searching / system cache Error searching /mnt/disk1/security4/system-cache/HSSV113201/vdisk1.img Done searching
September 8, 20196 yr Author what is the probability of getting the required file if I use the 3rd option?
Archived
This topic is now archived and is closed to further replies.