+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: Linux on RockPro64 (https://forum.pine64.org/forumdisplay.php?fid=101)
+--- Thread: How to reset board to default state? (/showthread.php?tid=11211)
How to reset board to default state? - kkdao - 08-31-2020
I have a Rockpro64 board in which I flashed an Ubuntu OS via an eMMC and installed a system onto it. However, I messed something up during the install and would like to completely start from scratch. There is nothing important on the drive I have attached to the board like this setup here, expect I have an NVMe M.2 SSD: https://notmandatory.org/rockpro64-pt1/
So I would like to unmount the drive, reformat and redo the LVM volumes I had setup, and do anything else necessary to go back to default configuration settings so I can start from scratch trying to install that system again.
Any tips or pointers would be greatly appreciated!
RE: How to reset board to default state? - evilbunny - 08-31-2020
(08-31-2020, 05:48 PM)kkdao Wrote: I have a Rockpro64 board in which I flashed an Ubuntu OS via an eMMC and installed a system onto it. However, I messed something up during the install and would like to completely start from scratch. There is nothing important on the drive I have attached to the board like this setup here, expect I have an NVMe M.2 SSD: https://notmandatory.org/rockpro64-pt1/
So I would like to unmount the drive, reformat and redo the LVM volumes I had setup, and do anything else necessary to go back to default configuration settings so I can start from scratch trying to install that system again.
Any tips or pointers would be greatly appreciated!
All data/settings are on the emmc chip, you just need to reflash it and it will be back to defaults...
RE: How to reset board to default state? - kkdao - 09-01-2020
(08-31-2020, 11:39 PM)evilbunny Wrote:I hoped that would be the case, but when I tried to re-install the system above again before, I would get systemd.service 'depenedency' errors relating to the mount point(08-31-2020, 05:48 PM)kkdao Wrote: I have a Rockpro64 board in which I flashed an Ubuntu OS via an eMMC and installed a system onto it. However, I messed something up during the install and would like to completely start from scratch. There is nothing important on the drive I have attached to the board like this setup here, expect I have an NVMe M.2 SSD: https://notmandatory.org/rockpro64-pt1/
So I would like to unmount the drive, reformat and redo the LVM volumes I had setup, and do anything else necessary to go back to default configuration settings so I can start from scratch trying to install that system again.
Any tips or pointers would be greatly appreciated!
All data/settings are on the emmc chip, you just need to reflash it and it will be back to defaults...
RE: How to reset board to default state? - evilbunny - 09-01-2020
(09-01-2020, 12:30 AM)kkdao Wrote:(08-31-2020, 11:39 PM)evilbunny Wrote:I hoped that would be the case, but when I tried to re-install the system above again before, I would get systemd.service 'depenedency' errors relating to the mount point(08-31-2020, 05:48 PM)kkdao Wrote: I have a Rockpro64 board in which I flashed an Ubuntu OS via an eMMC and installed a system onto it. However, I messed something up during the install and would like to completely start from scratch. There is nothing important on the drive I have attached to the board like this setup here, expect I have an NVMe M.2 SSD: https://notmandatory.org/rockpro64-pt1/
So I would like to unmount the drive, reformat and redo the LVM volumes I had setup, and do anything else necessary to go back to default configuration settings so I can start from scratch trying to install that system again.
Any tips or pointers would be greatly appreciated!
All data/settings are on the emmc chip, you just need to reflash it and it will be back to defaults...
You might need to unmount the partitions, I use etcher and it does it automatically for me.
RE: How to reset board to default state? - kkdao - 09-01-2020
(09-01-2020, 12:45 AM)evilbunny Wrote:I've actually tried re-flashing the eMMC with Etcher with a new image of the Ubuntu OS, but I still get errors when trying to run the system again. After looking deeper into the errors I have figured out there is an issue with my drive still being mounted somehow. So when I do 'e2fsck -f /dev/nvme0n1' or 'fsck.ext4 /dev/nvme0n1' I get back:(09-01-2020, 12:30 AM)kkdao Wrote:(08-31-2020, 11:39 PM)evilbunny Wrote:I hoped that would be the case, but when I tried to re-install the system above again before, I would get systemd.service 'depenedency' errors relating to the mount point(08-31-2020, 05:48 PM)kkdao Wrote: I have a Rockpro64 board in which I flashed an Ubuntu OS via an eMMC and installed a system onto it. However, I messed something up during the install and would like to completely start from scratch. There is nothing important on the drive I have attached to the board like this setup here, expect I have an NVMe M.2 SSD: https://notmandatory.org/rockpro64-pt1/
So I would like to unmount the drive, reformat and redo the LVM volumes I had setup, and do anything else necessary to go back to default configuration settings so I can start from scratch trying to install that system again.
Any tips or pointers would be greatly appreciated!
All data/settings are on the emmc chip, you just need to reflash it and it will be back to defaults...
You might need to unmount the partitions, I use etcher and it does it automatically for me.
ext2fs_open2: bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/nvme0n1
The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an exy2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
but when I try running e2fsck with the suggested alt superblock i get:
/dev/nvme0n1 contains a LVM2_member file system
I did all this in root FYI (sudo -) after SSHing into my system.
Another thing I probably should've mentioned at the beginning was WHY this all occurred in the first place and it's because I accidentally unplugged the power cord from the outlet while the system was on and running. So that's why the mount point is somehow messed up seemingly.