A content of the entire system partition has been deleted

Well, there isn’t much more we can do. I also noticed device’s names changing at boot. That’s why UUID’s are better then /dev/sd designations. If the partition was formatted and not overwritten it can be recovered using a tool (in ex.: testdisk). Otherwise just forget it, maintain backups and, if you want to clarify what happened, try to replicate the problem. Formatting drives can be tricky. It is always a good idea to double check what you’re doing, like @gohlip said.

In that 2nd link (post 18), you said you chrooted into Manjaro.
How did you chroot? mhwd-chroot/manjaro-chroot or the ‘traditional chroot’?
Don’t forget you have 2 Manjaro’s and if you use these methods, you may have chrooted into the wrong manjaro (sda5). And did you mount $esp before chrooting?
Furthermore, even if you have chrooted properly, did you exit after doing the stuff. Did you continue other operations thinking you are in livecd OS when in fact the operations apply to that Manjaro installed partition? [That’s why I discourage people making chroot, if possible]

And yes, these are possible causes, and you may have done everything properly.
But the fact is that most times (especially by ‘experts’) we make mistakes without realizing it because we thought we know we did such simple things correctly.

Again, not saying you’re wrong or made a mistake (we can’t tell, even you can’t tell).
We just don’t know. I think we should just put this episode down as an open case and move on.

ps: I myself have made many mistakes (chroot, dd, more…) and in a few times don’t even realize it.

@mbb
Luckily for me, I had nothing important on that cleared partition, so I do not need to recover anything from this partition.
What is important to me, I would like to discover what was a most probable cause of this issue, just to eliminate potential risk factor and use the system with confidence.

@gohlip
Answering you: I was using sudo mhwd-chroot-shell command and after I got a prompt to choose the system partition, I chose number 0 (from: 0 = sda2; 1 =sda5; 2=sda7). And I am sure I used exit command after doing the stuff. After all I rebooted.
And after I restored GRUB from sda2, I was using the system (on sda2) for ca 3 days, without any issue. So IMHO, it is less probably, that this GRUB issue was a direct cause of data loss few days later.

At the end of the you are not going to admit if you made a mistake or not, this is 2018 it is always something else or some one else to blame.
What I will reinforce is in 30 years never has a installer on win/Linux made any decisions that I did not authorise before hand it is not possible for that to happen, we make the decisions. not the installer not chroot not the keyboard, we mount the partitions, we yes we make the mistakes, we conveniently forget what we did and blame it on the tools.
Every user has made mistakes I did just what you did a few years ago and deleted 500gb of data, how did it happen well its called human error I was trying to rush the phone rang next thing all data was lost, now I could blame the phone, I could blame the Wife, I could blame the partitioning tool but no it was human error simple as that no user is infallible, not you not me, not anybody, Just accept what has happened learn from it
not blame everything else for what is most likely a simple human error.
The best way to fix it is like this
200_s

5 Likes

You hit the nail on the head there @mandog. Everyone’s done it, but nobody likes to admit it. Hell, I flushed 4 TB of data a few months back with a bad dd command. I was in a rush and i was flustered, and sh*t happens sometimes.

My heart dropped when I realized what Id done. Then I shrugged it off because I had another mirrored 4 TB backup at home, and another off site. Backups turn those moments from a catastrophe into a mere inconvenience. Backup, backup, backup, it can’t be repeated enough.

4 Likes

The problem is that in this case I do not remember doing something incorrect :left_speech_bubble:
I realize that many problems are simple human error and please believe me, that if I would make some mistake, I would admit it, as I did in the second sentence of this thread, writing: “I mistakenly installed the second GRUB”.
And here we have 3 similar cases (my, @AgentS, @emerilin), where everyone:

  • was using Manjaro Installer (in different versions),
  • had 2 internal disks,
  • used ext4 (at least me and @AgentS ).

Perhaps this is a pure coincidence, but perhaps a composition of some of these three factors builds a (rarely occuring) explosive mixture :bomb::boom:

Highly, highly unlikely.

You can test this by running a VM with the same setup, then trying to replicate the same steps as you performed several days ago.

Of course, given the amount of formatting, re-partitioning, and OS installation you’ve done it’s going to be very difficult to replicate.

If you’re concerned there’s a lower-level issue you might consider wiping the machine and starting from a clean slate. That way there’s no left-over configuration which may get in the way or produce spurious, unreplicatable issues.

Plus you have less stuff to blame.

1 Like

I totally agree about wiping the drive. Totally wipe the partition tables and their backup entries with a dd command. You can reinstall what you want back via imagining. That way if you ever have to recover data again you don’t have a dozen old partition entries to confuse your recovery software. You should also get in the habit of backing up your partition tables. That is the surest way to get your data back with the proper file names.

You really need to simplify things. What your doing now is causing you nothing but grief. Go to VM’s if you insist on running a bunch of different OS’s at once.

Hey, careful there. I (and wongs) have lots and tons of OS’s , nothing from VM’s.
Don’t blame it on the system when it’s the user outside the system. As you said, " nobody likes to admit it. " Ha ha.

ps: I wouldn’t have written this if you are ‘other people’. They would have taken offence. Not you.
Is that a compliment? Nah! Ho Ho Ho!. couldn’t resist. Ngah Ngah Ngah!

