Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

MAX Data service fails to start after installation

Views:
107
Visibility:
Public
Votes:
0
Category:
max-data
Specialty:
san
Last Updated:

Applies to

MAX Data Installation
Red Hat Enterprise Linux (RHEL) 
Community Enterprise Operating System (CentOS)

Issue

  • After installing and configuring MAX Data, max_setup will not start following a reboot.

[root@wrx-madmax-2 ~]# systemctl status max_setup -l
 max_setup.service - SDM automated setup service
   Loaded: loaded (/usr/lib/systemd/system/max_setup.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2018-09-13 16:06:22 PDT; 5s ago
   Process: 14668 ExecStart=/usr/bin/max_configurator.py setup --up --log_to_console (code=exited, status=1/FAILURE)
   Main PID: 14668 (code=exited, status=1/FAILURE)

 

  • Attempting to start max_setup may lead to the following:

[root@wrx-madmax-2 ~]# systemctl start max_setup
Job for max_setup.service failed because the control process exited with error code. See "systemctl status max_setup.service" and "journalctl -xe" for details.

 

  • Running journalctl -xe shows:

11/21/2019 15:32:49 INFO Building all applications file system
11/21/2019 15:32:49 INFO Building file systems for application: 'oracle'
11/21/2019 15:32:49 INFO Building file system for m1fs: 'oracle'
11/21/2019 15:32:49 INFO Creating new file system (provision flow) for m1fs: 'oracle'
11/21/2019 15:32:49 INFO Executing mkfs (options: --force --acl --nodiscard --UUID=ca074564-3c85-4512-8e8b-32061af45166, T1 devices: /dev/pmem0p1, T2 devices: /dev/disk/by-path/fc---lun-0 /dev/disk/by-path/fc---lun-0 /dev/disk/by-path/fc---lun-0 /dev/disk/by-path/fc---lun-0)
11/21/2019 15:32:49 ERROR MKFS failed, command output: mkfs.m1fs version 18.1
Open error for '/dev/disk/by-path/fc---lun-0' - Device or resource busy
11/21/2019 15:32:49 INFO Rolling back all applications

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support