Accidentally over wrote a ISO to my time machine backup disk
Hello I'm looking for some help recovering the data from a time machine sparseimage file.
At some point I must have accidentally wrote an iso image to my mounted Time Machine backup instead of the USB disk it was intended. Currently when I run
hdiutil attach -nomount -noverify -noautofsck /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle
I get
/dev/disk2 FDisk_partition_scheme
/dev/disk2s2 0xEF
And when I mount it using mount_cd9660, I can see the contents of the image I intended to write to a USB stick.
However if I access the image via Finder and view its contents, I can see
Tims-MBP:~ timpotter$ ls -l /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle/
total 56
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.bckup
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.plist
drwxrwxrwx 1 timpotter staff 502442 Nov 5 16:53 bands
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.bckup
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.plist
-rwxrwxrwx 1 timpotter staff 1137 Nov 5 14:52 com.apple.TimeMachine.Results.plist
-rwxrwxrwx 1 timpotter staff 7892 Nov 5 16:52 com.apple.TimeMachine.SnapshotHistory.plist
-rwxrwxrwx 1 timpotter staff 0 Mar 12 2018 token
Is it safe to simply copy the contents to a newly created sparseimage file? Any thoughts or suggestions?
mac backup
add a comment |
Hello I'm looking for some help recovering the data from a time machine sparseimage file.
At some point I must have accidentally wrote an iso image to my mounted Time Machine backup instead of the USB disk it was intended. Currently when I run
hdiutil attach -nomount -noverify -noautofsck /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle
I get
/dev/disk2 FDisk_partition_scheme
/dev/disk2s2 0xEF
And when I mount it using mount_cd9660, I can see the contents of the image I intended to write to a USB stick.
However if I access the image via Finder and view its contents, I can see
Tims-MBP:~ timpotter$ ls -l /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle/
total 56
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.bckup
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.plist
drwxrwxrwx 1 timpotter staff 502442 Nov 5 16:53 bands
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.bckup
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.plist
-rwxrwxrwx 1 timpotter staff 1137 Nov 5 14:52 com.apple.TimeMachine.Results.plist
-rwxrwxrwx 1 timpotter staff 7892 Nov 5 16:52 com.apple.TimeMachine.SnapshotHistory.plist
-rwxrwxrwx 1 timpotter staff 0 Mar 12 2018 token
Is it safe to simply copy the contents to a newly created sparseimage file? Any thoughts or suggestions?
mac backup
2
The files you see in Finder (and withls
), are mostly information about the backup, not the actual backed-up data. The actual data is down in the "bands" subdirectory, and that's what got overwritten by the ISO image. There'll probably be some non-overwritten data (e.g. if you had a 50GB backup and overwrote it with a 500MB ISO, there'll be about 49.5GB of intact data), but it may include only parts of some files, and may not include information about which files are which. Data recovery will be difficult, and the results probably fragmentary.
– Gordon Davisson
Dec 15 '18 at 23:45
add a comment |
Hello I'm looking for some help recovering the data from a time machine sparseimage file.
At some point I must have accidentally wrote an iso image to my mounted Time Machine backup instead of the USB disk it was intended. Currently when I run
hdiutil attach -nomount -noverify -noautofsck /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle
I get
/dev/disk2 FDisk_partition_scheme
/dev/disk2s2 0xEF
And when I mount it using mount_cd9660, I can see the contents of the image I intended to write to a USB stick.
However if I access the image via Finder and view its contents, I can see
Tims-MBP:~ timpotter$ ls -l /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle/
total 56
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.bckup
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.plist
drwxrwxrwx 1 timpotter staff 502442 Nov 5 16:53 bands
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.bckup
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.plist
-rwxrwxrwx 1 timpotter staff 1137 Nov 5 14:52 com.apple.TimeMachine.Results.plist
-rwxrwxrwx 1 timpotter staff 7892 Nov 5 16:52 com.apple.TimeMachine.SnapshotHistory.plist
-rwxrwxrwx 1 timpotter staff 0 Mar 12 2018 token
Is it safe to simply copy the contents to a newly created sparseimage file? Any thoughts or suggestions?
mac backup
Hello I'm looking for some help recovering the data from a time machine sparseimage file.
At some point I must have accidentally wrote an iso image to my mounted Time Machine backup instead of the USB disk it was intended. Currently when I run
hdiutil attach -nomount -noverify -noautofsck /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle
I get
/dev/disk2 FDisk_partition_scheme
/dev/disk2s2 0xEF
And when I mount it using mount_cd9660, I can see the contents of the image I intended to write to a USB stick.
However if I access the image via Finder and view its contents, I can see
Tims-MBP:~ timpotter$ ls -l /Volumes/AirPort Disk/Tim’s MacBook Pro.sparsebundle/
total 56
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.bckup
-rwxrwxrwx 1 timpotter staff 500 Mar 12 2018 Info.plist
drwxrwxrwx 1 timpotter staff 502442 Nov 5 16:53 bands
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.bckup
-rwxrwxrwx 1 timpotter staff 516 Dec 15 10:20 com.apple.TimeMachine.MachineID.plist
-rwxrwxrwx 1 timpotter staff 1137 Nov 5 14:52 com.apple.TimeMachine.Results.plist
-rwxrwxrwx 1 timpotter staff 7892 Nov 5 16:52 com.apple.TimeMachine.SnapshotHistory.plist
-rwxrwxrwx 1 timpotter staff 0 Mar 12 2018 token
Is it safe to simply copy the contents to a newly created sparseimage file? Any thoughts or suggestions?
mac backup
mac backup
asked Dec 15 '18 at 19:32
Tim PotterTim Potter
11
11
2
The files you see in Finder (and withls
), are mostly information about the backup, not the actual backed-up data. The actual data is down in the "bands" subdirectory, and that's what got overwritten by the ISO image. There'll probably be some non-overwritten data (e.g. if you had a 50GB backup and overwrote it with a 500MB ISO, there'll be about 49.5GB of intact data), but it may include only parts of some files, and may not include information about which files are which. Data recovery will be difficult, and the results probably fragmentary.
– Gordon Davisson
Dec 15 '18 at 23:45
add a comment |
2
The files you see in Finder (and withls
), are mostly information about the backup, not the actual backed-up data. The actual data is down in the "bands" subdirectory, and that's what got overwritten by the ISO image. There'll probably be some non-overwritten data (e.g. if you had a 50GB backup and overwrote it with a 500MB ISO, there'll be about 49.5GB of intact data), but it may include only parts of some files, and may not include information about which files are which. Data recovery will be difficult, and the results probably fragmentary.
– Gordon Davisson
Dec 15 '18 at 23:45
2
2
The files you see in Finder (and with
ls
), are mostly information about the backup, not the actual backed-up data. The actual data is down in the "bands" subdirectory, and that's what got overwritten by the ISO image. There'll probably be some non-overwritten data (e.g. if you had a 50GB backup and overwrote it with a 500MB ISO, there'll be about 49.5GB of intact data), but it may include only parts of some files, and may not include information about which files are which. Data recovery will be difficult, and the results probably fragmentary.– Gordon Davisson
Dec 15 '18 at 23:45
The files you see in Finder (and with
ls
), are mostly information about the backup, not the actual backed-up data. The actual data is down in the "bands" subdirectory, and that's what got overwritten by the ISO image. There'll probably be some non-overwritten data (e.g. if you had a 50GB backup and overwrote it with a 500MB ISO, there'll be about 49.5GB of intact data), but it may include only parts of some files, and may not include information about which files are which. Data recovery will be difficult, and the results probably fragmentary.– Gordon Davisson
Dec 15 '18 at 23:45
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1384889%2faccidentally-over-wrote-a-iso-to-my-time-machine-backup-disk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1384889%2faccidentally-over-wrote-a-iso-to-my-time-machine-backup-disk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
The files you see in Finder (and with
ls
), are mostly information about the backup, not the actual backed-up data. The actual data is down in the "bands" subdirectory, and that's what got overwritten by the ISO image. There'll probably be some non-overwritten data (e.g. if you had a 50GB backup and overwrote it with a 500MB ISO, there'll be about 49.5GB of intact data), but it may include only parts of some files, and may not include information about which files are which. Data recovery will be difficult, and the results probably fragmentary.– Gordon Davisson
Dec 15 '18 at 23:45