08-06-2009
Fsck error
Hello
I own a SPARC Ultra 10 workstation (standalone) and when issuing the fsck command I get the following output on fs C0t0d0s7:
Phase 1 (checks blocks and sizes):
dada warning: /pci@lf;0/pci@1, 1/ide@3/dad@0,0(dad1): ATA Transport failed:reason, `incomplete'>
Uncorrectable data error:Block C18E70
dada warning: /pci@lf;0/pci@1, 1/ide@3/dad@0,0(dad1):
disk not responding to selection.
Is the file system corrupt. If so, what can I do to rectify it?
Many tanks
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Once in a while, I would think it advisable to run fsck -y to check the disk.
Should I sign in as su or sudo?
What is the difference and which is preferred?
Thank you in Advance! (4 Replies)
Discussion started by: rpatrick
4 Replies
2. Solaris
OS: Solaris 5.8
Everytime I run fsck -y I get: FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? yes
Do I need to run fsck with the backup superblock option or is there
some other option I should use. I have tried the format->analyze->read
option but that does not report any corrupt blocks.... (5 Replies)
Discussion started by: run_time_error
5 Replies
3. UNIX for Dummies Questions & Answers
I want to use fsck to check and repair my linux system. When I use this command, what do I need to pay attention to or what should I do to make job running successfully. Thanks for your inputs for a newbie. (3 Replies)
Discussion started by: duke0001
3 Replies
4. Solaris
Hello
I am getting this in dmesg:
/mount1: unexpected free inode 1262865, run fsck(1M) -o f
What are the options I should use with fsck?
thanks (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
5. UNIX for Dummies Questions & Answers
i want to know what does it mean by doing a consistentcy check fsck on a disk and why journaling filesystems dont need to do it
and what is meant by disk is in a consistent state when writing because entries are recorded in a journal and then to the metadata and then removed from journal (1 Reply)
Discussion started by: farhan_t49
1 Replies
6. Red Hat
Hi,
When I boot the linux kernel 2.6 , I was kicked out and request to run fsck manually.
After running fsck -y /dev/vg00/lvol3 and /dev/vg00/lvol4 and reboot,
I still get the same error and request me to run fsck .
I attach the console output in here .
Please advice to fix it .... (0 Replies)
Discussion started by: chuikingman
0 Replies
7. Solaris
Hello
I want to ask that how to mount and run fsck in SVM disk.In my scenario if i have to disks c0t0d0 and c0t1d0 these two disks are in Mirroring (raid1) if i want to run fsck on the disks than below are the right steps?
ok boot cdrom -s
mount /dev/dsk/c0t0d0s0 /a
cd /a
fsck... (3 Replies)
Discussion started by: jhonnybravo
3 Replies
8. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
9. Solaris
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
10. Solaris
Hello all,
I recently powered on my Netra AX1105 server only to be greeted with the following error message. I am not sure what to do here,
I cant fun fsck on OK prompt.. did ok>boot -r and now it keeps booting from net, then I run ok>boot disk then outputs the following message... and keeps... (3 Replies)
Discussion started by: br1an
3 Replies
sysdef(1M) System Administration Commands sysdef(1M)
NAME
sysdef - output system definition
SYNOPSIS
/usr/sbin/sysdef [-i] [-n namelist]
/usr/sbin/sysdef [-h] [-d] [-i] [-D]
DESCRIPTION
The sysdef utility outputs the current system definition in tabular form. It lists all hardware devices, as well as pseudo devices, system
devices, loadable modules, and the values of selected kernel tunable parameters.
It generates the output by analyzing the named bootable operating system file (namelist) and extracting the configuration information from
it.
The default system namelist is /dev/kmem.
OPTIONS
-i Prints the configuration information from /dev/kmem. This is the default and only needs to be specified if the configura-
tion information from both /dev/kmem and the system file specified with the "-n namelist" option is needed.
-nnamelist Specifies a namelist other than the default (/dev/kmem). The namelist specified must be a valid bootable operating system.
-h Prints the identifier of the current host in hexadecimal. This numeric value is unique across all Sun hosts.
-d The output includes the configuration of system peripherals formatted as a device tree.
-D For each system peripheral in the device tree, display the name of the device driver used to manage the peripheral.
EXAMPLES
Example 1: Sample output format
The following example displays the format of the sysdef -d output:
example% sysdef -d
Node 'SUNW,Ultra-5_10', unit #-1
Node 'packages', unit #-1 (no driver)
Node 'terminal-emulator', unit #-1 (no driver)
Node 'deblocker', unit #-1 (no driver)
Node 'obp-tftp', unit #-1 (no driver)
Node 'disk-label', unit #-1 (no driver)
Node 'SUNW,builtin-drivers', unit #-1 (no driver)
Node 'sun-keyboard', unit #-1 (no driver)
Node 'ufs-file-system', unit #-1 (no driver)
Node 'chosen', unit #-1 (no driver)
Node 'openprom', unit #-1 (no driver)
Node 'client-services', unit #-1 (no driver)
Node 'options', unit #0
Node 'aliases', unit #-1 (no driver)
Node 'memory', unit #-1 (no driver)
Node 'virtual-memory', unit #-1 (no driver)
Node 'pci', unit #0
Node 'pci', unit #0
Node 'ebus', unit #0
Node 'auxio', unit #-1 (no driver)
Node 'power', unit #0
Node 'SUNW,pll', unit #-1 (no driver)
Node 'se', unit #0 (no driver)
Node 'su', unit #0
Node 'su', unit #1
Node 'ecpp', unit #-1 (no driver)
Node 'fdthree', unit #0
Node 'eeprom', unit #-1 (no driver)
Node 'flashprom', unit #-1 (no driver)
Node 'SUNW,CS4231', unit #0 (no driver)
Node 'network', unit #0
Node 'SUNW,m64B', unit #0
Node 'ide', unit #0
Node 'disk', unit #-1 (no driver)
Node 'cdrom', unit #-1 (no driver)
Node 'sd', unit #1
Node 'dad', unit #1
Node 'pci', unit #-1 (no driver)
Node 'SUNW,UltraSPARC-IIi', unit #-1 (no driver)
Node 'pseudo', unit #0
[output truncated]
FILES
/dev/kmem default operating system image
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
hostid(1), prtconf(1M), nlist(3ELF), attributes(5)
SunOS 5.10 4 Oct 2004 sysdef(1M)