multibootusb deleted 90 GB of my data

[megitu]

I wanted to create a multiboot pendirve and put there my first ISO file - Manjaro Linux ( version 17.1.6). This ISO file was correct - verified with a checksum. Unfortunately, the multibootusb window has closed itself (as a result of some error). The last information I saw in multibootusb window, was that 75% of Manjaro files had already been created on USB.

Than it turned out, that over 90 GB of data on the partition, where ISO was stored, disappeared without any traces of any deleted files (now I have 90 GB more free space). I quickly realized that the data is lost and since then I have not done any file operations on this partition (fortunately, this is not a system partition).

Question: Does anyone guess what multibootusb could do that 90 GB of data disappeared and what can I do to recover it?

[mbusb]

Question: Does anyone guess what multibootusb could do that 90 GB of data disappeared and what can I do to recover it?

I don't think so. As per your statement, the 7zip was extracting ISO to your drive (hard disk or USB, not sure as you have not specified).

What is the hos system? Where is the log file?

[megitu]

System is Manjaro Linux. I intended to create a multiboot USB (on pendrive). And 90 GB of data disappeared from the partition of HDD, where ISO file was stored. Unfortunately, this issue occurred yesterday and today the log file: /tmp/multibootusb.log does not contain entries from yesterday.

[megitu]

I suggest not to place log from multibootusb in /tmp as it is cleared daily.

A Linux system log from this day: https://pastebin.com/63iYLwLd At 22:47 I installed multibootusb, and the crash occurred somewhere in the next hour - very likely at 23:26. There is a suspicious entry here: Apr 04 23:26:47 pcn systemd-coredump [17610]: Process 17430 (multibootusb) From what I remember: I restarted the computer, checked the pedriva USB using gparted and gnome-disk-utility and formatted it in FAT using gnome-disk-utility (previously it was formatted as ISO9660), I created a partition and I named it P4G.

[mbusb]

Will see where to place log file in next release.

On Fri 6 Apr, 2018, 8:58 PM megitu, notifications@github.com wrote:

I suggest not to place log from multibootusb in /tmp as it is cleared daily.

A Linux system log from this day: https://pastebin.com/63iYLwLd At 22:47 I installed multibootusb, and the crash occurred somewhere in the next hour - very likely at 23:26. There is a suspicious entry here: Apr 04 23:26:47 pcn systemd-coredump [17610]: Process 17430 (multibootusb) From what I remember: I restarted the computer, checked the pedriva USB using gparted and gnome-disk-utility and formatted it in FAT using gnome-disk-utility (previously it was formatted as ISO9660), I created a partition and I named it P4G.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mbusb/multibootusb/issues/323#issuecomment-379289002, or mute the thread https://github.com/notifications/unsubscribe-auth/AEC34DwZ8dMMsIMV1kgV1RD3CV6IpoN_ks5tl4mRgaJpZM4TI6e2 .

[shinji-s]

kwi 04 23:19:08 pcn sudo[17429]: ja : TTY=pts/0 ; PWD=/home/ja ; USER=root ; COMMAND=/usr/sbin/multibootusb kwi 04 23:19:08 pcn sudo[17429]: pam_unix(sudo:session): session opened for user root by (uid=0) kwi 04 23:19:23 pcn udisksd[735]: Mounted /dev/sdb1 at /run/media/root/p4g on behalf of uid 0

kwi 04 23:25:41 pcn kernel: usb 2-1.7: reset high-speed USB device number 6 using ehci-pci kwi 04 23:25:46 pcn kernel: usb 2-1.7: device descriptor read/64, error -110

It appears the pendrive started malfunction at some point after mbusb started.

kwi 04 23:26:44 pcn kernel: FAT-fs (sdb1): FAT read failed (blocknr 2605) kwi 04 23:26:44 pcn kernel: FAT-fs (sdb1): bread failed in fat_clusters_flush kwi 04 23:26:44 pcn kernel: FAT-fs (sdb1): unable to read inode block for updating (i_pos 2318353) kwi 04 23:26:45 pcn udisksd[735]: Cleaning up mount point /run/media/root/p4g (device 8:17 no longer exists)

Then in the end the partition got unmounted, perhaps while the copying was still going on. It is not ideal but I don't find it strange that mbusb has crashed.

Did you identify any of lost files? Could it be that you had orphaned files (files that disappeared from a directory but still kept on the file system because some process keep handles to them unclosed) or large amount of journals that missed opportunity of cleaning)?

-shinji

[megitu]

I explain, although it is not important in explaining this issue. Initially, I started and closed multibootusb several times. At the beginning, the pendrive was formatted as ISO9660, so multibootusb did not want to work with it. Then I formatted it in FAT, naming p4g (but I did not create a partition, so multibootusb did not want to work with it again). Errors shown above are referring to my first (failed) try with pendrive called p4g (without a partion created on it). Finally, I reformatted it in FAT, created a partition and called P4G. Until then, everything was OK. I had a partition on the HDD, where I stored my data. These files were not used by other applications. There were 20 directories here, one of them was a directory with ISO files.

After the multibootusb dumped, 18 of these 20 directories disappeared without any trace, along with their contents - about 90 GB in several thousand files.

After this failure I checked the file system on this partition and there are no errors. "The file system is intact".

I am trying to recover these files, however, there are too many of them and I will probably fail :(