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

Groups > linux.debian.user > #200773 > unrolled thread

all files moved to lost+found

Back to article view | Back to linux.debian.user

Contents

  all files moved to lost+found Beco <rcb@beco.cc> - 2018-09-30 16:20 +0200
    Re: all files moved to lost+found Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-09-30 19:20 +0200
      Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-09-30 21:30 +0200
        Re: all files moved to lost+found Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-09-30 22:10 +0200
    Re: all files moved to lost+found David Christensen <dpchrist@holgerdanske.com> - 2018-09-30 20:30 +0200
      Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-09-30 21:30 +0200
        Re: all files moved to lost+found bw <bwtnguy@yahoo.com> - 2018-09-30 21:50 +0200
          Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-09-30 22:00 +0200
            Re: all files moved to lost+found Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-09-30 22:30 +0200
      Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-10-02 02:40 +0200
        Re: all files moved to lost+found David Christensen <dpchrist@holgerdanske.com> - 2018-10-02 04:10 +0200
          Re: all files moved to lost+found Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-10-02 05:50 +0200
            Re: all files moved to lost+found David Christensen <dpchrist@holgerdanske.com> - 2018-10-02 08:20 +0200
              Re: all files moved to lost+found Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-10-02 14:20 +0200
        Re: all files moved to lost+found Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-10-02 06:10 +0200
          Re: all files moved to lost+found David Christensen <dpchrist@holgerdanske.com> - 2018-10-02 08:40 +0200
            Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-10-04 05:10 +0200
              Re: all files moved to lost+found songbird <songbird@anthive.com> - 2018-10-04 13:40 +0200
                Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-10-05 03:00 +0200
                  Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-10-05 15:00 +0200
                    Re: all files moved to lost+found Gene Heskett <gheskett@shentel.net> - 2018-10-05 15:40 +0200
                      Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-10-10 06:20 +0200
                        Re: all files moved to lost+found Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-10-10 07:40 +0200
                          Re: all files moved to lost+found songbird <songbird@anthive.com> - 2018-10-10 23:40 +0200
                            Re: all files moved to lost+found Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-10-11 08:00 +0200
                              Re: all files moved to lost+found songbird <songbird@anthive.com> - 2018-10-11 14:50 +0200
                                Re: all files moved to lost+found Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-10-12 00:00 +0200
                        Re: all files moved to lost+found David Christensen <dpchrist@holgerdanske.com> - 2018-10-11 05:40 +0200
          Re: all files moved to lost+found Beco <rcb@beco.cc> - 2018-10-05 15:10 +0200

Page 1 of 2  [1] 2  Next page →

#200773 — all files moved to lost+found

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

Hi everyone,

I have a bit of a problem I never faced before and I'm in need of some
guidance that may require some patience if to do it right and not lose any
data.

I have a lenovo ideapad 320, and I changed its internal HD to a 2TB
seagate, 3 months ago.

In the last couple of weeks I got this "small" problem twice:

Laptop won't boot saying it couldn't read /home partition. The only
partition in the 2TB plus a swap. OS is in a SSD.

So, twice I could login as root single mode, run:

e2fsck -vy /dev/sda3

and boot ok after lots of messages of inodes failing to do their inodes
thing.

This time was different: I booted the machine and it won't complain, just
opened KDE with no icons on it. Blank desktop, with my owl wallpaper.

I was worried, moved to tty1, killed the desktop section and then run the
same e2fsck above. Again, lots of inodes errors.

No badblocks. I also run e2fsck -pckv /dev/sda3 which took 5 hours to
finish, and no badblocks.

Now, I rebooted it, and still, same empty /home/user

I notice on the other hand that there are A LOT of files under
/home/lost+found
All names are just numbers in the form "#383389933" and so on. Even
directories like that.

I used "file #339938383" to see what the file is about. I found some PGN
images, and I could also identify some of my directories. They seem to be
all there. Just the names are crazy, and they are not in /home/user.

Now that I never got before.

How should I proceed?

Is there a command that brings back lost+found files to theis
"found-and-not-lost" correct places?

Thanks guys.

Beco


-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [next] | [standalone]

#200774

On Sun, 30 Sep 2018 11:09:50 -0300 Beco said:

> Hi everyone,
> 
> I have a bit of a problem I never faced before and I'm in need of some
> guidance that may require some patience if to do it right and not lose any
> data.
> 
> I have a lenovo ideapad 320, and I changed its internal HD to a 2TB
> seagate, 3 months ago.
> 
> In the last couple of weeks I got this "small" problem twice:
> 
> Laptop won't boot saying it couldn't read /home partition. The only
> partition in the 2TB plus a swap. OS is in a SSD.
> 
> So, twice I could login as root single mode, run:
> 
> e2fsck -vy /dev/sda3
> 
> and boot ok after lots of messages of inodes failing to do their inodes
> thing.
> 
> This time was different: I booted the machine and it won't complain, just
> opened KDE with no icons on it. Blank desktop, with my owl wallpaper.
> 
> I was worried, moved to tty1, killed the desktop section and then run the
> same e2fsck above. Again, lots of inodes errors.
> 
> No badblocks. I also run e2fsck -pckv /dev/sda3 which took 5 hours to
> finish, and no badblocks.
> 
> Now, I rebooted it, and still, same empty /home/user
> 
> I notice on the other hand that there are A LOT of files under
> /home/lost+found
> All names are just numbers in the form "#383389933" and so on. Even
> directories like that.
> 
> I used "file #339938383" to see what the file is about. I found some PGN
> images, and I could also identify some of my directories. They seem to be
> all there. Just the names are crazy, and they are not in /home/user.
> 
> Now that I never got before.
> 
> How should I proceed?
> 
> Is there a command that brings back lost+found files to theis
> "found-and-not-lost" correct places?
> 
> Thanks guys.
> 
> Beco

Hi Beco,

As I understand it you had repeated disk failures and consecutively a massive
file-system	corruption.

The files in lost+found are those that are recovered by fsck. There are
probably unrecovered ones too (lost forever). As for restoring their original
names and directory hierarchy, I don't know if it is possible at all - other
than manually inspecting and renaming/relocating every one of them separately.
I think the best course of action would be dealing with the hardware and FS
corruption issue first, and then reformatting /home and restoring from backups.

-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#200779

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

On Sun, 30 Sep 2018 at 14:11, Abdullah Ramazanoğlu <ar018@yahoo.com> wrote:

> On Sun, 30 Sep 2018 11:09:50 -0300 Beco said:
>
> > Hi everyone,
> >
> > I have a bit of a problem I never faced before and I'm in need of some
> > guidance that may require some patience if to do it right and not lose
> any
> > data.
> >
> > I have a lenovo ideapad 320, and I changed its internal HD to a 2TB
> > seagate, 3 months ago.
> >
> > In the last couple of weeks I got this "small" problem twice:
> >
> > Laptop won't boot saying it couldn't read /home partition. The only
> > partition in the 2TB plus a swap. OS is in a SSD.
> >
> > So, twice I could login as root single mode, run:
> >
> > e2fsck -vy /dev/sda3
> >
> > and boot ok after lots of messages of inodes failing to do their inodes
> > thing.
> >
> > This time was different: I booted the machine and it won't complain, just
> > opened KDE with no icons on it. Blank desktop, with my owl wallpaper.
> >
> > I was worried, moved to tty1, killed the desktop section and then run the
> > same e2fsck above. Again, lots of inodes errors.
> >
> > No badblocks. I also run e2fsck -pckv /dev/sda3 which took 5 hours to
> > finish, and no badblocks.
> >
> > Now, I rebooted it, and still, same empty /home/user
> >
> > I notice on the other hand that there are A LOT of files under
> > /home/lost+found
> > All names are just numbers in the form "#383389933" and so on. Even
> > directories like that.
> >
> > I used "file #339938383" to see what the file is about. I found some PGN
> > images, and I could also identify some of my directories. They seem to be
> > all there. Just the names are crazy, and they are not in /home/user.
> >
> > Now that I never got before.
> >
> > How should I proceed?
> >
> > Is there a command that brings back lost+found files to theis
> > "found-and-not-lost" correct places?
> >
> > Thanks guys.
> >
> > Beco
>
> Hi Beco,
>
> As I understand it you had repeated disk failures and consecutively a
> massive
> file-system     corruption.
>
> The files in lost+found are those that are recovered by fsck. There are
> probably unrecovered ones too (lost forever). As for restoring their
> original
> names and directory hierarchy, I don't know if it is possible at all -
> other
> than manually inspecting and renaming/relocating every one of them
> separately.
> I think the best course of action would be dealing with the hardware and FS
> corruption issue first, and then reformatting /home and restoring from
> backups.
>
> --
> Abdullah Ramazanoğlu
>
>
>
Dear Abdullah,

Thanks for your reply. I tend to agree. I am still not sure what CAUSED the
problem in the first place.

