Stack Exchange Network

Stack Exchange network consists of 174 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

New answers tagged

1

This is what zpool labelclear is for. The disk still has ZFS metadata on it indicating that it is part of a zpool, because you removed the disk without telling ZFS about it first. To resolve the problem, use zpool labelclear -f <device>. This will wipe the ZFS labels from the device so that it can be used in another pool. -f is required when the ...


0

You need to enable/start also ntpdate. It synchronizes the clock even if the datetime is off by a lot. sysrc ntpdate_enable="YES" service ntpdate start Cheers!


4

"NASware" is just WD marketing speak for drive firmware they claim to have optimized for use in NAS devices. There is no specific action you need to take beyond just using the drive normally. However, you may wish to create your zpool with ashift=12 to ensure that it is aligned on 4K sector boundaries.


1

From the FreeBSD man: -h The system is halted at the specified time. -p The system is halted and the power is turned off (hardware sup- port required) at the specified time. I believe you need shutdown -p now.


1

Thank you for your help. Alas none of the above suggestions would work for me. After much reading and experimentation I found had to add the -r (to activate the regex) before the -i and this is the format I used for the regex, which seems to work. sed -r -i '' '/^120[.]152[.][0-9]{1,3}[.][0-9]{1,3}/d' /path/to/some/file to remove the ip 120.152.35.192 ...


0

I think your problem is that the . is working as a wildcard matching any character, instead of that use \. which would match a literal .. Unfortunately I don't know the differences with FreeBSD, but as this is a somewhat simple regex I imagine it should work. I would use as a generic regex (very simplified) for any IP the following: '/^[0-9]+\.[0-9]+\.[0-9]...


1

nginx will likely be able to read the files as needed withing being explicitly setting the file's group owner as the nginx user and for php-fpm the nginx user can simply be set as the listener php-fpm.d/php-fpm-user1.conf [grav] user = user1 group = use1 listen = /var/run/php-fpm-user1.sock listen.owner = www listen.group = www pm = dynamic pm....


0

I made a script that lists all of the GPTID and associated hard drive serial number and device name. #!/bin/bash #Use smartctl to get Serial Number - else dmesg is used USESMART=0 #save glabel status to temporary file CACHEGLABEL=1 if [ $CACHEGLABEL -eq 0 ] then GLCMD="glabel status" else GLTMP=/var/tmp/$0.glabel glabel status > $GLTMP GLCMD="cat $...


10

Those numbers are obviously bogus. Your SSD doesn't have that many sectors at all, let alone offline uncorrectable ones. Check for firmware updates for your SSD that will fix the problem. Otherwise, ignore it. If you're really paranoid, you could replace the drives, but in that case you should use different drives, not the same brand from the same ...


Top 50 recent answers are included