[gelöst] Jessie will nicht mehr starten

[Emess]

Habe ein Multiboot System
Part 1 Win
Part 2 Jessie /
Part 3 Jessie /home
Part 4 Testing /
Part 5 Testing /home

Jessie bleibt heut beim booten hängen. siehe Bild



Wer kann da helfen?

[Trollkirsche]

Hi,

Hast du probiert, dein Dateisystem manuell zu reparieren?

fsck -y /dev/sda5

Error 4 ist :
4 Filesystem errors left uncorrected

Am besten das mal von einem Live System aus machen.

[Emess]

hab es einfach mal von Buster gestartet

Code: Alles auswählen

root@buster:~# fsck -y /dev/sda5
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/sda5 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Invalid inode number for '.' in directory inode 1065503.
Fix? yes

Entry 'tmp' in /var/tmp/??? (1065503) has deleted/unused inode 1055683.  Clear? yes

Invalid inode number for '.' in directory inode 1065508.
Fix? yes

Entry '..' in .../??? (1065508) has deleted/unused inode 1054775.  Clear? yes

Invalid inode number for '.' in directory inode 1065509.
Fix? yes

Entry 'tmp' in /var/tmp/??? (1065509) has an incorrect filetype (was 2, should be 1).
Fix? yes

Invalid inode number for '.' in directory inode 1065514.
Fix? yes

Entry '..' in <1054703>/<1065514> (1065514) has an incorrect filetype (was 2, should be 1).
Fix? yes

Invalid inode number for '.' in directory inode 1065519.
Fix? yes

Entry 'tmp' in /var/tmp/??? (1065519) has deleted/unused inode 1062292.  Clear? yes

Invalid inode number for '.' in directory inode 1065533.
Fix? yes

Entry '..' in .../??? (1065533) has deleted/unused inode 1062224.  Clear? yes

Pass 3: Checking directory connectivity
'..' in /usr/share/kde4/apps/kspaceduel/icons/hicolor/32x32 (1065503) is /var/tmp (1050807), should be /usr/share/kde4/apps/kspaceduel/icons/hicolor (1065502).
Fix? yes

Unconnected directory inode 1065504 (/usr/share/kde4/apps/kspaceduel/icons/hicolor/32x32/???)
Connect to /lost+found? yes

'..' in /usr/share/kde4/apps/kspaceduel/icons/hicolor/22x22 (1065508) is ... (1054775), should be /usr/share/kde4/apps/kspaceduel/icons/hicolor (1065502).
Fix? yes

Unconnected directory inode 1065509 (/var/tmp/???)
Connect to /lost+found? yes

'..' in /usr/share/kde4/apps/kspaceduel/icons/hicolor/16x16/actions (1065514) is <1054703> (1054703), should be /usr/share/kde4/apps/kspaceduel/icons/hicolor/16x16 (1065513).
Fix? yes

'..' in /usr/share/kde4/apps/kspaceduel/sprites/playerinfo (1065519) is /var/tmp (1050807), should be /usr/share/kde4/apps/kspaceduel/sprites (1065518).
Fix? yes

'..' in /usr/share/doc/kde/HTML/en/kspaceduel (1065533) is ... (1062224), should be /usr/share/doc/kde/HTML/en (662518).
Fix? yes

Pass 4: Checking reference counts
Inode 662518 ref count is 115, should be 114.  Fix? yes

Inode 1050807 ref count is 3, should be 6.  Fix? yes

Inode 1054703 ref count is 0, should be 1.  Fix? yes

Inode 1062221 ref count is 1, should be 2.  Fix? yes

Inode 1065502 ref count is 7, should be 5.  Fix? yes

Inode 1065504 ref count is 3, should be 2.  Fix? yes

Inode 1065508 ref count is 3, should be 2.  Fix? yes

Inode 1065509 ref count is 3, should be 2.  Fix? yes

Unattached inode 1065510
Connect to /lost+found? yes

Inode 1065510 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065511
Connect to /lost+found? yes

Inode 1065511 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065512
Connect to /lost+found? yes

Inode 1065512 ref count is 2, should be 1.  Fix? yes

Inode 1065513 ref count is 4, should be 3.  Fix? yes

Unattached inode 1065515
Connect to /lost+found? yes

Inode 1065515 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065516
Connect to /lost+found? yes

Inode 1065516 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065517
Connect to /lost+found? yes

Inode 1065517 ref count is 2, should be 1.  Fix? yes

Inode 1065518 ref count is 4, should be 3.  Fix? yes

Unattached inode 1065520
Connect to /lost+found? yes

Inode 1065520 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065521
Connect to /lost+found? yes

Inode 1065521 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065522
Connect to /lost+found? yes

Inode 1065522 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065523
Connect to /lost+found? yes

Inode 1065523 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065524
Connect to /lost+found? yes

Inode 1065524 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065525
Connect to /lost+found? yes

Inode 1065525 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065526
Connect to /lost+found? yes

Inode 1065526 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065527
Connect to /lost+found? yes

Inode 1065527 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065528
Connect to /lost+found? yes

Inode 1065528 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065529
Connect to /lost+found? yes

Inode 1065529 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065530
Connect to /lost+found? yes

Inode 1065530 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065534
Connect to /lost+found? yes

Inode 1065534 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065535
Connect to /lost+found? yes

Inode 1065535 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065536
Connect to /lost+found? yes

Inode 1065536 ref count is 2, should be 1.  Fix? yes

Unattached inode 1065545
Connect to /lost+found? yes

Inode 1065545 ref count is 2, should be 1.  Fix? yes

Pass 5: Checking group summary information
Block bitmap differences:  +4203554 +(4203556--4203557) +4203559 +(4203561--4203562)
Fix? yes

Free blocks count wrong (4794120, counted=4794118).
Fix? yes

Free inodes count wrong (1839974, counted=1839993).
Fix? yes


/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 269463/2109456 files (0.2% non-contiguous), 3607546/8401664 blocks
root@buster:~# 

[Emess]

Wieso auch immer das hat geklappt.
Großes Lob an das Forum. Hier kümmert man sich sich echt um jeden DAU!

[Emess]

Hi,

Hast du probiert, dein Dateisystem manuell zu reparieren?

fsck -y /dev/sda5

Error 4 ist :
4 Filesystem errors left uncorrected

Hatte von Buster über root auf jessie zugegriffen. Danach war es kaputt.

[Trollkirsche]

Wieso auch immer das hat geklappt.
Großes Lob an das Forum. Hier kümmert man sich sich echt um jeden DAU!

Kein Problem, ich freu mich das ich dir helfen konnte