11-26-2018
I'm not familiar with Buffalo NAS specifically but there are two different architectures of RAID controller.
One stores the array configuration information on the disks, including type of array (Raid 0,1,3,5,6 or whatever) and the disk member number of that array. When this type of controller fails you can replace it with a new one which, at boot, will read the disk labels and run with the previous RAID array(s).
The second, and most common type, stores the array configuration in its own NVRAM and if the controller fails you have to find a way of resetting the correct configuration into NVRAM. Often this is by using some new disks to configure the same array and then swapping the disks back to the originals. The manufacturer would usually be referred to for advice.
It seems to me like the NTFS filesystem is not as it was so your recovery technique was flawed. Perhaps the disks are in the wrong order or something like that. Kali doesn't like what it's seeing. It might be quicker to initialise the array and restore from backup.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Percent complete SCO 5.0.6 / No longer an issue (0 Replies)
Discussion started by: Henrys
0 Replies
2. AIX
I created a RAID 5 array and when I list out the attributes of the "hdisk" it reports back raid_level = 5 but the RAID level of the array = false. What does this actually indicate about my array? I've never paid much attention to this until now since I have a disk reporting failure I want to make... (0 Replies)
Discussion started by: scottsl
0 Replies
3. UNIX for Advanced & Expert Users
Hi guys,
i must install an old old old ml370 server...
I must create a RAID 5 with my 4 SCSI disk.
I need a SmartStart disk for create it or a Floppy Disk called "Array configuration Tool". I don't find it on the hp website...:mad::mad::mad:
Anyone have it??
Thanks in advance.
Zio (0 Replies)
Discussion started by: Zio Bill
0 Replies
4. Solaris
Hi Peeps,
Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it.
Anyone got any ideas on how to remove the EFI label?
Thanks in advance
Martin (2 Replies)
Discussion started by: callmebob
2 Replies
5. Emergency UNIX and Linux Support
One of my very old drive farm servers had an OS fault and can't boot now but I'd like to restore some files from it. I tried booting Ubuntu from a CD, but it couldn't see the drives -- possibly because they're RAIDed together. Is there a good way to get at my files?
The data in question is a... (2 Replies)
Discussion started by: CRGreathouse
2 Replies
6. Red Hat
Dear all ,
i ve configured raid 0 in redhat machine(VM ware), by following steps:
#mdadm -C /dev/md0 -l 0 -n 2 /dev/sdb1 /dev/sdc1
#mkfs.ext3 /dev/md0
#mdadm --detail --scan --config=mdadm.conf >/etc/mdadm.conf
then
mounted the/dev/md0 device and also added a entry in fstab.
how... (2 Replies)
Discussion started by: sriniv666
2 Replies
7. Debian
I am installing a Debian Server on a:
HP Proliant DL380 G4
Dual CPU's 3.20 ghz / 800 mhz / 1MB L2
5120 MB RAM
6 hard disks on HP Smart Array 6i controller (36.4 GB Ultra320 SCSI HD each)
I will be using this server to capture VHS video, encode, compress, cut, edit, make DVD's, rip... (0 Replies)
Discussion started by: Marcus Aurelius
0 Replies
8. What is on Your Mind?
No rest for the weary, a Revive Ad Server I am responsible for experienced a MySQL injection attack due to a vulnerability uncovered in the past few months. I was busy developing Vue.js code for the forums and thought to myself "I will get around to upgrading to Revive 4.2.0 (supposedly the... (0 Replies)
Discussion started by: Neo
0 Replies
DUO(3) BSD Library Functions Manual DUO(3)
NAME
duo -- Duo authentication service
SYNOPSIS
#include <duo.h>
duo_t *
duo_open(const char *ikey, const char *skey, const char *progname, const char *cafile);
void
duo_set_conv_funcs(duo_t *d, char *(*conv_prompt)(void *conv_arg, const char *, char *, size_t),
void (*conv_status)(void *conv_arg, const char *msg), void *conv_arg);
void
duo_set_host(duo_t *d, const char *hostname);
void
duo_set_ssl_verify(duo_t *d, int bool);
duo_code_t
duo_login(duo_t *d, const char *username, const char *client_ip, int flags, const char *command);
const char *
duo_geterr(duo_t *d);
void
duo_close(duo_t *d);
DESCRIPTION
The duo API provides access to the Duo two-factor authentication service.
duo_open() is used to obtain a handle to the Duo service. ikey and skey are the required integration and secret keys, respectively, for a
Duo customer account. progname identifies the program to the Duo service. cafile should be NULL or the pathname of a PEM-format CA certifi-
cate to override the default.
duo_set_conv_funcs() may be used to override the internal user conversation functions. conv_prompt is called to present the user a login
menu and prompt, and gather their response, returning buf or NULL on error. It may be set to NULL if automatic login is specified with
DUO_FLAG_AUTO. conv_status is called to display status messages to the user, and may be NULL if no status display is needed. conv_arg is
passed as the first argument to these conversation functions.
duo_set_host() may be used to override the default Duo API host.
duo_set_ssl_verify() may be used to override SSL certificate verification (enabled by default).
duo_login() performs secondary authentication via the Duo service for the specified username. client_ip is the source IP address of the con-
nection to be authenticated, or NULL to specify the local host. The following bitmask values are defined for flags:
DUO_FLAG_AUTO Attempt authentication without prompting the user, using their default out-of-band authentication factor.
DUO_FLAG_SYNC Do not report incremental status during authentication (e.g. voice callback progress) - only issue one status message
per authentication attempt.
If not NULL, the command to be authorized will be displayed during push authentication.
duo_geterr() returns a description of the last-seen error on the specified Duo API handle. The returned constant string should not be modi-
fied or freed by the caller.
duo_close() closes and frees the specified Duo API handle.
RETURN VALUES
duo_open() returns a pointer to the configured Duo API handle, or NULL on failure.
duo_login() returns status codes of type duo_code_t, which may have the following values:
DUO_OK User authenticated
DUO_FAIL User failed to authenticate
DUO_ABORT User denied by policy
DUO_LIB_ERROR Unexpected library error
DUO_CONN_ERROR Duo service unreachable
DUO_CLIENT_ERROR Invalid client parameters to API call
DUO_SERVER_ERROR Duo service error
In the event of a DUO_*_ERROR return, duo_geterr may be called to recover a human-readable error message.
duo_geterr() returns a constant string which should not be modified or freed by the caller.
SEE ALSO
pam_duo(8), login_duo(1)
AUTHORS
Duo Security <duo_unix@duosecurity.com>
BSD
October 31, 2010 BSD