<DC-IRC>
[Discord] <yannkaelig> Thx. I will do some reading on that.
<DC-IRC>
[Discord] <yannkaelig> Well, I would like to come back to the subject regarding the empty space at the beginning of my sdcards I have formatted with sdformatter. I notice that after installing the image as recommended by the guide, using the tools balenaetcher, the empty space still remain and I'm unable to understand if this empty space is really important or not.
<DC-IRC>
[Discord] <yannkaelig> Well, I would like to come back to the subject regarding the empty space at the beginning of my sdcards I have formatted with sdformatter. I notice that after installing the image as recommended by the guide, using the tools balenaetcher, the empty space still remain and I'm unable to understand if this empty space is really important or not in our use case.
<DC-IRC>
[Discord] <yannkaelig> Well, I would like to come back to the subject regarding the empty space at the beginning of my sdcards which I have formatted with the software sdformatter. I notice that after installing the image as recommended by the guide, using the tools balenaetcher, the empty space still remain and I'm unable to understand if this empty space is really important or not in our use case.
<DC-IRC>
[Discord] <yannkaelig> Well, I would like to come back to the subject regarding the empty space at the beginning of my sdcards which I have formatted with the software sdformatter. I notice that after installing the armbian iso as recommended by the guide, using the tools balenaetcher, the empty space still remain and I'm unable to understand if this empty space is really important or not in our use case.
<DC-IRC>
[Discord] <yannkaelig> Well, I would like to come back to the subject regarding the empty space at the beginning of my sdcards which I have formatted with the software sdformatter. I notice that after installing the armbian img as recommended by the guide, using the tools balenaetcher, the empty space still remain and I'm unable to understand if this empty space is really important or not in our use case.
<DC-IRC>
[Discord] <igorpec> SoC / hw is definining this empty space
<DC-IRC>
[Discord] <igorpec> and you don't need to format anything, we overwrite everything
<DC-IRC>
[Discord] <c0rnelius77> If you are referring to the offset before the partition this is normal. Although it is not really required for AW it is for other SoC's. Its where U-Boot gets flashed to.
<DC-IRC>
[Discord] <menu> sdformatter has utility when the partition table is completely trashed, but otherwise USBImager should be able to handle it
<DC-IRC>
[Discord] <yannkaelig> My bad, I didn't mean formatted but this empty space got after using the sdformatter. And this space is not overwritten as you can see /dev/mmcblk0p1 8192 14876671 14868480 7.1G 83 Linux
<DC-IRC>
[Discord] <yannkaelig> OK, wait, do you mean that even if sdformatter create this empty space, writting the ARMBIAN img will recreate this empty space ?
<DC-IRC>
[Discord] <c0rnelius77> The offset shouldn't really change.
<DC-IRC>
[Discord] <c0rnelius77> Well the IMG's produced have an offset already so when they are flashed to an SD that offset should be there. It shouldn't vary in size because the card is smaller or bigger.
<DC-IRC>
[Discord] <c0rnelius77> Even official RPI imgs have an offset now. I don't believe it is really required in that case but its common practice to do so and a safe bet.
<DC-IRC>
[Discord] <yannkaelig> How and where is this offset "recorded" in the img ?
<DC-IRC>
[Discord] <yannkaelig> It will always be 4MB for the cubietruck img, whatever the size of the sdcard is ?
<DC-IRC>
[Discord] <c0rnelius77> Should be yes
<DC-IRC>
[Discord] <c0rnelius77> Why are you worried about 4MB?
<DC-IRC>
[Discord] <yannkaelig> Not worried, this is something totally new for me, since on archlinx ARM there is nothing about that and the offset start at 2MB. So I wonder why such difference, and what is the impact on the write/read or lifetime of the sdcard if there is one.
<DC-IRC>
[Discord] <c0rnelius77> Yeah they just leave it at 2048 because Allwinner doesn't need an offset. Its not hurting anything though.
<DC-IRC>
[Discord] <yannkaelig> I see. It's clear now, thank you very much
<DC-IRC>
[Discord] <c0rnelius77> ur welcome.
<DC-IRC>
[Discord] <yannkaelig> I wonder if there are other people here still with a cubietruck
<DC-IRC>
[Discord] <yannkaelig> I also bought the HDD RAID subboard.
<DC-IRC>
[Discord] <yannkaelig> But I get an issue and I can not boot from the SATA because of a time out. I tried to debug the issue following recommandation from a guy on the uboot channel, but not being an expert I unable to fix the issue by myself
<DC-IRC>
[Discord] <yannkaelig> But I get an issue and I can not boot from the SATA in PM mode because of a time out. I tried to debug the issue following recommandation from a guy on the uboot channel, but not being an expert I unable to fix the issue by myself
<DC-IRC>
[Discord] <yannkaelig> But I get an issue and I can not boot from the SATA in PM mode because of a time out. I tried to debug the issue following recommandation from a guy on the uboot channel, but not being an expert I do not have the skill to fix the issue by myself
<DC-IRC>
[Discord] <c0rnelius77> I have an old one someone gave me, but I don't have an HDD in it and use it as a print server. I suspect though it would be u-boot related in nature.
<DC-IRC>
[Discord] <yannkaelig> Well, it's indeed uboot and it only occur during a cold booting. If you boot a linux kernel and then reboot it will work and the SATA drive recognized
<DC-IRC>
[Discord] <yannkaelig> Well, it's indeed uboot and it only occur during a cold booting. If you boot a linux kernel and then reboot it will work and the SATA drive on the subboard recognized
<DC-IRC>
[Discord] <c0rnelius77> There is a PREBOOT feature in u-boot. It might need a `sleep` added to it, so it can catch it the first time around. In my case I use it on an Odroid N2 to boot via SATA over USB. Might by worth trying though. ```+CONFIG_USE_PREBOOT=y