Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 28, 2019, 00:50 by bouncingc...@gmail.com: > In your situation, I would: > 1) backup everything important ASAP. > and (assuming your init is systemd): > 2) read here > https://www.linuxuprising.com/2019/05/how-to-force-fsck-filesystem.html > 3) do something like a one-off use of > fsck.mode=f

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 15:57, David wrote: > On Sat, 28 Sep 2019 at 15:05, David wrote: > > > I had another thought: if you care curious about where the problem > > is, maybe you could run some read-only command that reads > > every part of your disk, and see if it gets stuck anywhere. > > For ex

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 15:05, David wrote: > I had another thought: if you care curious about where the problem > is, maybe you could run some read-only command that reads > every part of your disk, and see if it gets stuck anywhere. > For example: > # find / -xdev -type f -exec md5sum '{}' \; O

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Buy spinrite from www.grc.com, that will work, but after fixing, I would copy to a new drive. You will need a dos disk but this program works well. On Fri, 27 Sep 2019 22:38:59 -0400, local10 wrote: > > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > > Hi, I assume you are attempting to follo

Re: whereis/whatcontains xserver-xorg-legacy?

On Fri, Sep 27, 2019 at 11:55:44PM -0500, David Wright wrote: > On Sat 28 Sep 2019 at 00:19:00 (-0400), Felix Miata wrote: [...] > > Or, which of the > > confusion of Debian's package management tools can show me detail of what's > > in the > > files it contains without bothering to download for

Re: Running a music player via cron

Hi, > >> setleds: Error reading current flags setting. Maybe you are not on the >> console?: ioctl KDGKBLED: Ioctl() inapproprié pour un périphérique > > Seems you're not logged in. > The "setleds +num" works only, if you're logged in, e.g. having a > window manager running. hmmm strange, as I

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 12:39, local10 wrote: > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > It's telling you that the filesystem itself is broken/unreadable. > > I assume you know what inodes are, if not then you should > > read about that. > > In such a case, I think that it is not possib

Re: whereis/whatcontains xserver-xorg-legacy?

