Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.ubuntu    |    I preferred Xubuntu, seemed a bit faster    |    134,474 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 133,455 of 134,474    |
|    Paul to All    |
|    Re: need a dd copy line to zero fill thi    |
|    12 Oct 23 02:37:28    |
      From: nospam@needed.invalid              On 10/11/2023 4:04 PM, bilsch01 wrote:       > On 10/10/2023 6:59 PM, Mike Easter wrote:       >> bilsch01 wrote:       >>> Windows wont format the drive because it says it's read only, however       DISKPART tells me it's not read only. Can't I just zero fill it and start over?       >>       >> Rufus 'ordinary' (quick, not quick, and check for bad blocks - but not       zero) format will probably (highly likely) format it. If I want to zero you       could use diskpart after rufus formats it.       >>       >> Personally, I would just Rufus quick, not not-quick, not check bad blocks       and not zero.       >>       >> Rufus is Win, small, free, and doesn't need install. It is also VERY good       Win tool for writing linux .iso/s to USB more than one way; hybrid or       dd-style. And can even do a form of persistence for some .iso/s.       >>       > I had looked at Rufus to start with, however it seemed Rufus didn't like the       flash drive, so I decided to zero fill it - which I just did. Next I used       current version of Rufus off of the web to make the drive a       > Ubuntu 22.04.03 installer using the downloaded Ubuntu iso. That worked, but       Rufus warned that maybe the version of Grub (that Rufus would use) might not       be absolutely compatible with the installer. I went ahead anyway. The drive       boots the 'Try Ubuntu'        option fine. But maybe a system installed with the drive might have a Grub       problem. I decided I won't use the installer to install right now.       >       > The reason I'm doing all this is I want to delete the SWAP partition I put       on my HDD when I installed my 20.04 system, and I heard that current version       of Ubuntu uses a SWAP file instead. There is a SWAP file even on my 20.04       system, but I have        concerns. I wrote a post on       > comp.sys.ibm.pc.hardware.storage       > about that.       >       > Thanks for your answer about Rufus. Actually, the reason I know about Rufus       is because you told me about it years ago on usenet.              This is a blurb from my notes.              *******       If you find Ubuntu booting slowly, because it searches for btrfs, mdadm,       this is caused by an invalid swap UUID. (This happens when you install       a second copy of Linux and swap is re-formatted.)              Your options are              Option 1               Edit /etc/fstab and correct the blkid of swap.              Option 2               Initramfs also has a swap check.               open /etc/initramfs-tools/conf.d/resume        replace RESUME=UUID=xxx with RESUME=none (or use the correct blkid!)        issue sudo update-initramfs -u        reboot your system               I did an update-grub just in case.               Another modification you could make, is /etc/default/grub        and change "quiet splash" to "quiet splash noresume" then update-grub.               It all depends on whether you want hibernation support, as to        which direction you go with the modifications. (Correct the BLKID, or        just blow the silly stuff away with noresume.)              *******              Now, I checked how my Ubuntu 22.04 is configured on the other machine.       Shocked I was.              /etc/default/grub        GRUB_TIMEOUT_STYLE=menu        GRUB_CMDLINE_LINUX_DEFAULT="noresume"       /etc/initramfs-tools/conf.d/resume        RESUME=UUID=f64d8e53-de8f-4f9a-b8e1-2fe07e66cfde <=== matches no BLKID,       sounds like an old swap value        I am a bad monkey,       for not taking my own advice.              And that was, in fact, the swap partition UUID when Ubuntu was first installed.              So it looks like, on the monitor to the left of me, that Ubuntu OS       used the boot-line "noresume" to bypass the fact I had not       corrected using update-initramfs -u .               Paul              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca