Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #267593

Re: Orphaned Inode Problem

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Feb 19, 2024 at 10:02:10AM -0500, Stephen P. Molnar wrote:
> I am running up to date Bookworm on my Debian platform:
> 
> Processor 	AMD FX(tm)-8320 Eight-Core Processor
> Memory 	8026MB (5267MB used)
> Machine Type 	Desktop
> Operating System 	Debian GNU/Linux 12 (bookworm)
> 
> I have been plagued with orphaned inodes. Last night the problem cane to a
> head. When I reboot the computer, after an orphaned inode incident created
> stop, it got as far as the user login. After the return I got the Windows
> infamous blue screen. Restarting produced the same problem.
> 
> Fortunately, I have another SSD used to test Bookworm, before updating on
> the SSD that is having the problem. I can access the problem drive and am in
> the process of backing up files.
> 
> I ran sudo e2fsck -f/dev/sdc1 and got:
> 
> Script started on 2024-02-19 08:15:52-05:00 [TERM="xterm-256color"
> TTY="/dev/pts/0" COLUMNS="100" LINES="24"]
> [?2004h(base) ]0;comp@AbNormal:
> ~comp@AbNormal:~$ sudo e2fsck -f
> /dev/sdc1lcaomosudo e2fsck -f /dev/sdc1
> [?2004l
> [sudo] password for comp:
> e2fsck 1.47.0 (5-Feb-2023)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> /lost+found not found.  Create<y>? yes
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> 
> /dev/sdc1: ***** FILE SYSTEM WAS MODIFIED *****
> /dev/sdc1: 7982363/121577472 files (0.3% non-contiguous),
> 421959365/486307328 blocks
> [?2004h(base) ]0;comp@AbNormal:
> ~comp@AbNormal:~$ [?2004l
> 
> Comments and suggestions will be appreciated.

This session doesn't show anything to worry about. As far as fsck
is concerned, the file system looks clean. Back up its contents as
quickly as you can and treat the disk with suspicion. There are
other candidate suspects for file system corruption (flaky power
supply, software doing silly things, kernel bugs, loose cables),
but the disk would be the pirmary.

Cheers
-- 
t

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Orphaned Inode Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2024-02-19 16:10 +0100
  Re: Orphaned Inode Problem <tomas@tuxteam.de> - 2024-02-19 18:30 +0100
    Re: Orphaned Inode Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2024-02-19 18:40 +0100
      Re: Orphaned Inode Problem <tomas@tuxteam.de> - 2024-02-19 18:50 +0100
      Re: Orphaned Inode Problem Jörg-Volker Peetz <jvpeetz@web.de> - 2024-02-21 12:10 +0100
        Re: Orphaned Inode Problem Henning Follmann <hfollmann@itcfollmann.com> - 2024-02-21 14:20 +0100
          Re: Orphaned Inode Problem Jörg-Volker Peetz <jvpeetz@web.de> - 2024-02-21 17:20 +0100
            Re: Orphaned Inode Problem <tomas@tuxteam.de> - 2024-02-22 07:10 +0100
            Re: Orphaned Inode Problem Henning Follmann <hfollmann@itcfollmann.com> - 2024-02-22 08:50 +0100
              Re: Orphaned Inode Problem Jörg-Volker Peetz <jvpeetz@web.de> - 2024-02-22 11:30 +0100
          Re: Orphaned Inode Problem gene heskett <gheskett@shentel.net> - 2024-02-22 05:30 +0100
        Re: Orphaned Inode Problem David Christensen <dpchrist@holgerdanske.com> - 2024-02-21 19:20 +0100
          Re: Orphaned Inode Problem Gremlin <scott-andrews@columbus.rr.com> - 2024-02-21 22:40 +0100
    Re: Orphaned Inode Problem Eike Lantzsch ZP5CGE / KY4PZ <zp6cge@gmx.net> - 2024-02-19 20:20 +0100
      red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem) Andy Smith <andy@strugglers.net> - 2024-02-20 01:50 +0100
        Re: red SATA cables "notoriously bad"? Felix Miata <mrmazda@earthlink.net> - 2024-02-20 02:20 +0100
          Re: red SATA cables "notoriously bad"? Andy Smith <andy@strugglers.net> - 2024-02-20 02:30 +0100
            Re: red SATA cables "notoriously bad"? Felix Miata <mrmazda@earthlink.net> - 2024-02-20 03:10 +0100
              Re: red SATA cables "notoriously bad"? David Christensen <dpchrist@holgerdanske.com> - 2024-02-20 10:30 +0100
                Re: red SATA cables "notoriously bad"? gene heskett <gheskett@shentel.net> - 2024-02-20 14:50 +0100
            Re: red SATA cables "notoriously bad"? gene heskett <gheskett@shentel.net> - 2024-02-20 04:10 +0100
              Re: red SATA cables "notoriously bad"? Andy Smith <andy@strugglers.net> - 2024-02-20 04:20 +0100
                Re: red SATA cables "notoriously bad"? gene heskett <gheskett@shentel.net> - 2024-02-20 04:40 +0100
        Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode  Problem) gene heskett <gheskett@shentel.net> - 2024-02-20 03:40 +0100
        Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode  Problem) jeremy ardley <jeremy.ardley@gmail.com> - 2024-02-20 04:40 +0100
          Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem) Eike Lantzsch ZP5CGE / KY4PZ <zp6cge@gmx.net> - 2024-02-20 11:00 +0100
            Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem) Eike Lantzsch ZP5CGE / KY4PZ <zp6cge@gmx.net> - 2024-02-20 11:20 +0100

csiph-web