Cannot open file delete Starting udev

[kimwally]

Hi a friend of mine has been getting this error message on the latest PcLinusOs 2012.8 :

Cannot open file delete
Starting udev

and so I suggested
fsck /dev/sdx (replacing x for each partition)
which they apparently did.
Now they have this message:

e2fsck from util-linux-ng 2.18
e2fsck 1.42 (29-Nov-2011)
e2fsck: need terminal for interactive repairs
e2fsck 1.42 (29-Nov-2011)
e2fsck: need terminal for interactive repairs
fsck: fsck.swap: not found
fsck: Error 2 while executing fsck.swap for /dev/sda5
e2fsck 1.42 (29-Nov-2011)
e2fsck: need terminal for interactive repairs

Should we just re-install the whole thing or is there a way it can be fixed using terminal commands?
thanks
kim

[Just17]

Cannot open file delete
Starting udev

Those messages are normal and can be ignored.

[kimwally]

Kim wrote
Thanks, I just received another email from my friend, again using the live disk and logged into a terminal -this is the result,

[root@localhost ~]# fsck /dev/sda1
fsck from util-linux-ng 2.18
e2fsck 1.42 (29-Nov-2011)
/dev/sda1: recovering journal
/dev/sda1; clean, 149627/2528061 files, 1431056/10092544 blocks
[root@localhost ~]# fsck /dev/sda2
fsck from util-linux-ng 2.18
e2fsck 1.42 (29-Nov-2011)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda2
Could this be a zero-length partition?




Now this is a look at the partition table (prepared earlier


Disk/dev/sda: 500.1 GB, 500107862016 bytes

18 heads, 4 sectors /track, 13566294 cylinders,

Total 976773168 sectors

Units=sectors of *512 = 512 bytes

Sector size(logical/physical):512 bytes/512 bytes

I/O size(minimum/optical):512 bytes/512 bytes

Disk identifier:0x993e7d17

 

Device Boot     Start               End                 Blocks           id      System

/dev/sda1*               4          80744399       40372198       83     Linux

/dev/sda2     8074440        976773167     448014384        5     Extended

/dev/sda5     8074440          89380799         4318198      82     Linux swap/ Solaris         

/dev/sda6   89380804        976773167         4439682      83     Linux




[root@localhost ~]#


So. please let us know -what to do next? thanks again

[kjpetrie]

/dev/sda2 is an extended partition and has (as fsck suggests) no content. It is a placeholder for the logical partitions. The only partitions he can run fsck on are /dev/sda1 and /dev/sda6.

Is there a problem or is he just not expecting to see status messages? These are quite normal in a complex system and can be useful for debugging when there is something to debug.

[kimwally]

Kim wrote

Thanks again -such a relief to have "gurus on tap!"
The original idea of using fsck is to try and deal with this error message that keeps popping up

Cannot open file delete
Starting udev

So, now I guess we should move to the next  -> fsck /dev/sda6

Is that a good move now?

[kjpetrie]

These are not error messages. They are just for information. If everything works leave well alone.

[kimwally]

Hi again,
She just sent me this.....any advice? what to do next?


[root@localhost ~]# fsck /dev/sda5
-bash:fsck/dev/sda5: No such file or directory
[root@localhost ~]# fsck /dev/sda6
fsck from util-linux-ng 2.18
e2fsck 1.42 (29-Nov-2011)
/dev/sda6 contains a file system with errors, check force.
Pass 1: Checking inodes,blocks, and sizes
Error reading block 61341855 (Attempt to read block from filesystem resulted in short read) while getting n ext inode from scan. Ignore error<y>? yes
Pass 2: Checking directory structure
Error reading block 59777084 (Attempt to read block from filesystem resulted in short read) while getting n ext inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Directory inode 14942410, block 0, offset 0: directory corrupted
Salvage<y>? yes
Missing '.' in directory inode 14942410
Fix <y>? yes
Setting filetype for entry'.' in (14942410) to 2
Missing '..' in directory inode 14912410.
Fix<y> yes
Setting filetype for entry'.' in (14942410) to 2
Error reading block 59777125 (Attempt to read block from filesystem resulted in short read) while getting n ext inode from scan. Ignore error<y>? yes

And it continues for all the different blocks which seems to be a lot and I answered for yes to fix.
Next lot of narrative:

Entry '11cc3f944e3704d17512fa4c54c57d065d.png' in /Mary/.thumbnails/normal (15337455) has deleted/unused inode 15337472. Clear<y>? yes
Pass3: Checking directory connectivity
Unconnected directory inode 14912410(/???/???)
Connect to /lost+found?<y>?yes
'..' in/Mary/ g.config (14942410) is <NULL inode> (0) should be /Mary (14942209)
Fix<y>? yes
Unconnected directory 14942411 (/Mary/ g.config/??)
Connect to /lost+found<y>?
'..' in/Mary/ .local/share/akonadi (14942491) is <NULL inode> (0) should be /Mary (14942309)
Fix<y>?
 
And it continues to"

Pass 4: Checking reference counts
Inode 2 ref count is 1, should be 5. Fix<y>? yes

And it continues:

Pass 5: Checking group summary information .............
..... (a whole of numbers) ............
Fix<y>?yes

/dev/sda6:*******FILE SYSTEM WAS MODIFIED ******
/dev/sda6: 9287/27738112 files (0.9% non-contiguous), 2048321/110924045 blocks
[root@localhost ~]#

[kjpetrie]

That partition was severely corrupted. It might be worth looking at what's in Lost & Found or copying that somewhere for later analysis, in case it's something important.

Otherwise, all seems fine, unless there's a specific problem.