Re: No /
Thanks David. Steps 1 through 6 describe just how the present drama unfolded. Good thinking. This is, I imagine, also what happens anytime power is taken away before COW has been able to do its thing. Is there a way to fix this, or is a re-installation the only remedy? Michael Am Montag, dem 13.03.2023 um 14:03 -0500 schrieb David Wright:
Re: No /
Thanks David. Steps 1 through 6 describe just how the present drama unfolded. Good thinking. Am Montag, dem 13.03.2023 um 14:03 -0500 schrieb David Wright:
Re: No /
Hello Tom, thanks for the reply. Good detective work. No, actually not; it's the SSD with the Debian on it. Michael Am Mittwoch, dem 08.03.2023 um 12:45 + schrieb Tom Furie:
Re: No /
I'd like to help my system find its root, and so be able to complete the boot up. Michael Am Dienstag, dem 07.03.2023 um 11:45 -0500 schrieb Dan Ritter: > Michael Lee wrote: > > Is it possible to reinstall the system and still retain the > > settings, > > logins, etc.? > > Not as such. > > That said: what do you actually want to accomplish? There may be > ways to do what you want with less effort. > > -dsr- >
No /
Is it possible to reinstall the system and still retain the settings, logins, etc.? Michael Lee
Boot Errors
While running the stable branch of 64-bit Debian, rebooted into an alternative OS, but forgot to unmount a USB device beforhand. Shutdown was taking too long, so forced it anyway. Now when I try to start Linux, I get these error messages: [1.922640] platform gpio_ich.2.auto: failed to claim resource 0:[io 0x0480-0x04ff] [8.934607] BTRFS error (device sdc2): parent transid verify faild on 176160768 wanted 680981 found 680979 [8.934649] BTRFS error (device sdc2): failed to read block groups 1 - 5 [8.935724] BTRFS error (device sdc2): open_ctree failed mount: mounting /dev/sdc2 on /root failed: invalid argument failed to mount /dev/sdc2 as root file system Then the initramfs command prompt appears. A little hard to find much on that. Read in the btrfs wiki that <-o ro,usebackuproot> with the mount command could help when the "wanted" and "found" numbers were not too far apart. mount -t btrfs -o ro,usebackuproot /dev/sdc2 TRIED with: /sysroot GOT: mount: mounting /dev/sdc2 on /sysroot failed: invalid argument TRIED with: / GOT: mount: mounting /dev/sdc2 on / failed: invalid argument TRIED with: /root GOT: mount: mounting /dev/sdc2 on /root failed: invalid argument Is this a GRUB issue, a btrfs issue, or must I reinstall the operating system, and if so where can I find out which files must be preserved in order to maintain continuity?
Error Message
Hello, I would like to know what I am supposed to do about this error message. Would appreciate guidance. M Lee Nicht alle Paketquellenindizes konnten heruntergeladen werden Die Software-Paketquelle steht möglicherweise nicht mehr zur Verfügung oder ist aufgrund von Netzwerkproblemen nicht erreichbar. Sofern für diese Software-Paketquelle noch eine ältere Paketliste verfügbar ist, wird diese verwendet. Anderenfalls wird diese Software-Paketquelle gänzlich ignoriert. Bitte prüfen Sie Ihre Netzwerkverbindung und vergewissern Sie sich ebenfalls, dass die Adresse der Software-Paketquelle korrekt in den Einstellungen eingetragen ist. The repository 'http://ftp.de.debian.org/debian stretch/updates Release' does not have a Release file.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.http://ftp.de.debian.org/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.http://ftp.de.debian.org/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
RE: Stepping down ethernet card speed
Yeah, mii-tools lets you do that. If that doesn't work, then ethtool should. -Original Message- From: Florian Ernst [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 7:06 AM To: [EMAIL PROTECTED] Subject: Re: Stepping down ethernet card speed Hello Ross, Ross Boylan wrote: Because of some network problems, it looks as if I need to tell my ethernet card to operate at a certain speed, rather than letting it autosense. How do I do that? Is it a run-time thing (e.g., ifconfig), or do I need to set it as a kernel option on load? Perhaps mii-diag might help you... [EMAIL PROTECTED]:~$ apt-cache show mii-diag Package: mii-diag (...) Description: A little tool to manipulate network cards Examines and sets the MII registers of network cards. . This is a general program. You can find specialized programs for several network cards in the nictools-pci and nictools-nopci packages. From its manpage: -A, --advertise [Mode] Change the capabilities advertised by your network interface. Currently the following modes are allowed: 100baseT4, 100baseTx 100baseTx-FD, 100baseTx-HD, 10baseT, 10baseT-FD and 10baseT-HD. (...) -F, --fixedspeed Force your network interface to a speed mode. Currently the following modes are allowed: 100baseT4, 100baseTx 100baseTx- FD, 100baseTx-HD, 10baseT, 10baseT-FD and 10baseT-HD. To set the speed automagically once the network starts up I personally use this: [EMAIL PROTECTED]:~$ cat /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) auto eth0 iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 up mii-tool -F 100baseTx-FD eth0 Any comments are appreciated... HTH, Flo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
make is really slow!
Hi, I'm completely stumped. I recently upgraded my Debian system from a 2.2 kernel to 2.4.18, and since then it has slowed to a near-halt (on a Celeron 733). Where it's most notable is if I run make. For example, make menuconfig takes about two full minutes to bring up the dialog boxes. And then, running make dep takes a solid TWO HOURS after saving my kernel changes. And then (yeah, it gets even better) running make-kpkg --revision=custom.1.0 kernel_image takes a whopping FOUR HOURS to finish! I could be approaching this whole thing all wrong, but I checked the version of make, and it is: shiner:~# make -v GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i386-pc-linux-gnu On another Debian machine which runs JUST FINE on a 2.4.18 kernel (a Celeron 500), the version of make is: [EMAIL PROTECTED]:~$ make -v GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i586-pc-linux-gnu Is it possible that make is slow on the Celeron 733 because it's the wrong architecture (i386, instead of i586)? And if so, how on earth do I upgrade it? I've tried apt-get upgrade and apt-get install (my apt sources are set to the unstable debian source), but it just keeps telling me I already have the updated versions. I fear there may be a bigger problem here though. HELP! (And thanks to anyone who can provide it!). ~~ Michael Lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: make is really slow!
Yep. I wish it were that simple. :( ~~ michael lee -Original Message- From: David Roundy [mailto:[EMAIL PROTECTED] Sent: Friday, May 17, 2002 1:55 PM To: debian-user@lists.debian.org Subject: Re: make is really slow! On Fri, May 17, 2002 at 11:46:55AM -0600, Michael Lee (TOR) wrote: I recently upgraded my Debian system from a 2.2 kernel to 2.4.18, and since then it has slowed to a near-halt (on a Celeron 733). Where it's most notable is if I run make. Have you tried rebooting using your old kernel? -- David Roundy http://civet.berkeley.edu/droundy/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: make is really slow!
Considering everything was fine under the 2.2 kernel, I don't think it's a swap issue. :( I also checked gcc. Anyone have any comments about my suspicions of running i386 builds on a Celeron (Coppermine) machine? OR better yet... any thing that I could have just completely missed? (This is most likely the case). -Original Message- From: Sean 'Shaleh' Perry [mailto:[EMAIL PROTECTED] Sent: Friday, May 17, 2002 2:00 PM To: Michael Lee (TOR) Cc: debian-user@lists.debian.org Subject: Re: make is really slow! On 17-May-2002 Michael Lee (TOR) wrote: Hi, I'm completely stumped. I recently upgraded my Debian system from a 2.2 kernel to 2.4.18, and since then it has slowed to a near-halt (on a Celeron 733). Where it's most notable is if I run make. is swap enabled? Do you have enough? This is not make's fault, all it does is follow the recipe. The real sluggishness you are seeing is from the compilation which is handled by gcc. But still, the problem is not the programs it is either your kernel config or your system config. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: make is really slow!
Well, this Celeron 700 has 256 MB of RAM. Here's the swap useage. So that looks okay to me. I'll check some of the hard drive stuff you mentioned. shiner:/# free -t total used free sharedbuffers cached Mem:254180 223784 30396 0 11688 158716 -/+ buffers/cache: 53380 200800 Swap: 1228932 201228912 Total: 1483112 2238041259308 shiner:/# And thanks to everyone throwin' ideas at me: I REALLY appreciate it!!! (Keep it coming if you think of more!). :) -- Michael Lee -Original Message- From: Craig Dickson [mailto:[EMAIL PROTECTED] Sent: Friday, May 17, 2002 2:15 PM To: debian-user@lists.debian.org Subject: Re: make is really slow! Michael Lee (TOR) wrote: Hi, I'm completely stumped. I recently upgraded my Debian system from a 2.2 kernel to 2.4.18, and since then it has slowed to a near-halt (on a Celeron 733). Where it's most notable is if I run make. For example, make menuconfig takes about two full minutes to bring up the dialog boxes. And then, running make dep takes a solid TWO HOURS after saving my kernel changes. And then (yeah, it gets even better) running make-kpkg --revision=custom.1.0 kernel_image takes a whopping FOUR HOURS to finish! I could be approaching this whole thing all wrong, but I checked the version of make, and it is: shiner:~# make -v GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i386-pc-linux-gnu On another Debian machine which runs JUST FINE on a 2.4.18 kernel (a Celeron 500), the version of make is: [EMAIL PROTECTED]:~$ make -v GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i586-pc-linux-gnu Is it possible that make is slow on the Celeron 733 because it's the wrong architecture (i386, instead of i586)? And if so, how on earth do I upgrade it? I've tried apt-get upgrade and apt-get install (my apt sources are set to the unstable debian source), but it just keeps telling me I already have the updated versions. I fear there may be a bigger problem here though. HELP! (And thanks to anyone who can provide it!). I don't think make being an i386 package has anything to do with it. The speed increase of recompiling for i586 or whatever wouldn't be all that dramatic, and besides, you changed your kernel, not your make. I have a Celeron 700 running an i386 make 3.79.1, and see no such problems. You should try booting your old 2.2 kernel and see if the problem goes away. If it does, then the kernel is the only difference. You might want to look at your swap usage. How much memory does this machine have? Also, what differences are there between the 2.2 and 2.4 kernel configurations? It could be that your 2.4 kernel is not set up for efficient usage of your hard disk. hdparm can tell you whether DMA and multi-sector I/O are being used; check that under both kernels. Craig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: make is really slow!
No, under the old kernel, everything was great. I upgraded and everything slowed down. At the same time, I upgraded a similar machine with a slightly slower CPU. It suffered no degredation of any kind when upgrading the kernel. Michael Lee (TOR) Service Architect TELUS Corporation 910-222 Bay Street Toronto, Ontario M5K 1A1 Tel: 416.507.7564 [EMAIL PROTECTED] -Original Message- From: David Roundy [mailto:[EMAIL PROTECTED] Sent: Friday, May 17, 2002 2:16 PM To: debian-user@lists.debian.org Subject: Re: make is really slow! On Fri, May 17, 2002 at 11:57:35AM -0600, Michael Lee (TOR) wrote: Yep. I wish it were that simple. :( From that I presume you got the same slowness even under the old kernel? -- David Roundy http://civet.berkeley.edu/droundy/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: make is really slow!
Whew! I just got back from the data centre. As I was getting ready to boot into the old kernel, something that Craig Dickson pointed out struck me: check the DMA settings. Well i rebooted and went into my BIOS settings. There was this weird option (with no descriptions) that said, Load Optimal Settings for fastest performance. So I chose it, then looked to see what it did. I didn't see anything blatant. BUT, I did notice that my U-DMA setting wasn't enabled. So I enabled it, booted (with my new kernel) and everything's cool. So in the end (as usual) the error was: user too close to equipment. (Boy, I'm dumb). -Original Message- From: David Roundy [mailto:[EMAIL PROTECTED] Sent: Friday, May 17, 2002 2:37 PM To: debian-user@lists.debian.org Subject: Re: make is really slow! On Fri, May 17, 2002 at 12:18:46PM -0600, Michael Lee (TOR) wrote: No, under the old kernel, everything was great. I upgraded and everything slowed down. But if you boot back into the old kernel, does it speed up again? -- David Roundy http://civet.berkeley.edu/droundy/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
