I am using Fedora 14 64 bit with two 1T drives. There is a Raid 1 for the important information and I use a Raid 0 for cached files that can be generated on the fly. Yesterday my Raid 0 went into read only mode.
Here are a couple of tests:
What caused the Raid 0 drive from /dev/md1 to get removed? Is there a way to get it back to active sync?
I have tried:
But it can not open /dev/sda2: Device or resource busy.
I have an interesting issue Ubuntu Server 8.04, The server has been running for quite a while (not designed or put together by me) but recently it has started segfualting and now will not boot apart from in read-only mode. I see the following errors in dmesg.
I have a weird problem here with a 9.04 server. We have a raid 5 disk formatted in EXT4 which remounted automatically when we accessed to the lost+found folder which is in the root of that disk.
I tried to delete it but I can't. It's a bit annoying because I have to prevent all users and backups to access to that folder.
Could any RAID gurus kindly assist me on the following RAID-5 issue?I have an mdadm-created RAID5 array consisting of 4 discs. One of the discs was dropping out, so I decided to replace it. Somehow, this went terribly wrong and I succeeded in marking two of the drives as faulty, and the re-adding them as spare.
Now the array is (logically) no longer able to start:
mdadm: Not enough devices to start the array.Degraded and can't create RAID ,auto stop RAID [md1]
Code: mdadm --create --assume-clean --level=5 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 As I don't want to ruin the maybe small chance I have left to rescue my data, I would like to hear the input of this wise community.
my setup P4 3.4GHZ 2GB Ram Gigabit Ethernet Drive Configuration 1 x 750GB Sata Connected To My Raid Controller in ide mode 1 x 120GB IDE HDD 1 x 250GB IDE HDD
my problem, I Am trying to install f12 and the only drive that it sees is the 750GB Sata,it is not seeing the other 2 ide drives The raid controller is an ite 8212 in ide mode The Bios Sees the drives just F12 doesnt
I'm looking to set up a server with attached mass storage device and tape autoloader to run linux. It's set up under Windows at the moment. Goal is to have users, connecting from individual workstations and laptops, backup their data to the linux server. On their personal machine, some users run linux, some MacOS, some Windows. I plan to set up the 5 500 GB drives as RAID5. I understand that if setting up as software raid the format is "physical volume for RAID". Under this setup, will Windows users be able to read/write and function as expected? I can't assume only linux user access.
I have a custom server built with Intel motherboard and RADI 10. The RAID controller is on the motherboard. I'm about to install fedora 11 x86 64 bit on it. Should I be experiencing any issues with anything that any of you have come across? I did a checksum check on the iso files and those were good. Also, someone sent me this link..
[URL]
However, I have a hardware RAID, not software RAID.
How can we know which Raid level is useful for the server E.g Mail, Web, Database server. Also things we can keep in mind before configuring RAID / LVM on live servers.
I hope this is the right section, it looks like though. I have a small nas ( via artigo a2000 ) with 2 sata hd 1tb each with raid 1 and lvm on top configured and working great.
sda1 and sdb1 ==> md0 raid1 for /boot sda2 and sdb2 ==> md1 raid1 for swap sda3 and sdb3 ==> md2 raid1 as physical volume then volume group and lvs on top ( / is a logial volume of these )
I wish to upgrade the current fedora 12 32bit installation I have on it doing a fresh install. But because I have a lot of data on md2 ( 600GB worth ) which I don't want to copy across somewhere else first, I need to know how ( i am pretty sure i can ) to mount md2 during the installation. This way I can use the data I already have on it.
Im having a hard time trying to change my raid configuration. Here is my situation:
A have two HDs that I configured in instalation time to work as raid squid proxy-cache. they are both 40GB. 40+40=80GB. So, I want to change it to two of 160GB. 160+160=320GB.
I have: sdc1=40GB sdd1=40GB
im adding / want: sda1=160GB sdb1=160GB
I want to remove the two 40GB and use only the two 160GB for my proxy. The thing is that when I remove the two 40GB, the system crashes at startup telling me that the raid cant be done then file system check fales too. Im wondering if there is a file a have to edit to change to point it to /dev/sda1 intead of /dev/sdc1 for example, so my system would start up looking for sda1(160GB) and sdb1(160GB) intead of sdc1(40GB) and sdd1(40GB).
I would like to mount a disc that was previously used in the Intel Software Matrix RAID array (fake-raid). If I try to mount it I get:
mount: /dev/sdd1 already mounted or tempb busy
I think my dmraid is refusing to mount it beause of some RAID "flag". I would like to get rid of it, but unfortunately I cant do that on my system (theres no such RAID):
[root@ox mnt]# dmraid -r /dev/sdd ERROR: isw: Could not find disk /dev/sdd in the metadata no raid disks and with names: "/dev/sdd"
There are several posts recommending to uninstall dmraid completely from the system. Isnt there smarter solution in removing such a flag?
I have had no problem installing Fedora OS on any of my Dell servers prior to this post. Anyway, I wouldn't call this a problem but recently, we bought another DELL server with Quad Core, 4GB, etc... AND this model has 2 swappable SAS Harddrives.
I wouldn't call myself an expert but then again I am not a newbie too. However, I have never setup any RAID before and now I am forced to setup RAID1 on this server. So, in a way, I am a newbie in setting up RAID
Would someone please point me in the right direction as I have no idea what I am supposed to do to setup the RAID. FYI, I will be installing Fedora 10 64bit on this server. I would appreciate if you can start from the very beginning, ie. partitioning, formatting the harddrives during OS installation, etc..
I was recently requested to try and convert a running system to RAID level 1. I did not succeed in this task. However, I am still interested in accomplishing this task in a test environment.What I did was create a RAID device with a device missing e.g.
Once the RAID was up and running I created the /etc/mdadm.conf file so that it would activate the RAID device on boot. Once the device was created I copied all the data from the running root filesystem to the /dev/md0 device. The only directory that I didn't copy was the /proc directory. When I rebooted the machine I had a kernel panic and the system couldn't find /dev/root. I would greatly appreciate it if someone could provide some information/tips regarding the problem.
I'm looking to set up a bit of a home server, and am wondering about storage. What I'd like is something like RAID 6, which has good redundancy built-in, but with this being a home server, I'd prefer to start a little smaller and leave room to build it up in future. I'd been looking at commercial products like the 'drobo', which seems fairly ideal, but I'd really like to see if I can do it myself. I understand that throwing the RAID into an LVM will allow for some expansion, but the last time I checked, most RAID setups called for the same sized disks, or at least limited the array by the size of the smallest disk present.
What I'd like is the ability to build a basic framework with a few cheap disks, and then as things start filling up, to be able to add larger ones (perhaps eventually pulling out smaller ones as though they'd failed and replacing them with big ones)
I have a computer running Fedora 11. I wanted to use samba in my office. So I configured the /etc/samba/smb.conf ,but it did not work well : Windows can find samba,but when I tap in username and password,samba request them again , and the same thing continues in a loop. So I copied another computer's smb.conf (which is also a Fedora 11,samba runs well in this one).I copied this file to /etc/samba/ ,then samba can't satart up . I read from /var/log/samba/log.smbd.log : Unable to open configuration file "/etc/samba/smb.conf": Permission denied Even if I use: chmod 777 /etc/samba/smb.conf
why I can't login samba from Windows:
[global] workgroup = MYGROUP server string = Samba Server Version %v ; netbios name = MYSERVER ; interfaces = lo eth0 192.168.1.99/24
I had a RAID1 'device' build on two physical partitions on two drives. One of the disk controllers died and software RAID did the job - now I am working on the degraded array.
Now I want to put the old disk (sdb) back, and I am not sure what will happen. Both disks have 'raid auto' partitions. And sdb file structure from before of the failure. The raid code will find inconsistency between both partitions. What will it decide? Will it start coping from the currently running system (sda) all the data to the old one (sdb) at the boot time, as I wish?
I don't want to it to write from the old one to the new one, as some months passed and lots of changes happened to the data.
I don't think it has anything to do with the config file. More to do with SElinux. I need to know how to configure SElinux so I can see my samba share when SELinux is on. When I setenforce 0 I can seen all the files and folders set it to setenforce 1 cannot see anything.
Here is the output when I ran [root@fileserver /]# getsebool -a | grep smb allow_smbd_anon_write --> on smbd_disable_trans --> on
These two options were off I tried turning them on.
This is another one of the commands I tried running. I did change a few options but I am not sure which I do need to change. I am running a stand alone server so I don't need the DC option.
[root@fileserver /]# getsebool -a | grep samba samba_domain_controller --> off samba_enable_home_dirs --> off samba_export_all_ro --> on samba_export_all_rw --> off samba_share_nfs --> off use_samba_home_dirs --> on
net ads join -U admin_name admin passwordgives the following error: Failed to join domain: failed to lookup DC info for domain 'domain_name' over rpc: Logon failureIn the log, is the error messagewinbindd/winbindd_ads.c:ads_cached_connection(127) ads_connect for domain SPCRANE failed: Cannot read passwordkinit admin@domain_name works correctly, so kerberos is working. The ticket is generated, and I can see it with klist. the smb.conf file has the matching realm. It is configured identically like a redhat 5 box that does work
So I finally managed to get my Samba file server working () but now I have a question. On the server I have 4 folders, each being used for a certain topic. How would I set the folders as read only but not the contents, so that way remote users can read/write to the folder but can't delete or rename the folder itself? Also, if I restart the Linux box it will cease to show on the Windows Network unless I delete the Samba share and remake.
I have a multi user system for my roommates and myself that has separate folders for each of us. I've got user authentication working with samba, but unless I set every file and folder readable/writeable by all users, I can't browse it or edit the files.This isn't ideal as the shares are open to other users access, so I'm hoping there's a way to keep folders at 750 and files at 660 while allowing samba users to browse, delete and edit.Also, the samba share is actually a mounted NFS share from another server. Both the NFS server and the Samba server have the same users/uid's. When a file is created from a Windows host via the Samba client, the NFS server's permissions do show that the correct user owns the files, but since the files aren't mode 666 but 640 I can't edit or delete the file.
I am trying to setup my webserver and I am trying to make a website to run under suexec but somehow I cannot start my apache it directly fails and SELinux is giving me errors and don't really know what to do with it, it is giving me some command to type but not sure if this will make my server less secure. The SELinux error is as follow:
Code: Summary: SELinux prevented httpd reading and writing access to http files.
Detailed Description: SELinux prevented httpd reading and writing access to http files. Ordinarily httpd is allowed full access to all files labeled with http file context. This machine has a tightened security policy with the httpd_unified turned off, this requires explicit labeling of all files. If a file is a cgi script it needs to be labeled with httpd_TYPE_script_exec_t in order to be executed. If it is read-only content, it needs to be labeled httpd_TYPE_content_t, it is writable content. it needs to be labeled httpd_TYPE_script_rw_t or httpd_TYPE_script_ra_t. You can use the chcon command to change these contexts. Please refer to the man page "man httpd_selinux" or FAQ [URL] "TYPE" refers to one of "sys", "user" or "staff" or potentially other script types.
Allowing Access: Changing the "httpd_unified" boolean to true will allow this access: "setsebool -P httpd_unified=1"
Fix Command: setsebool -P httpd_unified=1
I will write down how I did setup my server so maybe you can see a mistake I did. First I changed my Apache httpd.conf I added the following to it: Code: NameVirtualHost 192.168.1.2:80 <VirtualHost 192.168.1.2:80> ServerName localhost DocumentRoot /var/www/html DirectoryIndex index.html index.html index.shtml index.php </VirtualHost>
Then I created the username "ulyaoth" with the group "ulyaoth" as I specified with my suexec, then I created all the directories as specified in my httpd.conf and "chown ulyaoth:ulyaoth (dirname)" them to the right group and username.
I have Ubuntu9.10 installed in my desktop and the version of thunderbird is 2.0.0.23 and I am facing a problem that if I open any attached document from my mail, it open in Read-Only mode. To make changes I have to save the file or click on edit button but if I click on edit button then file get renamed as Untitled document.
I've rebooted my system like 30 minutes ago...and all the sudden I get the error related the that program in ubuntu 8.04 that checks the disk after reboot for bugs an stuff like that. The error is caused by "read only system" mode. It can't write anything onto the HDD. I can't even change /etc/fstab file with nano or anything else. Btw is server edition. I mean when I want to save the file (fstab) same damn thing read-only system how can I change that?
I use to be able to mount a usb and stick and copy over files to it. Now when I plug it in it mounts as read only and I cannot change it. I did not change anything on the system. I have su access and really nothing is new on this laptop. Any thoughts one what i can look at? I need to write data to usb all the time. I rebooted too. same issues.
I've tried to install Fedora 11, both 32 and 64 on my main machine.It could not install as it stops on the first install window. I've already filed a bug but really haven't seen any feed back yet.The bug has something to do with Anaconda and the Raid array but I really can't tell.
I have an Intel Board (see signature). I am running intel raid software under W7 currently.It works fine. But, I'm wondering, when I attempt to install F!!, is my current raid set-up causing problems? Do I need to get rid of the intel raid software and use a Fedor/Linux raid program to manage the raid array??
I have a software RAID 1 (mirroring) on my 2 hard drives configured through OpenSuse 11.3 installer. When I boot from the OpenSuse 11.3 install DVD in rescue mode, the RAID isn't recognized, ie attempting to mount /dev/md0 results in 'bad superblock' messages. I can still mount individual disks in the array though (/dev/sda1, /dev/sdb1, I did it read-only so not to corrupt the array). I also tried booting from the Centos 5.5 install DVD in rescue mode on the same computer and it has no problems finding the RAID 1. I was able to mount /dev/md0. Is the OpenSuse 11.3 install DVD in the rescue mode not supposed to find the RAID 1 or am I doing something wrong here?
I had a corrupted superblock in my RAID boot drive (/dev/md0), which I fixed with fsck in Recovery Mode.However, after rebooting, the same boot-up problem (hanging for hours) persists.When I re-enter Recovery Mode to examine the boot drive, I found its superblock was corrupted again (which I fixed again using fsck).Is there a proper reboot procedure which is gentle on the boot drive, such that it doesn't corrupt it? Or, is something else amiss