Seite 2 von 2

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 26. Aug 2016, 21:12
von tom_hain
Anbei der Screenshot vom Acer wenn der NetworkError kommt. Hoffe, Du kannst damit was anfangen :nw
ErrorMessage.jpg
ErrorMessage.jpg (3.96 MiB) 3559 mal betrachtet
"Writing primary volume" klingt schon verdächtig..

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 27. Aug 2016, 10:45
von Nobby1805
Sorry ... leider nicht :(
Aber du verwendest das interne Recovery-Modul des H340 ... oder machst du das von einem USB-Stick ?

Du könntest noch einmal versuchen, auf der Platte eine Partition von 20480 MB zu erstellen (ich habe das gerade auf meinem virtuellen Testsystem noch einmal getestet, klappt da auch dann wenn die Partition unter W10 eingerichtet worden ist)

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 27. Aug 2016, 16:21
von Nobby1805
Ich kann "writing Primary voilume failed" inzwischen auf meinem Testsystem reproduzieren ... morgen werde ich mal versuchen, mehr herauszufinden

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 28. Aug 2016, 10:57
von Nobby1805
Jetzt bin ich verblüfft ... weil ich mir 100% sicher bin, dass in der Vergangenheit schon andere Erfahrungen gemacht worden sind :nw

1. Versuch: DISKPART clean unter W10 -> kein Erfolg
Release Date: 09/29/2007\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
DeviceIoControl IOCTL_STORAGE_GET_DEVICE_NUMBER failed for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\, error 1
X:\ is not a good match because it is on PhysicalDisk 0 and not 1
no good choices for primary volumes
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume
[8/27/2016 4:04:28 PM 608] Listener Created
\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
D:\ is not a good match because it is on PhysicalDisk 2 and not 1
E:\ is not a good match because it is on PhysicalDisk 3 and not 1
DeviceIoControl IOCTL_STORAGE_GET_DEVICE_NUMBER failed for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\, error 1
X:\ is not a good match because it is on PhysicalDisk 0 and not 1
no good choices for primary volumes
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume
[8/27/2016 4:14:49 PM 600] Listener Created
[8/27/2016 4:16:51 PM 638] Listener UdpCallback
[8/27/2016 4:16:51 PM 638] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/27/2016 4:16:51 PM 638] Listener Respond to 192.168.1.77
[8/27/2016 4:17:00 PM 638] Listener TcpEventCallback
[8/27/2016 4:17:00 PM 638] Listener TcpConditionCallback from 192.168.1.77
Number of active connections: 0
Received Connection
Writing primary volume failed
[8/27/2016 4:17:08 PM 638] Closing socket
[8/27/2016 4:17:08 PM 638] Closing socket
SessionComplete: Number of active connections: 0
[8/27/2016 4:17:08 PM 638] Closing socket
2. Versuch 20 GB Partition (20480 MB) unter XP angelegt -> klappt
\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
GetDiskFreeSpaceW failed for volume \\?\Volume{1d6b72c4-6d49-11e6-bce3-806e6f6e6963}\, error 1005
GetVolumeInformationW failed for volume \\?\Volume{1d6b72c4-6d49-11e6-bce3-806e6f6e6963}\, error 1005
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
D:\ *IS* a good match because because it is the first partition on disk 1
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume \\?\Volume{1d6b72c4-6d49-11e6-bce3-806e6f6e6963}\
[8/28/2016 9:59:39 AM 600] Listener Created
[8/28/2016 10:00:32 AM 63c] Listener UdpCallback
[8/28/2016 10:00:32 AM 63c] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:00:32 AM 63c] Listener Respond to 192.168.1.77
[8/28/2016 10:00:32 AM 63c] Listener UdpCallback
[8/28/2016 10:00:32 AM 63c] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:00:32 AM 63c] Listener Respond to 192.168.1.77
[8/28/2016 10:00:35 AM 63c] Listener TcpEventCallback
[8/28/2016 10:00:35 AM 63c] Listener TcpConditionCallback from 192.168.1.77
Number of active connections: 0
Received Connection
[8/28/2016 10:00:45 AM 63c] Socket::Read - timed out, retrying (asked for 4 bytes)
GetDiskFreeSpaceW failed for volume \\?\Volume{1d6b72c4-6d49-11e6-bce3-806e6f6e6963}\, error 1005
GetVolumeInformationW failed for volume \\?\Volume{1d6b72c4-6d49-11e6-bce3-806e6f6e6963}\, error 1005
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
Restoring volume \\?\Volume{1d6b72c4-6d49-11e6-bce3-806e6f6e6963}\
Physical location: 1:1
Setting progress bar upper bound to: 21476173824
Disk geometry: length 21476173824, sector size 512, cluster size 4096, clusters 5243206
File allocation bitmap: size 5243206, LCN 0
Locked the volume.Progress: 10
Progress: 11
Progress: 12
Progress: 13
Progress: 14
[8/28/2016 10:01:30 AM 63c] Socket::Write - send error 10054
[8/28/2016 10:01:30 AM 63c] Socket::Write - send error 10054
[8/28/2016 10:01:30 AM 63c] Closing socket
ClientFile::ReadFile - send operation failed
Progress: 100
Writing primary volume failed
[8/28/2016 10:01:30 AM 63c] Closing socket
[8/28/2016 10:01:30 AM 63c] Closing socket
SessionComplete: Number of active connections: 0
[8/28/2016 10:01:30 AM 63c] Closing socket
da hatte ich das anlaufende Recovery dann abgebrochen

3. Versuch 18 GB angelegt (XP) -> klappt nicht
\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
D:\ *IS* a good match because because it is the first partition on disk 1
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume \\?\Volume{15f89944-6d4a-11e6-a6cc-806e6f6e6963}\
[8/28/2016 10:06:35 AM 60c] Listener Created
[8/28/2016 10:06:56 AM 628] Listener UdpCallback
[8/28/2016 10:06:56 AM 628] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:06:56 AM 628] Listener Respond to 192.168.1.77
[8/28/2016 10:06:56 AM 628] Listener UdpCallback
[8/28/2016 10:06:56 AM 628] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:06:56 AM 628] Listener Respond to 192.168.1.77
[8/28/2016 10:06:58 AM 628] Listener TcpEventCallback
[8/28/2016 10:06:58 AM 628] Listener TcpConditionCallback from 192.168.1.77
Number of active connections: 0
Received Connection
Restoring volume \\?\Volume{15f89944-6d4a-11e6-a6cc-806e6f6e6963}\
Physical location: 1:1
Partition size (18876985344) does not match the file (21476173824)
Volume \\?\Volume{15f89943-6d4a-11e6-a6cc-806e6f6e6963}\ is NOT a good match - (246726144) does not match the file (21476173824)
Volume \\?\Volume{15f89944-6d4a-11e6-a6cc-806e6f6e6963}\ is NOT a good match - (18876985344) does not match the file (21476173824)
DeviceIoControl IOCTL_STORAGE_GET_DEVICE_NUMBER failed for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\, error 1
Volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\ is NOT a good match - (3162112) does not match the file (21476173824)
Writing primary volume failed
[8/28/2016 10:07:03 AM 628] Closing socket
[8/28/2016 10:07:03 AM 628] Closing socket
SessionComplete: Number of active connections: 0
[8/28/2016 10:07:03 AM 628] Closing socket
4. Versuch 22 GB XP -> klappt nicht
\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
GetDiskFreeSpaceW failed for volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\, error 1005
GetVolumeInformationW failed for volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\, error 1005
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
D:\ *IS* a good match because because it is the first partition on disk 1
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\
[8/28/2016 10:11:37 AM 600] Listener Created
[8/28/2016 10:11:57 AM 61c] Listener UdpCallback
[8/28/2016 10:11:57 AM 61c] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:11:57 AM 61c] Listener Respond to 192.168.1.77
[8/28/2016 10:11:57 AM 61c] Listener UdpCallback
[8/28/2016 10:11:57 AM 61c] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:11:57 AM 61c] Listener Respond to 192.168.1.77
[8/28/2016 10:11:58 AM 61c] Listener TcpEventCallback
[8/28/2016 10:11:58 AM 61c] Listener TcpConditionCallback from 192.168.1.77
Number of active connections: 0
Received Connection
GetDiskFreeSpaceW failed for volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\, error 1005
GetVolumeInformationW failed for volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\, error 1005
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
Restoring volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\
Physical location: 1:1
Partition size (23071878144) does not match the file (21476173824)
Volume \\?\Volume{c9618dc3-6d4a-11e6-8150-806e6f6e6963}\ is NOT a good match - (246726144) does not match the file (21476173824)
GetDiskFreeSpaceW failed for volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\, error 87
GetVolumeInformationW failed for volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\, error 87
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
FSCTL_ALLOW_EXTENDED_DASD_IO failed, error 87
Volume \\?\Volume{c9618dc4-6d4a-11e6-8150-806e6f6e6963}\ is NOT a good match - (23071878144) does not match the file (21476173824)
DeviceIoControl IOCTL_STORAGE_GET_DEVICE_NUMBER failed for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\, error 1
Volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\ is NOT a good match - (3162112) does not match the file (21476173824)
Writing primary volume failed
[8/28/2016 10:12:02 AM 61c] Closing socket
[8/28/2016 10:12:02 AM 61c] Closing socket
SessionComplete: Number of active connections: 0
[8/28/2016 10:12:02 AM 61c] Closing socket
5. Versuch DISKPART clean auf XP -> klappt nicht (da bin ich mir sicher, dass das schon mal geklappt hat :(
\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
DeviceIoControl IOCTL_STORAGE_GET_DEVICE_NUMBER failed for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\, error 1
X:\ is not a good match because it is on PhysicalDisk 0 and not 1
no good choices for primary volumes
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume
[8/28/2016 10:15:33 AM 5fc] Listener Created
[8/28/2016 10:15:51 AM 618] Listener UdpCallback
[8/28/2016 10:15:51 AM 618] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:15:51 AM 618] Listener Respond to 192.168.1.77
[8/28/2016 10:15:51 AM 618] Listener UdpCallback
[8/28/2016 10:15:51 AM 618] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:15:51 AM 618] Listener Respond to 192.168.1.77
[8/28/2016 10:15:52 AM 618] Listener TcpEventCallback
[8/28/2016 10:15:52 AM 618] Listener TcpConditionCallback from 192.168.1.77
Number of active connections: 0
Received Connection
Writing primary volume failed
[8/28/2016 10:15:56 AM 618] Closing socket
[8/28/2016 10:15:56 AM 618] Closing socket
SessionComplete: Number of active connections: 0
[8/28/2016 10:15:56 AM 618] Closing socket
6. Versuch 20 GB (20480 MB) auf W10 -> klappt nicht
\\.\PHYSICALDRIVE0 is too small in size to be the primary volume
\\.\PHYSICALDRIVE1 is our best physical disk
C:\ is not a good match because it is on PhysicalDisk 0 and not 1
D:\ *IS* a good match because because it is the first partition on disk 1
CSessionManager::CSessionManager() - Using PrimaryDisk 1 and Primary Volume \\?\Volume{86ed8044-6d4d-11e6-9b98-806e6f6e6963}\
[8/28/2016 10:31:16 AM 61c] Listener Created
[8/28/2016 10:31:38 AM 630] Listener UdpCallback
[8/28/2016 10:31:38 AM 630] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:31:38 AM 630] Listener Respond to 192.168.1.77
[8/28/2016 10:31:38 AM 630] Listener UdpCallback
[8/28/2016 10:31:38 AM 630] Listener ProcessUdpPacket from 192.168.1.77, size 1
[8/28/2016 10:31:38 AM 630] Listener Respond to 192.168.1.77
[8/28/2016 10:31:40 AM 630] Listener TcpEventCallback
[8/28/2016 10:31:40 AM 630] Listener TcpConditionCallback from 192.168.1.77
Number of active connections: 0
Received Connection
Restoring volume \\?\Volume{86ed8044-6d4d-11e6-9b98-806e6f6e6963}\
Physical location: 1:1
Partition size (21474836480) does not match the file (21476173824)
Volume \\?\Volume{86ed8043-6d4d-11e6-9b98-806e6f6e6963}\ is NOT a good match - (246726144) does not match the file (21476173824)
Volume \\?\Volume{86ed8044-6d4d-11e6-9b98-806e6f6e6963}\ is NOT a good match - (21474836480) does not match the file (21476173824)
DeviceIoControl IOCTL_STORAGE_GET_DEVICE_NUMBER failed for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\, error 1
Volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\ is NOT a good match - (3162112) does not match the file (21476173824)
Writing primary volume failed
[8/28/2016 10:31:44 AM 630] Closing socket
[8/28/2016 10:31:44 AM 630] Closing socket
SessionComplete: Number of active connections: 0
[8/28/2016 10:31:44 AM 630] Closing socket
Es klappt also NUR wenn eine Partition von 20480 MB unter XP angelegt wird :nw

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 28. Aug 2016, 11:09
von Nobby1805
Nachtrag: ich habe noch einen Test gemacht ...

Platte mit DISKPART clean "gelöscht" und dann aber Option 2, Werkseinstellungen, gewählt ... dann läuft das Recovery an

jetzt frage ich mich, wo ist der Unterschied zwischen einer neu gekauften Platte (mit der das Recovery Option 1 definitiv geklappt hat) und einer Platte die mit DISKPART clean gelöscht wurde :nw

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 28. Aug 2016, 11:32
von tom_hain
Wow! Vielen Dank für die Zeit und Energie, die Du in mein Problem investierst. Ich versuche es jetzt noch einmal DISKPART clean und dem Werkseinstellung.

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 28. Aug 2016, 14:13
von tom_hain
System ist wiederhergestellt - aber Daten sind leider weg :-(
Obwohl er eine ganze Zeit mit "Wiederherstellen" verbracht hat.
Naja, zum Glück habe ich ein Backup gemacht. Das wird wieder eingespielt....

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 28. Aug 2016, 16:33
von Nobby1805
Wenn du Werkseinstellung gemacht hast dann durften die Datenplatten natürlich NICHT im System eingebaut sein :(

Re: Daten Festplatten nicht verfügbar nach Server Restore

Verfasst: 28. Aug 2016, 17:13
von Nobby1805
Ich sehe gerade, der Thread läuftz unetr WHS2011 ... ich versschiebe ihn nach WHS v1

@tom_hain: denk daran, den veralteten McAffee zu entfernen, der hat schon öfter Probleme gemacht