WTF? File-system is in read-only in FC2 AGAIN?!?!


Recommended Posts

gahahahdjl;dlsjf;lksjdf;lasjd;lwaewjekr

I can't beleive this, but the same thing is happening to me again as it did in this post:

https://www.neowin.net/forum/index.php?show...2&hl=lock+/home

I can't figure out what the heck is causing it, but I'm afraid to reboot because last time i rebooted i ended up losing a lot of data and ended up having to reinstall.

now, there is no mail coming into my server because the file system is in read-only mode.

Is there anyway for me to scan my disk for error without rebooting?

Please help. Thanks

-Nic

mtab:

  Quote

/dev/hda2 / ext3 rw 0 0

none /proc proc rw 0 0

none /sys sysfs rw 0 0

none /dev/pts devpts rw,gid=5,mode=620 0 0

usbdevfs /proc/bus/usb usbdevfs rw 0 0

/dev/hda1 /boot ext3 rw 0 0

none /dev/shm tmpfs rw 0 0

/dev/hdb1 /mnt/backup ext3 rw 0 0

sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0

fstab
  Quote

LABEL=/                /                      ext3    defaults        1 1

LABEL=/boot            /boot                  ext3    defaults        1 2

none                    /dev/pts                devpts  gid=5,mode=620  0 0

none                    /dev/shm                tmpfs  defaults        0 0

none                    /proc                  proc    defaults        0 0

none                    /sys                    sysfs  defaults        0 0

/dev/hda3              swap                    swap    defaults        0 0

/dev/cdrom              /mnt/cdrom              udf,iso9660 noauto,owner,kudzu,ro 0 0

/dev/fd0                /mnt/floppy            auto    noauto,owner,kudzu 0 0

/dev/hdb1              /mnt/backup            ext3    defaults        0 0

Last time this happened it came up with a bunch of bad blocks on my hard drive or something. Coincidentally, last time it happened it was during a RAR processes. I ran a RAR processes over the weekend, but everything has been working through this morning and then this afternoon Ximian started barking at me because it can't access my mail box folder because of read-only crap.

The RAR processes takes file from my / mount point to my /mnt/backup point, so there is no writing in / done by rar, that I know of.

Thats the only similarity i can find, however.

Any ideas?

-Nic

Ummm.. You do know that /home isn't even mounted right now.

Try adding this to your fstab (where hd?? is the volume for /home):

/dev/hd?? /home ext3 defaults 0 0

Or issue a mount command (but this won't stay after a reboot).

  nic said:
I can't beleive this, but the same thing is happening to me again as it did in this post:

https://www.neowin.net/forum/index.php?show...2&hl=lock+/home

That's probably because your used the mount command and then rebooted.

Drives mounted in this fashion don't stay mounted from one boot to the next.

You need to add a reference in the fstab file to mount the drive on each boot.

(mtab just tells you what is currently mounted so don't go editing it).

Ok, out of crisis zone.

Ran fsck /dev/hda2 and it found a TON of orphaned inodes that it "fixed". I'm not sure what kind of damage i'm looking at at my files, but everything seems to be fine now. And it said some peculiar things while rebooting but it seems to be fine. I think i'll probably go for 1 more reboot to see if those peculiar things go away this time.

I think there is some sort of problem between RAR and RSYNC. The first time this happened they were both running at the same time, working on the same files. This time I ran my RAR processes over the weekend and disabled my RSYNC backup. The RAR processes was done by this morning and all morning server ran fine. Then just before I went to lunch i re-enabled my RSYNC cron job to backup everyones data and when I got back from lunch is when my filesystem was on read-only lock down.

Very strange.... Where do i even go to submit a bug or something?

-Nic

[Edit] Ok, i've rebooted and shutdown a couple of times now and this is the only weird message that comes up during shutdown.:

  Quote
KDSKBENT: Invalid Argument

failed to bind key 255 to value 557

Not sure if it is serious or not. Time to fire up google. [/Edit]

Edited by nic
  nic said:
mtab:/dev/hda2 / ext3 rw 0 0

none /proc proc rw 0 0

none /sys sysfs rw 0 0

none /dev/pts devpts rw,gid=5,mode=620 0 0

usbdevfs /proc/bus/usb usbdevfs rw 0 0

/dev/hda1 /boot ext3 rw 0 0

none /dev/shm tmpfs rw 0 0

/dev/hdb1 /mnt/backup ext3 rw 0 0

sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0

fstab:

LABEL=/                /                      ext3    defaults        1 1

LABEL=/boot            /boot                  ext3    defaults        1 2

none                    /dev/pts                devpts  gid=5,mode=620  0 0

none                    /dev/shm                tmpfs  defaults        0 0

none                    /proc                  proc    defaults        0 0

none                    /sys                    sysfs  defaults        0 0

/dev/hda3              swap                    swap    defaults        0 0

/dev/cdrom              /mnt/cdrom              udf,iso9660 noauto,owner,kudzu,ro 0 0

/dev/fd0                /mnt/floppy            auto    noauto,owner,kudzu 0 0

/dev/hdb1              /mnt/backup            ext3    defaults        0 0

*whoosh* :blink:

This is what scares me about linux..

  nic said:
Ok, out of crisis zone.

Ran fsck /dev/hda2 and it found a TON of orphaned inodes that it "fixed". I'm not sure what kind of damage i'm looking at at my files, but everything seems to be fine now. And it said some peculiar things while rebooting but it seems to be fine. I think i'll probably go for 1 more reboot to see if those peculiar things go away this time.

I think there is some sort of problem between RAR and RSYNC. The first time this happened they were both running at the same time, working on the same files. This time I ran my RAR processes over the weekend and disabled my RSYNC backup. The RAR processes was done by this morning and all morning server ran fine. Then just before I went to lunch i re-enabled my RSYNC cron job to backup everyones data and when I got back from lunch is when my filesystem was on read-only lock down.

Very strange.... Where do i even go to submit a bug or something?

-Nic

[Edit] Ok, i've rebooted and shutdown a couple of times now and this is the only weird message that comes up during shutdown.:

Not sure if it is serious or not. Time to fire up google. [/Edit]

bugzilla.redhat.com, just make sure the bug hasn't been posted already

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Don’t care about a wrestling union. No normal person should care. 
    • Limassol, Cyprus. Just south of Turkey. NOT Russia.
    • Hello, Given the reports of Chinese Mini PCs shipping with malware, I would recommend wiping the machine and performing a clean install of Windows on it before use.  From what I can infer from the reports, the Mini PCs that shipped with malware were not the result of targeted purposeful action on the part of the device manufacturers (which is something that has happened with low-cost Android smartphones and TV boxes from China) but rather due to lax security in the manufacturing process.   Getting back to the subject at hand, there are a few steps you will want to go through before wiping the Mini PC: You can start preparing even before the Mini PC arrives.  Once you have ordered it and know the brand and model, go to the manufacturer's website and download all of the latest device drivers, BIOS (UEFI) firmware updates, machine-specific software (if any), and manuals.  Many Mini PC manufacturers do not do a lot of customization of their device drivers, just shipping whatever device drivers the the silicon vendors provide.  I still recommend downloading them, though, just in case there are some customizations or for initial install since those are the drivers you know the manufacturer validated for the Mini PC.  Store these in a safe place, so you have them ready when the Mini PC arrives. Use Microsoft's Windows Media Creation Tool to create an installation USB.  You can also create a directory on installation USB--like C:\DRIVERS\ or whatnot--and store the extracted device drivers there in case you need them while or after installing Windows. Once the Mini PC arrives, and you have your Windows installation USB available, you can proceed with wiping the PC and doing the clean install.  Here's how you do that, step-by-step: Check the computer and make sure you know how to boot it from a USB flash drive (may be a specific key you have to press when the computer is powered on, or a change to the BIOS (UEFI) firmware settings.  The PC may tell you what key combination you need to press to boot from another drive, or the manual for the PC may it. Plug the USB flash drive into the computer and power it up using the means to have it boot from the Windows install USB. Once the computer finishes booting, it should be at a Windows installation screen. Do not agree to any prompts, copyright licenses, or click on any buttons. Press the Shift + F10 keys together to open a Command Prompt. Run DISKPART to start the command-line disk partitioning utility. The command line prompt will change to DISKPART>. At the DISKPART> prompt, type LIST DISK to get the numbers of all drives installed in the system. Make a note of what number is assigned to what drive (if the Mini PC has more than one drive).  At the DISKPART> prompt, type SEL DISK n  where n is the number of the drive containing Windows. At the DISKPART> prompt, type CLEAN and this will erase the GPT/MBR code from the beginning of the drive. *WARNING:* After performing the clean operation, the drive now be blank/erased, and everything on it will be gone (all files, etc.).  You can exit DiskPart and just continue with the Windows installation as you normally would.  If needed, you can install the device drivers you put on the Windows install media to get your network connection up and running, and from there run Windows Update to get the operating system and device drivers up to date Regards, Aryeh Goretsky
    • Why? Amazon has some great shows and Fallout was near perfect.
  • Recent Achievements

    • Week One Done
      cac1lll earned a badge
      Week One Done
    • One Month Later
      Falcon.ai earned a badge
      One Month Later
    • Week One Done
      Falcon.ai earned a badge
      Week One Done
    • Dedicated
      EYEREX earned a badge
      Dedicated
    • First Post
      Electronic Person earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      628
    2. 2
      ATLien_0
      238
    3. 3
      Xenon
      166
    4. 4
      neufuse
      142
    5. 5
      +FloatingFatMan
      123
  • Tell a friend

    Love Neowin? Tell a friend!