nciht
Vice Admiral
- Registriert
- Okt. 2017
- Beiträge
- 6.993
Disclaimer: Bin absolut kein Linux-Pro
Ich hatte auf meinem HTPC (Ubuntu 20.04 LTS) ein Firmware-Raid (Raid 5 vom Mainboard her) am laufen, welches auf NTFS formatiert ist (zum Datei-Austausch mit Windows).
Leider hat ein Stromausfall vor ein paar Tagen das OS zerschossen und nachdem ich im Recovery-Modus ergebnislos einiges probiert hatte, hab ich Ubuntu einfach neu installiert. Das Raid will er aber jetzt nicht ohne weiteres wieder einbinden.
sudo mount /dev/dm-1 /pfad/von/vorher gibt aus
sudo ntfsfix /dev/dm-1 gibt aus
sudo fsck /dev/dm-1 gibt instant einfach nur aus: fsck from util-linux 2.34
In der grafischen Oberfläche kommt folgende Fehlermeldung: "Unknow error when mounting /dev/dm-1 (udisks-error-quark, 0)"
Gibt es ne Möglichkeit das Raid irgendwie wieder einzubinden, oder muss ich es samt Datenverlust neu aufsetzen (ggf. weil auch das Raid beschädigt ist)?
Ich hatte auf meinem HTPC (Ubuntu 20.04 LTS) ein Firmware-Raid (Raid 5 vom Mainboard her) am laufen, welches auf NTFS formatiert ist (zum Datei-Austausch mit Windows).
Leider hat ein Stromausfall vor ein paar Tagen das OS zerschossen und nachdem ich im Recovery-Modus ergebnislos einiges probiert hatte, hab ich Ubuntu einfach neu installiert. Das Raid will er aber jetzt nicht ohne weiteres wieder einbinden.
sudo mount /dev/dm-1 /pfad/von/vorher gibt aus
Failed to read last sector (15628064766): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/mapper/isw_baeidfecbi_HomeServer': Invalid argument
The device '/dev/mapper/isw_baeidfecbi_HomeServer' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/mapper/isw_baeidfecbi_HomeServer': Invalid argument
The device '/dev/mapper/isw_baeidfecbi_HomeServer' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Mounting volume... Failed to read last sector (15628064766): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
FAILED
Attempting to correct errors... Failed to read last sector (15628064766): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
FAILED
Failed to startup volume: Invalid argument
Failed to read last sector (15628064766): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Trying the alternate boot sector
$MFT LCN (4) or $MFTMirr LCN (976754047) is greater than the number of clusters (879766335).
Unrecoverable error
Volume is corrupt. You should run chkdsk.
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
FAILED
Attempting to correct errors... Failed to read last sector (15628064766): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
FAILED
Failed to startup volume: Invalid argument
Failed to read last sector (15628064766): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Trying the alternate boot sector
$MFT LCN (4) or $MFTMirr LCN (976754047) is greater than the number of clusters (879766335).
Unrecoverable error
Volume is corrupt. You should run chkdsk.
sudo fsck /dev/dm-1 gibt instant einfach nur aus: fsck from util-linux 2.34
In der grafischen Oberfläche kommt folgende Fehlermeldung: "Unknow error when mounting /dev/dm-1 (udisks-error-quark, 0)"
Gibt es ne Möglichkeit das Raid irgendwie wieder einzubinden, oder muss ich es samt Datenverlust neu aufsetzen (ggf. weil auch das Raid beschädigt ist)?
Zuletzt bearbeitet:
