Read-Only File System after Upgrade Kernel under CentOS 7
Hi all,
I upgraded the kernel of CentOS 7 to 4.11.4, and reboot the VM. After that, I cannot change anything in the system. No matter what I do, it says Read-only file system.
I want to work with the latest kernel, what's the correct way to upgrade kernel under CentOS 7 on Google Cloud Engine?
Thank you very much!
Try remounting the filesystem
sudo mount -o remount,rw /dev/sda3
Related
Anyone did Catalina kernel debug? I tried to copy the development edition of kernel from KDK folder(Catalina 536) to /System/Library/Kernels in the VMWare fusion target VM (Catalina beta8) according their readme file, anyhow that folder is readonly, you cannot copy any file there,
anyone has the solution?
One possible way is that reboot into recovery mode, but with VMWare fusion VM, it seems both latest version (Beta 8) and one vmx download from internet are not working, I tried both Cmd-R and 'reboot recovery' with nram settings.
Remoutning the root file system using
$ mount -u -w /
Worked for me to be able to copy the new kernel over. However my laptop is still slowly booting the debug kernel so I have not been able to verify end to end kernel debugging yet.
I installed CentOS 7.6 on a system with NVME drive. Everything went successfuly and the system was behaving as expected. It came with kernel 3.10 by default so I upgraded the kernel to the latest (5.1.5) and changed kernel boot order in grub. However, whenever the system is rebooted with 5.x kernel version, it goes into emergency mode with the below error:
Could not boot
/dev/centos/root doesn't exist
/dev/centos/swap doesn't exist
/dev/mapper/centos-root doesn't exist
The system reboots just fine if I switch back to kernel version 3.10. I am getting this error only with 5.x version.
I compared /boot/initramfs for both 3.x and 5.x and saw below kernel drivers included in 3.x, but not in 5.x
lsinitrd -k <5.x kernel version>
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvdimm
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvdimm/libnvdimm.ko.xz
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvdimm/nd_btt.ko.xz
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvdimm/nd_pmem.ko.xz
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvme
usr/lib/modules/3.10.0-57.el7.x86_64/kernel/drivers/nvme/host
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvme/host/nvme-core.ko.xz
usr/lib/modules/3.10.0-957.el7.x86_64/kernel/drivers/nvme/host/nvme.ko.xz
Therefore, I performed the below command to include nvme drivers in 5.x and rebuilt initramfs.
echo 'add_drivers+=" nvme "' > /etc/dracut.conf.d/nvme.conf
Once I did this, I could see nvme drivers being included in 5.x initramfs (different filenames though).
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvdimm
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvdimm/nd_btt.ko
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvdimm/nd_pmem.ko
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvme
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvme/host
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvme/host/nvme-fabrics.ko
usr/lib/modules/5.1.5-1.el7.elrepo.x86_64/kernel/drivers/nvme/host/nvme-tcp.ko
I rebooted the system again with 5.x kernel version and again I get the same error. I also read up about some rootdelay in case the device is delayed in being detected by the kernel, however, I didn't try that given the system starts just fine with kernel 3.x.
Does anyone have any idea what might be going on here?
I have just succesfully installed Arch Linux on my Laptop that also runs windows 10. My problem is that there is no visible boot menu where I can choose my os, it always just starts windows. when I run
cfdisk
it lacks the option of adding a bootable flag to my linux partition.
Is there any way of adding a boot menu?
Thanks in advance
Check out Dual boot with windows
You can install system-boot
mount /dev/sda5 /mnt
mkdir /mnt/boot
mount /dev/sda2 /mnt/boot #mount EFI
run this command to install bootloader
bootctl install
And then
cp /usr/share/systemd/bootctl/arch.conf /boot/loader/entries/
Now just modify the arch.conf and enjoy your archlinux.
I have successfully installed and run the OSX 10.11 on virtualbox a few while ago and I was able to successfully work with it and install xcode 7 on it and work with it without problems.
Now after a few days I have come to it and I have run the virtual machine and got the following error!!
It says: "Checking catalog file, incorrect number of thread records". It keeps working a while and finishes with closing the VM.
I didn't make any changes to it. I even created a new machine again using the existing ".VMDK" file and still no change.
I really need the data on it. Can you please help me with fixing the virtual machine? I have a .VMDK file with the size of 43 GB.
Thanks in advance.
Thanks GOD, I could finally find a solution for this problem. I launched another Mac virtual machine and followed this link on Youtube and installed Diskwarrior on the vm and from this vm, I could repair the other .VMDK file using Diskwarrior. I hope it helps :)
I had the same problem, found a simplier solution. I booted the virtual machine with Ubuntu live cd.
In terminal:
sudo apt install hfsprogs
# HFS file system consistency check, use fdisk -l to find your disk indetifier
sudo fsck.hfsplus /dev/sda2
I have a Mac running OSX El Capitan, which cannot easily mount a Linux ext3 filesystems. I have a USB drive with exactly this file system and need to access.
OSXFUSE + Ext2 FUSE module seems not to work as I have installation errors that might be related to El Capitan being too new (the Ext FUSE module conplains about that at least). There is another commercial product, called Paragon ExtFS, that throws me similar problems for the trail version.
Now, I am thinking of an alternative by using VirtualBox, with an Ubuntu 14.04 that mounts the drive.
I added the following line to /etc/fstab
/dev/sdb1 /media/mystuff ext3 defaults 1 2
but rebooting my machine makes no difference. I have to add that this USB drive is USB3.
What am I doing wrong? Can I technically mount a USB drive that Mac per standard does not understand?
Yes, you can mount ext3 in Ubuntu running in VirtualBox on your El Capitan.
That's what worked for me (I had 12.04, but it shouldn't matter):
Get the latest VirtualBox and VirtualBox Extension Back from https://www.virtualbox.org/wiki/Downloads
Make sure your Ubuntu has been shut down, navigate to virtual machine Settings -> Ports -> USB
Enable USB Controller, choose USB2.0 just in case as most USB3 devices are backwards compatible. Add your device to the list.
Start your Ubuntu, log in and check for devices:
sudo fdisk -l
Make sure you have ext3 as System. It may also be Linux LVM nowadays. If so, proceed with https://superuser.com/a/116634
mount manually:
sudo mount /dev/sdb1 /media/mystaff