ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Logs: -> irc.armbian.com
stipa_ has joined #armbian
stipa has quit [Ping timeout: 260 seconds]
stipa_ is now known as stipa
norwich_ has joined #armbian
norwich has quit [Ping timeout: 268 seconds]
norwich_ is now known as norwich
xoan725451235261 has joined #armbian
xoan72545123526 has quit [Ping timeout: 268 seconds]
xoan725451235261 is now known as xoan72545123526
xoan725451235267 has joined #armbian
xoan72545123526 has quit [Ping timeout: 268 seconds]
xoan725451235267 is now known as xoan72545123526
WindBag is now known as Object
archetech has quit [Quit: Konversation terminated!]
xoan725451235263 has joined #armbian
xoan72545123526 has quit [Ping timeout: 252 seconds]
xoan725451235263 is now known as xoan72545123526
stipa_ has joined #armbian
stipa has quit [Ping timeout: 268 seconds]
stipa_ is now known as stipa
samythemany1 has quit [Ping timeout: 258 seconds]
crabbedhaloablut has quit [Ping timeout: 258 seconds]
crabbedhaloablut has joined #armbian
lemonzest has joined #armbian
stipa has quit [Ping timeout: 260 seconds]
stipa has joined #armbian
Herc has quit [Remote host closed the connection]
Herc has joined #armbian
kolla has quit [Quit: %fog relay%]
kolla has joined #armbian
xoan725451235263 has joined #armbian
xoan72545123526 has quit [Ping timeout: 268 seconds]
xoan725451235263 is now known as xoan72545123526
xoan725451235262 has joined #armbian
xoan72545123526 has quit [Ping timeout: 260 seconds]
xoan725451235262 is now known as xoan72545123526
xoan725451235269 has joined #armbian
xoan72545123526 has quit [Ping timeout: 252 seconds]
xoan725451235269 is now known as xoan72545123526
aasami_ has joined #armbian
aasami_ has quit [Quit: Lost terminal]
xoan725451235265 has joined #armbian
xoan72545123526 has quit [Ping timeout: 252 seconds]
xoan725451235265 is now known as xoan72545123526
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
xoan725451235261 has joined #armbian
Object is now known as mpmc
xoan72545123526 has quit [Ping timeout: 260 seconds]
xoan725451235261 is now known as xoan72545123526
xoan725451235269 has joined #armbian
xoan72545123526 has quit [Ping timeout: 252 seconds]
xoan725451235269 is now known as xoan72545123526
stipa_ has joined #armbian
stipa_ is now known as stipa
stipa has quit [Ping timeout: 252 seconds]
xoan725451235261 has joined #armbian
xoan72545123526 has quit [Ping timeout: 252 seconds]
xoan725451235261 is now known as xoan72545123526
quantum_ has joined #armbian
<quantum_>
Anyone know why this would ruin two SD cards, one 32GB and the other 64GB? dd if=Armbian_22.02.2_Odroidn2_jammy_current_5.10.103_xfce_desktop.img of=/dev/sda bs=4M status=progress
<quantum_>
After doing this, each now presents as having 7.43GB total.
<quantum_>
I did # dd if=/dev/zero of=/dev/sda and it says 'no more space' at 7.43GB.
<quantum_>
I went into gdisk and did an 'x' and 'z' but no change.
<[TheBug]>
quantum_: we actually went through this when you left yuesterday, the images you mention will mount successfully and work, I am thinking it may be your understanding of what you are doing that is confusing you.
<quantum_>
The first is a Sandisk and the second is a Transcend.
<[TheBug]>
um first, the image auto re-sizes the partition to match the sized of the sdcard on first boot
<[TheBug]>
this is so when we ship it to you it is a smaller file
<[TheBug]>
and so it can fit different size cards
<[TheBug]>
it is a function at boot time that will make it the full size
<quantum_>
gparted shows the SD as having a total of 7.43GB.
<Armbian-Discord>
<Tenkawa> quantum_: after that image is put on the card until it is booted it will look like that on a N2/N2+.. that's how it is suppose to look
<quantum_>
This is after zeroing the whole SD. Something is fundamentally wrong.
<clever>
quantum_: what does lsblk output?
<Armbian-Discord>
<Tenkawa> "how" are you zeroing the sd?
<Armbian-Discord>
<Tenkawa> also what clever asked
<Armbian-Discord>
<clever> the total size of the SD card shouldnt change, the extra space will turn into unallocated space
<Armbian-Discord>
<Tenkawa> @clever only after its booted
<Armbian-Discord>
<clever> he said earlier, dd if=/dev/zero of=/dev/sda
<Armbian-Discord>
<clever> even before its booted, the unused space will be reported as unused space
<Armbian-Discord>
<Tenkawa> its will "match" the image size after dd
<Armbian-Discord>
<clever> thats how partitioning works
<Armbian-Discord>
<Tenkawa> incorrect
<Armbian-Discord>
<Tenkawa> not with a predefined image
<Armbian-Discord>
<Tenkawa> and whole disk image
<Armbian-Discord>
<clever> partitioning cant change the size of sda
<Armbian-Discord>
<clever> only sda1/sda2...
<Armbian-Discord>
<Tenkawa> if you were dd to a part yes
<[TheBug]>
clever your being tricked by the question asked
<[TheBug]>
the device is a constant size
<[TheBug]>
the loop device I show in my image is smaller 6.1GB
<[TheBug]>
because it has not been burned to a device
<quantum_>
lsblk shows sda correctly as 56.4G
<[TheBug]>
so he is comparing apples and oranges
<clever>
quantum_: which device in that lsblk is the SD card?
<Armbian-Discord>
<Tenkawa> exactly
<quantum_>
/dev/sda
<clever>
quantum_: double-check, what did you run the dd to zero it against?
<quantum_>
So try to flash Armbian again?
<[TheBug]>
So my only question is have you taken the SDcard and tried to boot it?
<[TheBug]>
what happens when you try to boot?
<[TheBug]>
what does serial console look like?
<quantum_>
# dd if=/dev/zero of=/dev/sda
<quantum_>
It stopped at 7.43GB. "Out of space"
<clever>
quantum_: can you run it again, and take a screenshot of the output?
<quantum_>
Don't have a serial console connect.
<quantum_>
Run zero?
<clever>
yes
<[TheBug]>
quantum_: well I have a few things i can extract from what you have told me so far .. 1. your usine a usb to sdcard adapter to burn this as it is showing as /dev/sda and not an mmc block device like /dev/mmcblk[0-1]
<[TheBug]>
so if you are seeing weird issues first thing I would do is check your adapter
<[TheBug]>
some do weird things
<clever>
[TheBug]: ah good point, is the usb adapter SDHC compatible!
<[TheBug]>
yeah again, thats reason I say get different adapter or care reader/writer
<quantum_>
... just like the 64GB Transcend.
<[TheBug]>
cause that seems a bit funky to me
<quantum_>
I'll try a diff SD adapter which I have.
<[TheBug]>
sounds like you using some old cheap reader/writer for maybe old cards and it has some arbitrary limit
<Armbian-Discord>
<Tenkawa> try a smaller blocksize too
<Armbian-Discord>
<Tenkawa> I usually never push it higher than higher than 2M with those adapters
<quantum_>
Well I can't, it has a header connector.
<quantum_>
Not setting a bas= when zeroing.
<quantum_>
bs=
<Armbian-Discord>
<Tenkawa> you should
<Armbian-Discord>
<ManoftheSea> writing zeros to flash isn't the right way to zero it out
<quantum_>
I'll try bs=1M
<Armbian-Discord>
<ManoftheSea> you want to trim the disk, not write the whole thing
<[TheBug]>
"Most likely, your card reader can't read SDXC cards, which have capacities from 64GB to 2TB and use exFAT. Check to see if there is an SDXC logo somewhere near the card reader."
<Armbian-Discord>
<ManoftheSea> try to blkdiscard the SD
<Armbian-Discord>
<ManoftheSea> also... why are you setting a blocksize at all?
<quantum_>
It's an "Insignia" USB3 card reader/writer. No SDXC logo.
<quantum_>
Setting blocksize to speed up transfer.
<[TheBug]>
I think you have very cheap card reader/writer and it not support the media you are trying to us, it will cut at 8GB only
<[TheBug]>
use*
<[TheBug]>
and it may not write the media correctly at that size
<quantum_>
It's worked with my 128G cards until this week.
<[TheBug]>
hm? then you have some mystery wrapped in an engima
<quantum_>
Maybe that was a fluke.
<[TheBug]>
enigma*
<Armbian-Discord>
<ManoftheSea> How does the BS speed up the transfer?
<Armbian-Discord>
<ManoftheSea> This will clear the flash on the card, allowing the controller to zero it all out.
<quantum_>
I've always had trouble getting Armbian to work on my N2+, until I got help from 'unsual user' on the forum. Switching to a Fedora kernel fixed it.
<quantum_>
blkdiscard: /dev/sda: not a block device
<ArmbianHelper>
^ balenaEtcher - Flash OS images to SD cards & USB drives
<Armbian-Discord>
<ManoftheSea> we have two problems, the first is if sda isn't the right device, in which case you're dangerous to yourself for running that; the second is if sda is the right device but that's the actual error.
<[TheBug]>
he probably pulled out and reinserted the adapter so its device changed
<Armbian-Discord>
<ManoftheSea> I need a better understand of how you're doing this. What's your underlying OS? Are you using a virtual machine?
<clever>
quantum_: what does "ls -l /dev/sda" say?
<clever>
quantum_: and "df -h /dev/" ?
<quantum_>
Etcher says my "32MB" (32GB) SD is too small.
<quantum_>
-rw-r--r-- 1 root root 7980113920 Aug 30 07:52 /dev/sda
<clever>
quantum_: yep, theres your problem
<clever>
you wrote to /dev/sda when sda was not present
<clever>
so you created a FILE called sda
* [TheBug]
slow claps
<clever>
and then /dev/ ran out of space, so > and it says 'no more space' at 7.43GB.
<[TheBug]>
you sure are clever, clever
<quantum_>
OS is Debian 11. No VM.
<Armbian-Discord>
<ManoftheSea> hah.
<Armbian-Discord>
<ManoftheSea> Good find, clever
<quantum_>
Filesystem Size Used Avail Use% Mounted on
<quantum_>
udev 7.5G 7.5G 0 100% /dev
<Armbian-Discord>
<ManoftheSea> so then you need to rm /dev/sda
<Armbian-Discord>
<Tenkawa> yep
<quantum_>
meh?!
<clever>
that also explains why your dd was so blazing fast
<clever>
youve been writing to ram
<Armbian-Discord>
<Tenkawa> I had just noticed it too looking at the pastes
<quantum_>
goddam...
<Armbian-Discord>
<Tenkawa> (just lookd at them)
<Armbian-Discord>
<ManoftheSea> /dev is a temporary filesystem in memory.
mintelodiaz has joined #armbian
<[TheBug]>
quantum, when you insert the reader/writer or the sdcard, you should run 'dmesg' to see what device shows up
<[TheBug]>
if you unplug/replug a device like a card reader/writer over and over
<[TheBug]>
the actual device name will change and interate
<quantum_>
rm: remove regular file '/dev/sda'? y
<[TheBug]>
/dev/sd, sdb, sdc, etc
<Armbian-Discord>
<ManoftheSea> better still, use Etcher, which will help you to find the device as well as help prevent you from damaging other parts of your system
<[TheBug]>
not the worst idea I heard all day ^
<[TheBug]>
lol
<Armbian-Discord>
<ManoftheSea> so wait... is it possible he's just been overwriting the file in memory this whole time, and that's why the SD hasn't been changing?
<quantum_>
Un/replugged the reader, dmesg shows /dev/sda, but Etcher still thinks sda is 32MB.
<Armbian-Discord>
<clever> lsblk reports the 32gig sandisk as being 32 MB
<clever>
quantum_: thats another thing i was confused about, lsblk said it was 32mb, so why did dd say 7gig?, the file is why
<[TheBug]>
yes, file overrides the device inode
<Armbian-Discord>
<Tenkawa> Also have to watch out for gvfs trying to grab on to devices too if you have it running
<[TheBug]>
you basically plug in device,create node, then wrote a file over the node, the node wont be created again till you remove file and re-insert device
<[TheBug]>
actually I assume somewhere in there you disconnect the device first so this is why it writes the file
quantum_ has quit [Remote host closed the connection]
<[TheBug]>
I feel like we need a historian to recap this adventure
quantum_ has joined #armbian
<quantum_>
blkdiscard: /dev/sda: BLKDISCARD ioctl failed: Operation not supported
<clever>
quantum_: double-check "ls /dev/sda", is it a file or block device?
quantum_ has quit [Remote host closed the connection]
quantum_ has joined #armbian
<quantum_>
clever: brw-rw---- 1 root disk 8, 0 Aug 30 08:16 /dev/sda
<clever>
yep, it is now a block device
<clever>
i suspect that the USB adapter doesnt support discard
<quantum_>
Ok, understand. Have to order a new one.
<clever>
my laptop has a proper mmc bus, not a usb adapter
<quantum_>
... with SDXC (or whatever that was)
<clever>
so when i plug an SD card into my lattop, it shows up as /dev/mmcblk0
<Armbian-Discord>
<ManoftheSea> well, the discard isn't entirely necessary.
<Armbian-Discord>
<ManoftheSea> Maybe the controller will identify the zeros and do it internally.
<clever>
and then anything should work
<quantum_>
Unfort I don't have an SD slot in the commercial HP laptop.
<Armbian-Discord>
<ManoftheSea> But still, we want to make sure the correct device is identified when plugged in, that it isn't mounted, that the device node is created in /dev/ and then write to the SD card.
<[TheBug]>
I mean one of the things I would do if you removed the /dev/sda file and re-insterted the device and are seeing weirdness, is I would reboot because making that file and then having insetred it before could have caused some weirdness. Past that I would use a different adapter maybe?
<Armbian-Discord>
<ManoftheSea> So if it's unplugged, then remove the sda file. replug, dmesg to identify it, then gdisk to that block device.
<quantum_>
MotS I've confirmed that /dev/sda goes away when I unplug. But plug it back and it shows as 32MB.
<quantum_>
gdisk: Disk /dev/sda: 62688 sectors, 30.6 MiB
<clever>
i would say that the 32gig sandisk card has entirely failed
<clever>
and you should switch to the 64gig card, and try to image it
<quantum_>
Ok.
<Armbian-Discord>
<ManoftheSea> that's weird.
<quantum_>
More like it... Disk /dev/sda: 118374400 sectors, 56.4 GiB
<Armbian-Discord>
<ManoftheSea> I thought we had the sda file in place, such that you never wrote the 32 megs to the smaller card
<quantum_>
I did have the file, but have deleted it now, and have proven a block device.
<quantum_>
It's writing the image slowly, like god intended...
<quantum_>
Thank satan...
<quantum_>
Ok now xfce boots to the 64G SD card, but I get the ever-rotating circle, so I need to go through the exercise of 'usual user' to lay down the Fedora kernel. Then it should work.