For some reason my system crash yesterday and I had to power down the machine (the only bit of information I still remember it mentioned CPU2 stop for few seconds). The next day my system only shows grub console. I tried to mount the partition but failed. here's what i tried
Code:
# mount -t ext4 /dev/dm-1 /mnt/oldboot
mount: wrong fs type, bad option, bad superblock on /dev/mapper/XXXXXX,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
How do I recreate an LVM raid 1 partition, without destroying data on the discs? I have a 650GB data partition which is a raid 1 array with ext3. Two days ago, the system (Ubuntu 9.04) started to refuse to write to it, claiming no space left on device - even if there is ca. 102GB free left, if the disk is 85% full (according to df)! Interestingly, removing a couple of GB did not help, after reboot the disk was again full..
I did the "tune2fs -m 0" trick and then forced file check on next reboot by "sudo touch /forcefsck" .. and the result is that the raid partition is gone. I have the two physical drives /dev/sd*, unmounted, but the /dev/md1 is no longer there. What can I do to re-create it, without losing the data? I realized that I ran tune2fs on the physical partitions /dev/sd* - was I supposed to run it on /dev/md1?
I reformatted a ntfs drive to fat32, meaning to only reformat one partition on the drive. Because the partition table is overwritten I cannot simply restore the old partition table. Any thoughts on tools that I can use to manually re-create the partitions and save the data?
OpenSUSE 11.2 server, Gigabyte GA-MA790X-UD4P sda for system, 3 ext4 partitions, working fine.sdb promise RAID1 for data, 1 ext4 partition, working fine.sdc is an eSATA docking station for data backup, 1 encrypted ext4 partition -- here lies the problem.
This configuration has been functional for months until I decided to add two more external drives (sdc) to rotate through backups. I had difficulty with encyption on the first new drive and eventually decided to start over. Using the gui Yast Expert Partitioner, I deleted the single partition. That began a real nightmare...
Since deleting the partition, the system detects drives inserted in the docking station, but does not report them (including a different fully functional drive and a brand new unused drive). I have tested all drives on other computers and they function perfectly. I have rebooted the system several times while troubleshooting this issue.
Could not recreate the partition on server (since it does not recognize the drive), so I used Gparted on another computer - it all went without a hitch, formatted ext4. But when I placed the drive in the dock, the drive still was detected but not recognized.
The partitioning on disk /dev/sdc is not readable by the partitioning tool parted, which is used to change the partition table.
You can use the partitions on disk /dev/sdc as they are. You can format them and assign mount points to them, but you cannot add, edit, resize, or remove partitions from that disk with this tool.
Yast partitioner shows drives: sda, sda1, sda2, sda3, sdb, sdb1 sbc is not listed.
So how did partition deletion cause this issue, and how do I correct the problem? It is possible that my difficulties encrypting the first new drive are related (it's not my first time doing it successfully). It seems the problem is in the Kernel or configuration. I have invested many hours in forums and on google - tried dozens of possible fixes. I'm beginning to suspect system corruption or a bug, however all other system functions are working perfectly.
Although I am new to Fedora/Linux I hope to contribute to the community once I'm on my feet with the OS.I am trying to update the graphics driver (Intel), so I downloaded the file, realized I needed to update libdrm, downloaded that, too, and am now on the step of installing libdrm 2.4.23.I am at the step of typing 'make install' on the command line, and get this error message:libtool: Version mismatch eror. This is libtool 2.2.6b Debian Debian-2.2.6b-2, but the definition of this LT_INIT comes from libtool 2.2.10. You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2 and run autoconf again.It appears that I have a newer version of libtools than is needed. How do I recreate aclocal.m4 with macros from an older libtool version, specifically 2.2.6b Debian-2.2.6b-2? Or is the problem with LT_INIT?
I've done three Fedora 12 installs recently. Two were from the complete DVD. generic and KDE versions. In both cases, KDE desktop was by default graced with nice translucent panel where the icons for Firefox & etc. could frolic and play and exhibit single-click behavior. The third system started out as a Vista laptop that got a rootkit. Booted to a Live CD, backed up my data, did an install. It took a bit to get all the required KDE packages installed, but even so I didn't get that desktop panel. I found the "add panel" control, and I can add widgets to it, but I can't figure out how to recreate that desktop panel.
My most recent F11 -> F12 was a near-fiasco, because I had the bad luck of foolishly having two distinct physical drives in the same system, where the /(root) partition on each drive had exact same UUID (result of partition cloning and neglect to change the UUID on the copy)
BUT! the UUID redundancy was not the initial trigger of my problems (its near-disastrousness played itself out only while I was REMEDYING the initial problem). The initial trigger: insufficient space on my /boot partition. "preupgrade" neglected to properly assess the space and/or warn me about it before proceeding.
In addition, the automatic cycling out of grub kernel entries came to bite me (part of many factors of the near-fiasco) because after the unfinished upgrade i had only one working kernel left to boot into, until I messed up that remaining one (too long a story), and then grub-install messed up my booting because of duplicate UUID. At any rate, at the end of what looked like a good preupgrade-reboot-upgrade-package-install process the post-install phase lingered a looong time, then I found myself booted into the old Fedora 11 kernel with absolutely NO modules (corresponding /lib/modules had been erased by the upgrade!) Somehow the system ran, but no USB, no wifi, no ethernet, no way to easily place the right kernel rpm onto the hard drive (had to unscrew the drive,etc., to copy over the correct kernel rpm). (Plus, file /boot/preupgrade/vmlinuz, left over from the arrested upgrade, was NOT the right target upgrade kernel version (2.6.32.9-70.fc12), so it didn't help either because it didn't have its modules either. The target /lib/modules (version 2.6.32.9-70.fc12) WERE there, but the kernel itself was NOT, due to upgrade running out of space on the /boot partition).
(Oh, and the preupgrade/upgrade had deleted my /var/cache/yum/preupgrade/ packages; hence my inability to quickly (re)install the 2.6.32.9-70.fc12 kernel rpm -- why!? it hadn't successfully finished the process!)
(Also, FWIW, i ended up rescuing the system through "rpm -i --force <kernel>", many an F12 rescue boot, chrooting, /boot/grub/grub.conf & fstab edits, tune2fs/uuidgen, running grub on command-line ("setup (hd0)"), etc., etc.)
So, any tips out there on phasing out the old-school /boot partition scheme, the safest and easiest way (without destroying a working system, of course)?
I am trying to install a box here where my /storage partition is about 2.5T.I had setup the partitioning with suse, while testing, and all worked well.Now when trying to install CentOs 5.5 it gives me an error, that my boot partition is on a gpt partition and this machine cannot boot that.Also I don't see the option to create XFS partitions from the installer.Can 5.5 support GPT @ install time?
I have a brand new thinkpad X301 with 4GB of RAM and thinking of getting fedora 11 on it. The plan is to have it triple boot with vista/seven and hopefully OSx86. I am aware of the 4 primary partitions limit on an MBR disk. I was thinking of having a swap file instead of swap partition and not creating a boot partition as well. If I install the boot loader(GRUB?) on the root partition will I be able to boot it without any problems by using vista's boot loader?
Or Maybe I should install GRUB on the MBR and add all the other operating systems on it? Does anyone have any objections for not creating a swap partition or a boot partition? When comes to desktop environment I've been using KDE in the past, is there any major advantage of using Gnome over it? KDE seems to look really nice on fedora where Gnome is maybe more stable?
I've just (finally!) gotten around to upgrading a couple of machines at a company I do some work for. One machine had a problem when I rebooted onto the new system. During the boot sequence, when it was checking and mounting the filesystems, it was unable to find the /boot partition. Now, this machine does run LVM on all but the /boot partition. The two SATA drives are mirrored, and they have the same partition layout:
Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
I got the system to boot by commenting out the /boot partition in /etc/fstab, but this is certainly only a temporary solution. The other system that I upgraded came up just fine, as have several of my own. Unfortunately, I am doing these two systems by remote control via ssh as I have only limited plysical access to them. (I did have to get to it to figure out why it didn't boot up..)
I have a Fedora 11 with 2.6.30.9-96.fc11.i686.PAE kernel.I accidently deleted my boot partition by
Code: mkfs.ext3 /dev/sda1 Is there a way to repair the boot partition without reinstalling Fedora? I still work with the booted system, but I think a can't reboot :-(
I've been upgrading a Fedora server over the years. Once it was Fedora Core 2 now it is Fedora 10. Now I want to continue the upgrade process and upgrade the server to Fedora 11. The problem is that the boot partition is 100MB but Fedora 11 wants a 200MB boot partition. Looking at Fedora 13 it seems a boot partition of 500MB is gonna be the norm. I would just resize the boot partition but there is a LVM directly after it taking up the rest of the drive.
How do I resize my boot partition in this scenario?
My current line of thought is to use G4L to backup both partitions, then restore the boot partition to a large drive, increase the size with parted then restore the LVM backup after it.
So far G4L has been reluctant to backup the boot partition of Fedora on a test rig to an NTFS drive. Not sure if I should be backing up the image to a ext3 drive.
i accidentally on purpose deleted my boot partition and rewrite something on it. Now i'd like to know how can i restore it. All i have now is the live cd. It's really bugging me that i can't have something nice for more than a week i'm seriously thinking to give my money back to old billy the kid or better to get an abacus and some sheets of paper and never again touch a computer.
I have installed FC12 on a system that previously had FC9, (My dads PC) So far everything is great (except adobe flash ), however when i installed it I erroneously assumed it would use the old /home folder, I think I miss interpreted what I read during install. the old data is still on the disk but I cannot mount it because it contains a boot partition. I tried to use GParted to modify the old partition but was unable to modify LVM???
How can I remove the old boot partition and rename the folder so I can mount it and access the files on it. There was nothing really important lost, it would just save me a lot of time if I could access the files.
I rebuilt a server and am now trying to recover my large data arrays. The server was ubuntu 10.04lts before. I decided to rebuild it with CentOS simply because I am more familiar with it. I had 2 raid-5 arrays on the old server:4 x 1tb -> md0 5 x 2tb -> md1 The newly built server does not know about these arrays yet. How can I reassemble the arrays without loosing my data? I know the data can still be accessed because booting the server with a live-cd mounts and shows the arrays just fine. Should I boot with a live cd and copy the mdadm config file?
One of our servers crashed due to hard drive problems. We were able restore data from backups; however the only info on the samba PDC portion of the server we have are the local and domain SIDs. Armed with only this info; is there a way to recreate the previous domain so the users and machine accounts could recognize it?
I installed fedora 10 on my laptop as a partition with vista. However i'm now not able to boot into my vista partition as everytime I try it comes with an error saying "bootmgr" is missing. Below is whats in my grub.conf file. However I am able to access my vista partition through fedora.
I was creating dual-boot WinXP on my machine with F10 allready installed.
On my 1st try, windows froze when inspecting hardware, so I deleted boot partition with fdisk and then it works.
I installed succesfully XP on last partition on my drive, but XP won't boot because of hal.dll error (forums says it can be repaired by changing boot.ini).
Now what I want is to create new boot partition to reinstall grub.
I'm trying to do that from gparted live cd:
From gparted live, i entered console and did "fdisk /dev/sda".
When i type 'p', here is my output:
Code:
when I try to type 'n' to create a new partition, it tells me "No free sectors available".
Before /boot was on /dev/sda1 (Start@1, End@13), and NTFS was on /dev/sda13.
I have Vista and F11 dual booted on my system. I wan't to resize Fedora(I think Vista has already been shrunk as far as It can) and install Debian as a third OS. Fedora takes up all the free space and I am only using a small amount of the partition. I am not sure of the best way to do this. Can I boot the Debian live cd and resize Fedora at the partion step? Or do I need to boot a live F11 cd, repartition and then boot the debian cd? Or is there a better way?
I have a weird problem with an sata partition. This drive is onle volume of an md raid set, and has one partition filling the whole drive. of type "fd" ( linux raid autodetect). When my machine boots, the drive containing this partition is present as /dev/sdc. However, the partition is not - there is no /dev/sdc1. If I look at the partition table in fdisk, all appears to be fine. If I do anything that causes the partition table to be rescanned (such as writing in fdisk, or running partprobe, ... ), the partition shows up fine at that point and all data is present and when I assemble the RAID using it, its in sync. This drive is attached to the same (motherboard) controller as my other drives which have their partitions recognized just fine.
I have fedora 12 installed on a laptop with an LVM partition, /dev/hda5 logiacal partion in the /dev/hda4 one, a boot partition on /dev/hda3 and a FAT on /dev/hda2 for win data. There was also a 10GB free partion left from older works on /dev/hda1. Now the /boot partition was set to only 0,2GB and this conflicts with the kernel updates. I freed the 10GB section, formatted it to ext 4 and copied all stuff from the /boot sector on it. now the old /boot is mounted in the grub.conf on a UUID and not the /dev/hda3 as it comes up on fdisk.
I would now like to swith the boot from the small /dev/hda1 partiotn to the larger /dev/hda3 one, but don't know how to manage it with grub (fedora, i understand it's grub-legacy).
I am Quad booting my lappy with Fedora 12, Opensuse Karmic and Vista. Previously Grub2 is not recognising Fedora partition. Now i have managed to add Fedora entry to Grub2. But i got another problem, after selecting Fedora from grub menu, i cant get login window. I can see fedora sign at the bottom right corner of Laptop LCD.
I have daul boot systems on Dell computers. Dell includes a Utility partition on /dev/sda1 which you are supposed to be able to boot by pressing F12 when booting. I've tried various ways to boot into it. Most recently I put
title Dell Utility rootnoverify (hd0,0) chainloader +1
boot partition was not being automounted after booting into Fedora 13, yet I was still installing updates, including kernel updates. What has ended up happening is I have old kernels (from removed/outdated packages) that still live in my boot partition, and the new kernels (from my updates) live on the root filesystem under the /boot directory. So when I reboot, grub only sees the old kernels.To demonstrate this, here are some lists.These are the contents of my actual boot partition (grub sees these):
Code: vmlinuz-2.6.34.7-56.fc13.i686 (packaged not installed) vmlinuz-2.6.34.7-61.fc13.i686 (packaged not installed)
I'm trying to set up my Fedora 15 installation to automatically mount (with all privileges needed for read/write access w/o a password prompt) an ext4 partition on the same HDD. Below is the output of sudo fdisk -l.
Code:
Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors Units = sectors of 1 * 512 = 512 bytes
[code]....
Partition table entries are not in disk order I'm trying to automount /dev/sda8, I believe. I'll check that when I've rebooted to by Ubuntu partition, 'cause that's where I know how to do it. I tried to use pysdm, since that's what I used to do the same thing in Ubuntu, but it wasn't found by the Fedora package manager.
I'm using fc14, and put the /boot directory on a standalone partition. Now, there's something changed in MBR, and the grub has been overwrote, now I wants to fix the grub by another bootable usb-disk with grub, to use 'setup (hd1)' to fix it. but the situation cause the /boot has nothing and the partition contain essential files does not under the directory 'boot'. then setup failed.
