2020. 2. 23. 01:48ㆍ카테고리 없음
I’ve been on holidays for three full weeks and it was amazing. I’ll get back to writing about boring stuff soon, but I thought I’d post a quick summary of some issues I’ve had with my home-built NAS recently and what I did to fix it.Where Are The Disks Gone?I got an email one evening with the following message.I do enjoy the “Faithfully yours, etc” and the post script is the most enlightening bit. See where it says UUUU? Yeah, that’s not good. There are 8 disks that make up that device (/dev/md0), so it should look more like UUUUUUUU. But why would 4 out of 8 disks just up and disappear?
I thought it was a little odd myself. I had a look at the ITX board everything was attached to and realised that those 4 drives were plugged in to a PCI SATA-II card. It seems that either the slot on the board or the card are now failing intermittently. I say “seems” because that’s all I can think of, as the S.M.A.R.T. Status of the drives is fine.Resolution, BabyThe short-term fix to get the filesystem back on line and useable was the classic “assemble” switch with mdadm. Long time readers of this blog may have witnessed me doing something similar with my QNAP devices from time to time. After panic rebooting the box a number of times (a silly thing to do, really), it finally responded to pings.
Checking out /proc/mdstat wasn’t good though. Dan@openmediavault:$ cat /proc/mdstat Personalities: raid6 raid5 raid4 unused devices: Notice the lack of, erm, devices there? That’s non-optimal.
The fix requires a forced assembly of the devices comprising /dev/md0. Dan@openmediavault:$ sudo mdadm -assemble -force -verbose /dev/md0 /dev/sdabcdefhi sudo password for dan: mdadm: looking for devices for /dev/md0 mdadm: /dev/sda is identified as a member of /dev/md0, slot 0. Mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1. Mdadm: /dev/sdc is identified as a member of /dev/md0, slot 3. Mdadm: /dev/sdd is identified as a member of /dev/md0, slot 2. Mdadm: /dev/sde is identified as a member of /dev/md0, slot 5. Mdadm: /dev/sdf is identified as a member of /dev/md0, slot 4.
Mdadm: /dev/sdh is identified as a member of /dev/md0, slot 7. Mdadm: /dev/sdi is identified as a member of /dev/md0, slot 6. Here are a few links to some news items and other content that might be useful. Maybe.
have added as a customer, deploying an E8-D24 array for use with genomic sequencing work. You can read more about that.
Something went pear-shaped with my mail provider, so I decided to use Gmail for my NAS email notifications. QNAP has some built-in smarts and works out of the box.
For my environment, though, with Gmail take a little extra effort. In short, you’ll need to turn on 2FA and create an. This project seems finished now (and I love it) –.
recently published a. If you’ve been involved in storage administration, this from the good doctor, might be just your thing. did a announcements.
I’ve been participating in the tech version of “Blogtober” because I was going to be writing and it’s October. You can find out a bit more about it. I recently had the opportunity to replace a bunch of ageing 2TB drives in my OpenMediaVault NAS with some 3TB drives. I run it in a 6+2 RAID-6 configuration (yes, I know, RAID is dead). I was a bit cheeky and replaced 2 drives at a time and let it rebuild. This isn’t something I recommend you do in the real world.
Everything came up clean after the drives were replaced. I even got to again to tell it I had 0 spares. The problem was that the size of the filesystem in OpenMediaVault was the same as it was before. When you click on Grow it expects you to be adding drives. So, you can grow the filesystem, but you need to expand the device to fill the drives.
I recommend taking a backup before you do this. And I unmounted my shares before I did this too.If you’re using a bitmap, you’ll need to remove it first. Mdadm -grow /dev/md0 -bitmap nonemdadm -grow /dev/md0 -size maxmdadm -wait /dev/md0mdadm -grow /dev/md0 -bitmap internalIn this example, /dev/md0 is the device you want to grow. It’s likely that your device is called /dev/md0. Note, also, that this will take some time to complete. The next step is to expand the filesystem to fit the RAID device.
Open Media Vault Guide
It’s a good idea to run a filesystem check before you do this. Fsck /dev/md0Then it’s time to resize (assuming you had no problems in the last step). Resize2fs /dev/md0You should then be able to remount the device and see the additional capacity. Big thanks to kernel.org for having some useful instructions. I recently upgraded my home-brew NAS from OpenMediaVault 2.2.14 to openmediavault 3.0.86. It’s recommended that you do a fresh install but I thought I’d give the upgrade a shot as it was only a 10TB recovery if it went pear-shaped (!).
Open Media Vault Setup
They also recommend you disable all your plugins before you upgrade.Apt-get all of the thingsIt’s an OS upgrade as well as an application upgrade. In an ssh session I ran apt-get update && apt-get dist-upgrade && omv-updateThis gets you up to date, then upgrades your distro (Debian), and then gets the necessary packages for omv. I then ran the omv upgrade. Omv-release-upgradeThis seemed to go well.
I rebooted the box and could still access the shared data. When I tried to access the web UI, however, I could enter my credentials but I couldn’t get in. I then ran omv-firstaidAnd tried to reconfigure the web interface. It kept complaining about a file not being found. So I ran dpkg -l grep openmediavaultThis told me that there was still a legacy plugin (openmediavault-dnsmasq) running. I’d read on the forums that this might cause some problems. So I used apt-get to remove it.
Apt-get remove openmediavault-dnsmasqThe next time I ran apt-get it told me there were some legacy packages present that I could remove. Apt-get autoremove dnsmasq dnsmasq-base libnetfilter-conntrack3After that, I was able to login in to the web UI with no problems and everything now seems to be in order. When my new NAS arrives I’ll evacuate this one and rebuild it from scratch.
Open Media Vault Vs
There are a fair few changes in version 3 and it’s worth checking out. You can download the ISO image from.DNS MattersThe reason I had the dnsmasq plugin installed in the first place was that I’d been using the NAS as a DHCP / DNS server. This had been going reasonably well, but I’d heard about and wanted to give that a shot. That’s a story for another time, but I did notice that my OMV box hadn’t updated its /etc/resolv.conf feel correctly, despite the fact that I’d reconfigured DNS via the web GUI. If you run into this issue, just run dpkg-reconfigure resolvconfAnd you’ll find that resolv.conf is correctly updated. Incidentally, if you’re a bit old-fashioned and don’t like to run everything through DHCP reservations, you can add a second set of static host entries to dnsmasq on your pi-hole machine by following.
You can file this article under “not terribly useful but something I may refer to again in the future”. I’ve been migrating a bunch of data from one of my QNAP NAS devices at home to my NAS. Monit, my “faithful employee”, sent me an email to let me know I was filling up the filesystem on the OMV NAS.By default OMV alerts at 80% full. You can change this though. Just jump on a terminal and run the following: nano /etc/default/openmediavaultAdd this line to the file OMVMONITSERVICEFILESYSTEMSPACEUSAGE=95Then run the following commands to update the configuration omv-mkconf collectdmonit restart collectdOf course, you need to determine what level of filesystem usage you’re comfortable with.
In this example, I’ve set it to 95% as it’s a fairly static environment. If, however, you’re capable of putting a lot of data on the device quickly, then 5% buffer may be insufficient. I’d also like to clarify that I’m not unhappy with QNAP, but the device I’m migrating off is 8 years old now and it would be a pain to have to recover if something went wrong.
If you’re interested in reading more about Monit you can find documentation. My homebrew NAS running OpenMediaVault (based on Debian) started writing to me recently. I’d had a disk failure and replaced the disk in the RAID set with another one. Everything rebuilt properly, but then this mdadm chap started sending me messages daily.
'This is an automatically generated mail message from mdadmrunning on openmediavaultA SparesMissing event had been detected on md device /dev/md0.Faithfully yours, etc.P.S. The /proc/mdstat file currently contains the following:Personalities: raid6 raid5 raid4md0: active raid6 sdi0 sda8 sdb6 sdc5 sdd4 sde3 sdf2 sdh12 blocks super 1.2 level 6, 512k chunk, algorithm 2 8/8 UUUUUUUUunused devices: 'Which was nice of it to get in touch. But I’d never had spares configured on this md device.
The fix is simple, and is outlined. In short, you’ll want to edit /etc/mdadm/mdadm.conf and changes spares=1 to spares=0. This is assuming you don’t want spares configured and are relying on parity for resilience. If you do want spares configured then it’s probably best you look into the problem a little more.
Following on from my brief look at FreeNAS, I thought I’d do a quick article on as well. While it isn’t quite as mature as FreeNAS, it is based on. I’ve had a soft spot for Debian ever since I was able to get it running on a I had lying about many moons ago. The Jensen is no longer with us, but the fond memories remain.
Anyway Firstly, you can download OpenMediaVault. It’s recommended that you install it on a hard drive (ideally in a RAID 1 configuration) rather than on USB or SD cards. Theoretically you could put it on a stick and redirect the more frequently written stuff to a RAM disk if you really didn’t want to give up the SATA ports on your board. I decided to use an SSD I had laying about as I couldn’t be bothered with more workarounds and “tweaks”.