Fw: Fwd: How do I troubleshoot wireless network dropping?
I wouldn't recommend using ifconfig to enable or disable your second network card. It is somewhat deprecated. Try using ifup and ifdown. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jul 5, 2020, 9:23 PM, Borden Rhodes wrote: >> Use ps x to see how many copies of wpa_supplicant are running. If you have >> multiple copies started from the command line the wifi won't stay connected. >> I had the same problem. > > Thank you for the suggestion. I checked when it started dropping and, not only > was there one instance of wpa_supplicant running, it was the same instance > (judging from its PID) > >> Keep off the Intel card when you use the USB dongle, maybe one interfere with >> the other > > Another good suggestion. I've tried disabling it from ifconfig. The interfaces > use consistent device naming, so the names shouldn't be getting mixed up. > > I've isolated, what I think are, the journal lines from when my connection > dropped today: > > wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-DISCONNECTED bssid=a0:##:##:##:##:0a > reason=4 locally_generated=1 > wpa_supplicant[1555]: dbus: wpa_dbus_property_changed: no property > SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 > wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD > wpa_supplicant[1555]: wlp10s0: SME: Trying to authenticate with > a0:##:##:##:##:0a (SSID='WiFiNetwork' freq=2462 MHz) > wpa_supplicant[1555]: wlp10s0: Trying to associate with a0:##:##:##:##:0a > (SSID='MyNetwork' freq=2462 MHz) > wpa_supplicant[1555]: wlp10s0: Associated with a0:##:##:##:##:0a > wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 > wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE > type=COUNTRY alpha2=CA > wpa_supplicant[1555]: wlp10s0: WPA: Key negotiation completed with > a0:##:##:##:##:0a [PTK=CCMP GTK=CCMP] > wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-CONNECTED - Connection to > a0:##:##:##:##:0a completed [id=0 id_str=] > > For the purposes of these log entries, "WiFiNetwork" is the SSID of my > network, but the log literally shows "MyNetwork" in the next line when > it's trying to associate. I have no idea what this network is and I > can't find it configured anywhere. So is it possible that someone's > trying to MAC-jack my laptop?
Fw: Fw: Fw: Grub cannot see my new hard drive
Nothing seems good enough. Do you want a picture? I'm not typing all of that in on my tablet. Let's just let it go. I'm working on understanding grub. I'm going to boot from a USB flash drive. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jul 3, 2020, 7:37 AM, David Wright wrote: > On Thu 02 Jul 2020 at 21:17:57 (+), Matthew Campbell wrote: >> On Jul 2, 2020, 1:08 PM, David Wright wrote: >> > On Thu 02 Jul 2020 at 08:12:00 (+), Matthew Campbell wrote: >> >> On Jul 1, 2020, 7:50 PM, David Wright wrote: >> >> > On Wed 17 Jun 2020 at 05:14:22 (+), Matthew Campbell wrote: >> >> >> […] >> >> >> I booted from a USB 2.0 flash drive into Grub2. >> >> >> […] >> >> >> /dev/sdb is the new 4 TB Toshiba External USB 3.0 hard drive. >> >> >> […] >> >> >> The hard drive, /dev/sdb, always responds faster than the USB flash >> >> >> drives so it is always /dev/sdb. >> >> >> >> >> >> Now Debian Linux is running on my new hard drive using /dev/sdb1 as >> >> >> the root partition. >> > […] >> >> The 4 TB hard drive uses a GPT type partition table, not an MBR type >> >> table, which is why the computer can't see it. It can't make sense of GPT >> >> tables. >> > >> > If your computer can't make sense of GPT tables, how are you able to >> > run Debian Linux from its first partition? >> > >> > I think what you might be trying to say is that you haven't managed to >> > boot from a GPT disk connected by USB. But if you can boot with Grub >> > from an MBR stick, that suggests that something is missing on your >> > GPT disk. >> > >> > Have you tried to install Grub on your 4TB disk? What did it say? >> > Were there any error messages. >> > >> > How is this disk partitioned? Did you do it, or is it just as it >> > was bought? I'll give you an example of how I have system disks >> > partitioned. You don't necessarily have to follow it, but it might >> > help you to deal with yours. >> > >> > --✄ >> > […] >> > --✄ >> > >> > This drive is inside a 2000-built PC. (It can't boot from any sort of >> > USB device.) The second partition table shows the protective MBR, >> > which contains the Grub code for the PC to boot from. >> > >> > The first partition table is the GPT one. Partitions 4 and 5 are >> > for root filesystems, one for stretch and one for buster. When >> > bullseye is released, I'll most likely overwrite the stretch one. >> > Partition 3 is for swap, and 6 is for /home. Both these are encrypted >> > in different ways. >> > >> > That leaves the more interesting ones. Partition 2 is to enable the >> > drive to be used to boot an EFI system, and is obviously unused by >> > this PC. (I could "borrow" it for more swap, but the PC only has >> > 500MB memory, so probably pointless for the tasks it does.) >> > >> > Partition 1 is where Grub puts the Second Stage code that it requires >> > to read the disk partition table and filesystems, so that it can find >> > grub.cfg, the kernel and initrd. On a "real" MBR disk, there is >> > typically plenty of room between the partition table and the first >> > partition for this code, but on a GPT disk, that space is where >> > the partition table itself resides; so Grub has to find somewhere >> > else. That's what partition 1 is for. >> > >> > My *guess* is that your Grub is booting ok, but has no (or little) >> > Second Stage code to determine anything about the drives beyond >> > their existence, so you just get the Grub prompt. >> > >> > Note that it's not important where Grub puts its code, only that >> > there is some space somewhere. On this laptop, my BIOS Boot >> > partition is sda9, because BIOS booting was late to the party >> > on what was bought as a Windows/EFI/GPT machine. > >> The computer's startup/settings menu does not detect the 4 TB drive so it >> does not list it as a bootable device. > > Yes, I have no idea what criteria it uses to display devices, > nor whether it can display more than one device, nor whether > the connection type matters, and so on. > >> I cannot boot from the 4 TB drive. > > We gathered that, hence the thread. > >> It gives me an error saying that it cannot find the file system UUID >
Fw: Fw: Grub cannot see my new hard drive
Man, that text really got screwed up. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 14, 2020, 6:20 PM, Matthew Campbell wrote: > The internal hard drive was visible to Grub, as was the other external USB > hard drive, a Western Digital drive. Having an external hard drive connected > with USB is not the problem. Grub was on /dev/sda and used to boot the > Western Digital drive just fine, until Grub was reconfigured to boot the > Toshiba hard drive instead. > > name=Matthew%20Campbell=trenix25%40pm.me > > Original Message > On Jun 13, 2020, 4:00 PM, The Wanderer wrote: > >> On 2020-06-13 at 18:44, David Christensen wrote: [that on 2020-06-13 at >> 15:38, Matthew Campbell wrote:] >> /dev/sda: Toshiba MK1234GS, 111.8 GiB >> (Internal) >> /dev/sr0: MATSHITADVD-RAM UJ-850S , DVD R/W (Internal IDE) >> >> /dev/sdb: Toshiba External USB 3.0 3.7 TiB >> /dev/sdc: PNY 32 USB 2.0 FD >> 28.9 GiB If I'm reading things correctly, this "Toshiba External USB 3.0" - >> labeled here as /dev/sdb - is the drive which is at the core of the reported >> problem. I'm wondering whether the fact that it's an external hard drive, >> connected over USB3, might be relevant to the fact that GRUB and the BIOS >> are not detecting it. There are systems out there which have some of their >> USB ports hanging off of an internal USB hub chip, such that in order for >> the ports to be visible to the rest of the system, a driver for that hub is >> needed. If GRUB etc. doesn't have a compatible driver for that hub, the USB >> port to which this external drive is connected might not even be detected in >> the first place. >> All USB ports are USB 2.0. That's *probably* not a >> problem relative to the fact that this is a USB3 external hard drive, but it >> certainly can't be helping. > I like to use the manufacturer diagnostic >> utility to wipe and test > hard drives: > > >> https://storage.toshiba.com/consumer-hdd/support/product > > Entering >> "MK1234GS" and "MK1234GSXIDE" into the edit box makes me > think your HDD is >> no longer supported. But, there are many FOSS > tools that you can use >> instead. Unless I'm mixing up my reading of the information posted thus far, >> this is the internal hard drive, /dev/sda, which has Windows - not the >> /dev/sdb which has Linux. As such, I don't see how it's relevant to the fact >> that the latter is not visible to GRUB. -- The Wanderer The reasonable man >> adapts himself to the world; the unreasonable one persists in trying to >> adapt the world to himself. Therefore all progress depends on the >> unreasonable man. -- George Bernard Shaw
Fw: Fw: Grub cannot see my new hard drive
The internal hard drive was visible to Grub, as was the other external USB hard drive, a Western Digital drive. Having an external hard drive connected with USB is not the problem. Grub was on /dev/sda and used to boot the Western Digital drive just fine, until Grub was reconfigured to boot the Toshiba hard drive instead. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 13, 2020, 4:00 PM, The Wanderer wrote: > On 2020-06-13 at 18:44, David Christensen wrote: [that on 2020-06-13 at > 15:38, Matthew Campbell wrote:] >> /dev/sda: Toshiba MK1234GS, 111.8 GiB > (Internal) >> /dev/sr0: MATSHITADVD-RAM UJ-850S , DVD R/W (Internal IDE) >> > /dev/sdb: Toshiba External USB 3.0 3.7 TiB >> /dev/sdc: PNY 32 USB 2.0 FD > 28.9 GiB If I'm reading things correctly, this "Toshiba External USB 3.0" - > labeled here as /dev/sdb - is the drive which is at the core of the reported > problem. I'm wondering whether the fact that it's an external hard drive, > connected over USB3, might be relevant to the fact that GRUB and the BIOS are > not detecting it. There are systems out there which have some of their USB > ports hanging off of an internal USB hub chip, such that in order for the > ports to be visible to the rest of the system, a driver for that hub is > needed. If GRUB etc. doesn't have a compatible driver for that hub, the USB > port to which this external drive is connected might not even be detected in > the first place. >> All USB ports are USB 2.0. That's *probably* not a > problem relative to the fact that this is a USB3 external hard drive, but it > certainly can't be helping. > I like to use the manufacturer diagnostic > utility to wipe and test > hard drives: > > > https://storage.toshiba.com/consumer-hdd/support/product > > Entering > "MK1234GS" and "MK1234GSXIDE" into the edit box makes me > think your HDD is > no longer supported. But, there are many FOSS > tools that you can use > instead. Unless I'm mixing up my reading of the information posted thus far, > this is the internal hard drive, /dev/sda, which has Windows - not the > /dev/sdb which has Linux. As such, I don't see how it's relevant to the fact > that the latter is not visible to GRUB. -- The Wanderer The reasonable man > adapts himself to the world; the unreasonable one persists in trying to adapt > the world to himself. Therefore all progress depends on the unreasonable man. > -- George Bernard Shaw
Fw: Monitor Font During Boot
Use the setfont command to change your console font on the fly. Look in /usr/share/consolefonts for available choices and try them out. I use setfont /usr/share/consolefonts/Uni3-TerminusBold32x16.psf.gz systemd sets it while booting too. I haven't figured that part out yet. It's a systemd related service. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 13, 2020, 5:41 AM, Stephen P. Molnar wrote: > I have a LG Flatron 24EN33TW-B LED LCD Monitor on my Debian Buster > Linux platform. > > I have just changed the screen driver from nouveau to nvidia by running > 'sudo apt install nvidia-driver. > > Before the change of drivers the initial font on the screen on booting > the system was a large, ugly font, during the second portion of the boot > process the font changed to a smaller, better looking font. After the > change the r\font remained large and ugly until the login screen when > the font becomes the same as the Desktop. > > Other than this I have had no problems with the operation of the computer. > > My question is what happen, and more importantly, should I be worried > about impending doom? > > Thanks in advance. > > -- > Stephen P. Molnar, Ph.D. > www.molecular-modeling.net > 614.312.7528 (c) > Skype: smolnar1
Fw: Grub cannot see my new hard drive
name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 12, 2020, 11:46 PM, David Christensen < dpchr...@holgerdanske.com> wrote: On 2020-06-12 17:58, Matthew Campbell wrote: > I hope I don't create a fight with this. > > I booted the Debian netinst disc and installed Linux on /dev/sdb1 as the root > partition. My computer is old. Computer make and model? Processor? RAM module quantity, size, and slot? HDD makes, models, interfaces, and sizes? Optical drive supported media? Toshiba Satellite laptop, possibly P19 or P190, something like that. I don't remember and can't find it. enp10s8 10-baseT ethernet wlp3s0 2.4 & 5 GHz wifi adapter (uses nonfree firmware package, already downloaded) Intel Centrino Core 2 CPU T5200 @ 1.60 GHz 2048 MB of RAM, type & number of pins unknown, laptop profile /dev/sda: Toshiba MK1234GS, 111.8 GiB (Internal) /dev/sr0: MATSHITADVD-RAM UJ-850S , DVD R/W (Internal IDE) /dev/sdb: Toshiba External USB 3.0 3.7 TiB /dev/sdc: PNY 32 USB 2.0 FD 28.9 GiB System BIOS version: V3.30 UUID: C08D94F8158FD811815F001636D1AA94 Memory: 640 kB + 2047 MB > The system BIOS does not see this hard drive, nor does Grub, but the Linux > kernel does. Please post the BIOS/CMOS Setup configuration variable names, available options, and current values for anything related to drives, boot order, etc.. Boot order: CD/DVD PNY USB 2.0 FD - (USB 2.0) TOSHIBA MK1234GSXIDE S WD 2500BMV Eternal - (USB 2.0) FDD (Not present) LAN (Not configured) > I'm running the 4.19.0-9-686-pae kernel, #1 SMP Debian 4.19.118-2 and Buster > 10.4.0. > > The installation program tried to set up Grub on /dev/sda, but since Grub > cannot see /dev/sdb the system gets stuck in rescue mode. It sees two hard > drives hd0 and hd1, but says both have unknown filesystems. I had to install > Linux on a 32 GB USB flash drive just to get my computer to boot. Now I can > boot Windows again too. The flash drive is _really_ slow. Which device (/dev/sda or /dev/sdb) is Windows and which is Debian? Windows Vista factory installed on /dev/sda2 (Boot flag active) (Only Windows) Debian Linux installed on /dev/sdb1 (Could not set the boot flag) (Only Linux) Where do the names 'hd0' and 'hd1' come from? Grub when booting /dev/sda. Grub enters rescue mode. Used ls. What is the make and model of your USB flash drive? Answered above. Are you using a USB 2.0 port or a USB 3.0 port? All USB ports are USB 2.0. > Grub has /dev/sdb1 listed as an option, but says the disk does not exist and > to load the kernel first, which of course is on the new hard drive partition > /dev/sdb1 which I can access just fine after starting the kernel. The catch > is that I have to boot the flash drive /dev/sdc1 to do so thus making it the > root filesystem. I have always installed GRUB to a drive device node -- e.g. /dev/sda -- and never to a partition device node -- e.g. /dev/sdb1. How do you boot the USB flash drive? Plugged it in and booted. Uses DOS MBR. /dev/sdc1 set to active. Uses ext4. > 1) How can I help Grub see and use /dev/sdb1 ? What you are attempting is called "dual-boot". I avoid that. I install one small SSD in each computer and install one operating system. My servers have large HDD's in RAID. One server has the bulk of my data (download, music, pictures, video, etc.). I installed Samba and use it as a file server for my LAN. > 2) Can I create a CD or USB flash drive with which to boot the computer so it > loads the kernel and mounts /dev/sdb1 as the root file system? That is possible, but the above is better. > 3) How long is my flash drive likely to last? Will it wear out as I continue > to use it? Will reading from it damage it, or just writing to it? I use SanDisk Ultra Fit USB 3.0 16 GB flash drives for live drives. I have also used them as system drives in the past. I like the small form factor that does not stick out (and get broken off), but they run hot and are not very fast. The interactive user experience can be choppy, especially if multiple processes write to the flash drive at the same time. None have died yet, but macOS Time Machine smoked (!) a 128 GB drive after about a year. > 4) How exactly does Grub work? What is the process, step by step? > How do I configure Grub to do what I want? > The installation program seems determined to do everything its own way. I set up my machines so that the system drive is /dev/sda. I configure the Debian Installer to install GRUB there. If you want to learn more about GRUB: 1. Enter the command 'apropos grub' and then read the listed manual pages. man: command not found Therefore no man -k 2. Read the Debian Installation Guide: https://www.debian.org/releases/stable/installmanual I'll check that out. Thanks you. 3. Use a search engine to find additional information, such as the GRUB project site: https://www.gnu.org/software
Fw: Grub cannot see my new hard drive
name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 12, 2020, 8:32 PM, elvis < el...@dogonfire.com> wrote: On 13/6/20 10:58 am, Matthew Campbell wrote: > I hope I don't create a fight with this. > > I booted the Debian netinst disc and installed Linux on /dev/sdb1 as > the root partition. My computer is old. The system BIOS does not see > this hard drive, nor does Grub, but the Linux kernel does. I'm running > the 4.19.0-9-686-pae kernel, #1 SMP Debian 4.19.118-2 and Buster 10.4.0. > > The installation program tried to set up Grub on /dev/sda, but since > Grub cannot see /dev/sdb the system gets stuck in rescue mode. It sees > two hard drives hd0 and hd1, but says both have unknown filesystems. I > had to install Linux on a 32 GB USB flash drive just to get my > computer to boot. Now I can boot Windows again too. The flash drive is > _really_ slow. > > Grub has /dev/sdb1 listed as an option, but says the disk does not > exist and to load the kernel first, which of course is on the new hard > drive partition /dev/sdb1 which I can access just fine after starting > the kernel. The catch is that I have to boot the flash drive /dev/sdc1 > to do so thus making it the root filesystem. > > 1) How can I help Grub see and use /dev/sdb1 ? > > 2) Can I create a CD or USB flash drive with which to boot the > computer so it loads the kernel and mounts /dev/sdb1 as the root file > system? This is what you want. The kernel and initrd can be on a separate partition to the root filesystem. Append root=/dev/sdb1 to change the root from the ramdisk. Or as on my Debian system, it ignores the kernel line and seems to find the root filesystem anyhow. Handy when I mess up the order of the disks and sdc1 becomes sdb1. No idea how it does it, magic I guess. Response: It finds the correct disk/partition because each has a unique identifier UUID which Grub looks for. Grub can't see my /dev/sdb so telling it to boot /dev/sdb1 won't help because it can't see the hard drive. It will claim that the drive or partition does not exist. > > 3) How long is my flash drive likely to last? Will it wear out as I > continue to use it? Will reading from it damage it, or just writing to it? > > 4) How exactly does Grub work? What is the process, step by step? How > do I configure Grub to do what I want? The installation program seems > determined to do everything its own way. > > Thank you for your assistance in these matters. > > name=Matthew%20Campbell=trenix25%40pm.me > > > > -- Himself, he never took too seriously. His work most seriously.
Fw: How long will this take?
I wipe a new drive for two reasons. 1) I like to make sure it's nice and clean which makes me comfortable. It bothers me if I don't. 2) I can make a reasonable determination about which sectors were used when setting up the partition table(s) and any boot loaders so I know which sectors were used and need to be backed up. Yes, I'm actually going to use dd to back up that space outside of any partition and store it elsewhere so I can restore it later if it is needed. I prefer to be safe rather than sorry. In today's cyberspace you just can't run without a backup. It's not a question of if you will be attacked, but when and how. I refuse to pay a ransom. If you get a used drive and you are curious then sure, you could go snooping around. I remember when we used a VAX running VMS back in college. It would allocate some huge amount of disk space when compiling our C programs, even though it wasn't used or cleared. I found old deleted emails from other users in that slack space. Yes, they were in plain text. We later found an option to use when compiling our programs to prevent that so our programs didn't have to use as much space which was limited by a disk quota. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 10, 2020, 6:58 AM, Anders Andersson wrote: > On Wed, Jun 10, 2020 at 3:33 PM Nicolas George wrote: >> >> Anders Andersson (12020-06-10): >> > Except wiping a disk is trivial. Just start the job and come back >> > later to a clean disk. It's not like you have to wipe it by hand. I do >> > it routinely before I put a disk to use that's going to be used for a >> > couple of years. >> >> There is no "except" about: define your threat model; if it requires >> wiping, wipe. If it does not, wiping is just a waste of time, little or >> lots, still a waste. And it is a waste of power too. >> >> There are many things that are trivial to do with a hard drive and could >> benefit security in far-fetched scenarios. Did you wipe the possible >> traces of cocaine? Did you weight it to check it matches the specs? Did >> you take pictures of all angles? All these and many others are trivial. >> Why one but not the others? > > Because the police raiding my house for dealing drugs is not a > realistic threat. Looking at my drives for running Tor could be.
Fw: How long will this take?
I have started the process over from the beginning. It seems to respond well to obs=4M as the write speed has gone from 3.7 MB/s to 28.2 MB/s, which is about the same as where it was with obs=1M. It should take a couple of days to complete this write process. The WD drive that I have, which is connected to a separate USB2 port, showed a write speed of 27.5 Mb/s. I am using: dd if=/dev/zero of=/dev/sdb obs=4M status=progress The read speed was faster, of course. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 9, 2020, 2:39 AM, Nicolas George wrote: > Christopher David Howie (12020-06-08): > I'd suggest simply adding > "status=progress" which gives you a summary every > second including bytes > written, elapsed time, and average transfer rate. How do you add > "status=progress" to a process that has already been running for three days? > Regards, -- Nicolas George
Re: How long will this take?
# cat /proc/24283/fdinfo/1 pos: 877106917376 flags: 011 mnt_id: 21 # Is that in bytes? stdin and stderr both show a position of zero. name=Matthew%20Campbell=trenix25%40pm.me Original Message On Jun 8, 2020, 1:32 PM, Nicolas George wrote: > Matthew Campbell (12020-06-08): > I bought a new 4 terrabyte hard drive that > is connected with a USB > cable using USB2. It took about 32 hours to read > every sector on the > drive to look for bad sectors. I started blanking the > sectors using > /dev/zero last Friday night. It still isn't done. Is there a > way I can > find out how much data a particular process has written to the > disk? > I'm using Debian 10.4. Sending a USR1 signal to a running 'dd' > process makes it print I/O sta‐ tistics to standard error and then resume > copying. Fron dd(1). Also, you can go read /proc/$(pidof dd)/fdinfo, it > contains the information too. Note that it becomes much slower as it nears > the center of the disk. Regards, -- Nicolas George
How long will this take?
I bought a new 4 terrabyte hard drive that is connected with a USB cable using USB2. It took about 32 hours to read every sector on the drive to look for bad sectors. I started blanking the sectors using /dev/zero last Friday night. It still isn't done. Is there a way I can find out how much data a particular process has written to the disk? I'm using Debian 10.4. dd if=/dev/zero of=/dev/sdb ibs=4096 count=976754646 name=Matthew%20Campbell=trenix25%40pm.me
