This is certainly a poor design, as you can read many seasoned admins who have updated their iDRAC only to have it killed. One possible cause is not by doing all the incremental updates, doing updates from an old iDRAC to one many revisions newer is a sure way to kill things, but even then there is no guarantee based on the amount of failures. List of threads of people's dead iDRAC's:........

First of all make sure that you don't have the write-lock or write-protect switch enabled on the SDCard or USB drive. If the above is not the case, then follow these instructions: Solution - Clear Read Only Attribute Hit "Windows Key+R" and enter "cmd" to enter the command prompt: Now type the following :........

This is the reason that I don't like the new ADATA USB drives such as the UV128/64GB or 128GB drives and other ones that look to be the same style (the green sliding USB connector). They just don't work well from new and never work properly at any point. [ 788.242463] usb 1-1.2: new high-speed USB device number 16 using ehci-pci [ 788.339816] usb 1-1.2: New USB device found, idVendor=125f, idProduct=db8a [ 7........

By default at least on Centos 7 nfs only allows 8 connections and starts 8 nfsd daemons. To fix this edit this file:/etc/sysconfig/nfs Edit the line "RPCNFSDCOUNT" (uncomment it so it looks like this: RPCNFSDCOUNT=30 In the example above we are setting 30 nfsd daemons to run (or in other words 30 connections are possible this way).........

This is the closest way to disabling it without using the "libata.force=noncq" kernel boot option is to set the queue to a depth of 1 which doesn't actually disable it. Change the sdc below to match the device you want to disable NCQ for. [root@officebox ~]# echo "1" > /sys/block/sdc/device/queue_depth Errors that indicate you are having a performance issue are these in messages or dmesg relating to N........

cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid10 sdc1[0] sdb1[2] 1953382400 blocks super 1.2 512K chunks 2 far-copies [2/1] [U_] resync=PENDING bitmap: 15/15 pages [60KB], 65536KB chunk Solution force repai........

On a test machine Iwas never able to access to a newly created 4th partiton. As we can see there are dev devices for everything but the 4th partition. The normal "partprobe" or "kpartx" or kernel being told to rescan the block device didn't help (only a reboot did). fdisk -l /dev/sda Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units........

Here is a simple MP3 player and now there's a reason to understand why the supplied cable has some kind of capacitor and is very short. These devices can be VERY finicky and any voltage fluctuation or difference is enough to cause issues. Take for example the error messages from Linux Mint: [804829.895414] usb 1-1: USB disconnect, device number 11 [806961.109030] usb 1-1: new high-speed USB device number 12 using xhci_hcd........

1.) Replicate the number of partitions in your new drives. gdisk /dev/sda gdisk /dev/sdb I created 3 partitions of the same same size. partition #1: +1G (/boot) partition #2: +60G (swap) partition #3: rest of it (/) #note if you are using GPT/gdisk you need to create separate a partition at least 1MB in size (in my case I would a 4th partition and mark it type ef02).........

This was a surprising bug but I unplugged all drives for an array md127. At first it was just 1 drive and mdadm seemed to notice this. I unplugged the second drive taking the array offline but mdadm did not realize it was offline and still showed a non-existent disk as being part of it. This created problems trying to unmount it or even to stop this array with mdadm freezing. As for how to fix it I can only think of making sure you are not in a mounted path of........

It is already known this is not possible mdadm --create /dev/md3 --level 10 --layout=f2 --raid-devices=2 /dev/sdc1 /dev/sdd1 mdadm: /dev/sdc1 appears to be part of a raid array: level=raid10 devices=2 ctime=Sat Dec 24 18:44:29 2016 mdadm: /dev/sdd1 appears to be part of a raid array: level=raid10 devices=2 ctime=Sat Dec 24 18:44:29 2016 Continue creating ar........

Device Boot Start End Blocks Id System /dev/sdc1 1 132 1060256+ fd Linux raid autodetect Partition 1 does not end on cylinder boundary. Partition 1 does not start........

for disk in `fdisk -l|grep "Disk /dev"|awk '{print $2}'|sed s/://g`; do echo "$disk" && smartctl -d ata -a "$disk" -T permissive|grep -iE 'Device Model:|Serial Number:' echo "---------------" done *Make sure you have smartctl from smartmon tools installed Sample output: /dev/sdc Device Model: ........

root (hd2,1) Filesystem type unknown, partition type 0x83 grub> root (hd2,2) root (hd2,2) Filesystem type is ext2fs, partition type 0x83 grub> setup (hd2) setup (hd2) Checking if "/boot/grub/stage1" exists... no Checking if "/grub/stage1" exists... no #weird thing about grub is that the drive you enter is considered hd0 For example when booted fu........

mdadm --create /dev/md1 --level 10 --raid-devices=2 /dev/sdb2 /dev/sdc2 --layout=f2 --metadata=0.90 Note that layout=f2 or layout=n2 is very important as without it you'll get a complaint like this: mdadm --create /dev/md0 --level 10 --raid-devices /dev/sdb1 /dev/sdc1 missing missing mdadm: invalid number of raid devices: /dev/sdb1 It is basically more like a prop........

[3805108.257042] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) [3805108.257052] sd 0:0:0:0: [sda] Write Protect is off [3805108.257054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3805108.257066] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3805108.257083] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) [3805108.257090] sd 0:0:0:0: [sda] Write Protect is off........

