This means that data was corrupted which could not be mounted at boot- which usually… again… is caused by hardware failure. It does that to prevent further data loss.
All the symptoms above suggest hardware issues, too.
And really, given your machine specs, you should have had No Trouble installing Zorin in the first place.
I am sorry to say this- But I would strongly suggest you check all the hardware involved. It may just be a loose or bad sata drive cable. But I definitely am leaning toward Hardware Troubles of this.
I endorse your views regarding this.
But,Friend,when I am trying to install openSUSE-15.2 Leap (64-bit) version,then how come the installer is running and functioning successfully??? Without any issues whatsoever???
I understand your point. I do not have that answer; I lack enough information.
It may be that OpenSUSE is more forgiving about investigating Hardware whereas Zorin is more strict and investigative.
Or it may be that Zorin is glitching.
But for you, as the controller and user, it still may be best to check all hardware in any case, just to be sure.
Then why Windows 10 and MX-Linux are running successfully? If there is an hardware issue,these OS as a whole should have glitch somewhere along the functioning!
Isn’t that so?
I ran Seatools applications under Windows 10 for all of my Seagate drives. Surprisingly, S.M.A.R.T. check and short drive self test were all success as result.
What to do now?
tabatiti@comparado:~$ xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
1920x1080 (0x2d9) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew 0 clock 67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
