similar to: SSD as system drive - partitioning question

I just ordered a new machine that's destined to become a Centos 6 application server for a publishing company, and decided to get one with a 40GB SSD as well as a standard hard drive. I'm thinking that I can put most of the operating system on that drive and have the home directories and whatnot on the regular hard drive. Are there any pitfalls lying in wait for an unwary person like me

What would the performance impact be of splitting up a 64 GB SSD into four partitions of 16 GB each versus having the entire SSD dedicated to each pool? Scenario A: 2 TB Mirror w/ 16 GB read cache partition 2 TB Mirror w/ 16 GB read cache partition 2 TB Mirror w/ 16 GB read cache partition 2 TB Mirror w/ 16 GB read cache partition versus Scenario B: 2 TB Mirror w/ 64 GB read cache SSD 2 TB

Hi, I''ve ordered a new server with: - 4x600GB Toshiba 10K SAS2 Disks - 2x100GB OCZ DENEVA 2R SYNC eMLC SATA (no expander so I hope no SAS/ SATA problems). Specs: http://www.oczenterprise.com/ssd-products/deneva-2-r-sata-6g-2.5-emlc.html I want to use the 2 OCZ SSDs as mirrored intent log devices, but as the intent log needs quite a small amount of the disks (10GB?), I was wondering

I want to set up a multiple "mode" computer with four separate Centos installations on it. The objective here is to have a "spare computer" that I can boot up into any of four "modes" depending on what I'm swapping it in for a the moment. For example, I want to be able to boot it up as a webserver, or as a fileserver, or as a LTSP-enabled application server.

I can't seem to figure out how to partition for install. I've tried both CentOS 8 and 7.7 netinstalls. I've got 3 disks: sda (big hardware RAID array), sdb (SSD), and sdc (internal SD card for booting). I want to put /boot on sdc, /usr on sdb, and / on sda. I don't care what format is used on sdb and sdc, whatever will let it boot. I want LVM on sda so that I can use

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So

I plan to upgrade an existing C7 computer which currently has one 256 GB SSD to use mdadmin software RAID1 after adding two 4 TB M2. SSDs, the rest of the system remaining the same. The system also has one additional internal and one external harddisk but these should not be touched. The system will continue to run C7. If I remember correctly, the existing SSD does not use a M2. slot so they

I'm encountering an issue booting Linux using SYSLINUX 3.62 on a FAT16 partition. There are a variety of possible causes, but I figured I'd start here. My hardware is an embedded system using an off-the-shelf COM Express module with a Phoenix BIOS. Mass storage is provided by an Intel Z-U130 Solid State Drive (aka "Intel Value SSD"). The SSD is much like a standard USB Flash

The other admin I work with seems to have found a bug in the installer. The setup is: two internal SSD drives. Once the GUI gets to "select drive to install on", he goes to <ctl><alt><f2>, creates a RAID 1, and partitions it, regular MBR (they're small). 1G for /boot as the first partition, 2G for swap as the second partition, and the rest for / as partition 3.

Hello, I have noticed I have the following in my dmesg: [319769.043163] nbd: registered device at major 43 [319769.104176] nbd11: unknown partition table [319769.130273] device fsid c2598ff2-1e3e-4edf-ab19-1f7ab41b0160 devid 1 transid 125743 /dev/nbd11 [319769.130522] btrfs: force lzo compression [319769.130528] btrfs: disk space caching is enabled [319802.926547] Btrfs detected SSD devices,

Hi folks, For people who might be interested, here is how btrfs performs with two partitions on a single SSD drive in a RAID-1 mirror. This is on a Dell E4200 with Core 2 Duo U9300 (1.2GHz), 2GB RAM and a Samsung SSD (128GB Thin uSATA SSD). Version 1.03c ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block--

what file system are you using?? ssd drives have different characteristics that need to be accomadated (including a relatively slow write process which is obvious as soon as the buffer is full), and never, never put a swap partition on it, the high activity will wear it out rather quickly.? might also check cables, often a problem particularly if they are older sata cables being run at a possibly

> On 01/11/2023 01:33 PM, H wrote: >> On 01/11/2023 02:09 AM, Simon Matter wrote: >>> What I usually do is this: "cut" the large disk into several pieces of >>> equal size and create individual RAID1 arrays. Then add them as LVM PVs >>> to >>> one large VG. The advantage is that with one error on one disk, you >>> wont >>>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''ve been unable to find anything definitive about what happens if I use RAID0 to join an SSD and HDD together with respect to performance (latency, throughput). The future is obvious (hot data tracking, using most appropriate device for the data, data migration). In my specific case I have a 250GB SSD and a 500GB HDD, and about 250GB of

Greetings, I have a system x3100 m4 system with 64GB SSD for OS and 2x2tb for data as MD device (software RAID). It had Fedora 17 with EFI/ I tried to install centos 6. deleting the existing partitions on the SSD /dev/sdc. sda and sdb are the 2x2tb md device mounted on /home. no joy. googling Questions: 1. Where do I locate the boot loader? /dev/sdc? is MBR (the default with Centos) enough

On 08/09/2017 10:46 AM, Chris Murphy wrote: > If it's a bad sector problem, you'd write to sector 17066160 and see if the > drive complies or spits back a write error. It looks like a bad sector in > that the same LBA is reported each time but I've only ever seen this with > both a read error and a UNC error. So I'm not sure it's a bad sector. > > What is

On 01/11/2023 01:33 PM, H wrote: > On 01/11/2023 02:09 AM, Simon Matter wrote: >> What I usually do is this: "cut" the large disk into several pieces of >> equal size and create individual RAID1 arrays. Then add them as LVM PVs to >> one large VG. The advantage is that with one error on one disk, you wont >> lose redundancy on the whole RAID mirror but only on

Hi, I have a custom linux system that runs off a FAT32 usb flash disk. I use syslinux to make it bootable and load the kernel. I'm trying to boot now from a SSD SATA disk (500GB) but it's not working and I can't figure out why. BIOS show that no bootable disk were found. What I already tried (linux fdisk): 1- Creating a new DOS partition table on the SSD, a FAT32 (type b), and

On 08/09/2017 01:48 PM, hw wrote: > Robert Moskowitz wrote: >> I am building a new system using an Kingston 240GB SSD drive I pulled >> from my notebook (when I had to upgrade to a 500GB SSD drive). >> Centos install went fine and ran for a couple days then got errors on >> the console. Here is an example: >> >> [168176.995064] sd 0:0:0:0: [sda] tag#14

On 01/11/2023 02:09 AM, Simon Matter wrote: > What I usually do is this: "cut" the large disk into several pieces of > equal size and create individual RAID1 arrays. Then add them as LVM PVs to > one large VG. The advantage is that with one error on one disk, you wont > lose redundancy on the whole RAID mirror but only on a partial segment. > You can even lose another