If I need to change HD? (I'm not convinced, HD seems ok). Is there any kind
of hardware problem with LENOVO IDEAPAD 320? Maybe... But what?

And the logs... I looked at various logs, no problems, except some minor
drivers that won't read (like wireless and nvidia).
Same old, same old.

Now this, this is my first time. To loose ALL /home?? In the first morning
boot, without warning, just a clean boot and a empty desktop?

What sorcery is that?

Beco





-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

#200783

On Sun, 30 Sep 2018 16:26:18 -0300 Beco said:

> On Sun, 30 Sep 2018 at 14:11, Abdullah Ramazanoğlu <ar018@yahoo.com> wrote:
> 
> > On Sun, 30 Sep 2018 11:09:50 -0300 Beco said:
> >  
> > > Hi everyone,
> > >
> > > I have a bit of a problem I never faced before and I'm in need of some
> > > guidance that may require some patience if to do it right and not lose  
> > any  
> > > data.
> > >
> > > I have a lenovo ideapad 320, and I changed its internal HD to a 2TB
> > > seagate, 3 months ago.
> > >
> > > In the last couple of weeks I got this "small" problem twice:
> > >
> > > Laptop won't boot saying it couldn't read /home partition. The only
> > > partition in the 2TB plus a swap. OS is in a SSD.
> > >
> > > So, twice I could login as root single mode, run:
> > >
> > > e2fsck -vy /dev/sda3
> > >
> > > and boot ok after lots of messages of inodes failing to do their inodes
> > > thing.
> > >
> > > This time was different: I booted the machine and it won't complain, just
> > > opened KDE with no icons on it. Blank desktop, with my owl wallpaper.
> > >
> > > I was worried, moved to tty1, killed the desktop section and then run the
> > > same e2fsck above. Again, lots of inodes errors.
> > >
> > > No badblocks. I also run e2fsck -pckv /dev/sda3 which took 5 hours to
> > > finish, and no badblocks.
> > >
> > > Now, I rebooted it, and still, same empty /home/user
> > >
> > > I notice on the other hand that there are A LOT of files under
> > > /home/lost+found
> > > All names are just numbers in the form "#383389933" and so on. Even
> > > directories like that.
> > >
> > > I used "file #339938383" to see what the file is about. I found some PGN
> > > images, and I could also identify some of my directories. They seem to be
> > > all there. Just the names are crazy, and they are not in /home/user.
> > >
> > > Now that I never got before.
> > >
> > > How should I proceed?
> > >
> > > Is there a command that brings back lost+found files to theis
> > > "found-and-not-lost" correct places?
> > >
> > > Thanks guys.
> > >
> > > Beco  
> >
> > Hi Beco,
> >
> > As I understand it you had repeated disk failures and consecutively a
> > massive
> > file-system     corruption.
> >
> > The files in lost+found are those that are recovered by fsck. There are
> > probably unrecovered ones too (lost forever). As for restoring their
> > original
> > names and directory hierarchy, I don't know if it is possible at all -
> > other
> > than manually inspecting and renaming/relocating every one of them
> > separately.
> > I think the best course of action would be dealing with the hardware and FS
> > corruption issue first, and then reformatting /home and restoring from
> > backups.
> >
> > --
> > Abdullah Ramazanoğlu
> >
> >
> >  
> Dear Abdullah,
> 
> Thanks for your reply. I tend to agree. I am still not sure what CAUSED the
> problem in the first place.
> 
> If I need to change HD? (I'm not convinced, HD seems ok). Is there any kind
> of hardware problem with LENOVO IDEAPAD 320? Maybe... But what?
> 
> And the logs... I looked at various logs, no problems, except some minor
> drivers that won't read (like wireless and nvidia).
> Same old, same old.
> 
> Now this, this is my first time. To loose ALL /home?? In the first morning
> boot, without warning, just a clean boot and a empty desktop?
> 
> What sorcery is that?
> 
> Beco
 
It is indeed a bit strange to have a major FS corruption without preceeding
symptoms (eg. messages).

It looks as if your drive has a big cache and don't flush it properly (but
reports a successful flush back to OS). So from OS point of view everything
seems OK, but F/S corruption becomes visible upon the next power-on. Just a
guess. Could be anything.

I would suggest following David's recommendation. (AIUI you won't install the
diagnostic tool. You boot it from CD/USB and run it stand-alone.)

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#200778

On 9/30/18 7:09 AM, Beco wrote:
> Hi everyone,
> 
> I have a bit of a problem I never faced before and I'm in need of some
> guidance that may require some patience if to do it right and not lose any
> data.
> 
> I have a lenovo ideapad 320, and I changed its internal HD to a 2TB
> seagate, 3 months ago.
> 
> In the last couple of weeks I got this "small" problem twice:
> 
> Laptop won't boot saying it couldn't read /home partition. The only
> partition in the 2TB plus a swap. OS is in a SSD.
> 
> So, twice I could login as root single mode, run:
> 
> e2fsck -vy /dev/sda3
> 
> and boot ok after lots of messages of inodes failing to do their inodes
> thing.
> 
> This time was different: I booted the machine and it won't complain, just
> opened KDE with no icons on it. Blank desktop, with my owl wallpaper.
> 
> I was worried, moved to tty1, killed the desktop section and then run the
> same e2fsck above. Again, lots of inodes errors.
> 
> No badblocks. I also run e2fsck -pckv /dev/sda3 which took 5 hours to
> finish, and no badblocks.
> 
> Now, I rebooted it, and still, same empty /home/user
> 
> I notice on the other hand that there are A LOT of files under
> /home/lost+found
> All names are just numbers in the form "#383389933" and so on. Even
> directories like that.
> 
> I used "file #339938383" to see what the file is about. I found some PGN
> images, and I could also identify some of my directories. They seem to be
> all there. Just the names are crazy, and they are not in /home/user.
> 
> Now that I never got before.
> 
> How should I proceed?
> 
> Is there a command that brings back lost+found files to theis
> "found-and-not-lost" correct places?
> 
> Thanks guys.
> 
> Beco

Download and run Seagate's diagnostic tool on the 2 TB drive:

https://www.seagate.com/support/downloads/seatools/

(I have been using the bootable CD image for years ("legacy"), but it 
looks like they finally have a bootable USB image.)

Use a camera and take pictures of the various screens.  Transcribe them 
into a reply to this list.


Do you have backups?


David

[toc] | [prev] | [next] | [standalone]

#200780

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

On Sun, 30 Sep 2018 at 15:25, David Christensen <dpchrist@holgerdanske.com>
wrote:

> On 9/30/18 7:09 AM, Beco wrote:
> > Hi everyone,
> >
> > I have a bit of a problem I never faced before and I'm in need of some
> > guidance that may require some patience if to do it right and not lose
> any
> > data.
> >
> > I have a lenovo ideapad 320, and I changed its internal HD to a 2TB
> > seagate, 3 months ago.
> >
> > In the last couple of weeks I got this "small" problem twice:
> >
> > Laptop won't boot saying it couldn't read /home partition. The only
> > partition in the 2TB plus a swap. OS is in a SSD.
> >
> > So, twice I could login as root single mode, run:
> >
> > e2fsck -vy /dev/sda3
> >
> > and boot ok after lots of messages of inodes failing to do their inodes
> > thing.
> >
> > This time was different: I booted the machine and it won't complain, just
> > opened KDE with no icons on it. Blank desktop, with my owl wallpaper.
> >
> > I was worried, moved to tty1, killed the desktop section and then run the
> > same e2fsck above. Again, lots of inodes errors.
> >
> > No badblocks. I also run e2fsck -pckv /dev/sda3 which took 5 hours to
> > finish, and no badblocks.
> >
> > Now, I rebooted it, and still, same empty /home/user
> >
> > I notice on the other hand that there are A LOT of files under
> > /home/lost+found
> > All names are just numbers in the form "#383389933" and so on. Even
> > directories like that.
> >
> > I used "file #339938383" to see what the file is about. I found some PGN
> > images, and I could also identify some of my directories. They seem to be
> > all there. Just the names are crazy, and they are not in /home/user.
> >
> > Now that I never got before.
> >
> > How should I proceed?
> >
> > Is there a command that brings back lost+found files to theis
> > "found-and-not-lost" correct places?
> >
> > Thanks guys.
> >
> > Beco
>
> Download and run Seagate's diagnostic tool on the 2 TB drive:
>
> https://www.seagate.com/support/downloads/seatools/
>
> (I have been using the bootable CD image for years ("legacy"), but it
> looks like they finally have a bootable USB image.)
>
> Use a camera and take pictures of the various screens.  Transcribe them
> into a reply to this list.
>
>
> Do you have backups?
>
>
> David
>
>
>
>

Thanks David,

I'll give it a try. I just run

e2fsck -pckv /dev/sda3

It lasted 5 hours running. I took a picture, here is the transcript:

286708 inodes used (0.25% of 112926720)
3776 non-contiguous files (1.3%)
84 non-contiguous dir (0%)
ind/dind/tind blocks: 0/0/0
extent depth histogram: 285759/645
67067830 blocks used (14% of 451678229)
0 bad blocks
11 large files

240878 reg files
45498 dir
0 char devs
0 block devs
2 fifos
0 links
319 symbolic links
2 sockets
-----
286699 files


--------------

but if you look /home/user, it is just empty. Ok, I found a couple of
hidden files, like .bashrc, .profile, .config and things inside it. For
example, inside .config there are files like cache, git-config, etc.

Some are missing. My .ssh dir for example, with keys, missing.

Inside /home/lost+found is just madness

A LOT A LOT of #32432432 #2342342 #52343242 #5234234 #4234324
and many dirs:
#123123123/ #5235235234/
etc.

Should I install this software regardless? I mean, I don't want to start
installing things on the HD that I'm supposed to recover somehow.

What could cause this in the first place? Yesterday I turned it off ok,
went to sleep, and today the first boot and nothing on /home.


Regarding backup, I was afraid my last backup was 3 months old. It turns
out I have one just one month old. It is a big loss yet, but well, what can
you do after the fact...

Is it possible that this microcodes updating everyweek turned our computer
into timebombs? My laptop is new, debian was installed 3 months ago,
nothing much here.

I'm writing from my old laptop, 6 years old, debian, still working. The
same configuration I used in the new one. This old is DELL, the new one is
LENOVO.

Original HD was 1TB and no SSD. That was the only modification I made: SSD
with / root, and 2TB HD seagate with /home.

Yesterday I noticed while using google chrome to browse that everything
froze. I needed to go to tty1 (ALT+F1) and kill sddm (systemctl restart
sddm), and then back to ALT+F7 , login again, and all good to use.


Beco



-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

#200781

On Sun, 30 Sep 2018, Beco wrote:

> I'll give it a try. I just run
> 
> e2fsck -pckv /dev/sda3
> 
> It lasted 5 hours running. I took a picture, here is the transcript:
> 
> 286708 inodes used (0.25% of 112926720)
> 3776 non-contiguous files (1.3%)
> 84 non-contiguous dir (0%)
> ind/dind/tind blocks: 0/0/0
> extent depth histogram: 285759/645
> 67067830 blocks used (14% of 451678229)
> 0 bad blocks
> 11 large files
> 
> 240878 reg files
> 45498 dir
> 0 char devs
> 0 block devs
> 2 fifos
> 0 links
> 319 symbolic links
> 2 sockets
> -----
> 286699 files
> 
> 
> --------------
> 
> but if you look /home/user, it is just empty. Ok, I found a couple of
> hidden files, like .bashrc, .profile, .config and things inside it.

286699 files on a partition with only /home on it sounds a little high?

[toc] | [prev] | [next] | [standalone]

#200782

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

On Sun, 30 Sep 2018 at 16:40, bw <bwtnguy@yahoo.com> wrote:


>
> 286699 files on a partition with only /home on it sounds a little high?
>
>
Hi BW,

the directory lost+found is also in the /home partition.



Beco
-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

#200784

On 9/30/18, Beco <rcb@beco.cc> wrote:
> On Sun, 30 Sep 2018 at 16:40, bw <bwtnguy@yahoo.com> wrote:
>
>>
>> 286699 files on a partition with only /home on it sounds a little high?
>>
>>
> Hi BW,
>
> the directory lost+found is also in the /home partition.


Mine's 118,000 THIS time 'round because I've thinned it out over time.
If someone was using /home instead of /src or anything else for
development, it could easily go that high. I've either seen
instructions say to do that or I've seen users writing about problems
that were housed in that directory.

Playing around with npm plants a dot "not hidden" (grin) directory
under that /home hierarchy, too. That can grow in size real quick.
Been there, done that. :)

"Not hidden" dot cache and dot config directories would add up over
time, too, depending on one's style of backup combined with system
stability.

What about that 2TB sized hard drive on a laptop'ish, right? I've seen
where that's not compatible in *some* cases although I'm sure newer
equipment could handle it. I have secondhand, older equipment that all
has an expressed/recommended 1TB size limit, if that much.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#200809

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

On Sun, 30 Sep 2018 at 15:25, David Christensen <dpchrist@holgerdanske.com>
wrote:

>
> Download and run Seagate's diagnostic tool on the 2 TB drive:
>
> https://www.seagate.com/support/downloads/seatools/
>
> (I have been using the bootable CD image for years ("legacy"), but it
> looks like they finally have a bootable USB image.)
>
> Use a camera and take pictures of the various screens.  Transcribe them
> into a reply to this list.
>
>
>
>
Dear David, hi guys/girls that are following this problem.

First, the delay in my response is due to the fact that I'm fighting a lot
of parallel battles here, but I'm still trying to solve this problem.
In the next days I'll always try to reply.

I've done the bootable seagate HD test. It came up 100% ok, all tests. The
HD is new, I wouldn't expect different, but it is always reassuring to do
the real test and see the results.

To recap, I used the computer all day, since morning until late night. From
time to time, say, about 3 times that day, I noticed a small 5 seconds long
freeze. Sometimes, in other days, KDE wouldn't open plasmashell, but I did
not need to reboot; just open tty1, and run systemctl restart sddm, and it
would run ok. Not sure if this is related.

That night, I turned off the computer, no errors, nothing.

Next morning, first boot, it booted fast and I was faced with an empty
desktop. Also empty /home. After e2fsck, all my files reappeared as inode
numbers in lost+found. I was able to recover some of them, and I have
backup for others. But I'm not still putting them on the hard disk.

I'm still waiting for possible causes or solutions, or just to know what
have happened in the first place.

Is the "swap" partition something that could cause that if turned off by
"swapoff"? Because I remember turning it off during that afternoon. But I
used the computer a LOT until night, so, I don't think there was any link
to the disappearance of ALL files. Also, when I used swapoff, it was almost
without use anyway.

I read above from Abdullah, that it is very unlike to have such major FS
fail, and it looks like it didn't "flush" the night I turned off. This is
also my guess, it is the only thing that make sense. Maybe the inode table
was in the memory and got corrupted. But it is strange to figure that,
since the filesystem is EXT4, and it is very stable nowadays.

Someonelse asked if 2TB is ok for this laptop, Causey I believe, my inbox
got deleted, but yes, this configuration accepts a 2TB; also, this would be
a problem during the installation 3 months ago, and the consequences would
be far different from the reported problem here.

Thanks all for inputs and lets reason what else. I may be able to create a
virtualbox to test some theories in the future, to get to the bottom of it.
The laptop is still in guarantee period, I need to know if there is
something really wrong or if it was just an occasional, yet rare, event.

My best,

Beco


PS. Sorry for not copying Abdullah and Causey on the reply, my inbox got
cleaned here.

-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

#200810

On 10/1/18 5:31 PM, Beco wrote:
> On Sun, 30 Sep 2018 at 15:25, David Christensen <dpchrist@holgerdanske.com>
> wrote:
> 
>>
>> Download and run Seagate's diagnostic tool on the 2 TB drive:
>>
>> https://www.seagate.com/support/downloads/seatools/
>>
>> (I have been using the bootable CD image for years ("legacy"), but it
>> looks like they finally have a bootable USB image.)
>>
>> Use a camera and take pictures of the various screens.  Transcribe them
>> into a reply to this list.
>>
>>
>>
>>
> Dear David, hi guys/girls that are following this problem.
> 
> First, the delay in my response is due to the fact that I'm fighting a lot
> of parallel battles here, but I'm still trying to solve this problem.
> In the next days I'll always try to reply.
> 
> I've done the bootable seagate HD test. It came up 100% ok, all tests. The
> HD is new, I wouldn't expect different, but it is always reassuring to do
> the real test and see the results.
> 
> To recap, I used the computer all day, since morning until late night. From
> time to time, say, about 3 times that day, I noticed a small 5 seconds long
> freeze. Sometimes, in other days, KDE wouldn't open plasmashell, but I did
> not need to reboot; just open tty1, and run systemctl restart sddm, and it
> would run ok. Not sure if this is related.
> 
> That night, I turned off the computer, no errors, nothing.
> 
> Next morning, first boot, it booted fast and I was faced with an empty
> desktop. Also empty /home. After e2fsck, all my files reappeared as inode
> numbers in lost+found. I was able to recover some of them, and I have
> backup for others. But I'm not still putting them on the hard disk.
> 
> I'm still waiting for possible causes or solutions, or just to know what
> have happened in the first place.
> 
> Is the "swap" partition something that could cause that if turned off by
> "swapoff"? Because I remember turning it off during that afternoon. But I
> used the computer a LOT until night, so, I don't think there was any link
> to the disappearance of ALL files. Also, when I used swapoff, it was almost
> without use anyway.
> 
> I read above from Abdullah, that it is very unlike to have such major FS
> fail, and it looks like it didn't "flush" the night I turned off. This is
> also my guess, it is the only thing that make sense. Maybe the inode table
> was in the memory and got corrupted. But it is strange to figure that,
> since the filesystem is EXT4, and it is very stable nowadays.
> 
> Someonelse asked if 2TB is ok for this laptop, Causey I believe, my inbox
> got deleted, but yes, this configuration accepts a 2TB; also, this would be
> a problem during the installation 3 months ago, and the consequences would
> be far different from the reported problem here.
> 
> Thanks all for inputs and lets reason what else. I may be able to create a
> virtualbox to test some theories in the future, to get to the bottom of it.
> The laptop is still in guarantee period, I need to know if there is
> something really wrong or if it was just an occasional, yet rare, event.
> 
> My best,
> 
> Beco
> 
> 
> PS. Sorry for not copying Abdullah and Causey on the reply, my inbox got
> cleaned here.

If Seagate Seatools is happy with the 2 TB drive, that should eliminate 
the 2 TB drive, the cable, and the motherboard port as sources of the 
problem.


Just to be thorough, you should also check memory.  I've been using 
memtest86+ for years, but other people say there a better choices. 
STFW, pick one you like, download it, and run it.


STFW "lenovo ideapad 320", I see that there are many variants of that 
model.  However, I am unable to find technical specifications or a 
service manual.  Please post a description of the machine, the specific 
Lenovo part number/ whatever, and a URL to the exact same computer (if 
available).  If you have a URL for technical specifications and/or 
service manual, please post those.


Please run the following commands as root and post your complete console 
session (prompts, commands, and output):

# cat /etc/debian_version

# uname -a

# parted --list

# mount

# swapon

# df

# cat /etc/apt/sources.list

# ls /etc/apt/sources.list.d/

# cat /etc/apt/sources.list.d/*


Have you installed any software using means other than the Debian 
built-in package management tools?  E.g. download a source tarball, 
build it, install it; download a *.deb package and install it; etc.?


Have you changed, recompiled, or otherwise messed with the kernel?


David

[toc] | [prev] | [next] | [standalone]

#200811

On Mon, 1 Oct 2018 19:06:20 -0700 David Christensen said:
 
> If Seagate Seatools is happy with the 2 TB drive, that should eliminate 
> the 2 TB drive, the cable, and the motherboard port as sources of the 
> problem.

I'm not sure how an on-disk cache problem could definitively be caught without
power cycling. What if on-disk controller is ignoring all cache related
commands? (cache bypass, cache invalidate, cache flush)

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#200813

On 10/1/18 8:40 PM, Abdullah Ramazanoğlu wrote:
> On Mon, 1 Oct 2018 19:06:20 -0700 David Christensen said:
>   
>> If Seagate Seatools is happy with the 2 TB drive, that should eliminate
>> the 2 TB drive, the cable, and the motherboard port as sources of the
>> problem.
> 
> I'm not sure how an on-disk cache problem could definitively be caught without
> power cycling. What if on-disk controller is ignoring all cache related
> commands? (cache bypass, cache invalidate, cache flush)

I must depend upon Seagate to get their firmware and their diagnostics 
right.  If their firmware were so bad as to ignore all cache related 
commands, we'd probably hear about it.


Every disk that I have seen fail the manufacturer's diagnostic has also 
exhibited bad behavior in whatever computer it occupied.


But, the contrary is not true.  When it is false (e.g. bad behavior, 
passes diagnostic), either I'm confused, some other part of the computer 
is having issues, or both.  (PEBKAC is a common root cause.)


Then again, as the OP's computer seems to be a newer model, some 
hardware could be unsupported and/or the supporting device drivers could 
be incomplete and/or buggy.  I know Intel provides reference FOSS 
drivers for their stuff; does AMD?  Without a shopping list of the key 
chips in the OP's computer, there is no way to check support status.


David

[toc] | [prev] | [next] | [standalone]

#200827

On Mon, 1 Oct 2018 23:18:13 -0700 David Christensen said:
> On 10/1/18 8:40 PM, Abdullah Ramazanoğlu wrote:

> > I'm not sure how an on-disk cache problem could definitively be caught
> > without power cycling. What if on-disk controller is ignoring all cache
> > related commands? (cache bypass, cache invalidate, cache flush)  
> 
> I must depend upon Seagate to get their firmware and their diagnostics 
> right.  If their firmware were so bad as to ignore all cache related 
> commands, we'd probably hear about it.

I am not questioning the quality of the diagnostic tool, but there can
be situations where it is technically impossible to detect a failure. For
instance, a destructive cache test can write some data to disk, flush the
cache, invalidate the cache, and then reread the data just written. But if both
cache flush and cache invalidate don't work, then this scheme will produce a
false positive result.

