Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

maxdb error - disk not accessible

Hi all,

I restored my Maxdb and tried starting it.

I got an error that said "disk not accessible"

the error as in knldiag.err is (a part of it)

24976 ERR 11599 BTRACE -


> End of Stack Back Trace <----

2007-10-19 20:11:35 24976 ERR 7 Messages Begin of dump of registered messages

2007-10-19 20:11:35 24976 ERR 8 Messages End of the message list registry dump

2007-10-19 20:11:35 24976 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 146

2007-10-19 20:11:52 0 ERR 12006 DBCRASH Kernel exited without core and exit status 0x200

2007-10-19 20:11:52 0 ERR 12010 DBCRASH Kernel exited exit code 2

2007-10-19 20:11:53 ___ Stopping GMT 2007-10-19 18:11:53 7.6.00 Build 028-123-126-876

2007-10-19 20:13:07 --- Starting GMT 2007-10-19 18:13:07 7.6.00 Build 028-123-126-876

2007-10-19 21:21:15 25862 ERR 11000 d0_vatta Cannot open volume, No such file or directory

2007-10-19 21:21:15 25862 ERR 11000 d0_vatta Volume name '/sapdb/BW7/saplog/DISKL001'

2007-10-19 21:21:15 25058 ERR 11000 vattach dev0_vattach returned FALSE

2007-10-19 21:21:15 25058 ERR 20027 IOMan Attach error on log volume 1: Could not open volume

2007-10-19 21:21:15 25058 ERR 3 Admin Database state: OFFLINE

2007-10-19 21:21:15 25058 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2007-10-19 21:21:15 25058 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2007-10-19 21:21:18 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)

2007-10-19 21:21:19 ___ Stopping GMT 2007-10-19 19:21:19 7.6.00 Build 028-123-126-876

2007-10-19 21:23:10 --- Starting GMT 2007-10-19 19:23:10 7.6.00 Build 028-123-126-876

2007-10-19 21:23:24 25999 ERR 11000 d0_vatta Cannot open volume, No such file or directory

2007-10-19 21:23:24 25999 ERR 11000 d0_vatta Volume name '/sapdb/BW7/saplog/DISKL001'

2007-10-19 21:23:24 25978 ERR 11000 vattach dev0_vattach returned FALSE

2007-10-19 21:23:24 25978 ERR 20027 IOMan Attach error on log volume 1: Could not open volume

2007-10-19 21:23:24 25978 ERR 3 Admin Database state: OFFLINE

2007-10-19 21:23:24 25978 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2007-10-19 21:23:24 25978 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2007-10-19 21:23:25 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)

Please let me know any options as i need to complete this in another one days time.

Thanks

Regards

Hari

Former Member
replied

Hi Hari,

Ok, basically the same applies here as to your other post: if this is a production system then please open a Prio Very High Support message.

Although this forum is frequented by many experienced users and even MaxDB Developers it's not as tightly monitored as the Support messages are.

Concerning the problem: is the LOG Volume really available at that path (/sapdb/BW7/saplog/DISKL001) ? Is it perhabs locked by a different process (fuser ... ).

Have you tried to restart the server and then the db? Does the error still occur after that?

Best regards,

Lars

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question