Client crashes during backup


#1

It started after updating the client to version 2.3.4-cbt beta.

2018-12-21 05:00:59: Loaded -fileserv- plugin
2018-12-21 05:00:59: Loaded -fsimageplugin- plugin
2018-12-21 05:00:59: Loaded -cryptoplugin- plugin
2018-12-21 05:01:00: SQLite: recovered 30968 frames from WAL file C:\Program Files\UrBackup\urbackup\backup_client.db-wal code: 283
2018-12-21 05:01:00: urbackupserver: Server started up successfully!
2018-12-21 05:01:00: Started UrBackupClient Backend...
2018-12-21 05:01:00: FileSrv: Servername: -Home-PC-
2018-12-21 05:01:00: Found no SYSVOL on the same physical device as 'C'.
2018-12-21 05:01:00: Found no EFI System Partition
2018-12-21 05:01:01: Looking for old Sessions... 0 sessions
2018-12-21 05:01:01: Final path: D:\
2018-12-21 05:01:01: Final path: D:\
2018-12-21 05:04:51: Cannot read data from device (G:\)
2018-12-21 05:04:52: Device G:\ isn't NTFS formatted
2018-12-21 05:04:52: Server has new version 224 (client version: 0). Updating...
2018-12-21 05:04:52: Server update does not have feature cbt. Not updating.
2018-12-21 05:04:53: Device G:\ isn't NTFS formatted
2018-12-21 05:04:53: Device G:\ isn't NTFS formatted
2018-12-21 05:04:54: ERROR: Not found
2018-12-21 05:04:55: ERROR: Not found
2018-12-21 05:06:00: FileSrv: Servername: -Home-PC-
2018-12-21 05:06:00: Final path: D:\
2018-12-21 05:06:06: Change block tracking active on volume C:
2018-12-21 05:06:07: ERROR: Need previous client bitmap for image backup with CBT. Disabling CBT.
2018-12-21 05:06:07: Used FSB: 0 bytes
2018-12-21 05:06:07: ERROR: Fatal exception code 3221225477 at address 0x00007FFA72084BA5
2018-12-21 05:06:10: ERROR: Fatal exception (APPLICATION CRASHED). Crash dump written to "c:\TEMP\UrBackup\v2.0.0-20181221-050607-5152-8372.dmp"
2018-12-21 05:06:10: ERROR: Program abort (SIGABRT)

#2

You’re trying to backup something that isn’t formatted as NTFS, so backup can’t read the file system to backup.

Exclude all but your c: drive for backup


#3

Can you send me the file at c:\TEMP\UrBackup\v2.0.0-20181221-050607-5152-8372.dmp? Thanks!


#4

How do I send it? I tried by PM, but got a message it’s too big.


#5

Can you compress it (and encrypt it) and upload it somewhere (Dropbox, file sharing services, your own web space, etc.) and send me the link?


#6

Sent.


#7

It’s because of log_image_changed_files, so removing that may fix that. I’ll have to look into what goes wrong there, as I can’t make sense of the crash dump yet.


#8

Thanks, it worked :slight_smile: