![]() ![]() your /boot partition/directory needs to be big enough to hold these files. Normally I would do something like this: fsck. The main problem I have is I don't know what the names partitions of the virtual drives of the RAID are. The server has 4 HD using a hardware RAID5 system. On this situations some recommend to boot the server with a live linux image, like a SystemRescueCD or USB boot stick to get access to the root shell. clonezilla, gparted or systemrescuecd would make good live systems to use as a base for this. I can boot into a systemRescueCD no problem. if you don't currently have a spare partition free for this, you can shrink a swap partition to give yourself enough space to make a rescue partition (which you can populate with debootstrap).Īnd if you can't use a swap partition, you can set up a grub entry to boot into a live cd image (using the kernel and initrd from the iso).but you'll have to modify the initrd filesystem to have your correct IP address etc and make sure that sshd is running. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the hard disk partitions. temporarily set grub's default), ssh into, and run fsck on your real rootfs. Description: SystemRescue (formerly known as SystemRescueCd) is a Linux system rescue toolkit available as a bootable medium for administrating or repairing your system and data after a crash. That adds "-y" to the boot time fsck, so it doesn't risk the remote server being stuck waiting for someone to login at the console and run fsck.Īlso, just in case something like happens again, it's worthwhile having a rescue partition that you can boot (e.g. On systems where I created a separate /home partition, fsck runs fine with no errors.It's also a good idea on debian and debian-derivatives like ubuntu to edit /etc/default/rcS on remote servers and set "FSCKFIX=yes" Boot from a system rescue CD: Download - SystemRescueCd then in console mode only - do not use X - you can run fsck. Oddly enough, only the root '/' filesystem is affected. This behavior can be replicated by installing Linux Mint 16 into a virtual machine and running fsck as above. Applying all available updates doesn't solve the problem. However, after subsequent reboots, running 'fsck -f /dev/sda1' from live media fixes wrong block and inode counts each and every time. I used the Linux SystemRescueCd-6.0.2 Released on Feb 21, 2019. I can boot into a systemRescueCD no problem. fsck internally uses the respective filesystem checker command. After a fresh install, rebooting with SystemrescueCD or RIP Linux and running 'fsck -f /dev/sda' shows no errors. Use fsck to check all the partitions on the drive. Fsck Command Specific to a Filesystem Type. ![]() ![]() The root filesystem is formatted with ext4. I set the system to do a fsck at reboot by doing BOTH (which I suspect doing. Purely by accident, last week I noticed something odd with Linux Mint 16 Cinnamon and MATE 32-bit no codecs versions. Bye the way, I dumped MS in 1991, switched to OS2 and eventually Linux in 1999. Lenovo Thinkpads, in particular, work just fine with Linux Mint. You can use fdisk or df command to list the hard drive in Linux. You will need to run the command either as root user or use it with sudo. fsck options filesystem If you do not specify a filesystem, the system will analyze your fstab file ( /etc/fstab) for the devices to scan. Mostly I do machines with Windows but, perfectly good machines with borked Windows COAs get Linux Mint no codec version. The fsck command follows a pattern similar to most Linux commands. By way of introduction, I am employed by a large recycler in Vermont to refurbish computers for a living so, I'm familiar with memory and hard drive testing, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |