[Testing Update] 2018-11-22 - Kernels

update
testing

#21

In addition those senseless discussions make these threads hard to read and to follow.


#22

Children, keep your criticisms to “Off Topic”


#23

This linguistic comment flood also means there are no actual errors with this update. I confirm this! :wink:


#24

I encountered a kernel panic after the latest update


Chckrooting shows no new packages.
What can i do?


#25

restart with USB Install stick
check with gparted ( or fdisk -l)
that there is no errors for mount partitions

if you have others disks or multiOs
give return of

parted -l 
or 
fdisk -l

#26

@stephane
I checked all drives in gparted with no error

parted -l

gives this output

Model: ATA TOSHIBA THNSNJ51 (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  106MB  105MB   fat32        EFI system partition          boot, esp
 2      106MB   240MB  134MB                Microsoft reserved partition  msftres
 3      240MB   322GB  322GB   ntfs         Basic data partition          msftdata
 4      322GB   323GB  1074MB  fat32                                      msftdata
 5      323GB   512GB  188GB   ext4


Model: ATA Hitachi HTS54502 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  250GB  250GB               pv1   lvm


Model: ATA WDC WD1001FALS-0 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  1000GB  1000GB               pv2   lvm


Model: ATA TOSHIBA DT01ACA2 (scsi)
Disk /dev/sdd: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  1978GB  1978GB  ext4
 2      1978GB  2000GB  22.0GB  ext4


Model: TOSHIBA TransMemory (scsi)
Disk /dev/sdf: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      32.8kB  1930MB  1930MB  primary               boot
 2      1930MB  1934MB  4194kB  primary               esp

when chroot into the system i don’t see sdd2 not mounted as /var

sda                                                                              
├─sda1               vfat                 E69E-4438                              
├─sda2                                                                           
├─sda3               ntfs        Windows  7E7EA9D37EA9848D                       
├─sda4               vfat                 B262-EEC1                              /mnt/repchroot/boot
└─sda5               ext4        System   b779c489-ee07-42ed-9947-138c290cd556   /mnt/repchroot
sdb                                                                              
└─sdb1               LVM2_member          fUTWdz-Ogdc-RPfB-qTQa-bnpi-FPoz-OSEyjb 
  └─VG_backup-Backup ext4                 9d9099a2-1d96-4246-8d2b-d6c2ff67205c   
sdc                                                                              
└─sdc1               LVM2_member          B0ZjHd-fTUR-K6se-C7QS-jDl8-3PS5-KzVJzm 
  └─VG_backup-Backup ext4                 9d9099a2-1d96-4246-8d2b-d6c2ff67205c   
sdd                                                                              
├─sdd1               ext4                 0a2958c5-87c4-4de3-b885-61249cbdcf83   /mnt/repchroot/home
└─sdd2               ext4                 b0c52eff-9769-44c7-beaf-2764c6a8c97e   

So maybe there is a problem but fstab looks good

UUID=E69E-4438 /boot/efi vfat defaults,noatime 0 2
UUID=B262-EEC1 /boot vfat defaults,noatime 0 2
UUID=b779c489-ee07-42ed-9947-138c290cd556 / ext4 defaults,noatime,relatime 0 1
UUID=0a2958c5-87c4-4de3-b885-61249cbdcf83 /home ext4 defaults,noatime 0 2
UUID=b0c52eff-9769-44c7-beaf-2764c6a8c97e /var ext4 defaults,noatime 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0


#27

Since the kernel is complaining about a missing init, you can try to boot with “init=/bin/bash” added to the kernel command line. You should end up with a root shell and the root partition mounted read only. If this works you know at least that the kernel can mount your root fs. Another thing you can check (after booting from external media) is the integrity of the initramfs. Have you seen any error messages while it was recreated? Corruption can happen if no space is left on your /boot fs.


#28

@philm , can you add next version kernel 4.19.4 ?
they revert new x86 speculation


#29

ok restart with install USB key
start chroot
change mirrors to Stable

manjaro-chroot -a ( select manjaro) 
pacman-mirrors --set-branch stable 
pacman -Syyuu
exit ( quit chroot )

and reboot


#30

Thanks for the help.
But it looks like my system is screwed.

manjaro-chroot -a

does not work. And when manually mounting all partitions restoring grub does not work either.
From this point I dont wanna bother you any longer. I gonna use my backups for a clean installation. cya


#31

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.