similar to: Re : Alpha Server 1000A 5/400 Centos 4.3 instalerl can not find the hard drives

Displaying 20 results from an estimated 10000 matches similar to: "Re : Alpha Server 1000A 5/400 Centos 4.3 instalerl can not find the hard drives"

2006 Nov 11
0
Alpha Server 1000A 5/400 Centos 4.3 instal can not find the hard drives.
During the install of alpha Centos 4.3 I'm told by the Centos installer that the hard drives can not be found. Hard Drives have been properly configured in the ARC setup. ARC initialization of the drives works fine. I can create windows nt partitions Went thru the list of drivers provided by Centos but the installer has already loaded the the QLogic and Mylex DAC960 controller drivers. I
2007 Mar 28
3
changing swap size
Is it possible to change the swap size with out re-installing the system? Looking at the dd command but don't really know what to expect. Many thanks for your help -- This message has been scanned for viruses and dangerous content by MailScanner at caspercollege.edu and is believed to be clean.
2007 Feb 01
1
New time zone
Sorry if this has been covered.. What are the plans for making our Centos 4.4 servers compliant with the new time zone changes. Thanks -- This message has been scanned for viruses and dangerous content by MailScanner at caspercollege.edu and is believed to be clean.
2007 Jul 19
2
Compact Flash hard drives
Has anyone worked with either the Hitachi or Seagate Compact flash drives in an IDE to CF interface and set the up with EXT3 formatted partitions for use with LVM? I ASSuME that LVM is not for FAT32 formatted drives.
2004 May 05
0
recover data from failed hard drives on Fedora Core 1
Hi, I got a problem to recover data from Fedora core 1 hosts when hard drives fail. I know that the disks fail because there are error messages like the following logged in /var/log/messages. ..... arc144: Apr 24 12:52:53 arc144 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc144: Apr 24 12:52:53 arc144 kernel: hda: dma_intr: error=0x40 { UncorrectableError },
2006 Feb 20
0
problems accessing unused physical hard drives from Dom0
Hi, I run an Ubuntu Breezy Dom0 under Xen 3.0.1 (official Xen 2.6.12.6 kernels from xen-3.0.1-install.tgz). In the machine i''ve got 2 IDE ATA discs, hda and hdc. The Dom0 runs on hda1 (a big / partition), hda2 is swap. hdc is totally unused (an empty disc, exactly the same model that hda). 8 to 10 domU run from .img files located in /vserver without problems (unmodified kernel
2006 Aug 08
1
multiple hard drives
I am trying to understand how to use xen. Any help in answering the following questions would be appreciated. 1. Would xen allow one large hard drive partitioned with 6 or 8 partitions to be seen as servers? Each partition a server for example. 2. If I have multiple hard drives in one server, will xen allow me to boot each one and run each hard drive as a server. any help is
2008 Feb 12
3
Question on failing hard drives
In my Cent OS machine, I have 3 hard drives, an 80, and two 200gig hard drives. One of the drives is obviously starting to fail, but I'm not sure which one. Is there a command line command in Linux that will check the drive integrity on all the hard drives and tell me which one is going bad? Thanks Jim
2016 May 24
0
Hard drives being renamed
On 5/24/2016 2:08 PM, Pat Haley wrote: > > We are running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64 on a Quanta > Cirrascale, up to date with patches. We have had a couple of instances > in which the hard drives have become renamed after reboot (e.g. drive > sda is renamed to sdc after reboot). One time this occurred when we > rebooted following the installation of a 10GB NIC
2016 May 25
0
Hard drives being renamed
>> I've run into this with ZFS on Linux. The 'blkid' is useful to identify the >> target device and then add that to your fstab. I don't use device names >> at all anymore, too ambiguous (depending on the circumstance) in my >> opinion. Right. And there are other ways to identify disks unequivocally. Under CentOS, for example, I find the following
2016 May 25
0
Hard drives being renamed
>> I've run into this with ZFS on Linux. The 'blkid' is useful to identify the >> target device and then add that to your fstab. I don't use device names >> at all anymore, too ambiguous (depending on the circumstance) in my >> opinion. Right. And there are other ways to identify disks unequivocally. Under CentOS, for example, I find the following
2019 Feb 28
0
What files to edit when changing the sdX of hard drives?
Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > I want to lock in the SDA/SDB/SDC for my drives In short : use UUIDs or labels instead of hardcoding /dev/sdX. https://wiki.archlinux.org/index.php/persistent_block_device_naming Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog :
2019 Feb 28
0
What files to edit when changing the sdX of hard drives?
On Thu, Feb 28, 2019 at 11:52 AM mark <m.roth at 5-cent.us> wrote: > Nicolas Kovacs wrote: > > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : > > > >> I want to lock in the SDA/SDB/SDC for my drives > > > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > > >
2019 Feb 28
0
What files to edit when changing the sdX of hard drives?
> No, I dislike UUIDs. I dislike, strongly, lots of extra typing that > doesn't really get me anything. MAYBE, if you're in a Google or Amazon > datacenter, with 500,000 physical servers (I phone interviewed with them > 10 years ago)... but short of that? Nope. You can (perhaps should...) use the World Wide Name, which is a manufacturer ID unique to each disk. Contrary to the
2019 Mar 01
0
What files to edit when changing the sdX of hard drives?
On 2/28/19 10:04 PM, Jobst Schmalenbach wrote: > On Thu, Feb 28, 2019 at 05:19:49PM +0100, Nicolas Kovacs (info at microlinux.fr) wrote: >> Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: >>> I want to lock in the SDA/SDB/SDC for my drives >> >> In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > I **KNOW** how to use UUID's ... this is
2015 Aug 08
0
backing up email / saving maildir on external hard drives
Am 08. August 2015 06:56:55 MESZ, schrieb Kevin Laurie <superinterstellar at gmail.com>: >Hello, >Yesterday I tried to back up a 40GB maildir . >I tried to move the maildir from home to external HDD but failed. >Decided >then to compress it(which took several hours). Now changing the disk >format >from FAT to exFAT to allow the transfer for the large compressed file.
2015 Aug 09
0
backing up email / saving maildir on external hard drives
Am Samstag, den 08.08.2015, 21:45 +0530 schrieb Kevin Laurie: > Dear Christian, > Thanks for your feedback. > The HDD will not accept larger than 4GB (as its in FAT format). Its a > new > external HDD. Thinking of the best format(that would work with Mac , > Win > and Linux) .seems like a challenge. > What's your view on NTFS? And why not exFAT? > > Thanks >
2015 Aug 09
1
backing up email / saving maildir on external hard drives
Hi Felix, I would prefer having one HDD that works with all three OSes. That would be very convenient. Guess exFAT is my best bet. Its supported on Linux,Win and OS X. What do you reckon? Best Regards Kevin On Sun, Aug 9, 2015 at 2:46 PM, Felix Zielcke <fzielcke at z-51.de> wrote: > Am Samstag, den 08.08.2015, 21:45 +0530 schrieb Kevin Laurie: >> Dear Christian, >> Thanks
2015 Aug 11
2
backing up email / saving maildir on external hard drives
On 11.08.2015 15:45, G?tz Reinicke - IT Koordinator wrote: > talking of rsync and compression is may be also a bit misleading. > > On the destination there will be no compressed files if you transfer > with rsync! ...unless your dovecot is working with compressed maildir files. ;-) Kind Regards, Christian Schmidt -- No signature available. -------------- next part --------------
2015 Aug 11
0
backing up email / saving maildir on external hard drives
> Am 11.08.2015 um 17:56 schrieb Christian Schmidt <Christian.Schmidt at chemie.uni-hamburg.de>: > > On 11.08.2015 15:45, G?tz Reinicke - IT Koordinator wrote: >> talking of rsync and compression is may be also a bit misleading. >> >> On the destination there will be no compressed files if you transfer >> with rsync! > > ...unless your dovecot is