I have been running Fedora 12 since its release without issue with a hardware RAID1 of two 1.5TB drives and a root volume of 500GB on a separate drive. Last night, after rebooting my machine, I was greeted with the following:Checking filesystemsfsck.ext4: Unable to resolve 'UUID=<snip>78' [FAILED]and the option of shell access as root. After logging in, I ran blkid with these results:
I'm a beginner + in debian (ie I know how to launch basic command under a shell), and I very new to configuration problem.I have a running perfectly file server for probably more than 2 years that I never touch. That's the debian problem, when it's unning, it's forever, no reboot at all.I recently bought 2 new sata drive 1TB5, that I add to my system by adding to my old system a SATA PCI board without any problem.But, one of these 3 month old drive is already dead.So I try to replace it and that's where problem started.....First I did a#mdadm --manage /dev/md1 --remove /dev/sdb1, of course without sucess because sdb is dead
#mdadm --detail /dev/md1 /dev/md1: Version : 00.90.03
I was experimenting in virtual machines this evening with software RAID.I found Slackware's method straightforward and intelligible. The README is excellent. I found software RAID setup in Scientific Linux (RH Enterprise clone) and Debian convoluted and confusing.My only question regarding software RAID in Slackware is how the system notifies you about the failure of one component. I pulled one of the virtual disks offline to deliberately fail the array but I wasn't notified when rebooting. I didn't look too deeply into log files to be honest. Can it be set to automatically notify the admin about a failure?
I have built a small test server. I am planing on using this machine a an email and web server to test out its hosting capacities. in the future I will build a larger and more well equipped version.
AMD Athlon x2 2.0ghz 2 160gb SATA drives (hardware raid 1, done through the Motherboard) 2 gb ram (dual channel)
Like I said small test server. I am trying to install 10.04 server edition. When I get to the point of partitioning it asks me to activate the raid so I do. I get through the guided partitioning and get ready to write the file system to the drives and the screen goes red and says that it has failed. On a side note, this works if i install it on the same drives without any raid configuration.
I am trying to boot my F13 server that has 3 partitions (sda2,sdb2,sdc2) configured as RAID1 (md0), vg00 is on md0 and / is on vg00/lvol00 and boot is on /dev/sda1, sda3,sdb3 and sdc3 contain other non-OS data and I get the following errors dracut scanning devices sda3,sdb3,sdc3 for LVM logical volumes vg00/lvol00 vg00/lvol01 . dracut: Volume group "vg00" not found dracut: Skipping volume group vg00 dracut: Autoassembling MD Raid No root device round and then everything stops If I go in with rdshell and type in -
[Code]...
Ok I managed to solve it. When I originally installed F13 I had 2 partitions in md0 and later on I added /dev/sdc2 to make it a 3 partition Raid 1 array. My thinking was seeing that I had the extra space it wouldn't hurt to use it as another mirror. One month later after I booted the server I have found out it did hurt. I removed the 3rd partition and now it's fine again. I wonder though if it would be possible though to use that 3rd partition.
I have just upgraded to Fedora 14 from an older version. I now have problems mounting my RAID1 array, which was operating correctly until now. This is a software RAID which was initially built under Fedora 10.The array is md0, and is made of 2 SATA drives (sdc and sdd) which have only one partition. The underlying filesystem is NTFS. The array is assembled correctly and active, as reported by /proc/mdstat and mdadm -D.When I try to mount the array, I get this:
Code: [root@Goofy ~]# mount /dev/md0 /mnt/raid mount: you must specify the filesystem type
I have two 80 GB IDE hard disk. I have create raid1 partition in both drive using [URL] ink. raid is working fine. But i have copy some data on one hard disk (md0) but this data is not autometically copy in second hard disk(md1). I want when data is write on one hard disk, this data autometically write in second hard disk.
Just finished installing F14 with RAID1 setup for 2 hdd (SATA''s). Entire drives are mirrored, including SWAP. As I had done in the past, I was planning on installing grub on MBR of 2nd hdd. In prep for this I did the following to locate the grub setup files:
grub> find /grub/stage1 find /grub/stage1 (hd0,1)
[code]....
I was surprised, expected to get (hd0,0) & (hd1,0), not (hd0,1) & (hd1,1)
running "fdisk -l" I get:
Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors Units = sectors of 1 * 512 = 512 bytes
[code]....
MBR is the first 512 bytes of the drive. Each partition has a boot sector. In my case grub stage 1 is on 2nd partition of sda & 2nd partition of sdb. What i dont understand is how grub stage 1 can be on sda2 & sdb2, since I am assuming that sda1 & sdb1 would be the first partitions of the drives & therefore contain the MBR's. Maybe this might be because sda1 & sdb1 are SWAP partitions?
2xHDD 300GB RAID1 - OS part 2xHDD 1TB RAID1 - data part. Both arrays were created inside the bios-like setup.
During the installation of fedora I "checkboxed" only the 300GB OS raid and used it for the installation. Everything is ok with it. After installation finished and I rebooted, I tried to initialize my second RAID1, that's 1TB - I was able, it was OK, I created 1 max-size filesystem there and put some data in it. After reboot this filesystem didn't want to mount for some reason - so I commented it in fstab and to my surprise, when I reached linux - the partition for it doesn't exist!!! Here is some data:
My guess would be that I am not fully and properly initializing the second array, (it's marked as auto read only in cat /proc/mdstat) but I'm not sure how to proceed.
I have an existing Fedora 15 system installed from scratch.I've ordered a harddrive identical to my SDA and want to add it to my existing system as a RAID1 setup.I've googled around and cannot find recent clear instructions how to accomplish this. I don't want to reinstall everything from scratch. It should be possible to create the RAID1 using the existing data disk and then mirror everything up?
I have trawled through an extensive number of post on quite a few forums without even a step forward with this.
I have a fedora 13_x64 system with software raid1 for /boot and / (md0 and md1 respectively), swap is not raided.
I was doing an yum update through the software updater in gnome and the system froze.
I had to press reset to get any response from the machine.
Since then I have been getting the kernel panic above just after grub starts fedora.
I tried the previous kernel from the previous update and it has the same error.
At the worst I am prepared to load OS again but there is still some info and configs that I would like to access from the raid partitions before I go ahead.
Is there any way to access these partitions through a live CD or rescue environment?
Is there a method to bring this install back to life? or am I looking at a reinstall?
I have trawled through an extensive number of post on quite a few forums without even a step forward with this.
I have a fedora 13_x64 system with software raid1 for /boot and / (md0 and md1 respectively) , swap is not raided.
I was doing an yum update through the software updater in gnome and the system froze.
I had to press reset to get any response from the machine.
Since then I have been getting the kernel panic above just after grub starts fedora.
I tried the previous kernel from the previous update and it has the same error.
At the worst I am prepared to load OS again but there is still some info and configs that I would like to access from the raid partitions before I go ahead. Is there any way to access these partitions through a live CD or rescue environment?
Is there a method to bring this install back to life? or am I looking at a reinstall?
/dev/md0 (made from sda1 and sdb1) RAID1 /boot partition /dev/md1 (made from sda2, sdb2, and sdc2) RAID5 / partition
Earlier on I had some trouble with my sda drive, it dropped itself from both arrays, screwing up the mirroring of my two raid partitions participating in the /boot partition. I eventually got everything sorted out and back in sync. (I also have grub installed to MBR on both sda and sdb). Things are working fine regarding that, but since then I've had this issue:
During boot up, I'll get an error message that it could not mount my /boot partition (when fstab is set to either /dev/md0 or the UUID). It claims c9ab814c-47ea-492d-a3be-1eaa88d53477 does not exist!
My fstab:
Code:
[mark@mark-box ~]$ cat /etc/fstab # # /etc/fstab # Created by anaconda on Wed Jan 20 16:34:41 2010
[code]....
As far as I know, it isn't neccessary for /boot to be mounted always, correct? Although, as I understand, I need to have it mounted whenever making kernel changes correct?
I am using Fedora 8 in my PC and i'm trying to create a shared memory (below is the sample program) i'm getting error while creating shared memory. Can anyone pl tell what is the possible cause for this.
Im using FEDORA 12 (constantine )....Everything was working fine.....until yesterday when i tried login to my GUI(gdm) it says authentication failure. so i tried logging in from CLI and it didnt worked either...(it didnt say "password incorrect",rather it it simply reset the screen to "login name:",thats weird...right?)
Then i tried to login as root from from CLI (by default Fedora does not support root login to GUI?) and i was able to login.....
Then it said "System powering down in one minute"............. i didnt understand why that happened.....! but it didnt power down in one minute...
I tried changing my user passwd...still no change.....
When I attempted to install 64-bit Fedora from my DVD, it failed while installing packages with the unhandled exception:
" Traceback: File /usr/lib/anaconda/users.py, line 163, in setRootPassword, self.admin.setpassUser(rootuser,cryptPassword(pass word,algo=algo),True) File /usr/lib/anaconda/instdata.py,line 171, in write,algo=self.getPassAlgo()
[code]...
I know Python quite well but I have no idea why None is being passed as the first argument to self.admin.setpassUser when a non-None value is needed. The other curious thin is that the trace does not show the call to setpassUser() from the entry after it but rather to 'getPassAlgo(). Needless to say this but has kept me from installing Fedora 11 on my 64-bit machine.
When tried to install Chromium from add./remove programs, the following error crops up
Dependency resolution failed: A package could not be found that allows the action to complete:
libicui18n.so.40()(64bit) is needed by package chromium-.0.252.0-0.1.20091119svn32498.fc11.x86_64 (chromium) libicudata.so.40()(64bit) is needed by package chromium-.0.252.0-0.1.20091119svn32498.fc11.x86_64
I just completed the latest updates to Fedora 14 - I have mono and wine on the system as well - so they were also updated. Now the only screen I can get is the failsafe (bash).
How do I recover my KDE desktop? (I noticed there were some updates for the KDE as well). I suspect something has failed during the update (selinux was also updated).
I am facing bootup issue in Fedora 14.I troubleshoot the bootup issue i m facing probably because I have done change the name of volumes from disk utiltiy. I read somewhere that it should be done from another place (administration option, the last menu of fedora and there is some volume/disk management..like thing that give rod like blue/red picture of disk=>System-config-lvm) rather then disk utility under system tools. I think that my LVM path is not setup..due to rename of volume..it is mismatched somewhere...that includes path...finally using rescue disk i enter in shell prompt and mounted my system using chroot /mnt/sysimage then found that my /home is empty, so done some readings and found that using mount /dev/vg_brs/home /home i am able to get my home fixed that now appeared my user and whole data.
but that is till i m in shell prompt. Don't know where and how to fix/add this line so that boot loader of fedora will take this instead of something other that it is taking and not founding resulting in failure to boot with message (in between lines)
I cant access my box after upgrading from fedora 13 to 15 i wasn't near the computer during the process and i don't know if it asked for user and password ,but its upgrade and it need to have my old setting so why i'm not able to log in at all , even not as root.
P**sed right off now, tested this upgrade on two test systems before hand to make sure this would work.Upgrade my server from FC9 to FC10, it had two Encrypted XFS volumes on totalling 1.5TB of files which I don't have space to backup anywhere else.Have now upgraded and the Encrypted volumes are showing as not existing "volume name does not exist"
i've enabled quotas for a user on my fedora 10 distro but whenever i reboot the machine the boot.log contains the following message :"Enabling local filesystem after every startup i have to login as root and issue the quotaon -auv command to reenable quotas.what causes this failure on startup ? is there a workaround to solve this problem ?there is plenty of free space on the root partition that quotas are enabled.
It took me a while to get VNC going. It was easier with FC8-10. Once I got finished and was actually able to log in and see my remote desktop I tried to add some software... virtualbox.When I double click on the RPM I get popup that states."The action could not be completed. Failed to install file. You do not have the necessary privileges to perform this action" When I close that dialogue another one pops up that states" "The action could not be completed." When I click on more details the dialogue states. "Policykit authorization failure" How can I make this work?
After running a system update, on next boot I was unable to connect to the internet. I am running Fedora 12 KDE 4.4 x86_64 with a dsl connection. Network manager was keeping my ethernet card disabled. If I disabled NM control of the card I could manually enable it and connect to the internet, but on reboot it would be disabled again. I saw that the update did apply to NetworkManager so I did a downgrade. yum downgrade NetworkManager That seems to have fixed the problem.
Here's an interesting thing I noticed. When I did the downgrade, yum wanted to "Install" for dep NetworkManager-glib for the lower version, however didn't do anything to the same file on the latest version. Almost as if it wasn't installed. Now, with the downgraded version as current, yum wants to update both NetworkManager and NetworkManager-glib to the latest version. I couldn't swear to it, but I think the original update to NetworkManager did not include the *-glib dep, but now it does. Maybe that was the problem all along?
I have just installed Fedora 11 to my laptop and it appears I am in trouble. I have received two kernel failure messages, which I post below. What are the consequences of these issues and how can I solve them ?
