That makes sense, and is definitely what you would want if you are starting
from scratch.

Just figured I'd pass along that I did 1700 power cycles last night and no
failures occurred!

Thanks again for the help,

Chris

On Thu, Oct 8, 2015 at 6:08 PM, William Hermans <[email protected]> wrote:

> *The only reason i clear out the mbr in the directions, is just to help*
>> * guarantee the user doesn't run into random*
>> * complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)*
>>
>> * and it helps make sure they have a good state of the microSD...*
>>
>
> I'd also like to add that occasionally, and potentially semi, but not
> completely related. Sometimes you get an error message at boot instructing
> the user to to run fsck. I've found that simply running fsck when it asks
> does away with this "boot complaint" afterwords. i.e. the Problem has been
> fixed. Usually, this only happens after one does something like re-sizing
> the partition using fdisk when the disk is live. It does work, but the
> system temporarily gets confused by the existing partition table, until
> after fsck is run.
>
> On Thu, Oct 8, 2015 at 2:41 PM, Robert Nelson <[email protected]>
> wrote:
>
>> On Thu, Oct 8, 2015 at 4:35 PM, Christopher Stack <[email protected]>
>> wrote:
>> > Don't worry I had already made a backup img so continually messing
>> things up
>> > wasn't really an issue. Just takes a few minutes to download the img
>> back to
>> > the sd.
>> >
>> > It is similar to what is on both Robert's and your blogs, so I'm not
>> sure
>> > why it got messed up when I tried recreating the partition table as
>> well.
>> >
>> > Regardless:
>> >
>> > I skipped this step: Erase partition table/labels on microSD card and it
>> > appeared the base uboot directly from Roberts guide worked properly.
>> Then I
>> > added the patch from here
>> > http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue and
>> > repeated the procedure. On power up while holding 'a' on the keyboard
>> the
>> > boot process continued as desired. So knock on wood I think I got the
>> > bootloader replaced and the new patch worked.
>> >
>> > Thank you both for your help and Miki for the patch!
>> >
>> > Before I'm content is there any issue from not cleaning out the MBR?
>> Like if
>> > the img after the last patch is a different size then Robert's img file?
>> >
>> > Intending to run reboot tests overnight to make sure the patch clears
>> up the
>> > issue. Although if the "random" noise on the rx line spells out stop I'm
>> > going to be a little spooked.
>>
>> The only reason i clear out the mbr in the directions, is just to help
>> guarantee the user doesn't run into random
>> complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)
>>
>> and it helps make sure they have a good state of the microSD...
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/aXv6An1xfqI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to