Sponsored Content
Full Discussion: Data Access Error
Top Forums UNIX for Advanced & Expert Users Data Access Error Post 10279 by joseph_shibu on Monday 12th of November 2001 02:38:30 AM
Old 11-12-2001
Data Access Error

Dear Reader,


My Sun Machine comes to halt with a message 'Data Access Error'. What / Where could be wrong..??

Thanks in Advance....
 

9 More Discussions You Might Find Interesting

1. Solaris

solaris 8 hangs and data access error on reboot

Hi using solaris 5.8 on UltraSPARC-IIi 360MHz. I know it is an old hardware but similiar hardware is running fine. here is the issue, System booted : works okay for some time then display was hung so system was rebooted ..it gave data access error. again rebooted and it came up... (6 Replies)
Discussion started by: upengan78
6 Replies

2. Solaris

Fast Data Access MMU Miss

Hi All , I am unable to reinstall the OS on my Ultra Sparc 10. After the 1st CD is loaded when it goes for reboot its goes to ok prompt an its unable to boot. What could be reason for this behavior? while loading the OS its seems fine but unable to boot!! Then i tried changing the... (2 Replies)
Discussion started by: kumarmani
2 Replies

3. UNIX for Advanced & Expert Users

Linux: Access time of mapped data

Before I forget, I'm running on a RedHat 5 box with the following uname -a output: Linux gnc141c 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Now on to my question. I'm using a tool that maps a Matlab .mat file using the Linux mmap functionality and then... (1 Reply)
Discussion started by: rusttree
1 Replies

4. Ubuntu

fast data access mmu miss

hello, before i have install solaris 9, is good. I would like to install Ubuntu 10.04 on a Sun Blade 150 blade. I create cdrom iso burning with a 10x was open I made a boot ok: boot cdrom I get the following error: fast data access mmu miss i do probe-ide all reset-all always ... (2 Replies)
Discussion started by: philo_71
2 Replies

5. Solaris

Unable to login Solaris 10 Sparc - Data Access Error

Hello everyone, This is the first time I am installing Solaris. I have SunBlade 1500 Wrkstn. I installed Solaris 10 Sparc. The installation went successfully but I don't get the login screen. I get the following error message: Boot device: disk:a File and agrs:- Data Access Error Ok ... (4 Replies)
Discussion started by: mfsaeed
4 Replies

6. AIX

access data from a new disk was assigned another rootvg

Hello, I try to access to data after connect a new disk (hdisk1) to a AIX 7.1 system This new disk was assigned to a rootvg from another AIX 6.1 system. It seem not assigned to any vg but if I tried to assigned hdisk1 to rootvg i get : Data seem to be always here ... ouf ;-)... (4 Replies)
Discussion started by: Voran
4 Replies

7. Programming

Help with ISAM data access

We are using an ISAM database, it is called RTISAM and has been in place for many years. We access the data using AIX code and using FORTRAN programs. I have heard that there are ways to access this data via Visual Studio and C# with the use of either a FORTRAN dll or an ODBC driver. I'm... (2 Replies)
Discussion started by: KathyB148
2 Replies

8. Linux

Permissions and access to data

Hi Operating system Red Hat Enterprise 5.8, Data access Mac/PC environment on various OS levels. Access via smb I am trying to set up a data shared area where a user group can read and write to its own directory, but can only write to another groups directory. Example: I have set up two... (1 Reply)
Discussion started by: treds
1 Replies

9. Solaris

Solaris 10 boot problem - ERROR: Last Trap: Fast Data Access MMU Miss

Hello, We have a T5140 server with Solaris 10 and its suddenly throwing "segmentation core" when I login into the server and not showing any output for commands like df, mount etc. so I had to reboot the server to fix this issue. Please note that there's no boot disk mirroring. But... (2 Replies)
Discussion started by: prvnrk
2 Replies
HALT(8) 						Linux System Administrator's Manual						   HALT(8)

NAME
halt, reboot, poweroff - stop the system. SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h] /sbin/reboot [-n] [-w] [-d] [-f] [-i] /sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h] DESCRIPTION
Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or poweroff the system. If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked instead (with the -h or -r flag). For more info see the shutdown(8) manpage. The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run. OPTIONS
-n Don't sync before reboot or halt. -w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file). -d Don't write the wtmp record. The -n flag implies -d. -f Force halt or reboot, don't call shutdown(8). -i Shut down all network interfaces just before halt or reboot. -h Put all harddrives on the system in standby mode just before halt or poweroff. -p When halting the system, do a poweroff. This is the default when halt is called as poweroff. DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'. NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when /var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to do a hard halt or reboot. The -h flag puts all harddisks in standby mode just before halt or poweroff. Right now this is only implemented for IDE drives. A side effect of putting the drive in standby mode is that the write cache on the disk is flushed. This is important for IDE drives, since the kernel doesn't flush the write-cache itself before poweroff. The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is called or the -h switch will do nothing. AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
shutdown(8), init(8) Nov 6, 2001 HALT(8)
All times are GMT -4. The time now is 10:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy