burning flash drive with dd--fails
Why doesn't this work: dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda Here is the downloaded file in /home/doug/Downloads: -rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso Here is the fail message: dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory (Since I am IN that directory, I first tried without specifying the directory, but got the same failure.) Confused as usual--doug
On Saturday 24 July 2021, mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
MOST WORRYINGLY, the destination /dev/sda is often the first and most critical device in any system. On my system, /dev/sda is the device that contains my OpenSUSE operating system. If I were to dd to that device I would wipe out my OpenSUSE root partition. Are you VERY SURE the destination device is the correct one? I would normally write ISO's to USB-drives, and I would normally use SUSE Studio Imagewriter GUI to ease this task (the zypper package is called imagewriter). USB-drives would more likely have device names further down the alphabet, for example, I have one plugged as /dev/sdh right at this moment (the sda, sdb, sdc, .. sdh part depends on how many devices are resident in the system). (It's not necessarily wrong to use dd, but it's a command with no safeguards.) You want to be very sure of the destination before executing the dd. If in doubt, perhaps followup with another email to the list clearly stating what you are trying to achieve before proceeding further. However, if you are sure the destination is correct, I can see that the filename listed is Win10_21H1_English_x64.iso, so why have you supplied dd Win10_21H1_English_x64 without the iso suffix? The dd command could be amended to: dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64.iso of=/dev/correctdestination I WOULD NOT USE THE CORRECTED COMMAND UNLESS YOU ARE VERY VERY SURE about the destination. Michael
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
(Since I am IN that directory, I first tried without specifying the directory, but got the same failure.)
Confused as usual--doug
On July 23, 2021 at 8:12 PM Michael Hamilton <michael@actrix.gen.nz> wrote:
On Saturday 24 July 2021, mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
MOST WORRYINGLY, the destination /dev/sda is often the first and most critical device in any system. On my system, /dev/sda is the device that contains my OpenSUSE operating system. If I were to dd to that device I would wipe out my OpenSUSE root partition. Are you VERY SURE the destination device is the correct one?
Yes, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. I disconnected sda after the lightning strike, and I'll deal with it separately--it was never used, and installed on speculation that I might get ambitious and save some files to it. I may still do that, since it looks like there is some serious damage somewhere to the machine.
I would normally write ISO's to USB-drives, and I would normally use SUSE Studio Imagewriter GUI to ease this task (the zypper package is called imagewriter). USB-drives would more likely have device names further down the alphabet, for example, I have one plugged as /dev/sdh right at this moment (the sda, sdb, sdc, .. sdh part depends on how many devices are resident in the system). (It's not necessarily wrong to use dd, but it's a command with no safeguards.)
You want to be very sure of the destination before executing the dd. If in doubt, perhaps followup with another email to the list clearly stating what you are trying to achieve before proceeding further.
However, if you are sure the destination is correct, I can see that the filename listed is Win10_21H1_English_x64.iso, so why have you supplied dd Win10_21H1_English_x64 without the iso suffix? The dd command could be amended to:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64.iso of=/dev/correctdestination
Note that I had disconnected ssd /dev/sda. I used fdisk to determine what the usb stick was called, and it said sda. History (in part): 104 2021-07-22 02:00:37 fdisk -l 105 2021-07-22 02:11:34 smartctl -c/dev/nvme)n1 106 2021-07-22 02:12:36 smartctl -c/dev/nvme0n1 107 2021-07-22 02:13:02 smartctl -h 108 2021-07-22 02:18:09 smartctl --all /dev/sda 109 2021-07-22 02:20:43 smartctl --all /dev//dev/nvme0n1 110 2021-07-22 02:21:02 smartctl -h I was not aware of ImageWriter, but I will install it and run it--I'm not a fan of dd either, altho I have used it once or twice, under the tutelage of some other correspondent. Thanx for the information. I hope I will remember some of it; thanx to the lightning there are problems with this machine and one of them is that it cannot see any printer. Or anything else on the net except the router. (An also damaged laptop cannot do mail anymore, but can print! What a mess! I have ordered a cheapie refurb desktop to tide me over until I get things back in some kind of working order. --doug
I WOULD NOT USE THE CORRECTED COMMAND UNLESS YOU ARE VERY VERY SURE about the destination.
Michael
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
(Since I am IN that directory, I first tried without specifying the directory, but got the same failure.)
Confused as usual--doug
On Saturday 24 July 2021, mcgarrett wrote:
Note that I had disconnected ssd /dev/sda. I used fdisk to determine what the usb stick was called, and it said sda. History (in part):
If you need a way to do a quick check of what drives are connected to what device names, the lsscsi command is probably the easiest. For example, on my system: % lsscsi [0:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sda [1:0:0:0] disk ATA Samsung SSD 860 3B6Q /dev/sdb [2:0:0:0] disk ATA ST3000DM008-2DM1 CC26 /dev/sdc [3:0:0:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdd [6:0:0:0] disk Generic- USB3.0 CRW -0 1.00 /dev/sde [6:0:0:1] disk Generic- USB3.0 CRW -1 1.00 /dev/sdf [6:0:0:2] disk Generic- USB3.0 CRW -2 1.00 /dev/sdg [7:0:0:0] disk JetFlash Transcend 16GB 1100 /dev/sdh So my 16GB Transend stick is definitely /dev/sdh One nice thing about imagewriter is that it will only allow you to pick usb-drives. Best of luck with the lightning recovery. Michael
On July 23, 2021 at 10:05 PM Michael Hamilton <michael@actrix.gen.nz> wrote:
On Saturday 24 July 2021, mcgarrett wrote:
Note that I had disconnected ssd /dev/sda. I used fdisk to determine what the usb stick was called, and it said sda. History (in part):
If you need a way to do a quick check of what drives are connected to what device names, the lsscsi command is probably the easiest. For example, on my system:
% lsscsi [0:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sda [1:0:0:0] disk ATA Samsung SSD 860 3B6Q /dev/sdb [2:0:0:0] disk ATA ST3000DM008-2DM1 CC26 /dev/sdc [3:0:0:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdd [6:0:0:0] disk Generic- USB3.0 CRW -0 1.00 /dev/sde [6:0:0:1] disk Generic- USB3.0 CRW -1 1.00 /dev/sdf [6:0:0:2] disk Generic- USB3.0 CRW -2 1.00 /dev/sdg [7:0:0:0] disk JetFlash Transcend 16GB 1100 /dev/sdh
So my 16GB Transend stick is definitely /dev/sdh
One nice thing about imagewriter is that it will only allow you to pick usb-drives.
doug@linux1:~> lsscsi [4:0:0:0] cd/dvd HL-DT-ST DVDRAM GP08LU11 KX01 /dev/sr0 [5:0:0:0] disk VendorCo ProductCode 2.00 /dev/sda Now I'm even more confused. Several apps (including gParted, which has disappeared) say that the ssd is /dev/nvme0n1, but this app says it's /dev/sda. As I mentioned before, the drive that I was sure was called /dev/sda, an was add-on ssd. But the machine is all out of whack. In the meantime, I can't install imagewriter--it's a repo problem, apparently. I hope the temporary computer I ordered comes soon! When it does, I will try to reinstall everything and see what happens. --doug --doug
Best of luck with the lightning recovery.
Michael
On Sunday 25 July 2021, mcgarrett wrote:
..
doug@linux1:~> lsscsi [4:0:0:0] cd/dvd HL-DT-ST DVDRAM GP08LU11 KX01 /dev/sr0 [5:0:0:0] disk VendorCo ProductCode 2.00 /dev/sda
Now I'm even more confused. Several apps (including gParted, which has disappeared) say that the ssd is /dev/nvme0n1, but this app says it's /dev/sda. As I mentioned before, the drive that I was sure was called /dev/sda, an was add-on ssd. But the machine is all out of whack. In the meantime, I can't install imagewriter--it's a repo problem, apparently. ..
I don't have any nvme devices, so I'm not really in a good position to advise you. I think it may be that a device may be listed in both the NVME space and the SCSI space, I guess this is similar to what happens with USB, for USB lsusb will have an listing for the device and lsscsi will also have a listing. I see that lsscsi -v appears to try to list NVME devices, so that may provide more info. Then there is lsblk which will provide yet more info from the perspective of block device, including the structure of each sd device, for example: % lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232.9G 0 disk ├─sda1 8:1 0 500M 0 part /boot/efi ├─sda2 8:2 0 60G 0 part / ├─sda3 8:3 0 60G 0 part ├─sda4 8:4 0 96G 0 part └─sda5 8:5 0 16.4G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk └─sdb1 8:17 0 1.8T 0 part /home sdc 8:32 0 2.7T 0 disk ├─sdc1 8:33 0 2.6T 0 part /mnt/backup └─sdc2 8:34 0 101.4G 0 part /mnt/osbackup sdd 8:48 0 3.6T 0 disk └─sdd1 8:49 0 3.6T 0 part Michael
On July 23, 2021 at 11:13 PM James Knott <james.knott@jknott.net> wrote:
On 2021-07-23 9:47 p.m., mcgarrett wrote:
Note that I had disconnected ssd /dev/sda. I used fdisk to determine what the usb stick was called, and it said sda. History (in part):
What device does the mount command show everything is mounted on?
After almost a page of stuff, it comes up with /dev/nvme0n1p5 on /.snapshots type btrfs (rw,relatime,ssd,space_cache,subvolid=266,subvol=/@/.snapshots) /dev/nvme0n1p5 on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=265,subvol=/@/boot/grub2/i386-pc) /dev/nvme0n1p5 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=264,subvol=/@/boot/grub2/x86_64-efi) /dev/nvme0n1p5 on /home type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/home) /dev/nvme0n1p5 on /opt type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/opt) /dev/nvme0n1p5 on /root type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/root) /dev/nvme0n1p5 on /srv type btrfs (rw,relatime,ssd,space_cache,subvolid=260,subvol=/@/srv) /dev/nvme0n1p5 on /tmp type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/tmp) /dev/nvme0n1p5 on /usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/usr/local) /dev/nvme0n1p5 on /var type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@/var) /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) I remember /dev/nvme0p1, not ..p5. Don't know what this indicates. I think it is time for me to quit trying to diagnose this thing until I have a working machine to use, and I will reformat and reinstall and then see if I still have obvious problems. Thanx to all who have contributed; I will stop beating the dead horse now! --doug
Op zaterdag 24 juli 2021 03:47:47 CEST schreef mcgarrett:
es, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. Not some 'crazy' name. most likely nvme.....
Fot the rest: look at Ventoy, it seems a good tool to create bootable Windows install USBs -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 2021-07-23 9:20 p.m., Knurpht-openSUSE wrote:
Op zaterdag 24 juli 2021 03:47:47 CEST schreef mcgarrett:
es, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. Not some 'crazy' name. most likely nvme.....
Fot the rest: look at Ventoy, it seems a good tool to create bootable Windows install USBs
Imagewriter won't?
On July 23, 2021 at 11:47 PM Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2021-07-23 9:20 p.m., Knurpht-openSUSE wrote:
Op zaterdag 24 juli 2021 03:47:47 CEST schreef mcgarrett:
es, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. Not some 'crazy' name. most likely nvme.....
Fot the rest: look at Ventoy, it seems a good tool to create bootable Windows install USBs
Imagewriter won't?
Apparently there's a problem with a repo to install Imagewriter. "Please check if the URIs defined for this repository are pointing to a valid repository." --doug
On 2021-07-24 3:09 p.m., mcgarrett wrote:
On July 23, 2021 at 11:47 PM Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2021-07-23 9:20 p.m., Knurpht-openSUSE wrote:
Op zaterdag 24 juli 2021 03:47:47 CEST schreef mcgarrett:
es, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. Not some 'crazy' name. most likely nvme.....
Fot the rest: look at Ventoy, it seems a good tool to create bootable Windows install USBs
Imagewriter won't?
Apparently there's a problem with a repo to install Imagewriter. "Please check if the URIs defined for this repository are pointing to a valid repository." --doug
There is nothing wrong with that repository. It is (or should be) the main repository for your version. The URI for the main repository looks like this: http://download.opensuse.org/distribution/leap/$releasever/repo/oss/ where %releasever is the version number of your installed system, eg 15.2 or whatever. You can verify that URI on your system in YaST/Software Repositories.
On 24/07/2021 23.09, mcgarrett wrote:
On July 23, 2021 at 11:47 PM Darryl Gregorash <raven@accesscomm.ca> wrote: On 2021-07-23 9:20 p.m., Knurpht-openSUSE wrote:
Op zaterdag 24 juli 2021 03:47:47 CEST schreef mcgarrett:
es, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. Not some 'crazy' name. most likely nvme.....
Fot the rest: look at Ventoy, it seems a good tool to create bootable Windows install USBs
Imagewriter won't?
Apparently there's a problem with a repo to install Imagewriter. "Please check if the URIs defined for this repository are pointing to a valid repository."
Doug, you only have to tell yast to install it. Click, click, click. Or, the hard way: zypper install imagewriter That's all. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On July 23, 2021 at 11:20 PM Knurpht-openSUSE <knurpht@opensuse.org> wrote:
Op zaterdag 24 juli 2021 03:47:47 CEST schreef mcgarrett:
es, I am sure. sda was a 2nd ssd. Don't ask me how come the installed drive is this crazy name, but it is. Not some 'crazy' name. most likely nvme.....
Fot the rest: look at Ventoy, it seems a good tool to create bootable Windows install USBs
Will do. Thanx! --doug
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 2021-07-23 5:23 p.m., mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
(Since I am IN that directory, I first tried without specifying the directory, but got the same failure.)
Confused as usual--doug
If you want to write an ISO image to USB, you should use Imagewriter, which is designed to do just that. It's in the main repository. What Michael Hamilton said about your choice of the target for your proposed write also concerns me: It is quite unlikely that your USB stick is /dev/sda -- impossible, I would think.
On 7/23/21 3:23 PM, mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
Yep, makes perfect sense. You tried to use Win10_21H1_English_x64 The file name is Win10_21H1_English_x64.iso
On 2021-07-23 9:56 p.m., Bill Swisher wrote:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
Yep, makes perfect sense. You tried to use Win10_21H1_English_x64 The file name is Win10_21H1_English_x64.iso
I was wondering about that too. For that reason, I use filename completion to get the exact name. Just type in enough characters to identify the file and then press tab.
On July 23, 2021 at 11:15 PM James Knott <james.knott@jknott.net> wrote:
On 2021-07-23 9:56 p.m., Bill Swisher wrote:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
Yep, makes perfect sense. You tried to use Win10_21H1_English_x64 The file name is Win10_21H1_English_x64.iso
I was wondering about that too. For that reason, I use filename completion to get the exact name. Just type in enough characters to identify the file and then press tab.
Wow! Wish I'd known about that before! The 'IX folks have come up with a winner! Thanx--doug
I have always used unetbootin. Its been around since perhaps SuSE 10.0 You run it as root from the command line. CWSIV On Fri, 2021-07-23 at 19:23 -0400, mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: f
____________________________________________________________ Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more Taliban Slaying of Online Comic Sparks Anger, Apprehension http://thirdpartyoffers.juno.com/TGL3131/6104f4cda6ab274cd6610st03duc1 Justice Decides Against Trump on Tax Returns http://thirdpartyoffers.juno.com/TGL3131/6104f4cdc9f5774cd6610st03duc2 'Sobering' Findings After Partying in Provincetown http://thirdpartyoffers.juno.com/TGL3131/6104f4cded5b574cd6610st03duc3
I have come across "balenaEtcher". On 7/31/21 1:58 AM, Carl Spitzer {L Juno} wrote:
I have always used unetbootin. Its been around since perhaps SuSE 10.0 You run it as root from the command line.
CWSIV
On Fri, 2021-07-23 at 19:23 -0400, mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: f
____________________________________________________________
Top News - Sponsored By Newser <https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more>
* *Taliban Slaying of Online Comic Sparks Anger, Apprehension* <http://thirdpartyoffers.juno.com/TGL3132/6104f4cda6ab274cd6610st03duc1> * *Justice Decides Against Trump on Tax Returns* <http://thirdpartyoffers.juno.com/TGL3132/6104f4cdc9f5774cd6610st03duc2> * *'Sobering' Findings Af ter Partying in Provincetown* <http://thirdpartyoffers.juno.com/TGL3132/6104f4cded5b574cd6610st03duc3>
On 2021-07-23 7:23 p.m., mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
All else being equal, I'd trace the actual operation of system calls using "STRACE(1)" but 9a) that may no be available to you yet, and (b) what enlightenment it gives may not be useful or intelligible to you. nevertheless, its a start at looking "under the hood". -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg
On 31/07/2021 14.37, Anton Aylward wrote:
On 2021-07-23 7:23 p.m., mcgarrett wrote:
Why doesn't this work:
dd bs=4M if=/home/doug/Downloads/Win10_21H1_English_x64 of=/dev/sda
Here is the downloaded file in /home/doug/Downloads:
-rw-r--r-- 1 doug users 5824122880 Jul 22 22:20 Win10_21H1_English_x64.iso
Here is the fail message:
dd: failed to open '/home/doug/Downloads/Win10_21H1_English_x64': No such file or directory
All else being equal, I'd trace the actual operation of system calls using "STRACE(1)" but 9a) that may no be available to you yet, and (b) what enlightenment it gives may not be useful or intelligible to you. nevertheless, its a start at looking "under the hood".
You are late to the game :-P He simply forgot to write the .iso extension on the dd command. The command is telling the stark truth: file '/home/doug/Downloads/Win10_21H1_English_x64' truly does not exist. -- Saludos/Cheers Carlos E. R.
participants (11)
-
-pj -
Anton Aylward -
Bill Swisher -
Carl Spitzer {L Juno} -
Carlos E. R. -
Carlos E.R. -
Darryl Gregorash -
James Knott -
Knurpht-openSUSE -
mcgarrett -
Michael Hamilton