This is a great way to upgrade your RAID array or move it/copy it to a new set of hard drives. Eg. you have a current RAID 1 array on older/slower drives. Just add at least 1 of the new drives to the array, update grub/install it and then boot into it. Then you have a transparent data migration that is fully synchronized. mdadm --grow /dev/md126 --raid-devices 3 md127 : active raid1 sdc1........

The results are not bad, the Hitachi performs the same as it does in a SATA2 motherboard. However, the 2TB is much different, on a similar 2TB Toshiba I get about 198MB/s on a different motherboard vs the 2TB Hitachi which should produce similar results. This Dell Perc 6/i is on a PCI x8 riser card and is connected to a 12-port backplane. Adapter #0 Enclosure Device ID: 32 Slot Number: 0 Enclosure position: N/A De........

vgchange -ay 3 logical volume(s) in volume group "vg_12" now active lvscan inactive '/dev/vg_12/lv_root' [144.04 GB] inherit inactive '/dev/vg_12/lv_home' [1.00 GB] inherit inactive '/dev/vg_12/lv_swap' [7.85 GB] inherit........

mdadm --manage /dev/md3 --add /dev/sda1 cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : inactive sdd2[1] sdd1[2](S) 31270272 blocks md3 : active raid1 sda1[2] sdb1[1] sdc1[3](F) 943730240 blocks [2/1] [_U] [>....................]........

I chose this because I heard a lot of stories about scams and that many providers I contacted said they can't unlock the Canadian I717s (one said "my Bell server" is down). This method worked perfectly on my Bell I717M and should work for all I717 in Canada, I was able to insert a foreign SIMcard. This will work abroad too but remember entering CWM mode is different for I717's in other countries (at least theUS). Step 1 - Root + CWM........

Here's a proven example of what a bad hard drive can do, it was technically functioning OKin a RAID array but the system became extremely low and the load become high and IOWAIT was even higher and I always thought it was a bad application. The truth is that this failing 1TBHitachi has slowly gotten worse and caused huge slowdowns, (eg. 100% load on Thunderbird waiting for e-mails to load etc..). After swapping it out, tabs change instantly, emails are not lagged, and........

I like badblocks and don't know a better more reliable way of checking the drive. If there are no errors from badblocks and dmesg doesn't produce any SATA related errors, the drive should be good (for now at least). I also prefer to do read and write mode, yes it takes ages but it is really the best way of doing it. This gives me the most confidence in knowing that a drive, especially a new one is at least OK at the moment. To test in read only mode........

parted sdc.img GNU Parted 1.8.8 Using /home/one/sdc.img Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) unit&nb........

I backed up everything in the /mnt/sd_card directory thinking that some dataloss could occur for some reason but purposely left my microSDHC unbacked up thinking that "it won't touch that since it's external" and Samsung's and other manufacturers website even say this (that it won't be affected and not to worry etc). Apparently I was wrong, my microSD was "undetected" and asked to be formatted after the upgrade (there goes 3-months worth of family photos). No........

This doesn't seem to be widely known (maybe it's in some documentation that none of us read though)but there's an easy way to check the integrity of any mdadm array: sudo echo check > /sys/block/md0/md/sync_action -bash: /sys/block/md0/md/sync_action: Permission denied sudo will never work, this only works as root since echo is not actually a binary/command. It is built-into bash. /sys/devices/virtu........

I've only used it on Centos, soI thought I'd make a quick Debian guide: Install the DRBD Package apt-get install drbd8-utils Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libswfdec-0.8-0 Use 'apt-get autoremove' to remove them. The following........

I separated the 2 drives in the RAID 1 array. 1 is the old one /dev/sda and is out of date, while the separated other one /dev/sdc was in another drive and mounted and used with more data (updated). I wonder how mdadm will handle this: usb-storage: device scan complete md: md127 stopped. md: bind md: md127: raid array is not clean -- starting background reconstruction raid1: raid set md127 active with 1 out of 2 m........

From the package "parted" you can use the command "partprobe" to re-read the partition table. I really hate rebooting, and that's what Iloved to hear about AHCI motherboards, that they allow hotswap so you don't have to reboot. But that's only as good as the OS, if the OS does not reload the partition table you won't be able to do anything with that new drive you attached without rebooting. Yes, even without re-reading the partiton table Linux will........

The binary "iostat" comes from the package "sysstat" and is available on all Linux/Unix like platforms. Use the "-m" option to give you what you probably want, which is to see in MB/s how much bandwidth each disk is doing. iostat -m Linux 2.6.24.2 ((none)) 04/16/10 avg-cpu: %user %nice %system %iowait %steal %idle ........