Issue#2283: Linux - file system repair

  • Using open suse 11.4. Rebooting was informed that Root file system is currently mounted read only and to repair manually then reboot
    informed to ad- write do bash# mount-n-o remount,rw/
    This failed . Questions is there a simple way to repair the problem.

    Any suggestions to fix same would be appreciated .

    0 Answers

    Sorry, your answer is too short !

  • Issue#109061: Linux - Cannot find a way to mount an EXT4 file system so SAMBA has write access

    I have an NTFS external hard drive on my Raspberry Pi (raspian) which is slow and I think the file system driver is flakey. Trying to replace with with EXT4 external hard drive (no partitions) Logged in the to Pi, I can read and write the EXT4 drive just fine. I get write access through SAMBA with the NTFS drive, but none of the variations in MOUNTing gets me write access to the EXT4 drive through SAMBA I cannot find any log file entries explaining the failure to grant write access. Samba.conf attached as text file (shares near bottom of file) fstab attached as text file (same results when using MOUNT command) mount -l output attached as text file Any help greatly appreciated. Jonathan Attached Files fstab.txt (652 Bytes) mount list.txt (2.1 KB) smb.conf.txt (12.5 KB)

  • Issue#112649: Linux - File system with errors.... Fedora 21 emergency mode, can't read itable bloc

    Hi I've been using fedora core 21 along with win 7 in dual-boot for a while now without any problem. Now, suddenly from yesterday, the fedora installation is booting into the emergency mode. It says that dev/mapper/fedora-usr contains a file system with errors, check forced. After the check, it prints out some ineligible data and goes to emergency mode, asks me for the password, tells me to type journalctl -xb for sys logs or to press ctrl-D to try booting into default mode. Journalctl-xb spits out around 9300 lines, some of which are red, and ctrl-D goes back again into the emergency mode. Pls help... The windows installation runs just fine by the way.

  • Issue#174264: PC File system failure: aborting execution and another issue...

    Guys, I have a lot of issues with Ubi games, excuse me for my bad english, but I will try to explain all the issues: 1st (the MOST IMPORTANT): All the Ubisoft games have a problem that when I save a graphical configuration and I restart the game, it still executing in 2K resolution and with another graphical setup... This is very annoying because it messes my desktop and because I need to set it up again... 2nd: When I load Far Cry 4, appears a message error: File system failure: Aborting execution so I can't play... I'm very angry because the support doesn't answer me since a month ago, so I can't play any Far Cry...

  • Issue#176235: Linux - Need to resize (enlarge) a file system.

    Hi, My system is Suse Linux 11 PL4. I need to enlarge my file system /dev/sdb1. In my VM I enlarged /dev/sdb from 200GB to 300GB. I went in to the YAST expert partitioner and tried to resize /dev/sdb1 to the new maximum. But I got a message that says I need to unmount the file system. I tried doing this using both Yast and umount but both times got a message that the system was in use. What is the best way to get this filesystem resized? I have read about changing the kernel parameters to boot in single user mode. I am a little wary of this because I don't want to end up with a problem booting. If this is the correct approach please provide and example of the change to make. Thanks for any help. Mel

  • Issue#190155: Linux - an error occurred during the file system check

    ***an error occurred during the file system check ***Dropping you to a shell; the system will try ***to mount the filesystem(s), when you leave the shell. dracut Warning: filesystem) Generating "/run/initrampfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a buy report. To get more debug information in the report, reboot with "rd.debug" added to the kernel command line. Dropping to debuf shell. (Repair:/#

  • Issue#211988: Linux - How to force inode32 to xfs file system?

    Hi, I've just installed CentOS and unfortunately all LVM partitions are mounted with inode64 option. I need two of them to be inode32, however remounting it with optio inode32 does not work (still mounted as inode64). I've tried to add inode32 option to fstab file: Code: /dev/mapper/centos-root /                      xfs    defaults        0 0 UUID=2d99278e-0e88-4a16-9e13-04cb7eff4bcf /boot                  xfs    defaults        0 0 /dev/mapper/centos-local00 /local                  xfs    defaults,inode32        0 0 /dev/mapper/centos-var_lib /var/lib                xfs    defaults,inode32        0 0 /dev/mapper/centos-swap swap              &nbs

  • Issue#225826: Linux - The installer can't put a btrfs file system in a partition that already contains a file syst

    This could be a follow-up of this thread: Test made with an ISO built from Slackware64-current as of Thu Mar 3 20:05:41 UTC 2016. When trying to use a partition that already contains a file system as target, if a btrfs is chosen to format it this fails with an error message from mkfs.btrfs like e.g. "/dev/sda2 appears to contain an existing file system (ext4) use the -f option to force overwrite". Easy fix: sed -i "s/mkfs.btrfs/mkfs.btrfs -f/" /usr/lib/setup/SeTpartitions With the fix applied blkid confirms that the partition contains a btrfs file system. I assume that if the user wants to format to btrfs another partition (for /home, for instance) the -f option is still needed. Anyhow lilo fails when / contains a btrfs file system, but that's a known issue and not the point here.

  • Issue#231833: Linux - Suggestion: remove mentions of the ext3 file system in the installer.

    The ext3 file system has been dropped from the kernel since 4.3 and if chosen in 'setup' (file SeTpartitions) the user will end up with an ext4 file system anyway (see attached pic). So, not to let users believe that they still have a choice between two different file systems I suggest that ext3 be no more proposed in the list of Linux file systems. This won't remove the support for ext3 in existing file systems as the ext4 driver is backward compatible with them as pointed out by Linus Torvalds cf. Attached Thumbnails  

  • Issue#261699: Linux - swap file and partition reboot issue with free cmd

    I had a standard CentOS 7 partition layout with /boot, /, /var, and swap (2G) partitions carved out. So the free cmd showed me that I had 2G total. As a test, I added roughly 500MB more swap through a swap file: Code: # free # dd if=/dev/zero of=/extra-swap bs=1M count=500 # mkswap /extra-swap # swapon -a # free At this point, the free command returned same amount, roughly 2G. So I added the swap file to my fstab to make it persistent then rebooted: Code: # vim /etc/fstab ... /extra-swap          swap        swap      defaults 0 0 ... # reboot Upon reboot, the free cmd now showed 2.5G My question is, why did free not show the swap until reboot? Ideas and / or better ways to do this? SK

  • Issue#296313: Wich is the best file system for installing a Linux OS?

    I've been using ext4 for installing a Linux OS, however, I would like to know in for example reiserFS would be better, and wich would be the differences between them. I have installed Ubuntu, openSUSE, Debian and some of their distros. Thanks in advance for the help you can provide.

  • Issue#376053: Linux - Replicas of Block Group Descriptor Table of Ext3 file system is not getting updated:

    Hi, As you know, the block group descriptor table is replicated in various block groups starting from first block group. But the file system always uses the first block group's block descriptor table for it's operations. Suppose if you add/delete new files or re-size the existing file then the block group descriptor table will get updated. For e.g., if you add a new file and if it takes 10 data blocks the free blocks count will be reduced by 10 and free inodes count will be reduced by 1. Similarly, for other operations. What I am seeing is only first block group's block descriptor table is getting updated where as other replicas are not getting updated. I tried a) waited for some time to see if it has some delay to update the replicas. It didn't work b) I ejected the pen drive and plugged in to see if it updates the replicas on plug in. It also didn't work. I couldn't find any related information in the internet. I would like to know when will the replicas get updated. Please let m

  • Issue#377183: Where does the Camera ICD file located in a Linux RT CVS System?

    Where does the Camera ICD file located in a Linux RT CVS System? Camera ICD file location can be find on the following directory in a Linux RT system (CVS) /var/local/natinst/niimaqdx/Data Cheers,Ruchi

  • Issue#403760: Best file system for a 47TB partition in linux?

    I'm working to setup a server for Unitrends backup.  I have 47TB of usable space available.  I'm quite the linux noob and just stumbled into the 16TB limit on EXT4.   I'm running CentOS 6.5 what file system would be best here?  Looks like maybe XFS but I can't be sure since it looks like it will lose data if the server gets dumped for some reason. This is the source of my info. 

  • Issue#410254: Linux - Need help in understanding File system utilization expression

    Hi, The below file system utilization check command is being used in one of the solution. df -k | awk '$1~/^\/dev\//{keep="y"}NF==1{arg1==$1}NF==5{if(keep="y")print arg1,$0;keep="n"}NF==6{if(keep=="y")print;keep="n"}' I need to understand how the above expression is working. I do understand that it is concatenates two lines into one if the file system utilization is broken into two lines. The rest I'm unable to understand.

  • Issue#412540: Linux - issue with updating system

    Had this setup for a while now without any issues and just noticed today when I did apt-get update then apt-get upgrade it gets stuck. This is my old sources.list file: Code: deb jessie main deb-src jessie main deb jessie/updates main contrib deb-src jessie/updates main contrib # jessie-updates, previously known as 'volatile' deb jessie-updates main contrib deb-src jessie-updates main contrib # debian 8 "jessie" deb jessie main contrib non-free deb-src jessie main contrib non-free # jessie BACKPORTS #deb jessie-backports main # VirtualBox deb jessie contrib This is what what happened when I tried to apt-get upgrade Code: [email protected]:~#

  • Issue#450654: Linux - File System

    The Btrfs (B-Tree) file system is supported as a Technology Preview in Red Hat Enterprise Linux 7. This file system offers advanced management, reliability, and scalability features. It enables users to create snapshots, it allows for compression and integrated device management.

  • Issue#465461: LXer: 10 Essential Linux Commands For Navigating The File System

    Published at LXer: This guide shows 10 essential commands required for navigating the file system using the terminal. Find out where you are, how to move around, how to create folders, remove folders and create links. Read More...

  • Issue#488908: Linux - Where are I/O and file system source codes located in Ubuntu kernel files?

    i want to know. How the journaling file system works? Where are I/O and file system source codes located in Ubuntu kernel files? Thanks.

  • Issue#559739: Ubuntu - [Kali] Linux version of MS's sfc /scannow? For offline system repair.

    This was originally posted here however i have a slightly different use for having a utility that can provide sfc functionality. I regularly repair windows systems where i work after malware or virus removal you need to sometimes run an SFC scan however on this one particular system running the sfc /scannow from the command prompt yields a BSOD however i am unable to run the DART disk for windows because of some other error. I have a Kali Linux machine that i have set up for a Tech Assistant with partition tools hdd diagnostic utilities and the like. Is there a way i can run some kind of sfc scan on externally plugged in HDD's from Kali? Or as an alternative is there a hash sum database of windows system files that i could run an md5sum or shasum against in order to verify the integrity of the windows system files? I know its a rather odd request for a community of Linux administrators but i haven't found a Microsoft solution to the Micro

  • Issue#578839: Linux - unable to trace IN_MODIFY event for system file using inotify

    I am trying to track the changes happening to "/sys/class/net/eth0/carrier" using inotify. But if I try to track /tmp/one I am seeing it is giving expected result. Not able to understand what the problem is in the code. Can someone help me in doing the need ? Following is the program I am using. Code: /*This is the sample program to notify us for the file creation and file deletion takes place in “/tmp” directory*/ #include <stdio.h> #include <stdlib.h> #include <errno.h> #include <unistd.h> #include <sys/types.h> #include <sys/inotify.h> #include <poll.h> #define EVENT_SIZE  ( sizeof (struct inotify_event) ) #define EVENT_BUF_LEN    ( 1024 * ( EVENT_SIZE + 16 ) ) int main( ) {         struct inotify_event *event;         char buffer[EVENT_BUF_LEN];         struct pollfd poll_fd[1];         int ifd = inotify_init();    

  • Issue#610540: Linux - unable to unmount the file system

    [[email protected] scsi_host]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 13G 6.2G 6.1G 51% / tmpfs 931M 224K 931M 1% /dev/shm /dev/sda1 283M 33M 236M 13% /boot /dev/vx/dsk/mouryadg/vol1 200M 3.2M 185M 2% /mountpoint [[email protected] scsi_host]# umount /mountpoint ^C [[email protected] scsi_host]#df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 13G 6.2G 6.1G 51% / tmpfs 931M 224K 931M 1% /dev/shm /dev/sda1 283M 33M 236M 13% /boot /dev/vx/dsk/mouryadg/vol1 13G 6.2G 6.1G 51% /mountpoint [[email protected] scsi_host]# umount /mountpoint UX:vxfs umount.vxfs:ERROR : V-326299: cannot umount /mountpoint:Invalid argument UX:vxfs umount.vxfs:ERROR : V-326299: cannot umount /mountpoint:Invalid argument

  • Issue#634063: Linux - YUMI and Windows System Repair disc

    Please .. I need some explanation: First I created System Repair disc on Windows 7, it had 2 folders and 1 file: boot, sources and bootmgr , then I created a USB drive from those 3. Everything was OK and I was able to get to the System Repair options when I booted from that USB. Then I found that I could use 'multiboot' USB and used YUMI. In YUMI I found option to have multiple boots on one USB. I downloaded Windows 7 System Repair disc ISO, found in YUMI option 'Boot Repair Disk' and created it. When I started it I realized that's not the same as 'System Repair disc'. My question: could someone explain me how I could but 'System Repair disc' on multiboot? Thanks

  • Issue#653597: Redhat Linux cluster file system

    Redhat linux cluster GFS 2 mount is of size 1 TB but winscp is showing size of the directory as 101 TB. what could be the reason?

  • Issue#672686: LXer: Linux Kernel 4.1.25 LTS Improves the OCFS2 Shared-Disk Cluster File System

    Published at LXer: Sasha Levin has published details about the twenty-fifth point release for the Linux 4.1 kernel. Read More...

  • Issue#687850: Linux - File-system for portable HDD

    What is the best filesystem for a portable HDD cross compatible. I'm using Linux Mint. My Portable HDDs are between 500GB to 2TB.

  • Issue#703278: HP - System Recovery File Copy Issue

    Facing issue while running System Recovery Disk 1....  File Copy Fails From E:\PRELOAD\BASE22.swmTo Z:\RM\IMAGE\BASE.22.swm process freezed at 22% and From E:\PRELOAD\BASE21.swmTo Z:\RM\IMAGE\BASE.21.swm Process freezed at 17% no external device attached .....Recovery Discs are also verified by HP support executive. What to do now ???

  • Issue#737523: Linux - no ext3 and ext4 file system on fdisk?

    fdisk /dev/sda click l to list all the file system type. 0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris 1 FAT12 27 Hidden NTFS Win 82 Linux swap / So c1 DRDOS/sec (FAT- 2 XENIX root 39 Plan 9 83 Linux c4 DRDOS/sec (FAT- 3 XENIX usr 3c PartitionMagic 84 OS/2 hidden C: c6 DRDOS/sec (FAT- 4 FAT16 <32M 40 Venix 80286 85 Linux extended c7 Syrinx 5 Extended 41 PPC PReP Boot 86 NTFS volume set da Non-FS data 6 FAT16 42 SFS 87 NTFS volume set db CP/M / CTOS / . 7 HPFS/NTFS/exFAT 4d QNX4.x 88 Linux plaintext de Dell Utility 8 AIX 4e QNX4.x 2nd part 8e Linux LVM df BootIt 9 AIX bootable 4f QNX4.x 3rd part 93 Amoeba e1 DOS access a OS/2 Boot Manag 50 OnTrack DM 94 Amoeba BBT e3 DOS R/O b W95 FAT32 51 OnTrack DM6 Aux 9f BSD/OS e4 SpeedStor c W95 FAT32 (LBA) 52 CP/M a0 IBM Thinkpad hi eb BeOS fs e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a5 FreeBSD ee GPT f W95 Ext'd (LBA) 54 OnTrackDM6 a6 OpenBSD ef EFI (FAT-12/16/ 10 OPUS 55 EZ-Drive a7 NeXTSTEP f0 Linux/PA-RISC b 11 Hidd

  • Issue#746940: Linux - Script Issue with Tar Command: Either tar file created in wrong directory or not at all

    I'm written a bash script to do the following: - using find, grab all .aud files created daily in a certain directory - archive them in .tar.gz format in the same directory - give the archive a meaningful name with the hostname, file type and date of files created - using scp/ssh keys, move .tar.gz from the source to a logging server for storage Here is the code Code: find /ora/oracle/admin/RHNSatDB/adump -ctime -1 -and -name '*.aud' | xargs tar -czvf /ora/oracle/admin/RHNSat/adump "$(hostname -s).aud-$(date --date="24 hours ago" '+%F').tar.gz" sleep 30 scp /ora/oracle/admin/RHNSatDB/adump/*.tar.gz [email protected]:/logdata/linux_servers/ameda4aisrx0234/2016/jun sleep 30 rm -f /ora/oracle/admin/RHNSatDB/adump/*.tar.gz Number of issues where the script isn't working. For the xargs piece, if I don't use the absolute path, the .tar.gz file ends up where the cron job is ran from (/usr/local/bin) If I use the absolute path of /ora/oracle/admin/RHN

  • Issue#815200: Where is the root file system located in an embedded linux system?

    I've managed to get a zynq chip to run linux by putting a uEnv file, a Boot.bin file with an FSBL, bitstream, and Uboot on it, a kernel image, a dtb, and a ramdisk.image.gz.   The ramdisk image seems to be the one that runs, as I end up in a filesystem with all the normal directories, but there are no files in it, and any changes I make do not persist after powering down. So I seem to be in the initrd.   From what I've read, the purpose of initrd is simply to mount the root so I can use that, and the root DOES have persistent memory. But I don't know where that root filesystem is supposed to be.   I have an example SD card which DOES boot into the root filesystem, but I don't actually SEE it in the boot partition of the SD card. So where do I get the root filesystem, where do I put it on the SD card, and how do I get an initrd or an initramfs to mount it?   My best guess would be that the root is written into the BOOT.bin on the example card I have, but since I cant