[SOLVED] Stromausfall = kein boot mehr

Discussion in 'Proxmox VE (Deutsch)' started by DraycD, Aug 9, 2018.

  1. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    Hi, wir hatten hier einen Stromausfall. Nun startet proxmox nur noch in emergency mode.

    ich habe den verdacht das was mit der sda3 nicht stimmt. was kann ich machen? Ich will die Daten nicht verlieren / neu aufsetzen ... auf der sda sind die VM images drauf (weiss aber nicht auf 1,2 oder 3 - glaube aber auf sda3)

    was braucht ihr von mir das ihr mir helfen könnt?
     
  2. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    hab nun noch eine aufname vom Bootprozess:
     
  3. Alwin

    Alwin Proxmox Staff Member
    Staff Member

    Joined:
    Aug 1, 2017
    Messages:
    1,503
    Likes Received:
    131
    Schau dir mal /home/X-Backup an, das kann nicht gemountet werden. Im Rescue Mode die /etc/fstab editieren und den Eintrag auskommentieren. Dann sollte ein ordentlicher Boot möglich sein.
     
  4. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    0.0 meinst das is alles :eek:

    EDIT

    leider auch nach dem auskommentieren nix anders
     
    #4 DraycD, Aug 10, 2018
    Last edited: Aug 10, 2018
  5. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    107
    Likes Received:
    4
    Steht im dmesg-output uU, welche disk, die Probleme hat - vl. hilft ein manueller fsck (je nach Zustand der disk)
     
  6. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    bevor ichs vergess schon mal danke

    kann ich im emergency mode SSH aktiveren? das ich die ausgabe hier posten kann?
    er schreibt ca 20 seiten hin aber ich kann vll 1/2 hoch scrollen mehr geht nicht (warum auch immer)

    EDIT:
    so startet man den SSH Service:
    Code:
    sudo /etc/init.d/ssh start

    das ist der output:
    Code:
    1.699026] usb 1-1.3: New USB device found, idVendor=26e3, idProduct=106c
    [    1.699029] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    1.699032] usb 1-1.3: Product: EXCELDIGI Wireless Device
    [    1.699034] usb 1-1.3: Manufacturer: EXCEL
    [    2.140024] ata1.01: failed to resume link (SControl 0)
    [    2.140101] ata2.01: failed to resume link (SControl 0)
    [    2.300094] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
    [    2.300105] ata1.01: SATA link down (SStatus 0 SControl 0)
    [    2.300260] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
    [    2.300271] ata2.01: SATA link down (SStatus 0 SControl 0)
    [    2.303021] ata1.00: ATA-9: ST3000DM001-1ER166, CC46, max UDMA/133
    [    2.303024] ata1.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [    2.303094] ata2.00: ATA-8: Hitachi HTS547550A9E384, JE3OA60A, max UDMA/133
    [    2.303095] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [    2.308233] ata2.00: configured for UDMA/133
    [    2.308251] ata1.00: configured for UDMA/133
    [    2.308439] scsi 0:0:0:0: Direct-Access     ATA      ST3000DM001-1ER1 CC46 PQ: 0 ANSI: 5
    [    2.308810] sd 0:0:0:0: Attached scsi generic sg0 type 0
    [    2.309062] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
    [    2.309064] sd 0:0:0:0: [sda] 4096-byte physical blocks
    [    2.309112] sd 0:0:0:0: [sda] Write Protect is off
    [    2.309113] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [    2.309117] scsi 1:0:0:0: Direct-Access     ATA      Hitachi HTS54755 A60A PQ: 0 ANSI: 5
    [    2.309225] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [    2.309463] sd 1:0:0:0: Attached scsi generic sg1 type 0
    [    2.309761] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
    [    2.309763] sd 1:0:0:0: [sdb] 4096-byte physical blocks
    [    2.309768] scsi 2:0:0:0: Direct-Access     ATA      WDC WD60EZRZ-00G 0A80 PQ: 0 ANSI: 5
    [    2.309801] sd 1:0:0:0: [sdb] Write Protect is off
    [    2.309802] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [    2.309849] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [    2.309970] sd 2:0:0:0: Attached scsi generic sg2 type 0
    [    2.310008] sd 2:0:0:0: [sdc] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
    [    2.310009] sd 2:0:0:0: [sdc] 4096-byte physical blocks
    [    2.310022] sd 2:0:0:0: [sdc] Write Protect is off
    [    2.310024] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [    2.310049] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [    2.310064] scsi 3:0:0:0: Direct-Access     ATA      ST5000DM003-2FH1 0001 PQ: 0 ANSI: 5
    [    2.310198] sd 3:0:0:0: Attached scsi generic sg3 type 0
    [    2.310234] sd 3:0:0:0: [sdd] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
    [    2.310235] sd 3:0:0:0: [sdd] 4096-byte physical blocks
    [    2.310249] sd 3:0:0:0: [sdd] Write Protect is off
    [    2.310251] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
    [    2.310279] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [    2.346192] sd 1:0:0:0: [sdb] Attached SCSI disk
    [    2.369111]  sda: sda1 sda2 sda3
    [    2.370090] sd 0:0:0:0: [sda] Attached SCSI disk
    [    2.370379]  sdc: sdc1 sdc2 sdc5
    [    2.371040] sd 2:0:0:0: [sdc] Attached SCSI disk
    [    2.451193]  sdd: sdd1 sdd2 sdd5
    [    2.452086] sd 3:0:0:0: [sdd] Attached SCSI disk
    [    2.454484] Freeing unused kernel memory: 2412K
    [    2.454485] Write protecting the kernel read-only data: 20480k
    [    2.455038] Freeing unused kernel memory: 2008K
    [    2.458122] Freeing unused kernel memory: 1872K
    [    2.463187] x86/mm: Checked W+X mappings: passed, no W+X pages found.
    [    2.463188] x86/mm: Checking user space page tables
    [    2.467959] x86/mm: Checked W+X mappings: passed, no W+X pages found.
    [    2.510862] hidraw: raw HID events driver (C) Jiri Kosina
    [    2.511027] ahci 0000:06:00.0: version 3.0
    [    2.511172] ahci 0000:06:00.0: SSS flag set, parallel bus scan disabled
    [    2.511217] ahci 0000:06:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl IDE mode
    [    2.511219] ahci 0000:06:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
    [    2.511546] scsi host4: ahci
    [    2.511615] scsi host5: ahci
    [    2.511649] ata5: SATA max UDMA/133 abar m512@0xf7800000 port 0xf7800100 irq 26
    [    2.511651] ata6: SATA max UDMA/133 abar m512@0xf7800000 port 0xf7800180 irq 26
    [    2.513363] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
    [    2.514457] usbcore: registered new interface driver usbhid
    [    2.514458] usbhid: USB HID core driver
    [    2.514697] usbcore: registered new interface driver usbkbd
    [    2.514698] usbcore: registered new interface driver usbmouse
    [    2.549349] atl1c 0000:05:00.0: version 1.0.1.1-NAPI
    [    2.576372] input: EXCEL EXCELDIGI Wireless Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:26E3:106C.0001/input/input5
    [    2.576780] atl1c 0000:05:00.0 enp5s0: renamed from eth0
    [    2.636243] hid-generic 0003:26E3:106C.0001: input,hidraw0: USB HID v1.01 Keyboard [EXCEL EXCELDIGI Wireless Device] on usb-0000:00:1a.0-1.3/input0
    [    2.636342] input: EXCEL EXCELDIGI Wireless Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:26E3:106C.0002/input/input6
    [    2.636668] hid-generic 0003:26E3:106C.0002: input,hidraw1: USB HID v1.01 Mouse [EXCEL EXCELDIGI Wireless Device] on usb-0000:00:1a.0-1.3/input1
    [    2.636859] input: EXCEL EXCELDIGI Wireless Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/0003:26E3:106C.0003/input/input7
    [    2.652097] clocksource: Switched to clocksource tsc
    [    2.696120] hid-generic 0003:26E3:106C.0003: input,hidraw2: USB HID v1.01 Device [EXCEL EXCELDIGI Wireless Device] on usb-0000:00:1a.0-1.3/input2
    [    2.815238] md/raid1:md2: active with 2 out of 2 mirrors
    [    2.815254] md2: detected capacity change from 0 to 4996034002944
    [    2.826414] ata5: SATA link down (SStatus 0 SControl 300)
    [    3.138460] ata6: SATA link down (SStatus 0 SControl 300)
    [    3.195998] raid6: sse2x1   gen()  9748 MB/s
    [    3.243995] raid6: sse2x1   xor()  7603 MB/s
    [    3.291998] raid6: sse2x2   gen() 12173 MB/s
    [    3.339994] raid6: sse2x2   xor()  8852 MB/s
    [    3.387996] raid6: sse2x4   gen() 14198 MB/s
    [    3.435995] raid6: sse2x4   xor() 10680 MB/s
    [    3.435996] raid6: using algorithm sse2x4 gen() 14198 MB/s
    [    3.435997] raid6: .... xor() 10680 MB/s, rmw enabled
    [    3.435997] raid6: using ssse3x2 recovery algorithm
    [    3.436201] xor: automatically using best checksumming function   avx     
    [    3.436314] async_tx: api initialized (async)
    [    3.543221] random: crng init done
    [    3.810438] Btrfs loaded, crc32c=crc32c-intel
    [    4.205681] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
    [    5.019946] ip_tables: (C) 2000-2006 Netfilter Core Team
    [    5.073814] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
    
    die ausgabe: cfdisk /dev/sdb
    Bildschirmfoto 2018-08-10 um 11.28.00.png
     
    #6 DraycD, Aug 10, 2018
    Last edited: Aug 10, 2018
  7. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    107
    Likes Received:
    4
    sieht auf den ersten blick nicht auffaellig aus (aber vielleicht kommt davor/dahinter noch was relevantes)

    fsck bei den disks versuchen und haendisch mounten?
     
  8. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    bei der die ich vermute kann ichs nicht testen da sie in use ist:

    Code:
    fsck from util-linux 2.29.2
    e2fsck 1.43.4 (31-Jan-2017)
    fsck.ext2: No such file or directory while trying to open /etc/sda
    Possibly non-existent device?
    root@draycd:~# fsck /etc/sda1
    fsck from util-linux 2.29.2
    e2fsck 1.43.4 (31-Jan-2017)
    fsck.ext2: No such file or directory while trying to open /etc/sda1
    Possibly non-existent device?
    root@draycd:~# fsck /dev/sda
    fsck from util-linux 2.29.2
    e2fsck 1.43.4 (31-Jan-2017)
    /dev/sda is in use.
    e2fsck: Cannot continue, aborting.
    
    
    root@draycd:~# fsck /dev/sda3
    fsck from util-linux 2.29.2
    root@draycd:~# fsck /dev/sda2
    fsck from util-linux 2.29.2
    fsck.fat 4.1 (2017-01-24)
    /dev/sda2: 5 files, 576/516190 clusters
    root@draycd:~# fsck /dev/sda1
    fsck from util-linux 2.29.2
    e2fsck 1.43.4 (31-Jan-2017)
    ext2fs_open2: Bad magic number in super-block
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1
    
    The superblock could not be read or does not describe a valid ext2/ext3/ext4
    filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
     or
        e2fsck -b 32768 <device>
    
    root@draycd:~# clear
    
    root@draycd:~# fsck /dev/sda
    fsck from util-linux 2.29.2
    e2fsck 1.43.4 (31-Jan-2017)
    /dev/sda is in use.
    e2fsck: Cannot continue, aborting.
    
    
    root@draycd:~# fsck /dev/sda1
    fsck from util-linux 2.29.2
    e2fsck 1.43.4 (31-Jan-2017)
    ext2fs_open2: Bad magic number in super-block
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1
    
    The superblock could not be read or does not describe a valid ext2/ext3/ext4
    filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
     or
        e2fsck -b 32768 <device>
    
    root@draycd:~# fsck /dev/sda2
    fsck from util-linux 2.29.2
    fsck.fat 4.1 (2017-01-24)
    /dev/sda2: 5 files, 576/516190 clusters
    root@draycd:~# fsck /dev/sda3
    fsck from util-linux 2.29.2
    root@draycd:~#
    
    kann es daran liegen das es im lvm2 format ist?

    die ausgabe: cfdisk /dev/sdb
    [​IMG]

    #6
     
    #8 DraycD, Aug 10, 2018
    Last edited: Aug 10, 2018
  9. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    kann es was mit dem "invaid checksum" zu tun haben ? beim boot?

    konnte nun booten, nachdem ich alle hdd' aus der etc/fstab raus hab.
     
  10. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    107
    Likes Received:
    4
    welche "invalid checksum" meldung?

    vom dmesg output sieht es so aus, als gaebe es ein mdraid, vom cfdisk output als gaebe es zumindest ein lvm - lsblk zeigt eine recht hilfreiche uebersicht ueber die blockdevices an.
    fsck muesste in dem fall auf das lv mit dem filesystem gemacht werden.

    je nach inhalt der fstab koennte es sein, dass eine disk getauscht wurde/entfernt wurde ohne dass /etc/fstab angepasst wurde. Das wuerde das lange wait und den rescue mode erklaeren
     
  11. DraycD

    DraycD Member

    Joined:
    May 25, 2018
    Messages:
    30
    Likes Received:
    1
    er bootet wieder, es hatte mir die ISO HDD (sdb) und die Backup HDD (sdd) zerschossen.
    es war so wie du dachtest eine hdd die gemountet werden sollte hat den fehler verursacht.


    DANKE dir soooooooo sehr!
     
  12. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    107
    Likes Received:
    4
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice