Skip to main content

a plea for non-identical mirrors

When I set up my test environment earlier this year, I put two Samsung HD103UJ 1TB drives in the main file server, and configured them as a RAID-1 software mirror through mdadm. Just months later, smartd was spewing out messages about both drives: Device: /dev/sda, 8 Currently unreadable (pending) sectors.

That got me very worried... I replaced one of the drives with a WDC WD1000FYPS-01ZKB0, and rebuilt the mirror. Actually, I built new mdadm mirrors from smaller partitions to lessen the risk of a two-drive badblock scenario. Regardless, my data got moved, so now everything gets stored on two different drives. Different makes, manufacturers, models. Same size though.

The problem is, I can't RMA the drive. It's still in warranty, but when running badblocks -w on the drive, it shows no problems whatsoever. Moreover, the SMART status has gone back to: Current_Pending_Sector 0. So not only is the problem undetectable by badblocks, it even makes it go away in the SMART counters where it was visible in the first place.
First I thought that the problematic sectors got reallocated, but the SMART info suggests otherwise: Reallocated_Event_Count equals 0. If you want to look at your own drives, grep for _Pending_ and Reallocated_ in the smartctl -a output.

My conclusion: it was a very, very bad idea to make a mirror out of two identical drives (and aggravating the fact, they were the cheapest ones, too). Please remember: pick different drives to make up a mirror. A mirror image needs to be identical, but having it on identical media is a bad, bad thing.

And to round up, my final thoughts: how bad is a non-zero "Current_Pending_Sector" count, really ? And why can it go down without reallocation ?

Side note: I'm not saying Samsung drives are bad, I have 3 Samsung HD300LJ in a RAID-1 setup that are doing fine after more than 2 years of 24x7 service. But buying their 1TB drives left a sour aftertaste...

Comments

Popular posts from this blog

How to solve "user locked out due to failed logins" in vSphere vMA

In vSphere 6, if the vi-admin account get locked because of too many failed logins, and you don't have the root password of the appliance, you can reset the account(s) using these steps:

reboot the vMAfrom GRUB, "e"dit the entry"a"ppend init=/bin/bash"b"oot# pam_tally2 --user=vi-admin --reset# passwd vi-admin # Optional. Only if you want to change the password for vi-admin.# exitreset the vMAlog in with vi-admin These steps can be repeated for root or any other account that gets locked out.

If you do have root or vi-admin access, "sudo pam_tally2 --user=mylockeduser --reset" would do it, no reboot required.

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition).
But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now:
the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth
the phone connects to "Touch Adapter" device, also via bluetoothThe device doesn't allow step 2 if step 1 didn't s…

Multiple VLANs on a Synology NAS

Synology, like other SOHO/SMB NAS vendors, touts VLAN functionality with their current DSM 4.1 software. However, the web interface just lets you specify one VLAN tag to use over each eth interface (or bond interface).
Manual approachIn the busybox environment that you can ssh into as root (after enabling ssh through the webinterface), there's all the tools you need to use multiple VLANs over one link (eth or bond), however:
First you insert the 802.1q module into the Linux kernel:
 /sbin/lsmod | /bin/grep -q 8021q || /sbin/insmod /lib/modules/8021q.koThen you add each VLAN you need to every interface (bond0 in this example)
 /sbin/vconfig add bond0 4And finally you can configure IP addresses on every interface.vlan combination (bond0.4 in this example)
 /sbin/ifconfig bond0.4 192.168.4.1 broadcast 192.168.4.255 netmask 255.255.255.0The same type of script would work on a QNAP NAS too, by the way. They offer 8021q.ko and vconfig in their commandline environment as well.
Packets from…