Re: Write an install image to a flash drive?
>> On Aug 20, 2019, at 9:47 PM, Bob Bernstein wrote: >> >> On Tue, Aug 20, 2019 at 09:31:00PM -0400, Bob Bernstein wrote: >> >> I'm wondering: was there any preparation of the flash drive >> that should have been done before dd'ing the install-image.img >> onto it? Formatting? Filesystem? MBR? > > The above bit of speculation was inspired by this wiki article: > > https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/ > > > -- > What can be asserted without evidence can be > dismissed without evidence. >Hitchens' Razor I just did an install of 8.1 and all I did was dd the img file to a flash drive (I also used amd64). My guess is there’s something wrong with the image or your flash drive. Do you have another flash drive to test with? Also, is there an easy way to remove the first 2048 sectors from the image so the FFS part could be mounted using a vnd device? Or would this work without making changes? vnconfig -c /dev/vnd0 install.img mount /dev/vnd0a /mnt If the above works it would verify the image is correct. I’ll test in the AM if no one answers. Jason M.
Re: Write an install image to a flash drive?
On Tue, Aug 20, 2019 at 09:31:00PM -0400, Bob Bernstein wrote: > I'm wondering: was there any preparation of the flash drive > that should have been done before dd'ing the install-image.img > onto it? Formatting? Filesystem? MBR? The above bit of speculation was inspired by this wiki article: https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/ -- What can be asserted without evidence can be dismissed without evidence. Hitchens' Razor
Re: Write an install image to a flash drive?
On Tue, Aug 20, 2019 at 08:18:59PM -0400, Ron Georgia wrote: > ...you find a section labeled "Booting the install system from > USB." Section 2.2.6.1 to be exact. Once the image is > downloaded, from the command line prompt: Ach! Dawn breaks over Narrangansett Bay! > What platform are you using to create the USB install device? > Mac? Linux? NetBSD (my personal favorite)? I am doing all this on the netbsd system I want to upgrade. Thank you (and Robert too for his note) -- What can be asserted without evidence can be dismissed without evidence. Hitchens' Razor
Re: Write an install image to a flash drive?
Date:Tue, 20 Aug 2019 17:59:56 -0400 From:Bob Bernstein Message-ID: <20190820215955.GA819@nebby.localdomain> | Trying 'mount /dev/sd1' /mnt yielded "bad superblock." (Pretty | sure; I am typing these results from memory.) It is pretending to be a CD (image anyway) so you would need mount -t cd9660 -r /dev/sd1 /mnt | I _can't imagine_ how many stupid things I just did, but could | someone please tell me how to get that install image onto the | flash drive in a form that will boot? You cannot. "That" image is in ISO format, which have a booting method unique in the universe. You need an image set up for booting from a memory stick, which is much more similar to a regular drive than a CD (ISO format).Someone else will have to tell you which is the right image to use, but it isn't that one. kre
Re: Write an install image to a flash drive?
I would grab either 9BETA image or current. Get the image that ends with .img.gz. For example: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/images/NetBSD-9.0_BETA-amd64-install.img.gz Then, according to the NetBSD guide (page 5 if you printed out all 365 pages, as I did) you find a section labeled "Booting the install system from USB." Section 2.2.6.1 to be exact. Once the image is downloaded, from the command line prompt: $ gunzip NetBSD-9.0_BETA-amd64-install.img.gz $ dd if=NetBSD-9.0_BETA-amd64-install.img of=/dev/sd0 bs=2m Of course, substitute /dev/sd0 with whatever your USB device is. I noticed that the manual uses a block size of 2m instead of one; however, I do not believe using bs=1m or bs=2m will make a difference. What platform are you using to create the USB install device? Mac? Linux? NetBSD (my personal favorite)? On 8/20/19, 7:19 PM, "Bob Bernstein" wrote: I want to use a flash drive instead of a CD to upgrade from an old 'current' to our latest. This is being done on an ancient emachine amd64: NetBSD nebby 8.99.35 NetBSD 8.99.35 (GENERIC) #0: Wed Mar 13 06:27:34 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 I am new to flash drives. I did the following with a new Kingston 64GB right out of its FedEx mailing envelope: dd if=boot.iso of=/dev/rsd1d bs=1m The boot.iso was: http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/installation/cdrom/boot.iso Rebooting the emachine, it gave me a choice to boot from the Kingston, but there was no joy in Mudville. All attempts reverted to booting normally from the hd. Trying 'mount /dev/sd1' /mnt yielded "bad superblock." (Pretty sure; I am typing these results from memory.) I _can't imagine_ how many stupid things I just did, but could someone please tell me how to get that install image onto the flash drive in a form that will boot? Thank you -- What can be asserted without evidence can be dismissed without evidence. Hitchens' Razor
Write an install image to a flash drive?
I want to use a flash drive instead of a CD to upgrade from an old 'current' to our latest. This is being done on an ancient emachine amd64: NetBSD nebby 8.99.35 NetBSD 8.99.35 (GENERIC) #0: Wed Mar 13 06:27:34 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 I am new to flash drives. I did the following with a new Kingston 64GB right out of its FedEx mailing envelope: dd if=boot.iso of=/dev/rsd1d bs=1m The boot.iso was: http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/installation/cdrom/boot.iso Rebooting the emachine, it gave me a choice to boot from the Kingston, but there was no joy in Mudville. All attempts reverted to booting normally from the hd. Trying 'mount /dev/sd1' /mnt yielded "bad superblock." (Pretty sure; I am typing these results from memory.) I _can't imagine_ how many stupid things I just did, but could someone please tell me how to get that install image onto the flash drive in a form that will boot? Thank you -- What can be asserted without evidence can be dismissed without evidence. Hitchens' Razor
Re: wd pb: atactl standby, smart and errors
On 2019-08-20 12:52, tlaro...@polynum.com wrote: BTW, I read in the PR that the diff for 7.x was applied to 8.x but didn't get to current? It did, but apparently other changes to the driver undid its effect. Cheerio, hauke -- The ASCII Ribbon CampaignHauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344
Re: wd pb: atactl standby, smart and errors
On Tue, Aug 20, 2019 at 11:01:55AM +0200, Hauke Fath wrote: > On 2019-08-20 10:37, tlaro...@polynum.com wrote: > >Reported problems are like this: > > > >[ 51498.493926] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 > >bn 8740546; cn 8671 tn 2 sn 52), xfer 12f0, retry 0 > >[ 51498.503930] wd0: (uncorrectable data error) > > Sounds familiar - see kern/49457... Thank you for the pointer. Yes that sounds familiar but in my case I was setting the more "conservative" standby mode. So it seems that the error messages are "normal" (the time the disk goes back) at least when invoking SMART. BTW, I read in the PR that the diff for 7.x was applied to 8.x but didn't get to current? Best, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: wd pb: atactl standby, smart and errors
On 2019-08-20 10:37, tlaro...@polynum.com wrote: Reported problems are like this: [ 51498.493926] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 bn 8740546; cn 8671 tn 2 sn 52), xfer 12f0, retry 0 [ 51498.503930] wd0: (uncorrectable data error) Sounds familiar - see kern/49457... Cheerio, hauke -- The ASCII Ribbon CampaignHauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344
wd pb: atactl standby, smart and errors
Hello, Node: NetBSD 9.99.7/evbarm (earmv7hf, a20-olinuxino-lime2) disk: wd0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags) w/PRIO wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags) w/PRIO (In the dmesg above, two last lines, why the "NCQ (32 tags)" in one line, and "NCQ (31 tags)" in the next?) It shall be noted that this is an old disk I'm using for tests, so hardware problems are not excluded. Description: I was compiling packages on the node, the bulk of the work being done on memory (pkgsrc workdir allocated via tmpfs) only the binary packages being written on the wd disk (pkgsrc is also on disk, read-only). Since the disk was scarcely used, I set: # atactl wd0 setstandby 120 The ARM SoC has a SATA III connector and the disk is thus attached with a eSATA <-> SATA cable, the disk being physically in an external enclosure with USB or eSATA connectivity, the eSATA being used. Since neither the SoC nor the enclosure has fans, I have launched a bulk building during the night that could annoy nobody. (Just to say that I'm seeing the whole messages today and did not get the opportunity to see messages appearing individually to understand if a first error was caused by the disk sleeping, time for it to wake up or if error messages were repeated on a sufficiently long period to rule at sleeping diks problem.) Reported problems are like this: [ 51498.493926] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 bn 8740546; cn 8671 tn 2 sn 52), xfer 12f0, retry 0 [ 51498.503930] wd0: (uncorrectable data error) [ 51502.065095] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 bn 8740546; cn 8671 tn 2 sn 52), xfer 12f0, retry 1 [ 51502.075102] wd0: (uncorrectable data error) (same until retry 4) then [ 51516.577931] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 bn 8740546; cn 8671 tn 2 sn 52) [ 51516.587933] wd0: (uncorrectable data error) [ 51516.587933] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 bn 8740546; cn 8671 tn 2 sn 52) [ 51519.718148] wd0c: error reading fsbn 8740546 of 8740546-8740577 (wd0 bn 8740546; cn 8671 tn 2 sn 52), xfer 12f0, retry 0 [ 51519.728148] wd0: (uncorrectable data error) [ 51522.598338] wd0: soft error (corrected) xfer 12f0 Question: can this be linked with the power status (disk sleeping; driver retrying until command served?). I noticed too that if I query the SMART status, the first command failed with "time out"; a second command can fail with "SMART not enabled" while a third (sometimes the second depending on the time between the commands) succeeds. Which I attribute to the standby setting too. So what are the interactions between (idle, standby, sleep---not selected since man page says to use it with caution) and reading/writing? Can the errors be ignored and are just soft errors due to delay repowering up the disk and are the powering states reliable datawise? TIO, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
