You are not logged in.
Hi,
I want to upgrade from Helium to Boron. I made an attempt to make a bootable flash drive. But it failed multiple times for different reasons. My main question at this point is why dd can't write to exfat? Flash drive (4MB) is old. So is my netbook (eeepc 1000 asus). Way down below in the command line I changed 'bs=16M' (as per Debian instructions) to bs=4M because the old flash drive is just 4MB. What should I do?
###
### checksum .iso file
###
wlff@helium:~/Downloads$ sudo sha256sum boron-1-240124-i386.hybrid.iso
[sudo] password for wlff:
143bca297906898fd6acb6c2013511865faf8e4b8348fc619b52fcba672f129a boron-1-240124-i386.hybrid.iso
###
### verifying sha256sum.txt bunsenlabs.org >> seems okay
###
143bca297906898fd6acb6c2013511865faf8e4b8348fc619b52fcba672f129a boron-1-240124-i386.hybrid.iso
###
### extracting .iso (source: wiki.debian.org)
###
wlff@helium:~/Downloads$ 7z x -oextract_isofile -i\!pool/main boron-1-240124-i386.hybrid.iso
7-Zip [32] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,2 CPUs Intel(R) Atom(TM) CPU N270 @ 1.60GHz (106C2),ASM)
Scanning the drive for archives:
1 file, 1306066944 bytes (1246 MiB)
Extracting archive: boron-1-240124-i386.hybrid.iso
--
Path = boron-1-240124-i386.hybrid.iso
Type = Iso
Physical Size = 1306066944
Created = 2024-01-24 04:16:55
Modified = 2024-01-24 04:16:55
Everything is Ok
Folders: 104
Files: 99
Size: 97554700
Compressed: 1306066944
###
### checking contents iso file
###
wlff@helium:/media/wlff/BUNSENLABS_BORON$ ls -l
total 85
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 boot
-r--r--r-- 1 wlff wlff 20 Jan 24 2024 bunsen_version
lr-xr-xr-x 1 wlff wlff 1 Jan 24 2024 debian -> .
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 dists
dr-xr-xr-x 1 wlff wlff 10240 Jan 24 2024 firmware
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 install
dr-xr-xr-x 1 wlff wlff 4096 Jan 24 2024 isolinux
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 live
-r--r--r-- 1 wlff wlff 198 Jan 24 2024 md5sum.README
-r--r--r-- 1 wlff wlff 56623 Jan 24 2024 md5sum.txt
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 pool
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 pool-udeb
dr-xr-xr-x 1 wlff wlff 2048 Jan 24 2024 tools
###
### flash drive mounts automatically showing twice (2) in the file manager!. Error when ejecting flash drive
###
Error mounting /dev/sdb1 at /media/wlff/BUNSENLABS_BORON: Command-line `mount -t "iso9660" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500" "/dev/sdb1"
"/media/wlff/BUNSENLABS_BORON"' exited with non-zero exit status 32:
mount: /dev/sdb1 is already mounted or /media/wlff/BUNSENLABS_BORON busy
###
### In Windows10 I reformated Kingston_4G to exfat file type
### (I think it was listed as NTFS priviously, not sure)
### and I tried to copy Boron installation files onto it.
### Empty flash drive showing folder "System Volume Information",
### holding 2 files IndexerVolumeGuid and WPSettings.dat
### But now dd can't open /dev/sdc1 nor write to it
###
wlff@helium:~$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ext4 f901a9bf-971e-4cfc-9ba8-ace69923d499 /
├─sda2
└─sda5 swap f2a317c1-9467-4c4c-a7b9-37799a215f27 [SWAP]
sdc
└─sdc1 exfat Kingston_4G 40AF-0991 /media/wlff/Kingston_
wlff@helium:~/Downloads$ sudo dd if=boron-1-240124-i386.hybrid.iso of=dev/sdc1 bs=4M status=progress oflag=sync
[sudo] password for wlff:
dd: failed to open 'dev/sdc1': No such file or directory
Last edited by maurits (2025-01-09 17:31:30)
Offline
I forgot to type the preceding slash > /dev/sdc1
Now dd is copying -)
Last edited by maurits (2025-01-09 17:44:02)
Offline
Unfortunately no files got written to the flash drive. After ejecting flash drive does not automount anymore.
I still have a problem.
Offline
why dd can't write to exfat?
Go ahead and format it fat32; dd destroys that anyway.
sudo dd if=boron-1-240124-i386.hybrid.iso of=dev/sdc1 bs=4M status=progress oflag=sync
Don't use the partition number "of=/dev/sdc"
You must unlearn what you have learned.
-- yoda
Offline
I changed to another pendrive named SanDisk_16G. Still no luck.
wlff@helium:~/Downloads$ sudo dd if=boron-1-240124-i386.hybrid.iso of=/dev/sdb bs=4M status=progress
[sudo] password for wlff:
1304428544 bytes (1.3 GB, 1.2 GiB) copied, 172.605 s, 7.6 MB/s
311+1 records in
311+1 records out
1306066944 bytes (1.3 GB, 1.2 GiB) copied, 172.865 s, 7.6 MB/s
wlff@helium:~/Downloads$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ext4 f901a9bf-971e-4cfc-9ba8-ace69923d499 /
├─sda2
└─sda5 swap f2a317c1-9467-4c4c-a7b9-37799a215f27 [SWAP]
sdb iso9660 BUNSENLABS_BORON 2024-01-24-03-16-55-00
└─sdb1 vfat SANDISK_16G 9466-CAF8 /media/wlff/SANDISK_16G
###
### after ejecting and reinserting pendrive status has changed to iso9660
### also device does not show in file manager
###
wlff@helium:~$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ext4 f901a9bf-971e-4cfc-9ba8-ace69923d499 /
├─sda2
└─sda5 swap f2a317c1-9467-4c4c-a7b9-37799a215f27 [SWAP]
sdb iso9660 BUNSENLABS_BORON 2024-01-24-03-16-55-00
└─sdb1 iso9660 BUNSENLABS_BORON 2024-01-24-03-16-55-00
dd command is destroying vfat file format as well. No data are written to SanDisk. What should I do?
Last edited by maurits (2025-01-10 20:55:13)
Offline
This what dd
does. It totally rewrites the USB drive. It is correct the output of lsblk -f
Did you set the computer to boot from USB (in BIOS) and try to boot it? It should work. I once had an old eeepc 7 inch and it worked, that was a long time ago.
You should be able to reformat the usb drive later on after you have successfully installed boron with gparted
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
Current boot priority in BIOS show:
[Removable Dev.]
[HDD]
[CD-ROM]
In the right pane it says that a device enclosed in parenthesis has been diabeled. So it looks all three devices have been disabeled, which cannot be true since startup uses HDD every time. This doesn't make sense. I assume USB pen drive will get recognized as Removable Dev.
Also flash drive SanDisk_16G contains no data after dd-ing. Dd says it is copying all data to /dev/sdb but no confirmation of writing data to disk. Indeed no data got written to SanDisk.
I did figure out why file manager lists two flash drives when inserting one pen drive. The other drive is a multi flash reader sitting flush within the casing of the Asus netbook. I did not notice that at first. I haven't been using the netbook after Helium got released.
Last edited by maurits (2025-01-10 23:15:05)
Offline
I found some new information. https://support.siliconmechanics.com/po … e-using-dd. My process does not end with a single 0 on the last line. Which means data does not get written to disk.
As per other tips from the internet I umounted the flash drive before dd-ing Boron onto it. No luck with that either.
In /var/log/messges I tried to actively monitor what happens during dd-ing. The pen drive connecting gets properly recorded. But nothing about dd process.
wlff@helium:/var/log$ sudo tail -f messages
Jan 12 14:40:01 helium kernel: [ 3094.277660] scsi host3: usb-storage 1-2:1.0
Jan 12 14:40:02 helium kernel: [ 3095.297619] scsi 3:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
Jan 12 14:40:02 helium kernel: [ 3095.301285] sd 3:0:0:0: [sdc] 7856128 512-byte logical blocks: (4.02 GB/3.75 GiB)
Jan 12 14:40:02 helium kernel: [ 3095.302424] sd 3:0:0:0: [sdc] Write Protect is off
Jan 12 14:40:02 helium kernel: [ 3095.305413] sd 3:0:0:0: Attached scsi generic sg2 type 0
Jan 12 14:40:02 helium kernel: [ 3095.437604] sdc: sdc1
Jan 12 14:40:02 helium kernel: [ 3095.441365] sd 3:0:0:0: [sdc] Attached SCSI removable disk
Jan 12 14:41:33 helium upowerd[833]: energy 28.509600 bigger than full 28.450800
Jan 12 14:43:33 helium upowerd[833]: energy 28.543200 bigger than full 28.509600
Jan 12 14:44:55 helium kernel: [ 3388.213649] perf: interrupt took too long (6315 > 6293), lowering kernel.perf_event_max_sample_rate to 31500
Jan 12 14:45:33 helium upowerd[833]: energy 28.845600 bigger than full 28.543200
Jan 12 14:46:19 helium kernel: [ 3473.076351] sdc: sdc1
Where do I find more info on why nothing gets written to my several lash drives?
Offline
I used the cp command this time to write to /dev/sdc. Does it look like the installation files are all there?
Device sdb is a multi flash reader 128GB (micro sd). Strangely 100% use with only 1.3G data on it.
Device sdc is a pen drive 4GB (which was my target drive this time).
root@helium:/media/usb-drive# ls -al
total 93
dr-xr-xr-x 1 root root 2048 Jan 24 2024 .
drwxr-xr-x 5 root root 4096 Jan 12 22:26 ..
dr-xr-xr-x 1 root root 2048 Jan 24 2024 boot
-r--r--r-- 1 root root 20 Jan 24 2024 bunsen_version
lr-xr-xr-x 1 root root 1 Jan 24 2024 debian -> .
dr-xr-xr-x 1 root root 2048 Jan 24 2024 .disk
dr-xr-xr-x 1 root root 2048 Jan 24 2024 dists
dr-xr-xr-x 1 root root 10240 Jan 24 2024 firmware
dr-xr-xr-x 1 root root 2048 Jan 24 2024 install
dr-xr-xr-x 1 root root 4096 Jan 24 2024 isolinux
dr-xr-xr-x 1 root root 2048 Jan 24 2024 live
-r--r--r-- 1 root root 198 Jan 24 2024 md5sum.README
-r--r--r-- 1 root root 56623 Jan 24 2024 md5sum.txt
dr-xr-xr-x 1 root root 2048 Jan 24 2024 pool
dr-xr-xr-x 1 root root 2048 Jan 24 2024 pool-udeb
dr-xr-xr-x 1 root root 2048 Jan 24 2024 tools
root@helium:/media/usb-drive# df -h
Filesystem Size Used Avail Use% Mounted on
udev 485M 0 485M 0% /dev
tmpfs 100M 4.9M 95M 5% /run
/dev/sda1 14G 4.9G 8.2G 38% /
tmpfs 499M 0 499M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 499M 0 499M 0% /sys/fs/cgroup
tmpfs 100M 4.0K 100M 1% /run/user/109
tmpfs 100M 16K 100M 1% /run/user/1000
/dev/sdb1 1.3G 1.3G 0 100% /media/wlff/BUNSENLABS_BORON
/dev/sdc1 1.3G 1.3G 0 100% /media/usb-drive
Last edited by maurits (2025-01-13 01:42:56)
Offline