* Write test data to disk --> OK

* Flush on-disk cache --> Controller returns "OK" but doesn't do it.

* Invalidate the cache --> Controller again returns "OK", without doing it.
  Now, diag tool thinks the data is recorded on media and the cache is clear.
  In fact, it is not recorded and is solely on cache.

* Reread the data --> Success. Controller reads it from cache, while the diag
  tool thinks it is coming from the media.

In such a case, there is no way the diag tool can definitively test on-disk
cache.

Only sure way is power-cycling, as far as I can see.

> Then again, as the OP's computer seems to be a newer model, some 
> hardware could be unsupported and/or the supporting device drivers could 
> be incomplete and/or buggy.  I know Intel provides reference FOSS 
> drivers for their stuff; does AMD?  Without a shopping list of the key 
> chips in the OP's computer, there is no way to check support status.

Agreed.

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#200812

On Mon, 1 Oct 2018 21:31:27 -0300 Beco said:

> I've done the bootable seagate HD test. It came up 100% ok, all tests. The
> HD is new, I wouldn't expect different, but it is always reassuring to do
> the real test and see the results.

I am not familiar with seatools, but there are usually destructive and
non-destructive test suites in such tools. I hope you have run a destructive
one (which destroys data on disk) as some marginal errors can only be caught by
destructive tests.

> Is the "swap" partition something that could cause that if turned off by
> "swapoff"?

I don't think so.

> I read above from Abdullah, that it is very unlike to have such major FS
> fail, and it looks like it didn't "flush" the night I turned off. This is
> also my guess, it is the only thing that make sense. Maybe the inode table
> was in the memory and got corrupted. But it is strange to figure that,
> since the filesystem is EXT4, and it is very stable nowadays.

But the journal is passing through on-disk controller, too. If the drive is
mishandling its on-drive cache, then an FS corruption is still possible. Even
if journal writes are "direct", the drive could be ignoring that (i.e. caches
it nevertheless) without flushing it prior to power-off, corrupting the journal
as well.

If the FS survives through reboots, but falters when the laptop is power
cycled, then a cache flush issue is still probable.

Another test method might be hibernation. If resume from hibernation works,
then that rules out on-disk caching problem.

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#200814

On 10/1/18 9:07 PM, Abdullah Ramazanoğlu wrote:
> On Mon, 1 Oct 2018 21:31:27 -0300 Beco said:
> 
>> I've done the bootable seagate HD test. It came up 100% ok, all tests. The
>> HD is new, I wouldn't expect different, but it is always reassuring to do
>> the real test and see the results.
> 
> I am not familiar with seatools, but there are usually destructive and
> non-destructive test suites in such tools. I hope you have run a destructive
> one (which destroys data on disk) as some marginal errors can only be caught by
> destructive tests.

The only destructive test I recall from SeaTools is writing zeros to the 
disk.  Of course, you don't want to do that until the data recovery 
effort is complete. And, the OP seems to be ignoring recovery and still 
trying to use the drive (!).


>> Is the "swap" partition something that could cause that if turned off by
>> "swapoff"?
> 
> I don't think so.

+1


>> I read above from Abdullah, that it is very unlike to have such major FS
>> fail, and it looks like it didn't "flush" the night I turned off. This is
>> also my guess, it is the only thing that make sense. Maybe the inode table
>> was in the memory and got corrupted. But it is strange to figure that,
>> since the filesystem is EXT4, and it is very stable nowadays.

I'm not sure how much isolation the various parts of the Linux kernel 
now have from each other.  In the bad old days of monolithic kernels, 
everything inside the kernel could touch everything else in the kernel. 
A buggy driver in one subsystem could wreak havoc in any other subsystem.


> But the journal is passing through on-disk controller, too. If the drive is
> mishandling its on-drive cache, then an FS corruption is still possible. Even
> if journal writes are "direct", the drive could be ignoring that (i.e. caches
> it nevertheless) without flushing it prior to power-off, corrupting the journal
> as well.
> 
> If the FS survives through reboots, but falters when the laptop is power
> cycled, then a cache flush issue is still probable.
> 
> Another test method might be hibernation. If resume from hibernation works,
> then that rules out on-disk caching problem.
> 
> Regards

Hypotheses require experiments to confirm or refute them.


The chicken-and-egg problem is to get some solid data to start with. 
We'll see if the OP responds to my shopping list of requested commands.


David

[toc] | [prev] | [next] | [standalone]

#200881

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

>
> >> Is the "swap" partition something that could cause that if turned off by
> >> "swapoff"?
> >
> > I don't think so.
>
> +1
>
>
Good, I also suspected so. I'm a linux user since slackware installed from
floppies, I never saw something like that!

Look this "ls" command in the lost+found folder. It is amazing. Some of
those numbers are actually folders containing other files. Files inside the
folder have their names, which make things easier.

Be amazed:
http://sprunge.us/FlKCOY

The whole /home disapeared, EXCEPT:

http://sprunge.us/KnXpEJ

Isn't that puzzling??

I did last time only non-destructive tests using the seagate tool. I could
just today make a full backup (not that I was ignoring anyone, I know the
importance of backups. My laptop stayed turned off until I got the time to
properly do it).

