[2/5/2016][DEPRECATED]Script to automate GUI installation on Ubuntu

[dr5mn]

awesooooome. i am new on linux, let alone dev boards. thanks for the help

---

hi

i used that bash command and it provided me with options, but this error was returned. i used shutdown -r now to reboot but still the same error. have you seen this before?

[Terra854]

awesooooome. i am new on linux, let alone dev boards. thanks for the help

---

hi

i used that bash command and it provided me with options, but this error was returned. i used shutdown -r now to reboot but still the same error. have you seen this before?

Try running "sudo fsck /dev/mmcblk0p2" before running the script. Let me know if this solved the problem.

[dr5mn]

thanks for the feedback.

that drive is mounted, got
e2fsck: cannot continue, aborting.

then tried umount and sudo umount to unmount that drive, but just got
/: target is busy

should i try to reflash the ubuntu image to the sd card, or is there another solution?

[Terra854]

thanks for the feedback.

that drive is mounted, got
e2fsck: cannot continue, aborting.

then tried umount and sudo umount to unmount that drive, but just got
/: target is busy

should i try to reflash the ubuntu image to the sd card, or is there another solution?

If you have a linux system, you can insert the sd card into the system and try running:

Code:

sudo umount /dev/(the sd card partition containing the system)
sudo fsck /dev/(the sd card partition containing the system)

Then insert it back to the pine64 and try running the script again.

If you don't have a linux system or if the above fails, the only option is to reflash the image.

[tkaiser]

the only option is to reflash the image.

Really? What about issue 2 here: http://forum.pine64.org/showthread.php?tid=514

Is filesystem corruption considered something normal that can happen from time to time? Or might there be reasons for such stuff?

[Terra854]

the only option is to reflash the image.

Really? What about issue 2 here: http://forum.pine64.org/showthread.php?tid=514

Is filesystem corruption considered something normal that can happen from time to time? Or might there be reasons for such stuff?

I am aware about the counterfeit cards that are in circulation . I have planned to say later that if reflashing the image fails to solve the problem, then he should check to see if the card is counterfeit.

[dr5mn]

this is a sandisk sd card, tried a few ones and got the same result each time. (i only buy real ones )

i also followed all instructions to the letter. can't do fsck from the pine, kept telling me that /dev/mmcblk0p2 was mounted, and would not allow me to umount. if i put the card into another linux machine and do fsck it comes up with hundreds if not thousands of errors that need to be fixed.

fixed all errors by literally just holding in the y key, put card back into pine, ran the bash command and it executed the script by terra, but ended with another error: failed to fetch......components-arm64.yml.gz hash sum mismatch and also unable to parse package file......ports.....xenial_inrelease (1)

[tkaiser]

this is a sandisk sd card, tried a few ones and got the same result each time. (i only buy real ones )

i also followed all instructions to the letter. can't do fsck from the pine, kept telling me that /dev/mmcblk0p2 was mounted, and would not allow me to umount. if i put the card into another linux machine and do fsck it comes up with hundreds if not thousands of errors that need to be fixed.

fixed all errors by literally just holding in the y key, put card back into pine, ran the bash command and it executed the script by terra, but ended with another error: failed to fetch......components-arm64.yml.gz hash sum mismatch and also unable to parse package file......ports.....xenial_inrelease (1)

And you still don't get it that you can buy counterfeit cards through every retail channel? Wow!

Filesystem corruption happens for a reason! And I still don't get it why the Pine64 folks do not adjust their burning instructions for OS images so that they read: "ALWAYS CHECK YOUR SD CARD FIRST! Before you didn't succeed with either H2testw or f3 don't even think about downloading any OS image". But fortunately that's their problem (and their user's -- mostly newbies to the SBC world)

[dr5mn]

Thanks for the invaluable opinion and expert advice. The problem is clearly with all of the 5 sd cards I tried, from different brands and different retailers.

Is there anyone else who is willing to approach this like an adult and actually think of how we can provide a solution to the problem rather than an insult?


Sent from my iPad using Tapatalk

[tkaiser]

The problem is clearly with all of the 5 sd cards I tried, from different brands and different retailers.

Great, and instead of running the recommended tests you're wasting your own and other peoples' time. Issue 2 lists not one but several reasons for data corruption: http://forum.pine64.org/showthread.php?tid=514

These issues all exist and it's easy to rule this out. Before this isn't done it's just a waste of time to continue. Happy further suffering.