Debian Hardware :: Servers Which Contain SATA Disks And SAS Disks?
Feb 25, 2010
I have servers which contain SATA disks and SAS disks. I was testing the speed of writing on these servers and I recognized that SAS 10.000 disks much more slowly than the SATA 7200. What do you think about this slowness? What are the reasons of this slowness?
I am giving the below rates (values) which I took from my test (from my comparisons between SAS 10.000 and SATA 7200);
dd if=/dev/zero of=bigfile.txt bs=1024 count=1000000 when this comment was run in SAS disk server, I took this output(10.000 rpm)
(a new server,2 CPU 8 core and 8 gb ram)
1000000+0 records in
1000000+0 records out
1024000000 bytes (1.0 GB) copied, 12.9662 s, 79.0 MB/s (I have not used this server yet) (hw raid1)
i currently try to mount 4 internal sata disks using hal on a server installation?
i did
apt-get install hal and copied a .fdi script to /usr/share/hal/fdi/policy/10osvendor/30-storage-all.fdi
as far is i understand now i need a hal/dbus client gnome-volumen-manager seems to be one apt-get install gnome-volume-manager
now im stuck there is no such executable like gnome-volumen-manager thus, how does it work? how can i start it? how do i know if and why the .fdi script works or fails?
since its a server edition and its purpose should be a very minimized server install i dont want a GUI like gnome fully installed
I have/had a PC with several hard drives, and a mix of ubuntu and windows on multi boot.The old boot drive died screaming, and I need to start again. (But my data is safe! yay!)
Is there anything special about which drive can be the main drive to start booting from? Or to put it another way, can I install to any of the other 3 and expect it to work, or do I need to switch them around so a different drive is on the connections for the recently dead one?
i installed latest ubuntu server 9.10 on my mini itx board which i have 1 4gb IDE disk and 4x2TB sata disks attached no i want those disks to automount on startup is there a way without modifiying fstab? the thing is, i want to expand the storage over time (next hard disks in a few months) and maybe a second mainboard in a year so i need a simple way to mount everything without being to mainboard specific like doing fstab entries
used to run ARC linux and Windows 7 on my computer and i am now trying to install Ubuntu 10.10 X86_64When i used the live disc of Ubuntu 10.04 and load the installer it finds my four harddrive they way it should... sda,sdb,sdc,and sdd...When i however try the same with ubuntu 10.10 it displays my usb cardreaders drives first and then my hardrives as sde sdf sdg and sdh.I tried installing ubuntu with the reader unplugged and then reconnecting it after installation...But when i then boot with the reader attached it says it cannot mount drives sda,sdb,sdc and sdd becuase they are not ready.I think it is again detecting the usb cardreader before the sata controller ...Is there a way for me to alter the boot detection order so it will find my harddrives first and then the usb cardreaders ports ?
How to configure the master and slave on 5 Sata disks? Is there that or it is automatic.I install Debian, ok, master boot ok, on the first sataAnd at reboot, just after install, the boot hangs and no grub appears.
I've just removed fedora 10 and installed CentOS 5.4 both x86_56 on my Lenovo ThinkCentre 9091-CTO workstation, and observed serious performance degradation while intensive I/O operations and huge load without significant CPU consumption in user mode with about 50% in I/o wait.For example if I do the "tar xjvf some_large_tar.bz" file and run vmstat i get the output below. This is the only cpu and io intensive process running. The load gets up to 6 on C2D CPU and the machine has unacceptable responsivness.
[root@f00 ~]# vmstat 5 10 procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------ r b swpd free buff cache si so bi bo in cs us sy id wa st
I have Fedora 13 installed in a new computer, and form some weird reason, udev is skipping three of my HDs. Looging the output for udev --triger, the entries for the HDs are skipped
Code: [root@storage ~]# lspci 00:00.0 Host bridge: ATI Technologies Inc RD780 Northbridge only dual slot PCI-e_GFX and HT1 K8 part 00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A) 00:06.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port C) 00:07.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port D) 00:0a.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F) .....
Trying to install SUSE on a perfectly working PC that was running Windows. Blew away all the partitions and formated the drives.When trying to install SUSE, Installer will not detect my two hard disks. Tried with version 10.x, 11.1 and 11.2, without success.My Mobo is a XFX GeForce 8209, and my SATA drives are both Seagates (1x120GB, 1x320GB). I've tried different SATA mode selection (i.e. SATA, AHCI, and RAID) without any success either.I've tried to look for SATA controller drivers for my Mobo, to try to load on Installer startup, but failed there too.
I have a Dell Studio XPS running openSUSE 11.2 with dual mirrored disks (using Dell's SATA controller). Does anyone know how I can set up automatic monitoring of the disks so that I will be informed if either fail? I think smartd might be what I need here. Is that correct? I added: /dev/sda -a -d sat -m <my email> /dev/sda -a -d sat -m <my email>
smartd is running, but how do I know that it will report what I need? I also have a client with a Dell PowderEdge SC440 with SAS 5/iR also running openSUSE 11.2. They also require automatic monitoring. There doesn't seem to be a SAS directive for smartd. I notice that the newer release says it does support SAS disk. I upgraded to 5.39. On restart (with DEVICESCAN as the directive) I get the following in /var/log/messages for my SAS RAID disk.
Sep 18 10:47:26 harmony-server smartd[25234]: Device: /dev/sdb, Bad IEC (SMART) mode page, err=4, skip device I ran: smartctl -a /dev/sdb and got the result: smartctl 5.39.1 2010-01-28 r3054 [x86_64-unknown-linux-gnu] (openSUSE RPM) Copyright (C) 2002-10 by Bruce Allen, smartmontools
Device: Dell VIRTUAL DISK Version: 1028 Device type: disk Local Time is: Sat Sep 18 11:32:08 2010 JST Device does not support SMART Error Counter logging not supported Device does not support Self Test logging
Is there some other tool/package that does support DELL virtual disks?
I upgraded F14 to F15; However, F15 no longer recognizes my 3 sata disks connected through Marvell controller. The controller is an integrated Marvell chipset 88SE6480. The controller has its own manufacturer driver but it was intended for RHEL 5.4 (mv64xx) and installation of this driver fails to generate mv64xx driver.
1 Areca controller 1222 divided into 2x250Gb in RAID 1 for my Ubuntu installationm6x 2Tb in RAID 5 for my data (mounted as logical drive) resulting in 8Tb of available space (also visible in the disk utility of Ubuntu) Ubuntu 10.04 LTS
Now the problem; when I check the capacity in the file browser on my mounted data drive, I only see 5,1 Tb of total space.
when I start my raid5, only 2 disks of 3 are active on md0. The 3rd disk is inactive on md_d0.When I do mdadm --examine, the two active disks report 2 active, 2 working, 1 failed. the inactive disk resports 3 active, 3 working, 0 failed.
I am trying to create a new mdadm RAID 5 device /dev/md0 across three disks where such an array previously existed, but whenever I do it never recovers properly and tells me that I have a faulty spare in my array. More-specific details below. I recently installed Ubuntu Server 10.10 on a new box with the intent of using it as a NAS sorta-thing. I have 3 HDDs (2 TB each) and was hoping to use most of the available disk space as a RAID5 mdadm device (which gives me a bit less than 4TB.)
I configured /dev/md0 during OS installation across three partitions on the three disks - /dev/sda5, /dev/sdb5 and /dev/sdc5, which are all identical sizes. The OS, swap partition etc. are all on /dev/sda. Everything worked fine, and I was able to format the device as ext4 and mount it. Good so far.
Then I thought I should simulate a failure before I started keeping important stuff on the RAID array - no point having RAID 5 if it doesn't provide some redundancy that I actually know how to use, right? So I unplugged one of my drives, booted up, and was able to mount the device in a degraded state; test data I had put on there was still fine. Great. My trouble began when I plugged the third drive back in and re-booted. I re-added the removed drive to /dev/md0 and recovery began; things would look something like this:
I have some WD20EARS drives that I am trying to format into a pair of Linux software RAID1 devices. The problem is that at seemingly random steps during the process, the operating system decides the disk is a size much smaller than it actually is (2 TB, or as reported by the OS when it is acting normal, 1.82 TB). I follow this general layout of steps: first, I do fdisk -u /dev/sd[x], create a primary partition spanning the whole disk starting from sector 64 (to align the advanced format blocks properly). I set the partition type to fd (software RAID autodetect). Then, I assemble the arrays with mdadm:
Code: mdadm --create /dev/md[z] --level=raid1 --raid-devices=2 /dev/sd[x]1 dev/sd[y]1 And then I create an ext4 filesystem: Code: mkfs.ext4 /dev/md[z]
For reasons I can't understand, fdisk, parted, and gparted (basically, everything) decides at any random point in that process that my disks are not 1.82 TB, but instead something like 172 GB or 500 GB. Once that happens, nothing I do to try to get my disks back seems to work. I've tried using expert mode in fdisk to manually reset the number of cylinders to the correct amount, but this hasn't worked either. Nothing short of reinstalling the system seems to work (but when I boot the installer, it seems to recognize the correct size of the disks).
Using a fresh copy of server 10.04 im trying to simulate a failed raid array on a pair of 2tb disks. Here is the procedure i have been following so far:
- Remove the dead disk partitions from each of the raid 1 arrays (substitute the correct md devices and partitions) - mdadm /dev/md0 -r /dev/sdb2 - mdadm /dev/md1 -r /dev/sdb3
[code]....
I get an error here that sfdisk does not support gpt (guid partition table). I thought sfdisk did support gpt? It says to use parted, but i cant find a command that copies a partition table over from another disk in parted documentation. Any suggestions? I suppose i could make the partitions manually, but im writing a procedure for people who arent that technical and i need it to be simple enough to be run in my absence. manually building the partitions would be too hard for them.
When booting, the grub menu appears and allows me to boot from the internal hard disk (sda) any OS there, such as WHEEZY (sda9). On the external disk (sdb) there is a dd'd copy (not an installation) of SQUEEZE (sdb1), which at one time was on sda but which has different partition assigments listed in its grub.cfg than the current ones shown below for sda.
Code:
Select allNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 23G 0 part ├─sda3 8:3 0 1K 0 part ├─sda5 8:5 0 3.9G 0 part [SWAP] ├─sda6 8:6 0 11.7G 0 part ├─sda7 8:7 0 19.5G 0 part /home/norman/data
[code]....
Can I manually boot the SQUEEZE copy on sdb1 using grub commands (set, linux, initrd, boot) without disturbing the WHEEZY and other OSs on sda? Or will they be disrupted?Alternatively if for example JESSIE is installed in sdb3, for example, can it be booted similarly without affecting the installations on sda? I hesitate to try this by trial and error because of the work and time involved in rebuilding messed-up OSs to their desired configurations.
I've got a raid5 array of 4 disks with ubuntu 8.04 runing on it that is currently still working:
/dev/sda /dev/sdb /dev/sdc /dev/sdd
Smartmontools for /dev/sdc tell that there are 9 sectors pending for reallocation:
Code:
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 9 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 9 And /dev/sdd has increasing number of reallocated sectors (about 1 every couple of minutes):
Code:
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1735 /dev/sdc has failed a coulple of times this week (but I have always sucessfully readded it to raid5) . But the increasing number of reallocated sectores on /dev/sdd concerns me even more.
I'm affraid that during removal of /dev/sdd and adding new /devs/sdd disk, raid might fall appart. That's why I would try to do it in Ubuntu Live CD:If the raid falls appart (/dev/sdc fails) during the readding of new /dev/sdd disk, I might still remove the new /dev/sdd and return the previous one and assemble the raid with:
/dev/sda /dev/sdb /dev/sdd (old one that was previously removed)
Does assembling Raid in Ubuntu Live and adding new disk for /dev/sdd write anything on /dev/sda, /dev/sdb and /dev/sdc in the process of adding /dev/sdd into raid5?
I have given up (for now, at least) the idea of a raid solution but I will still have 2-3 hard disks available for my workstation. If I choose to reinstall from scratch,can I have essentially two different homes?
Got Wintendo7 on one samsung S-ATA disk. ( need it for starcraft2 and Homeworld2... sorry.. )
Now..: Booting Debian Unstable from USB or CD-ROM, then start installer. Tell it to install on second samsung S-ATA disk. Before I go on, I just feel i will get into some serious trouble with GRUB?
Or will the installer understand, and see the windows7 installation and add it to Grub?
If not, what should I do inside /boot/grub/menu.lst when Debian is up and running?
During installation when i set the partitions i have to provide a Name and a Label. What is the difference of these? It looks like only one should be needed. Any problems of using the same name for both?
I have installed a minimal system with openbox window decorator. (without any window manager) when i insert a flash disk to my computer, system doesn't mount it automaticly. i must mount it to a folder to use it.
I'm not sure how to do this. I checked the hard drive preferences and looked through the forums... I don't want to manually mount my hard drives(s) every time I boot up just to access my music and wallpapers.
Earlier today I installed Debian Squeeze with Gnome off the 64-bit CD 1. I didn't have my ethernet connected and ended up only getting a pretty minimal desktop with not much installed besides Gnome. This bothered me, as I thought I could install the whole desktop off the CD. I reinstalled, this time with my Ethernet connected. This time it took much more time and gave me what I wanted, a complete desktop. Simply put, what do I need to install everything that I currently have without having my Ethernet plugged in?
I am running Debian 3.2.0-0.bpo.2-amd64 on hyper-v, my / volume ran out of space and is sitting at 100%, I have extended the disk size on hyper-v, however when I go to Fdisk I see duplicates of each disk.
I have total of 2 vhds on the vm, so I see 4 disks under fdisk. Here is the output of fdisk
I'm trying to do some RAID managing with mdadm. I would like to sync my spare disk and then remove it from the array for making a backup out of it with dd command (the best way i can think of to get the current image of the whole system as it can't be done using the active RAID as source, because is constantly in use and changing). So, I have RAID1 array with 1 spare and 2 active disks (configuration listed below). Now I would like to force spare to sync and then remove it from array, although not faulty.
However, mdadm man page states: "Devices can only be removed from an array if they are not in active use. i.e. that must be spares or failed devices. To remove an active device, it must be marked as faulty first."
So, I'd have to mark a disk as faulty (which it is not) to be able to remove it from array. There seems to be several people reporting that they can't remove this faulty flag accidentally given to a drive. And mdadm does not give direct for such operation. Isn't there a way I could remove and add disks whenever feeling like it?? One way would be open the cover and physically remove the disk. I'm not taking the risk, though. System is almost always in use, so there is not much chance for me to power off for temporary disk removal.
RAID CONFIGURATION: ~# mdadm --detail /dev/md0 /dev/md0: Version : 00.90.03 Creation Time : Fri Aug 4 17:38:26 2006 Raid Level : raid1 Array Size : 238950720 (227.88 GiB 244.69 GB)