Now it is running a destructive test, and it will take more 5 hours to
finish. Until now (46%) all good. Anyway, I don't believe it is a HD issue.
If it was a cache not sync, it would affect only like 100 files opened at
the time of turning it off. Not the whole drive.

Regarding the "shop list", I use debian since etch (I used redhat before it
was sold, and suse -- again sold), and it is my policy to (almost) never
install software if not from sources. I only installed I believe "scidvspc"
(a chess program) in other laptop, not this one. I have 3 laptops, 2 local
servers, 1 server in my name at the university (as I'm a professor and my
students use them), and 2 outside the country (rented), all of them using
the same debian version.

$ uname -a
Linux raposa 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30)
x86_64 GNU/Linux

$ cat /etc/apt/sources.list
# generated by
# Debian Sources List Generator (Beta)
# 2013-01-13
# http://debgen.simplylinux.ch/

deb http://ftp.br.debian.org/debian/ stretch main contrib non-free
deb-src http://ftp.br.debian.org/debian/ stretch main contrib non-free

deb http://ftp.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ stretch-updates main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free

add to that the google chrome repository and we are done. (I used also
skype and spotify, not in repos, but again, not in this particular laptop,
so, yep... brand new laptop, 3 months of usage, still tweeking it, setting
my develop environment, vim, gcc, latex, fonts, etc.)


About the hardware itself, I add, from lshw:

   description: Notebook
   product: 81G3 (LENOVO_MT_81G3_BU_idea_FM_ideapad 320-15IKB)
   vendor: LENOVO
   version: Lenovo ideapad 320-15IKB
   description: CPU
   product: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

Other informations on this command regarding HD is not updated, since this
is a file from a backup and I can't run the command in the current machine
state (and I changed HD and added SSD to it). But the memory (RAM) is
SAMSUNG 8GB and a nvidia card with 4GB (that won't work, and I remember
adding backports to sources.apt and trying, then giving up, removing
backports, and cleaning the packages from it).


Also, another nice question you guys asked: hybernation or sleep: I never
use them. I always turn off completely, then in the next day, turn it on.

What else? Did I forget something? Sorry, I need to go to sleep now.

I'll keep updating as soon as I can, not so fast as I wish.

Thanks for your interest and tips.

My best,

 Béco

PS. I see this now:


> Another test method might be hibernation. If resume from hibernation
works,
> then that rules out on-disk caching problem.
>

I'll do it only after the destructive test is done, and I re-fill the
/home. I'm also thinking in installing a second linux distro in another
200GB partition I have free in the 2TB drive. (Summary: 2TB is 200GB free -
reserved for the future, 8GB swap, and the rest is /home)


OP done for today. Sincerely, Beco.


-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

#200889

Beco wrote:
...
> Good, I also suspected so. I'm a linux user since slackware installed from
> floppies, I never saw something like that!
...

  also, perhaps malware is a possibility?  once you said
chrome and other backport repositories i'm not sure i'd 
trust stuff coming from those as easily as from the main
archives as they may be high enough profile targets and 
worth someone's time to attack...

  i try to be careful about such things and it's helped
me avoid some common hack attempts.


  songbird

[toc] | [prev] | [next] | [standalone]

#200911

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

On Thu, 4 Oct 2018 at 08:34, songbird <songbird@anthive.com> wrote:

>   also, perhaps malware is a possibility?  once you said
> chrome and other backport repositories i'm not sure i'd
>
>
Of course it crosses ones mind, but from backport I used ONLY nvidia, then
back to nouveau when the video card wasn't recognized.
Chrome as malware facilitator, yes, it could be, but I doubt this strange
thing would happen. Lets try to focus on other possible explanations before
assuming that. But I'll run some sort of scanner just to be 100% sure,
thanks.

We need to keep in mind what happened if we are to solve the puzzle. I
don't know if there would be, for example, a LOG referring kernel panic at
some level.

Maybe somehow there is a EXT4 table of inodes that got lost? I'm not sure
how that would be. Is there anyone more familiar with the implementation of
linux, or we are just users guessing?

Reporting back the HD test, after the seagate destructive test, I can
safely rule out that the HD is in perfect condition.

I also installed a new grub menu (memtest86+) and I'll let it running
tonight. Tomorrow I'll post the results.

After HD and RAM, I would go to intel chip. It baffles me that nowadays,
every now and then, there is a new microcode update. Intel really did a job
on all of us.

Also, maybe systemd has some services that could do something like that.
Not sure. I used a new partition to install Devuan today. The dual boot is
set. Both distros are running ok, no problems at all, not signs of nothing.
Just a empty /home. This is really something new for me. I'm in this list
since emails were sent by paper, and I never saw that, even once.


My best,
Beco.

PS. Just to remind us how strange it is: stay 5 seconds wondering:

lost+found$ ls
http://sprunge.us/FlKCOY




-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

#200925

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

Dear linux users,

The memtest86+ came out clean.

I run out of ideas to what was the problem.

Wasn't it a very serious problem I would already stop writing emails. But
to have the whole /home disappear, is something that changes your
expectations for the whole linux experience.

It has to have a simple explanation hidden somewhere (and
testable/repeatable/provable, not just guesses)

Thanks,

Beco

-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web