I personally disagree , but take no offense. Running multiple OS’s on metal is looking for trouble unless you are extremely knowledgeable. Even then Microsoft will likely throw you a curve ball at a future upgrade and bork your system. The people that really know their stuff might get away with many OS’s with out major issues, but the average user will probably have big problems.

@gohlip may be the sensei when it cones to fixing borked boot issues, but look at how many help requests these multi boot systems generate on the forum. One OS per hard drive in my system. I use a hot swap rack and just run things clean and easy. If you play with fire you’ll likely get burned.

2 Likes

I have 5 hdds all running at least 12 systems on my desktop, i do a lot of partitioning the drive orders can and do change at boot time nothing to do with Linux, or partition managers. its a feature of sata drives they are all equal and no boot order that is why you have to use UUID to identify partitions not driove boot order.

I can honestly tell you even I make mistakes unknowingly after 30 years and with a memory that is old i do not remember what I did wrong, but i’m the operator everything is my responsibility not the machine it only does what I tell it to do it has no brain partitions can only be formatted if the operator mounts them 1st or changes their mind and forget to unmounted them, always if you change your mind reboot start again from scratch.

You are very correct on that point Users tend to forget how complex it can be 2 days ago i did a read test on one drive then i found i had done a random read/write test, Luckily it was the win 10 partition so no big deal. Luckily after a couple of hrs trying to reboot win10 it miraculously reached the desktop don’t ask me how, after a disc check and registry optimise win10 was saved, again i was distracted just for a milli second.
But this is 2018 should I blame the Gnome disk Utility I mean it is Gnome after all. Or was it the Sranglers music I was listening to, or divine intervention, No it was me I clicked proceed

3 Likes

A true (wise) word, and it should be nailed on top of every help forum.

None taken. {I seldom take offence, nothing special here :grin:}
But as they say,

It is not difficult if you know how.

or as a Chinese (Ivana Trump) saying goes… :rofl:

“Those who say it can not be done, should not interrupt those doing it.”

Or as a real Chinese (meaning ‘I’ :laughing: ) say…

He who has apples should give to those who have none.
Once given, is none of his business.

Ho Ho Ho.

3 Likes

There is one other possibility I hadn’t considered until now. I went through a situation 4 years ago where my GF’s windows computer had external drives in a dual bay hot swap tray that kept losing their partitions. This happened on three different occasions. This is when I started to get serious about backing up partition tables. I had done it before this but not that often.

At first I just attributed it to the fact it was Windows and NTFS and therefor a POS. The second time it happened about 6 months later I replaced the drive that had lost its partition table twice. The third time I finally clued in, it wasn’t anything to do with the drives or windows. It was the usb enclosure itself causing the problem. I assume it had a faulty controller that was causing the loss of the partitions. As long as you only had 1 drive in the rear slot of the caddy it was fine, but if you ran two drives sooner or later the first drive would lose its partition table and be unreadable.

I do not think the chances are high that this is occurring with you, but maybe you should download the phoronix test suite and run some tests on your hardware.

If it actually is a hardware issue I will be the first to offer you an apology.

1 Like

This is totally different with loosing one partition’ s data.

It is sad and a pity, that most people here have already been judges and came with a verdict, that it’s a user error, without any scientific proof. Very low level…

This is not a scientific approach IMO. IF there was a supposed bug somewhere, using a different setup (considering some specific setup factors triggered it), a not repeated issue would not mean there was no bug. Only the same setup could be used to replicate the situation. Just having backed up data/partitions can safeguard and this can be considered a temporary test bed.

As for the human error, it was my job to investigate accidents. We all new human error was most possible due to all strange and special situations of the work environment. But we first investigated thoroughly and tried to exclude/eliminate all possibilities of hardware/machine malfunction or erroneous design.

In my own case I was 100% conscious of what I had or not done. I was just lucky to observe the strange mounting . In OP issue he was not that lucky. So he has to prove to the early experts he is not an elephant.

I am more human friendly by choice. :sweat:

2 Likes

I think it is 99% most likely to be user error. There is a remote possibility that ext4, calamares, a hardware malfunction, or sunspots caused this to happen. Just playing the odds here. User error is the most likely probability.

Actually, it kind of is, just a different approach. You’re removing all unknown and uncontrolled variables and starting with what should be a known-good state. If the issue reoccurs then you have far fewer potential factors to investigate.

1 Like

Yes, it is a different approach.
My optic is to replicate/repeat the bug, if there is one, to prove user’s innocence.
Your approach eliminates this possibility, erasing the setup. This way “you are trying to exonerate” the software, meaning “its developers”.
The choice is yours. :face_with_head_bandage:

1 Like

Gentlemen (any ladies here?), I think we should all stop speculating. Including speculating the probability of an event. We do not have the conditions to work out the results of Baye’s Theorem here.

None of us are attributing blame, nor being uncharitable in our quest to find a conclusion.
After all, we all want to to help. Not having a conclusion nor a consensus may be disquieting, but let’s keep our cool.

1 Like

Dont you have some cr@ppy Win ME/Vista/8/10 quintuple boot/grub issue you need to work on @gohlip. I’m sure there’ll be another Windows user wanting you to fix his mess for him shortly if theres not allready. Ha Ha just giving you the gears :smile:

1 Like

Forum kindly sponsored by Bytemark