On Sat 28 Sep 2019 at 00:19:00 (-0400), Felix Miata wrote: > apt search and aptitude search find it, but > http://archive.debian.org/debian/pool/main/x/ and > http://ftp.us.debian.org/debian/pool/main/x/ and > https://sources.debian.org/prefix/x/ either don't have it, or it's hidden from > view usi

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 12:39, local10 wrote: > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > > > In such a case, I think that it is not possible to repair this filesystem. > > What I find weird about this that the filesystem (it's a root filesystem) > appears to be fully functional, it boots

whereis/whatcontains xserver-xorg-legacy?

apt search and aptitude search find it, but http://archive.debian.org/debian/pool/main/x/ and http://ftp.us.debian.org/debian/pool/main/x/ and https://sources.debian.org/prefix/x/ either don't have it, or it's hidden from view using a web browser. I tried installing it (in Buster), then examining

Re: Debian/Bullseye plasma screen doesn't lock

On Fri 27 Sep 2019 at 20:15:01 (-0400), Gary Dale wrote: > Since mid-August, my screen doesn't lock automatically after 10 > minutes (as I specified in the power management settings). I've tried > rebooting and resetting the power management setting but it's still > not locking. This has survived s

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > Hi, I assume you are attempting to follow a procedure similar > to this one: > https://www.smartmontools.org/wiki/BadBlockHowto#Repairsinafilesystem > > Yes, a different docum

Debian/Bullseye plasma screen doesn't lock

Since mid-August, my screen doesn't lock automatically after 10 minutes (as I specified in the power management settings). I've tried rebooting and resetting the power management setting but it's still not locking. This has survived several updates to the window management software. I tried se

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 09:47, local10 wrote: > > Started to get SMART self test errors and wanted to fix them before things > would get any worse: > > SMART Self-test log structure revision number 1 > Num Test_DescriptionStatus Remaining LifeTime(hours) > LBA_of_first_err

ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Hi, Started to get SMART self test errors and wanted to fix them before things would get any worse: SMART Self-test log structure revision number 1 Num  Test_Description    Status  Remaining  LifeTime(hours)  LBA_of_first_error # 1  Short offline   Completed: read failure   

Re: [Tutor] NumPy Generates ValueError: Some errors were detected ! Line #9 (got 42 columns instead of 1)

On Sat, 28 Sep 2019 at 03:49, Stephen P. Molnar wrote: > On 09/27/2019 09:55 AM, Stephen P. Molnar wrote: > > On 09/27/2019 09:28 AM, Mats Wichmann wrote: > >> On 9/27/19 5:47 AM, Stephen P. Molnar wrote: > >>> I am writing code to combine text files and I have encountered an > >>> error that I a

Re: GRUB key repeat too fast

On Friday 27 September 2019 17:03:41 Pascal Hambourg wrote: > Le 25/09/2019 à 17:27, Alberto Luaces a écrit : > > Pascal Hambourg writes: > >> Le 25/09/2019 à 13:34, Alberto Luaces a écrit : > >>> Pascal Hambourg writes: > I read a report about a similar issue in a Debian-related forum. > >>>

Re: GRUB key repeat too fast

Le 25/09/2019 à 17:27, Alberto Luaces a écrit : Pascal Hambourg writes: Le 25/09/2019 à 13:34, Alberto Luaces a écrit : Pascal Hambourg writes: I read a report about a similar issue in a Debian-related forum. IIRC, a workaround was to connect the keyboard to a USB port of different type (USB

Re: [Tutor] NumPy Generates ValueError: Some errors were detected ! Line #9 (got 42 columns instead of 1)

On 09/27/2019 09:55 AM, Stephen P. Molnar wrote: On 09/27/2019 09:28 AM, Mats Wichmann wrote: On 9/27/19 5:47 AM, Stephen P. Molnar wrote: 0 I am writing code to combine text files and I have encountered an error that I am having trouble solving. Google is no help. The code is: |#!/us

Re: Starting processes after installation

On Thu 26 Sep 2019 at 22:57:50 -0500, David Wright wrote: > On Wed 25 Sep 2019 at 18:12:25 (+0200), Sebastian Hyrwall wrote: > > On 2019-09-25 14:36, Dan Ritter wrote: > > > Sebastian Hyrwall wrote: > > >> Just a question. Is there anyone except me that thinks that autostarting > > >> processes a

Re: sshd fails to bind to port to IP on boot

solved issue ... thank u On Fri, Sep 27, 2019 at 11:55 AM Greg Wooledge wrote: > On Fri, Sep 27, 2019 at 11:44:25AM -0400, yoda woya wrote: > > The public interface is listed defined as > > > > # The public network interface > > allow-hotplug eno1 > > iface eno1 inet static > > address x

Re: sshd fails to bind to port to IP on boot

On Fri, Sep 27, 2019 at 11:44:25AM -0400, yoda woya wrote: > The public interface is listed defined as > > # The public network interface > allow-hotplug eno1 > iface eno1 inet static > address x.x.x.x > > > But I have that same configuration on another server and it works fine. Replace

Re: sshd fails to bind to port to IP on boot

Hi. Please do not top-post. On Fri, Sep 27, 2019 at 11:51:08AM -0400, yoda woya wrote: > How can I use to solve the problem: > > "ssh.service has "After=network.target", and network.target only waits > for interfaces marked as "auto" to come up." You have this in your /etc/network/inter

Re: sshd fails to bind to port to IP on boot

How can I use to solve the problem: "ssh.service has "After=network.target", and network.target only waits for interfaces marked as "auto" to come up." On Fri, Sep 27, 2019 at 11:26 AM Greg Wooledge wrote: > On Fri, Sep 27, 2019 at 11:16:51AM -0400, yoda woya wrote: > > Below is the error I g

Re: sshd fails to bind to port to IP on boot

The public interface is listed defined as # The public network interface allow-hotplug eno1 iface eno1 inet static address x.x.x.x But I have that same configuration on another server and it works fine. On Fri, Sep 27, 2019 at 11:42 AM yoda woya wrote: > # The public network interface

Re: sshd fails to bind to port to IP on boot

# The public network interface allow-hotplug eno1 iface eno1 inet static address 128.59.176.101 On Fri, Sep 27, 2019 at 11:25 AM Dan Ritter wrote: > yoda woya wrote: > > Below is the error I get. However the service works at boot if > > InternetAddress is commented out or set to 0.0.0.0

Re: sshd fails to bind to port to IP on boot

On Fri, Sep 27, 2019 at 11:16:51AM -0400, yoda woya wrote: > Below is the error I get. However the service works at boot if > InternetAddress is commented out or set to 0.0.0.0. The service works > manually ( /etc/init.d/ssh start) > -- Subject: A start job for unit ssh.service has begun executio

Re: sshd fails to bind to port to IP on boot

yoda woya wrote: > Below is the error I get. However the service works at boot if > InternetAddress is commented out or set to 0.0.0.0. The service works > manually ( /etc/init.d/ssh start) > -- Subject: A start job for unit ssh.service has begun execution > -- A start job for unit ssh.service h

Re: Starting processes after installation

On Fri 27 Sep 2019 at 07:04:28 (-0400), Dan Ritter wrote: > David Wright wrote: > > On Wed 25 Sep 2019 at 18:12:25 (+0200), Sebastian Hyrwall wrote: > > > On 2019-09-25 14:36, Dan Ritter wrote: > > > > It turns out that Debian is relatively old. I've been using it > > > > since 1996 or so, and it

Re: sshd fails to bind to port to IP on boot

Below is the error I get. However the service works at boot if InternetAddress is commented out or set to 0.0.0.0. The service works manually ( /etc/init.d/ssh start) -- Subject: A start job for unit ssh.service has begun execution -- A start job for unit ssh.service has begun execution. Sep 27 1

What is the percentage of market share for servers based on Debian Linux?

Good evening from Singapore, What is the percentage of market share for servers based on Debian Linux? Looking forward to hearing from you. Thank you very much. -BEGIN EMAIL SIGNATURE- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Su

Re: [Tutor] NumPy Generates ValueError: Some errors were detected ! Line #9 (got 42 columns instead of 1)

On 09/27/2019 09:28 AM, Mats Wichmann wrote: On 9/27/19 5:47 AM, Stephen P. Molnar wrote: 0 I am writing code to combine text files and I have encountered an error that I am having trouble solving. Google is no help. The code is: |#!/usr/bin/env python3# -*- coding: utf-8 -*-""" Created

Re: Rescuing hard disks

On Mon, Sep 23, 2019 at 03:11:07PM +0500, Alexander V. Makartsev wrote: If I understood this right, you have two disks with data and they were previously configured as RAID1 volume. What make\model RAID-controller do you use? Because "cages" by themselves offer only SATA\SAS ports for disks to co

Re: Starting processes after installation

David Wright wrote: > On Wed 25 Sep 2019 at 18:12:25 (+0200), Sebastian Hyrwall wrote: > > On 2019-09-25 14:36, Dan Ritter wrote: > > > It turns out that Debian is relatively old. I've been using it > > > since 1996 or so, and it was in version 2.1 back then. (I > > > haven't bothered to check thi

Option 66 tftp-server-name qemu debian-installer

Hi, I'm trying to use option 66 (tftp-server-name) as explain at (1) with the Debian installer in combination with Qemu. As I understand it, the following Qemu command should be used: boot -n -net user,tftp=,tftp-server-name=qemutftp,bootfile=pxelinux.0 In the cfg file I would have something li

Re: Diagnosing lockups

Charlie Gibbs composed on 2019-09-26 21:16 (UTC-0700): > I've set up a new machine with Buster (my first foray, my other > machines are still running Stretch). It frequently locks up so > hard that I have to hit the reset button. It seems to happen when > scrolling a Notepad window in Windows XP