Updating u-boot corrupt filesystem on Odroid N2
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Updating u-boot corrupt filesystem on Odroid N2
I have an Odroid N2+ with eMMC. I've installed CoreElec and Ubuntu 20.04 (mate) on it. Yesterday when I tried to update some packages, I've noticed there are some errors (see below). After rebooting, petitboot could not see Ubuntu. I've noticed when I ran "ls /media/boot" which points to that 128MB boot partition, I see non-English characters as directory and file names. I restored my boot partition form Ubuntu image file. As long as I don't update u-boot, I don't have any problem. Is this normal? I have the output during the update. I had 4 updates so I corrupt and restore the partition multiple times to figure out it was u-boot:
- odroid
- Site Admin
- Posts: 39110
- Joined: Fri Feb 22, 2013 11:14 pm
- languages_spoken: English, Korean
- ODROIDs: ODROID
- Has thanked: 2499 times
- Been thanked: 1381 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
We've tested the new uboot package with microSD and eMMC deivces. Petitboot also detected new bootloader well.
There was no issue so far.
We will try reproducing your issue tomorrow.
Did you install CoreELEC first and install Ubuntu 20.04 + Kernel 4.9 Mate image?
Which version of CE did you flash?
Which version of Petitboot do you run?
There was no issue so far.
We will try reproducing your issue tomorrow.
Did you install CoreELEC first and install Ubuntu 20.04 + Kernel 4.9 Mate image?
Which version of CE did you flash?
Which version of Petitboot do you run?
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
Thanks for your response. Please find the answers below:odroid wrote: ↑Wed Feb 23, 2022 5:03 pmWe've tested the new uboot package with microSD and eMMC deivces. Petitboot also detected new bootloader well.
There was no issue so far.
We will try reproducing your issue tomorrow.
Did you install CoreELEC first and install Ubuntu 20.04 + Kernel 4.9 Mate image?
Which version of CE did you flash?
Which version of Petitboot do you run?
1. I installed CoreELEC (CoreELEC-Amlogic-ng.arm-19.3-Matrix-Odroid_N2.img) first and then Ubuntu 20.04 (ubuntu-20.04-4.9-mate-odroid-n2-20210830.img). Here is my partition list if it helps (pastebin: https://pastebin.com/bCa1cW3f):
Code: Select all
$ sudo parted /dev/mmcblk0 unit MiB print
Model: MMC BJTD4R (sd/mmc)
Disk /dev/mmcblk0: 29820MiB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 4.00MiB 516MiB 512MiB primary fat16 boot, lba
2 516MiB 7753MiB 7237MiB primary ext4
3 7754MiB 29820MiB 22066MiB extended lba
5 7755MiB 7883MiB 128MiB logical fat16 lba
6 7884MiB 29820MiB 21936MiB logical ext4
3. I don't remember the version of petitboot. I ran pb-update before partitioning so it shouldn't be that old (I think November 2021). After the problem occurred I ran pb-update so it's updated to 20220129. After the update I couldn't even see CoreELEC. So I updated petitboot to 20220204 (flashing into MicroSD).
For me to reproduce the issue (with petitboot 20220204) I follow these steps:
1. Flash Ubuntu boot partition from ISO image into mine to fix the file system.
2. I ssh into Ubuntu and run the following command:
sudo apt install --reinstall u-boot
- tobetter
- Posts: 9779
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: Many
- Location: Paju, South Korea
- Has thanked: 624 times
- Been thanked: 1642 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
Don't you have any booting issue with Petitboot v20220204 before updating the U-boot?onderon wrote: ↑Thu Feb 24, 2022 7:04 amThanks for your response. Please find the answers below:odroid wrote: ↑Wed Feb 23, 2022 5:03 pmWe've tested the new uboot package with microSD and eMMC deivces. Petitboot also detected new bootloader well.
There was no issue so far.
We will try reproducing your issue tomorrow.
Did you install CoreELEC first and install Ubuntu 20.04 + Kernel 4.9 Mate image?
Which version of CE did you flash?
Which version of Petitboot do you run?
1. I installed CoreELEC (CoreELEC-Amlogic-ng.arm-19.3-Matrix-Odroid_N2.img) first and then Ubuntu 20.04 (ubuntu-20.04-4.9-mate-odroid-n2-20210830.img). Here is my partition list if it helps (pastebin: https://pastebin.com/bCa1cW3f):
2. CoreELEC-Amlogic-ng.arm-19.3-Matrix-Odroid_N2.imgCode: Select all
$ sudo parted /dev/mmcblk0 unit MiB print Model: MMC BJTD4R (sd/mmc) Disk /dev/mmcblk0: 29820MiB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4.00MiB 516MiB 512MiB primary fat16 boot, lba 2 516MiB 7753MiB 7237MiB primary ext4 3 7754MiB 29820MiB 22066MiB extended lba 5 7755MiB 7883MiB 128MiB logical fat16 lba 6 7884MiB 29820MiB 21936MiB logical ext4
3. I don't remember the version of petitboot. I ran pb-update before partitioning so it shouldn't be that old (I think November 2021). After the problem occurred I ran pb-update so it's updated to 20220129. After the update I couldn't even see CoreELEC. So I updated petitboot to 20220204 (flashing into MicroSD).
For me to reproduce the issue (with petitboot 20220204) I follow these steps:
1. Flash Ubuntu boot partition from ISO image into mine to fix the file system.
2. I ssh into Ubuntu and run the following command:
sudo apt install --reinstall u-boot
When you are able to reproduce the issue, can you please dump the first 1MB with these commands?
Code: Select all
sudo apt install --reinstall
sudo dd if=/dev/mmcblk0 of=N2.img bs=1M count=1
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
I don't have any issue before updating u-boot. I dumped the first 1MB of eMMC before and after corrupting the filesystem. there is no difference between them:tobetter wrote: ↑Thu Feb 24, 2022 11:07 amDon't you have any booting issue with Petitboot v20220204 before updating the U-boot?onderon wrote: ↑Thu Feb 24, 2022 7:04 amThanks for your response. Please find the answers below:odroid wrote: ↑Wed Feb 23, 2022 5:03 pmWe've tested the new uboot package with microSD and eMMC deivces. Petitboot also detected new bootloader well.
There was no issue so far.
We will try reproducing your issue tomorrow.
Did you install CoreELEC first and install Ubuntu 20.04 + Kernel 4.9 Mate image?
Which version of CE did you flash?
Which version of Petitboot do you run?
1. I installed CoreELEC (CoreELEC-Amlogic-ng.arm-19.3-Matrix-Odroid_N2.img) first and then Ubuntu 20.04 (ubuntu-20.04-4.9-mate-odroid-n2-20210830.img). Here is my partition list if it helps (pastebin: https://pastebin.com/bCa1cW3f):
2. CoreELEC-Amlogic-ng.arm-19.3-Matrix-Odroid_N2.imgCode: Select all
$ sudo parted /dev/mmcblk0 unit MiB print Model: MMC BJTD4R (sd/mmc) Disk /dev/mmcblk0: 29820MiB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4.00MiB 516MiB 512MiB primary fat16 boot, lba 2 516MiB 7753MiB 7237MiB primary ext4 3 7754MiB 29820MiB 22066MiB extended lba 5 7755MiB 7883MiB 128MiB logical fat16 lba 6 7884MiB 29820MiB 21936MiB logical ext4
3. I don't remember the version of petitboot. I ran pb-update before partitioning so it shouldn't be that old (I think November 2021). After the problem occurred I ran pb-update so it's updated to 20220129. After the update I couldn't even see CoreELEC. So I updated petitboot to 20220204 (flashing into MicroSD).
For me to reproduce the issue (with petitboot 20220204) I follow these steps:
1. Flash Ubuntu boot partition from ISO image into mine to fix the file system.
2. I ssh into Ubuntu and run the following command:
sudo apt install --reinstall u-boot
When you are able to reproduce the issue, can you please dump the first 1MB with these commands?When the partition table is corrupted, Petitboot cannot see OS installed in the eMMC and Petitboot does not use/access U-Boot in eMMC as well as apt install u-boot don't touch Petitboot. Petitboot v20220129 would not able to boot or recognize eMMC in certain condition and fixed version is after v20220204.Code: Select all
sudo apt install --reinstall sudo dd if=/dev/mmcblk0 of=N2.img bs=1M count=1
Code: Select all
odroid@odroid:~$ sudo diff N2-After.img N2-Before.img
odroid@odroid:~$
Code: Select all
Error: /dev/mmcblk0rpmb: unrecognised disk label
Warning: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error
Retry/Ignore? Ignore
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0rpmb: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Error: /dev/mmcblk0boot0: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot0: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Error: /dev/mmcblk0boot1: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Model: MMC BJTD4R (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 4194kB 541MB 537MB primary fat16 boot, lba
2 541MB 8130MB 7589MB primary ext4
3 8131MB 31.3GB 23.1GB extended lba
5 8132MB 8266MB 134MB logical fat16 lba
6 8267MB 31.3GB 23.0GB logical ext4
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
This is the content of /media/boot after it's corrupted:
Code: Select all
ls: cannot access ''$'\001''"?`'$'\f''?.+'$'\267\340': Input/output error
ls: cannot access '-??g'$'\003''h'$'\a''f.'$'\034\t\004': Input/output error
ls: cannot access '??o?'$'\023''('$'\003''?.'$'\017\005\030': Input/output error
ls: cannot access ''$'\001''???>h.k.4'$'\t\006': Input/output error
ls: cannot access ''$'\017\t''E?'$'\004''(?'$'\260': Input/output error
ls: cannot access ' f.c'$'\260''$': Input/output error
ls: cannot access 'f.??'$'\240': Input/output error
ls: cannot access ''$'\355''?.'$'\346''`': Input/output error
ls: cannot access ''$'\027'' '$'\032''I'$'\001''??'$'\260''.O?z': Input/output error
ls: cannot access ''$'\020''@'$'\001''???.'$'\252''`': Input/output error
ls: cannot access 'l'$'\364''c'$'\240\020''?'$'\027''.-i'$'\001': Input/output error
ls: cannot access ''$'\032''h'$'\022\t\002''?'$'\017\002''.'$'\003''*?': Input/output error
ls: cannot access ''$'\r''K'$'\032''h'$'\022''?'$'\307''_.'$'\267''?B': Input/output error
ls: cannot access ''$'\004''?'$'\006''K'$'\002''?'$'\003\003''.C?'$'\351': Input/output error
ls: cannot access ''$'\r''K'$'\032''h'$'\022''?'$'\307''_.'$'\267''?B': Input/output error
ls: cannot access ''$'\004''?'$'\006''K'$'\002''?'$'\003\003''.C?'$'\001': Input/output error
ls: cannot access ''$'\020\002\032''`d ??.'$'\020''@'$'\001': Input/output error
ls: cannot access 'B?'$'\020\002\032''`??.'$'\020''@'$'\001': Input/output error
ls: cannot access ''$'\024''c'$'\034''`p?'$'\001''".'$'\022\267\005': Input/output error
ls: cannot access ''$'\032''hB?pB'$'\032''`.2 '$'\001': Input/output error
ls: cannot access ']?'$'\240''?'$'\342''?'$'\020''?.'$'\004''F'$'\240': Input/output error
ls: cannot access ''$'\f''"'$'\001''?c'$'\267\b''?.'$'\274\366': Input/output error
ls: cannot access ''$'\001''4'$'\262''?q? ,.'$'\367''?o': Input/output error
ls: cannot access '??'$'\020''?ta.'$'\366\366': Input/output error
ls: cannot access 'L'$'\374''?'$'\240''|.'$'\021''1'$'\021': Input/output error
ls: cannot access '??'$'\001''@????.pf'$'\001': Input/output error
ls: cannot access 'Ze7J'$'\022''h'$'\334''e.?'$'\260': Input/output error
ls: cannot access '???'$'\347''?'$'\366''.'$'\340''a': Input/output error
ls: cannot access 'X?c'$'\240\243''a.?a': Input/output error
ls: cannot access '??-.O?': Input/output error
ls: cannot access ''$'\265''?.ko'$'\023': Input/output error
ls: cannot access ''$'\004'' ??7?'$'\006''K.[o'$'\023': Input/output error
ls: cannot access ''$'\f''?B?'$'\003\003\t''?.'$'\003''*'$'\b': Input/output error
ls: cannot access 'L?'$'\005\005\361\261'':'$'\f': Input/output error
ls: cannot access ''$'\253''h#gkh'$'\252''g.cg'$'\004': Input/output error
ls: cannot access ''$'\001''5'$'\034''4'$'\024''k'$'\374''o.'$'\362''b?': Input/output error
ls: cannot access ''$'\023''`'$'\006''!'$'\307''2'$'\021''`.'$'\002'' '$'\004': Input/output error
ls: cannot access 'vi.)i#': Input/output error
ls: cannot access ''$'\004''?.?'$'\366': Input/output error
ls: cannot access ''$'\032''`pG?'$'\371''.'$'\016''?'$'\003': Input/output error
ls: cannot access ''$'\b''f.?'$'\371': Input/output error
ls: cannot access ''$'\240''?|'$'\240''??'$'\002''e.hf': Input/output error
ls: cannot access '?'$'\362''.8R': Input/output error
ls: cannot access ''$'\364\240''??=???.'$'\347\240''?': Input/output error
ls: cannot access '??'$'\020''@??.?.'$'\020''c': Input/output error
ls: cannot access 'i?.'$'\004''H'$'\001': Input/output error
ls: cannot access '7?'$'\344''f'$'\366''f'$'\005''f.'$'\034''F': Input/output error
ls: cannot access '0@??'$'\275''?.(c': Input/output error
ls: cannot access ''$'\020''@'$'\262''?y?.Rc': Input/output error
ls: cannot access 'm'$'\337''-.'$'\n''?'$'\025\260''.'$'\001''kO': Input/output error
ls: cannot access ''$'\023\260\001''l'$'\252\261''0'$'\002''.'$'\035''F'$'\001': Input/output error
ls: cannot access ''$'\002\377\341''G': Input/output error
ls: cannot access ''$'\025''?'$'\006''?X.'$'\f''?.b.'$'\r': Input/output error
ls: cannot access 'YF???'$'\261''.'$'\002''?.': No such file or directory
ls: cannot access ''$'\024''?aF'$'\020\277''?'$'\260': Input/output error
ls: cannot access ''$'\001''6NE'$'\001''?.'$'\a''?'$'\032': Input/output error
ls: cannot access '??'$'\265''?``'$'\020''?.0'$'\373': Input/output error
ls: cannot access '8k'$'\032''h'$'\001''2'$'\032''`.O?'$'\240': Input/output error
ls: cannot access '?'$'\240''HFO?': Input/output error
ls: cannot access '?'$'\305''.?'$'\371': Input/output error
ls: cannot access ''$'\262''??? F'$'\020''?.9o': Input/output error
ls: cannot access ''$'\033''h'$'\334''B'$'\003''???.'$'\020''@'$'\262': Input/output error
ls: cannot access ''$'\001''?'$'\003\f\366''e'$'\367''?.0?0': Input/output error
ls: cannot access '??'$'\001''?'$'\003\260\001\033''.'$'\364''b?': Input/output error
ls: reading directory '.': Input/output error
''$'\364\240''??=???.'$'\347\240''?' ''$'\032''` k'$'\032''h.??@'
''$'\001\005\363''Bs?'$'\005\f''.'$'\001''?' ''$'\032''`pG?'$'\371''.'$'\016''?'$'\003'
''$'\344\t''?'$'\030\004''?'$'\177''t.'$'\034\031''$' ''$'\032''h'$'\022\t\002''?'$'\017\002''.'$'\003''*?'
''$'\351\034\023\267\002''?'$'\021''C.'$'\002\035\364' ''$'\032''h"?@RB?.'$'\307''R'$'\032'
''$'\001'' !f'$'\240''???. f!' ''$'\032''hB?pB'$'\032''`.2 '$'\001'
''$'\001''"'$'\363''@'$'\v''k?c.'$'\031''h'$'\005' ''$'\033''h'$'\334''B'$'\003''???.'$'\020''@'$'\262'
''$'\001''"?`'$'\f''?.+'$'\267\340' ' f.c'$'\260''$'
''$'\001''+'$'\001''?' '#`'$'\037''?'$'\022''k'$'\030''`.'$'\024''k'$'\005'
''$'\001'','$'\004''?'$'\030''k'$'\032''h.B?'$'\017' '#hO?zp#?'
''$'\001''3'$'\020''h'$'\034''+ ?.'$'\001\001\021' '#ho?'$'\023''Co?.'$'\003''C#'
''$'\001''4'$'\262''?q? ,.'$'\367''?o' '&.???'
''$'\001''5'$'\034''4'$'\024''k'$'\374''o.'$'\362''b?' '-??aqm?".'$'\004''F'
''$'\001''6NE'$'\001''?.'$'\a''?'$'\032' '-??g'$'\003''h'$'\a''f.'$'\034\t\004'
''$'\001''?'$'\350''B.'$'\b''3'$'\024' '-M? +hC?.@S+'
''$'\001''?'$'\003\f\366''e'$'\367''?.0?0' '0@??'$'\275''?.(c'
''$'\364''?'$'\004''F'$'\002\346\025''F.'$'\037''F'$'\352' '0F=`'$'\240''?.DI'$'\027'
''$'\355''?.'$'\346''`' '1f8f??p?."k'
''$'\265''?.ko'$'\023' '7?'$'\344''f'$'\366''f'$'\005''f.'$'\034''F'
''$'\262''??? F'$'\020''?.9o' '8k'$'\032''h'$'\001''2'$'\032''`.O?'$'\240'
''$'\001''???>h.k.4'$'\t\006' '<?'$'\035''k f'$'\032''h."?p'
''$'\371''?ch'$'\001''3'$'\003''?.'$'\240\003''c' '?'$'\261\001\b''??'$'\004''?.'$'\002\377'
''$'\240''?|'$'\240''??'$'\002''e.hf' '?'$'\267''.'$'\002''f'$'\027'
''$'\364''B'$'\f''?'$'\v''"'$'\f''"' '?'$'\362''.8R'
''$'\253''h#gkh'$'\252''g.cg'$'\004' '?'$'\305''.?'$'\371'
''$'\363''j'$'\004''3'$'\032''`?j.'$'\004''3'$'\032' '?'$'\240''.??<'
''$'\002\377\341''G' '?'$'\262''DO2 '$'\001''?.e'$'\262\036'
''$'\002\267\f''?C?'$'\002\002''.!?'$'\002' '?'$'\240''HFO?'
''$'\002\377''%!'$'\341''g' '?'$'\002''@*??!K.'$'\002''"'$'\032'
''$'\002''?(F??V?.ѱJ' '?'$'\030\001'' ?? ?.'$'\001''k'
''$'\003'',%?'$'\001'','$'\v''?' '?'$'\034''$?'$'\003\004\363''B.'$'\005''?'$'\024'
''$'\003''?'$'\022''k'$'\032''hb?.p'$'\002\032' '??'$'\001''?'$'\003\260\001\033''.'$'\364''b?'
''$'\003''?Q'$'\260\004''LC'$'\260''.'$'\004''K'$'\f' '??'$'\267''?'$'\005''k'$'\032''h.b?'$'\001'
''$'\004'' ??7?'$'\006''K.[o'$'\023' '??'$'\265''?``'$'\020''?.0'$'\373'
''$'\004''?'$'\006''K'$'\002''?'$'\003\003''.C?'$'\351' '??'$'\001''@????.pf'$'\001'
''$'\004''?'$'\006''K'$'\002''?'$'\003\003''.C?'$'\001' '??'$'\020''?ta.'$'\366\366'
''$'\004''?+hc`??.??' '??'$'\020''@??.?.'$'\020''c'
''$'\004''?.?'$'\366' '??-.O?'
''$'\006''?'$'\001'' '$'\001''F.??'$'\001' '??.'$'\023''?'$'\366'
''$'\006''?'$'\001'' '$'\001''F.m?'$'\001' '??.8?'
''$'\a''a.'$'\341\345\001' '??<?.??'$'\001'
''$'\b''?'$'\a''k'$'\033''h3?.'$'\f'' '$'\t' '???'$'\347''?'$'\366''.'$'\340''a'
''$'\b''f.?'$'\371' '????'$'\006''g'$'\b''k.'$'\004\277\035'
''$'\t''?'$'\a''7'\''?'$'\a''.??' '???G??X?.???'
''$'\f''"'$'\001''?c'$'\267\b''?.'$'\274\366' '??e !F'$'\240''?.??f'
''$'\f''2'$'\021''`'$'\032''i'$'\003''k.'$'\032''`p' '??o?'$'\023''('$'\003''?.'$'\017\005\030'
''$'\f''?B?'$'\003\003\t''?.'$'\003''*'$'\b' '?f'$'\016''?he'$'\274''?.'$'\307''F?'
''$'\r''?'$'\020\277\n''!'$'\001\306''.?'$'\260' '@*??'$'\023''KO?.'$'\240''2'$'\032'
''$'\r''K'$'\032''h'$'\022''?'$'\307''_.'$'\267''?B' '@d.C?'$'\001'
''$'\r''K'$'\032''h'$'\022''?'$'\307''_.'$'\267''?B' '@r?'$'\260''.?'$'\260\361'
''$'\017\t''E?'$'\004''(?'$'\260' 'B?'$'\020\002\032''`??.'$'\020''@'$'\001'
''$'\020\002\032''`d ??.'$'\020''@'$'\001' 'I?'$'\032''K'$'\005'' '$'\032''h.'$'\025''C'$'\035'
''$'\020'')'$'\t''?'$'\001''hbh.'$'\001''?'$'\017' 'L'$'\374''?'$'\240''|.'$'\021''1'$'\021'
''$'\020''?'$'\004''f.)k' 'L?'$'\005\005\361\261'':'$'\f'
''$'\020''@'$'\001''???.'$'\252''`' 'O?'$'\001\b''.G'$'\260''$'
''$'\020''@'$'\262''?y?.Rc' 'O?'$'\n\f''LJ'$'\362''B'
''$'\020''k.3?'$'\n' 'X?c'$'\240\243''a.?a'
''$'\021\267\004''?&k'$'\032''h.'$'\026''@'$'\036' 'YF???'$'\261''.'$'\002''?.'
''$'\022''?'$'\f''I'$'\240''??'$'\240''.'$'\006''?'$'\004' 'Ze7J'$'\022''h'$'\334''e.?'$'\260'
''$'\023\260\001''l'$'\252\261''0'$'\002''.'$'\035''F'$'\001' ']?'$'\240''?'$'\342''?'$'\020''?.'$'\004''F'$'\240'
''$'\023''`'$'\006''!'$'\307''2'$'\021''`.'$'\002'' '$'\004' 'f.??'$'\240'
''$'\023''`'$'\f''K'$'\032''hB?.'$'\020\002\032' 'i?.'$'\004''H'$'\001'
''$'\024''?aF'$'\020\277''?'$'\260' 'j '$'\001''!'$'\240''???.'$'\017'' '$'\b'
''$'\024''c'$'\034''`p?'$'\001''".'$'\022\267\005' 'l'$'\364''c'$'\240\020''?'$'\027''.-i'$'\001'
''$'\025''?'$'\006''?X.'$'\f''?.b.'$'\r' 'm'$'\337''-.'$'\n''?'$'\025\260''.'$'\001''kO'
''$'\025''K'$'\026''I'$'\032''h'$'\027''."?p' 'o?'$'\003''C#`'$'\020''?.'$'\021''j'$'\020'
''$'\025''K.'$'\003''??' 'o?.R?'$'\003'
''$'\027'' '$'\025''I.*h'$'\027' 'vi.)i#'
''$'\027'' '$'\032''I'$'\001''??'$'\260''.O?z' ''$'\177'' '$'\037''!'$'\240''???.m '$'\004'
- tobetter
- Posts: 9779
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: Many
- Location: Paju, South Korea
- Has thanked: 624 times
- Been thanked: 1642 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
If the 1MB of eMMC have no difference between before and after, the partition table is not corrupted at all but file system must be. This makes Petitboot not to load OS to boot menu.onderon wrote: ↑Thu Feb 24, 2022 12:08 pmI don't have any issue before updating u-boot. I dumped the first 1MB of eMMC before and after corrupting the filesystem. there is no difference between them:Code: Select all
odroid@odroid:~$ sudo diff N2-After.img N2-Before.img odroid@odroid:~$
This is not quite related to the problem what we are talking about, /dev/mmcblk0rpmb is a partition being used for security purpose but it's not being used by N2 at all. So you can ignore it.I don't think it's related to this issue but whenever I run "parted -l" I see some error messages:
Code: Select all
Error: /dev/mmcblk0rpmb: unrecognised disk label Warning: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error Retry/Ignore? Ignore
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
parted doesn't complain about partition table. I can see the content of other partitions (including Ubuntu root partition). I can even use CoreELEC. I also suspect the filesystem is corrupted. I should mention I copy FAT16 filesystem using GParted.
- tobetter
- Posts: 9779
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: Many
- Location: Paju, South Korea
- Has thanked: 624 times
- Been thanked: 1642 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
Ok, I am installing the set partition layout like yours with Ubuntu Mate and CoreELEC to eMMC. Let me try it out and get back to you.
- tobetter
- Posts: 9779
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: Many
- Location: Paju, South Korea
- Has thanked: 624 times
- Been thanked: 1642 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
That's strange...I've tried a couple of times with 2 eMMC cards and made the partition table like this, my test does not make any error with Petitboot and the first partition on eMMC also did not corrupted at all. I also don't see any significant change in U-Boot script which may corrupt a file system.
Code: Select all
GNU Parted 3.3
Using /dev/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: MMC 8GTF4R (sd/mmc)
Disk /dev/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 4194kB 537MB 533MB primary fat16 lba
2 541MB 4836MB 4295MB primary ext4
3 4836MB 7818MB 2982MB extended
5 4837MB 4971MB 134MB logical fat16
6 4972MB 7818MB 2846MB logical ext4
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
Thanks for your time. I have no idea what caused that issue on my side.
- tobetter
- Posts: 9779
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: Many
- Location: Paju, South Korea
- Has thanked: 624 times
- Been thanked: 1642 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
If you my understanding is correct, your eMMC is built manually by yourself or using your own script. I don't think the version of Petitboot is a matter since the problem is the FAT partition is corrupted after apt install. It is not relative the issue to resolve, I would like to comment a couple of things. 1) not necessary to skip 4MB for the first partition, only 1MB is fine for the boot loader. 2) If you install multiple OS images and number of partitions all does not exceed 4, not necessary to use extended partition since FAT partition table can manage 4 partitions.
-
- Posts: 7
- Joined: Wed Feb 23, 2022 11:03 am
- languages_spoken: english
- ODROIDs: Odroid N2+
- Has thanked: 6 times
- Been thanked: 0
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
Yes I partitioned it myself. Thanks for the comments. I didn't create the first two partitions. I flashed CoreELEC and then resize the second one and the rest. I created that extended partition just in case if I want to add another OS. I need to investigate it more. I let you know if I find the culprit.
- tobetter
- Posts: 9779
- Joined: Mon Feb 25, 2013 10:55 am
- languages_spoken: Korean, English
- ODROIDs: Many
- Location: Paju, South Korea
- Has thanked: 624 times
- Been thanked: 1642 times
- Contact:
Re: Updating u-boot corrupt filesystem on Odroid N2
Thank you for the explain, I realize that recently CoreELEC changes the partition layout due to their wide device support with single OS image. My suggestion is not to put multiple OSes into single memory card if possible and CoreELEC can run with budget SD memory card.onderon wrote: ↑Fri Feb 25, 2022 7:55 amYes I partitioned it myself. Thanks for the comments. I didn't create the first two partitions. I flashed CoreELEC and then resize the second one and the rest. I created that extended partition just in case if I want to add another OS. I need to investigate it more. I let you know if I find the culprit.
Who is online
Users browsing this forum: No registered users and 1 guest