After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md

Hi
I have a SUNW,Netra-440 with two SE 3300 SCSI each with two controllers. The server was working fine but after a boot, it can not see the metadevices stored in the 3300.
I have tried restarting the SE3300 and a boot -r from ok prompt but I still can see those disks or partitions.
Metaset Import
metaset: log01: setname "appvol": no such set
mount all SVM filesystems for group appvol
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d101
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d102
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d103
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d104
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d105
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d106
metaset: log01: setname "dbvol": no such set
mount all SVM filesystems for group dbvol
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d107
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d108
i can see the devices in /dev/md/appvol but i can't mount them.
Any ideas what this could be? using metaset shows nothing, metastat -s dbvol hangs.
Am I missing some patch or am I missing something here? is the SE3300 damaged? or is it a problem with SDS (solstice). I have solaris 9.
The system was working fine until we had to boot and power off to perform power tests in the rack.
thanks
Ryck
this is the output of prtdiag
root@log01 >prtdiag
System Configuration: Sun Microsystems sun4u Netra 440
System clock frequency: 177 MHZ
Memory size: 8GB
==================================== CPUs ====================================
E$ CPU CPU Temperature
CPU Freq Size Implementation Mask Die Amb. Status Location
0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
================================= IO Devices =================================
Bus Freq Slot + Name +
Type MHz Status Path Model
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1,1
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1c,600000/network@2
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1,1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@0
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@2
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@3
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,3f8
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,2e8
pci 33 MB isa/rmc-comm-rmc_comm (seria+
okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
pci 33 PCI0 SUNW,XVR-100 (display) SUNW,375-3290
okay /pci@1e,600000/SUNW,XVR-100
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@a
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@b
pci 33 MB pci10b9,5229 (ide)
okay /pci@1e,600000/ide@d
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1f,700000/network@1
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2,1
============================ Memory Configuration ============================
Segment Table:
Base Address Size Interleave Factor Contains
0x0 2GB 4 BankIDs 0,1,2,3
0x1000000000 2GB 4 BankIDs 16,17,18,19
0x2000000000 2GB 4 BankIDs 32,33,34,35
0x3000000000 2GB 4 BankIDs 48,49,50,51
Bank Table:
Physical Location
ID ControllerID GroupID Size Interleave Way
0 0 0 512MB 0,1,2,3
1 0 1 512MB
2 0 1 512MB
3 0 0 512MB
16 1 0 512MB 0,1,2,3
17 1 1 512MB
18 1 1 512MB
19 1 0 512MB
32 2 0 512MB 0,1,2,3
33 2 1 512MB
34 2 1 512MB
35 2 0 512MB
48 3 0 512MB 0,1,2,3
49 3 1 512MB
50 3 1 512MB
51 3 0 512MB
Memory Module Groups:
ControllerID GroupID Labels Status
0 0 C0/P0/B0/D0
0 0 C0/P0/B0/D1
0 1 C0/P0/B1/D0
0 1 C0/P0/B1/D1
1 0 C1/P0/B0/D0
1 0 C1/P0/B0/D1
1 1 C1/P0/B1/D0
1 1 C1/P0/B1/D1
2 0 C2/P0/B0/D0
2 0 C2/P0/B0/D1
2 1 C2/P0/B1/D0
2 1 C2/P0/B1/D1
3 0 C3/P0/B0/D0
3 0 C3/P0/B0/D1
3 1 C3/P0/B1/D0
3 1 C3/P0/B1/D1
root@log01 >

Hi,
thanks for your answer.
Yes format displays the physical devices, but metadb -i only shows the internal disks of the netra 440, not the ones in the 3320. metadb -s dbvol -i doesnt show anything.
metaset which is supposed to show me the metadevices, says the program is not registered.
cat /etc/lvm/md.tab has the configuration but since the scsi can be seen, the devices aren't mounted.
Any suggestions?
Cheers
Oscar
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootdisk
/pci@1f,700000/scsi@2/sd@0,0
1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootmirr
/pci@1f,700000/scsi@2/sd@1,0
2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare1
/pci@1f,700000/scsi@2/sd@2,0
3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare2
/pci@1f,700000/scsi@2/sd@3,0
4. c2t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> appvol
/pci@1c,600000/scsi@1/sd@8,0
5. c2t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol01
/pci@1c,600000/scsi@1/sd@9,0
6. c2t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol02
/pci@1c,600000/scsi@1/sd@a,0
7. c2t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol03
/pci@1c,600000/scsi@1/sd@b,0
8. c2t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol04
/pci@1c,600000/scsi@1/sd@c,0
9. c2t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol05
/pci@1c,600000/scsi@1/sd@d,0
10. c3t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol06
/pci@1c,600000/scsi@1,1/sd@8,0
11. c3t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1
/pci@1c,600000/scsi@1,1/sd@9,0
12. c3t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2
/pci@1c,600000/scsi@1,1/sd@a,0
13. c3t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3
/pci@1c,600000/scsi@1,1/sd@b,0
14. c3t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotAPP
/pci@1c,600000/scsi@1,1/sd@c,0
15. c3t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDB
/pci@1c,600000/scsi@1,1/sd@d,0
16. c4t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> APPVOLm
/pci@1d,700000/scsi@1/sd@8,0
17. c4t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@9,0
18. c4t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@a,0
19. c4t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@b,0
20. c4t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@c,0
21. c4t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@d,0
22. c5t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> d6Mirr
/pci@1d,700000/scsi@1,1/sd@8,0
23. c5t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1M
/pci@1d,700000/scsi@1,1/sd@9,0
24. c5t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2M
/pci@1d,700000/scsi@1,1/sd@a,0
25. c5t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3M
/pci@1d,700000/scsi@1,1/sd@b,0
26. c5t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1,1/sd@c,0
27. c5t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDBm
/pci@1d,700000/scsi@1,1/sd@d,0
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >metadb -s appvol -i
metadb: log01: setname "appvol": no such set
root@log01 >metaset
metaset: log01: metad client create: RPC: Program not registered
root@log01 >cat /etc/lvm/md.tab
# Copyright 2002 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)md.tab 2.4 02/01/29 SMI"
# md.tab
# metainit utility input file.
dbvol/d57 1 1 c2t12d0s0
dbvol/d58 1 1 c4t12d0s0
dbvol/d4 -m dbvol/d57 dbvol/d58 1
dbvol/d55 1 1 c2t11d0s0
dbvol/d56 1 1 c4t11d0s0
dbvol/d3 -m dbvol/d55 dbvol/d56 1
dbvol/d61 1 1 c3t8d0s0
dbvol/d62 1 1 c5t8d0s0
dbvol/d6 -m dbvol/d61 dbvol/d62 1
dbvol/d59 1 1 c2t13d0s0
dbvol/d60 1 1 c4t13d0s0
dbvol/d5 -m dbvol/d59 dbvol/d60 1
dbvol/d53 1 1 c2t10d0s0
dbvol/d54 1 1 c4t10d0s0
dbvol/d2 -m dbvol/d53 dbvol/d54 1
###dbvol/d51 1 1 c2t9d0s0
dbvol/d52 1 1 c4t9d0s0
#dbvol/d1 -m dbvol/d51 dbvol/d52 1
dbvol/d1 -m dbvol/d52 1
# SOFT Partitions
dbvol/d129 -p dbvol/d5 -o 19933376 -b 526336
dbvol/d128 -p dbvol/d5 -o 19407008 -b 526336
dbvol/d127 -p dbvol/d5 -o 18880640 -b 526336
dbvol/d126 -p dbvol/d5 -o 10489952 -b 8390656
dbvol/d125 -p dbvol/d5 -o 2099264 -b 8390656
dbvol/d123 -p dbvol/d4 -o 4724864 -b 133120
dbvol/d122 -p dbvol/d4 -o 4460640 -b 264192
dbvol/d121 -p dbvol/d4 -o 4196416 -b 264192
dbvol/d120 -p dbvol/d4 -o 32 -b 4196352
dbvol/d119 -p dbvol/d3 -o 30972032 -b 526336
dbvol/d118 -p dbvol/d3 -o 10489952 -b 20482048
dbvol/d117 -p dbvol/d3 -o 4196416 -b 6293504
dbvol/d116 -p dbvol/d3 -o 32 -b 4196352
dbvol/d115 -p dbvol/d2 -o 8925408 -b 526336
dbvol/d114 -p dbvol/d2 -o 8399040 -b 526336
dbvol/d113 -p dbvol/d2 -o 7872672 -b 526336
dbvol/d112 -p dbvol/d2 -o 7346304 -b 526336
dbvol/d111 -p dbvol/d2 -o 5247072 -b 2099200
dbvol/d110 -p dbvol/d2 -o 1050688 -b 4196352
dbvol/d109 -p dbvol/d2 -o 32 -b 1050624
dbvol/d108 -p dbvol/d1 -o 33554496 -b 1572864
dbvol/d107 -p dbvol/d1 -o 32 -b 33554432
dbvol/d124 -p dbvol/d5 -o 32 -b 2099200
dbvol/d138 -p dbvol/d4 -o 38416608 -b 133120
dbvol/d137 -p dbvol/d3 -o 31498400 -b 264192
dbvol/d136 -p dbvol/d4 -o 21637312 -b 16779264
dbvol/d135 -p dbvol/d4 -o 4858016 -b 16779264
dbvol/d134 -p dbvol/d6 -o 69212288 -b 23070720
dbvol/d133 -p dbvol/d6 -o 46141536 -b 23070720
dbvol/d132 -p dbvol/d6 -o 23070784 -b 23070720
dbvol/d131 -p dbvol/d6 -o 32 -b 23070720
dbvol/d130 -p dbvol/d5 -o 20459744 -b 526336
root@log01 >metadb -s dbvol -i
metadb: log01: setname "dbvol": no such set
root@log01 >\

Similar Messages

Error on boot: "Can not find script file "C:\ProgramData\Lenovo-20841.vbs".

Recently I'm getting an error dialog box on my T530 when I boot it into my OEM installation of Windows 8. The window title bar is "Windows Script Host", and the error message is:
Error on boot: "Can not find script file "C:\ProgramData\Lenovo-20841.vbs".
I pulled up an old backup, and I do have that file, along with a number of other ones that are missing from that directory. I'm attaching a screenshot of the files that are missing. Not sure why they would have been deleted (I know I didn't do it manually). Should I just restore the file? What about the other ones?
Thanks very much.

I am getting a different VBS script error than the one listed above.
Does anyone know how I can get this file? or recreate it?
I get a similar message saying that it can't find the file c:\programdata\Lenovo-11472.vbs
Also, my wireless just randomly resets - sometimes very few minutes - after I've been using the system for a while. It's brand new and I can't figure out what's going on. Could this be the issue?
When I restart, it stays stable for a while and then starts acting up again.
Thanks for your help!

How can I transfer my files/system in VAIO laptop (w/ S400 Firewire port) to my New Macbook Pro?

How can I transfer my files/system in VAIO laptop (w/ S400 Firewire port) to my New Macbook Pro?
Do I need to buy an adapter? How do I setup the software to make these two system connected?

r95941081 wrote:
Thanks for your answering. But the issue is that I'll often transfer a large amount files from PCs to the Macbook, and I'm explring the way to use firewire since there is indeed an i-S400 port in the VAIO laptop, and it's much faster.
USB 2 is faster than Firewire 400 and USB 3 is faster than Firewire 800
If it was another Mac you were transferring from then you could use Firewire Target Disk Mode which makes the boot drive of the old Mac appear on the desktop of the new Mac to rapidly copy files, but you have a Windows PC with no FWTDM capability.
So to connect the two machines requires a network be setup over Ethernet and mucking around with the complexities of all that and it still takes awhile to finish. One can't setup a network with a PC over USB or Firewire, only Firewire with another Mac.
You get a external USB drive, USB 3,2,1 is fine and just drag and drop copy, the machine does all the work and you go do something else until it's finished, then repeat the same with the Mac.
Fast simple and effective, let it copy overnight if you have too.
I routinely clone my entire hard drive via USB 2 and it only takes a hour and a half for 350GB.
By the time you figure out how to network a Mac and a PC over Ethernet and getting it work to transfer files, you could be done already via USB.

Mac OS X 10.6.8 desktop goes black 10 secs after booting, can remain apparently asleep for 15 mins. I can't prompt it to wake, until recently it would wake when peripheral were added (earphones). What is wrong, and how can this be fixed?

Mac OS X 10.6.8 statup problem: desktop goes black 10 secs after booting, can remain apparently asleep for 15 mins. I can't prompt it to wake, until recently it would wake when peripheral were added (earphones). What is wrong, and how can this be fixed?

You need to fresh install 10.6, programs fresh form original sources and return only vetted files (no TM migrations) from a regular storage drive
But this when erasing the drive use the Security Option: Zero All Data before installing 10.6
What has happened your data got corrupted and it's corrupted on the TM drive too.
So the Zero will map off bad sectors on your drive, the 10.6 install will be fresh, the programs will be fresh and only files will be returned, you'll find out in short order which ones they are.
Reducing bad sectors effect on hard drives
How to erase and install Snow Leopard 10.6
Once you are back up, then consider making a option key bootable clone.
Most commonly used backup methods explained

Can´t mount OCFS2 file system after Public IP modify

Guys,
We have an environment with 2 nodes with RAC database version 10.2.0.1. We need to modify the Public IP and VIP of the Oracle CRS. So we did the following steps:
- Alter the VIP
srvctl modify nodeapps -n node1 -A 192.168.1.101/255.255.255.0/eth0
srvctl modify nodeapps -n node2 -A 192.168.1.102/255.255.255.0/eth0
- Alter the Public IP
oifcfg delif -global eth0
oifcfg setif -global eth0/192.168.1.0:public
- Alter the IP´s of the network interfaces
- Update the /etc/hosts
When we start the Oracle CRS, the components starts OK. But when we reboot the second node, the OCFS2 file system didn´t mount. The following errors occurs:
SCSI device sde: 4194304 512-byte hdwr sectors (2147 MB)
sde: cache data unavailable
sde: assuming drive cache: write through
sde: sde1
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
lp0: using parport0 (polling).
lp0: console ready
mtrr: your processor doesn't support write-combining
(2746,0):o2net_start_connect:1389 ERROR: bind failed with -99 at address 192.168.2.132
(2746,0):o2net_start_connect:1420 connect attempt to node rac1 (num 0) at 192.168.2.131:7777 failed with errno -99
(2746,0):o2net_connect_expired:1444 ERROR: no connection established with node 0 after 10 seconds, giving up and returning errors.
(5457,0):dlm_request_join:786 ERROR: status = -107
(5457,0):dlm_try_to_join_domain:934 ERROR: status = -107
(5457,0):dlm_join_domain:1186 ERROR: status = -107
(5457,0):dlm_register_domain:1379 ERROR: status = -107
(5457,0):ocfs2_dlm_init:2007 ERROR: status = -107
(5457,0):ocfs2_mount_volume:1062 ERROR: status = -107
ocfs2: Unmounting device (8,17) on (node 1)
When we did the command to force the mount occurs the errors:
# mount -a
mount.ocfs2: Transport endpoint is not connected while mounting /dev/sdb1 on /ocfs2. Check 'dmesg' for more information on this error.
What occurs is that the OCFS2 is trying to connect with the older Public IP. My question is, how do i change the public IP in the ocfs2 ?
regards,
Eduardo P Niel
OCP Oracle

Hi, is correct you maybe check the /etc/cluster.conf file, maybe the configuration is wrong, you can also check the /etc/hosts file for verify the correct definition host names.
Luck
Have a good day.
Regards,

Every boot requires fsck. Makes file system read-only

Suddenly when I booted my Arch I got a message saying that there was a corruption in my /home and /var directories. The same message suggested to pass fsck as solution. The booting process hanged there without entering to the emergency login. I took a live cd an executed a fsck in all my ext4 file system and “repaired” the problem.
When I could log into the system if, for example, I want to write a file o do any operation (sudo for example) I get the message:
sudo: unable to open /var/db/sudo/lola/0: Read-only file system
If I reboot the PC again, the cycle begins again, this is: errors, asking for fsck, then, read-only FS.
Some info that you may find useful:
fstab
/dev/sda3 / ext4 defaults 0 1
/dev/sda5 /var ext4 defaults 0 1
/dev/sda6 swap swap defaults 0 0
/dev/sda7 /home ext4 defaults,user_xattr 0 1
df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 7.2G 6.6G 52% /
dev 1.9G 0 1.9G 0% /dev
run 1.9G 740K 1.9G 1% /run
/dev/sda3 15G 7.2G 6.6G 52% /
tmpfs 1.9G 536K 1.9G 1% /dev/shm
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs 1.9G 80K 1.9G 1% /tmp
/dev/sda7 80G 39G 37G 52% /home
/dev/sda5 6.8G 3.7G 2.8G 58% /var
/dev/sda2 358G 334G 25G 94% /media/windows
systemctl
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active running Arbitrary Executable File Formats File System Au
sys-devices-pci...000:00:1b.0-sound-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
sys-devices-pci...0-0000:02:00.0-net-eth0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.
sys-devices-pci...-0000:03:00.0-net-wlan0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.
sys-devices-pci...-1:0:0:0-block-sda-sda1.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda2.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda3.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda4.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda5.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda6.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda7.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...1:0:0-1:0:0:0-block-sda.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...5:0:0-5:0:0:0-block-sr0.device loaded active plugged TSSTcorp_CDDVDW_TS-L633C
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
tail -100 /var/log/errors.log
Jan 23 14:43:52 localhost kernel: [ 283.449542] ata2.00: error: { UNC }
Jan 23 14:43:52 localhost kernel: [ 283.451224] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:43:52 localhost kernel: [ 283.451228] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:43:56 localhost kernel: [ 287.394421] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Jan 23 14:43:56 localhost kernel: [ 287.394426] ata2.00: irq_stat 0x40000001
Jan 23 14:43:56 localhost kernel: [ 287.394430] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394435] ata2.00: cmd 60/08:00:00:84:9a/00:00:1e:00:00/40 tag 0 ncq 4096 in
Jan 23 14:43:56 localhost kernel: [ 287.394435] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 14:43:56 localhost kernel: [ 287.394438] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394440] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.394442] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394447] ata2.00: cmd 60/00:08:1f:53:4d/01:00:2d:00:00/40 tag 1 ncq 131072 in
Jan 23 14:43:56 localhost kernel: [ 287.394447] res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [ 287.394449] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394451] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.394453] ata2.00: failed command: WRITE FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394458] ata2.00: cmd 61/08:10:7f:6e:b7/00:00:30:00:00/40 tag 2 ncq 4096 out
Jan 23 14:43:56 localhost kernel: [ 287.394458] res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [ 287.394460] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394462] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.394464] ata2.00: failed command: WRITE FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394468] ata2.00: cmd 61/90:18:37:42:31/00:00:35:00:00/40 tag 3 ncq 73728 out
Jan 23 14:43:56 localhost kernel: [ 287.394468] res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [ 287.394471] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394472] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.396122] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:43:56 localhost kernel: [ 287.396125] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:43:56 localhost kernel: [ 287.396179] end_request: I/O error, dev sda, sector 760042271
Jan 23 14:43:56 localhost kernel: [ 287.396232] end_request: I/O error, dev sda, sector 817327743
Jan 23 14:43:56 localhost kernel: [ 287.396235] Buffer I/O error on device sda7, logical block 1133175
Jan 23 14:43:56 localhost kernel: [ 287.396282] end_request: I/O error, dev sda, sector 892420663
Jan 23 14:44:01 localhost kernel: [ 291.317005] ata2.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
Jan 23 14:44:01 localhost kernel: [ 291.317010] ata2.00: irq_stat 0x40000008
Jan 23 14:44:01 localhost kernel: [ 291.317014] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:44:01 localhost kernel: [ 291.317019] ata2.00: cmd 60/08:08:00:84:9a/00:00:1e:00:00/40 tag 1 ncq 4096 in
Jan 23 14:44:01 localhost kernel: [ 291.317019] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 14:44:01 localhost kernel: [ 291.317022] ata2.00: status: { DRDY ERR }
Jan 23 14:44:01 localhost kernel: [ 291.317024] ata2.00: error: { UNC }
Jan 23 14:44:01 localhost kernel: [ 291.318643] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:44:01 localhost kernel: [ 291.318647] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:44:01 localhost kernel: [ 291.546162] Aborting journal on device sda7-8.
Jan 23 14:54:20 localhost [ 7.837917] systemd[1]: Socket service syslog.service not loaded, refusing.
Jan 23 14:54:20 localhost [ 7.838515] systemd[1]: Failed to listen on Syslog Socket.
Jan 23 14:54:21 localhost kernel: [ 10.930157] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum backlight value
Jan 23 14:54:34 localhost dhcpcd[564]: dhcpcd not running
Jan 23 14:54:35 localhost dhcpcd[649]: dhcpcd not running
Jan 23 14:54:35 localhost dhcpcd[662]: dhcpcd not running
Jan 23 14:58:04 localhost su: pam_unix(su:auth): conversation failed
Jan 23 17:00:38 localhost systemd[1]: Failed to start Netcfg multi-profile daemon.
Jan 23 17:00:39 localhost [ 7.790297] systemd[1]: Socket service syslog.service not loaded, refusing.
Jan 23 17:00:39 localhost [ 7.790891] systemd[1]: Failed to listen on Syslog Socket.
Jan 23 17:00:39 localhost kernel: [ 11.363432] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum backlight value
Jan 23 17:00:55 localhost dhcpcd[612]: dhcpcd not running
Jan 23 17:00:55 localhost dhcpcd[618]: dhcpcd not running
Jan 23 17:00:55 localhost dhcpcd[626]: dhcpcd not running
Jan 23 17:01:23 localhost su: pam_unix(su:auth): conversation failed
Jan 23 17:04:55 localhost kernel: [ 274.346016] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Jan 23 17:04:55 localhost kernel: [ 274.346022] ata2.00: irq_stat 0x40000008
Jan 23 17:04:55 localhost kernel: [ 274.346025] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:04:55 localhost kernel: [ 274.346031] ata2.00: cmd 60/70:08:e8:83:9a/00:00:1e:00:00/40 tag 1 ncq 57344 in
Jan 23 17:04:55 localhost kernel: [ 274.346031] res 41/40:70:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:04:55 localhost kernel: [ 274.346034] ata2.00: status: { DRDY ERR }
Jan 23 17:04:55 localhost kernel: [ 274.346035] ata2.00: error: { UNC }
Jan 23 17:04:55 localhost kernel: [ 274.348151] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:04:55 localhost kernel: [ 274.348154] Buffer I/O error on device sda2, logical block 63796096
Jan 23 17:04:55 localhost kernel: [ 274.348159] Buffer I/O error on device sda2, logical block 63796097
Jan 23 17:04:55 localhost kernel: [ 274.348162] Buffer I/O error on device sda2, logical block 63796098
Jan 23 17:04:55 localhost kernel: [ 274.348164] Buffer I/O error on device sda2, logical block 63796099
Jan 23 17:04:55 localhost kernel: [ 274.348166] Buffer I/O error on device sda2, logical block 63796100
Jan 23 17:04:55 localhost kernel: [ 274.348168] Buffer I/O error on device sda2, logical block 63796101
Jan 23 17:04:55 localhost kernel: [ 274.348171] Buffer I/O error on device sda2, logical block 63796102
Jan 23 17:04:55 localhost kernel: [ 274.348173] Buffer I/O error on device sda2, logical block 63796103
Jan 23 17:04:55 localhost kernel: [ 274.348176] Buffer I/O error on device sda2, logical block 63796104
Jan 23 17:04:55 localhost kernel: [ 274.348178] Buffer I/O error on device sda2, logical block 63796105
Jan 23 17:04:59 localhost kernel: [ 278.257533] ata2.00: exception Emask 0x0 SAct 0x84 SErr 0x0 action 0x0
Jan 23 17:04:59 localhost kernel: [ 278.257539] ata2.00: irq_stat 0x40000008
Jan 23 17:04:59 localhost kernel: [ 278.257543] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:04:59 localhost kernel: [ 278.257549] ata2.00: cmd 60/08:38:00:84:9a/00:00:1e:00:00/40 tag 7 ncq 4096 in
Jan 23 17:04:59 localhost kernel: [ 278.257549] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:04:59 localhost kernel: [ 278.257551] ata2.00: status: { DRDY ERR }
Jan 23 17:04:59 localhost kernel: [ 278.257553] ata2.00: error: { UNC }
Jan 23 17:04:59 localhost kernel: [ 278.259233] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:03 localhost kernel: [ 282.157929] ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
Jan 23 17:05:03 localhost kernel: [ 282.157934] ata2.00: irq_stat 0x40000008
Jan 23 17:05:03 localhost kernel: [ 282.157938] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:05:03 localhost kernel: [ 282.157943] ata2.00: cmd 60/08:10:00:84:9a/00:00:1e:00:00/40 tag 2 ncq 4096 in
Jan 23 17:05:03 localhost kernel: [ 282.157943] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:05:03 localhost kernel: [ 282.157946] ata2.00: status: { DRDY ERR }
Jan 23 17:05:03 localhost kernel: [ 282.157947] ata2.00: error: { UNC }
Jan 23 17:05:03 localhost kernel: [ 282.159582] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:03 localhost kernel: [ 282.159588] Buffer I/O error on device sda2, logical block 63796096
Jan 23 17:05:07 localhost kernel: [ 286.069482] ata2.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Jan 23 17:05:07 localhost kernel: [ 286.069487] ata2.00: irq_stat 0x40000008
Jan 23 17:05:07 localhost kernel: [ 286.069491] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:05:07 localhost kernel: [ 286.069496] ata2.00: cmd 60/08:30:00:84:9a/00:00:1e:00:00/40 tag 6 ncq 4096 in
Jan 23 17:05:07 localhost kernel: [ 286.069496] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:05:07 localhost kernel: [ 286.069499] ata2.00: status: { DRDY ERR }
Jan 23 17:05:07 localhost kernel: [ 286.069501] ata2.00: error: { UNC }
Jan 23 17:05:07 localhost kernel: [ 286.071955] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:07 localhost kernel: [ 286.071959] Buffer I/O error on device sda2, logical block 63796096
Waiting for your help.
Thank you.

oh god, if my HD dies I will kill myself.
I did the SMART, short and long (following the ArchWiki) and got (will post the long as soon it ends):
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 7967 -
With more details:
smartctl -a /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.6.9-1-ARCH] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..55GSX
Device Model: TOSHIBA MK5055GSX
Serial Number: 897JC07RT
LU WWN Device Id: 5 000039 1f3c01f05
Firmware Version: FG001M
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Wed Jan 23 13:46:24 2013 PYST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 183) minutes.
SCT capabilities: (0x0039) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1320
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1807
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 7
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 7967
10 Spin_Retry_Count 0x0033 136 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1789
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 97
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 33
193 Load_Cycle_Count 0x0032 082 082 000 Old_age Always - 189405
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 39 (Min/Max 9/50)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 9
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 87
222 Loaded_Hours 0x0032 085 085 000 Old_age Always - 6001
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 320
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 634 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 634 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 00 84 9a 40 08 03:31:25.735 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 03:31:25.714 FLUSH CACHE EXT
61 18 08 07 82 b1 40 08 03:31:25.714 WRITE FPDMA QUEUED
61 08 00 0f 7d 31 40 08 03:31:25.714 WRITE FPDMA QUEUED
ea 00 00 00 00 00 a0 00 03:31:25.682 FLUSH CACHE EXT
Error 633 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 00 84 9a 40 08 03:31:21.832 READ FPDMA QUEUED
61 18 00 27 81 b1 40 08 03:31:21.451 WRITE FPDMA QUEUED
61 18 00 27 77 b1 40 08 03:31:20.425 WRITE FPDMA QUEUED
61 18 00 2f 8c b1 40 08 03:31:19.451 WRITE FPDMA QUEUED
61 18 00 ef 81 b1 40 08 03:31:18.445 WRITE FPDMA QUEUED
Error 632 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 0a 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 07 7f 09 40 08 03:16:43.581 READ FPDMA QUEUED
60 08 08 00 84 9a 40 08 03:16:43.559 READ FPDMA QUEUED
60 00 00 a7 5b 09 40 08 03:16:43.552 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:16:43.551 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 03:16:43.551 READ NATIVE MAX ADDRESS EXT
Error 631 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 0a 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 a7 5b 09 40 08 03:16:39.713 READ FPDMA QUEUED
60 08 00 87 b5 25 40 08 03:16:39.705 READ FPDMA QUEUED
60 00 00 8f 60 05 40 08 03:16:39.693 READ FPDMA QUEUED
60 08 00 e7 d4 54 40 08 03:16:39.692 READ FPDMA QUEUED
60 08 08 00 84 9a 40 08 03:16:39.678 READ FPDMA QUEUED
Error 630 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 12 04 84 9a 6e Error: WP at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
61 08 08 0e 4c b6 40 08 03:16:35.710 WRITE FPDMA QUEUED
61 08 08 0e 4c b6 40 08 03:16:35.710 WRITE FPDMA QUEUED
61 08 08 0e 4c b6 40 08 03:16:35.709 WRITE FPDMA QUEUED
61 98 18 8f 41 31 40 08 03:16:35.709 WRITE FPDMA QUEUED
61 08 08 0e 4c b6 40 08 03:16:35.708 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 7967 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Is there an equivalent to Solaris iostat -En in Linux? Havent found any. Remember that I can't install anything: read-only FS
Last edited by gromlok (2013-01-23 16:47:35)

Problems mounting global file system

Hello all.
I have setup a Cluster using two Ultra10 machines called medusa & ultra10 (not very original I know) using Sun Cluster 3.1 with a Cluster patch bundle installed.
When one of the Ultra10 machines boots it complains about being unable to mount the global file system and for some reason tries to mount the node@1 file system when it is actually node 2.
on booting I receive the message on the macine ultra10
Type control-d to proceed with normal startup,
(or give root password for system maintenance): resuming boot
If I use control D to continue then the following happens:
ultra10:
ultra10:/ $ cat /etc/cluster/nodeid
2
ultra10:/ $ grep global /etc/vfstab
/dev/md/dsk/d32 /dev/md/rdsk/d32 /global/.devices/node@2 ufs 2 no global
ultra10:/ $ df -k | grep global
/dev/md/dsk/d32 493527 4803 439372 2% /global/.devices/node@1
medusa:
medusa:/ $ cat /etc/cluster/nodeid
1
medusa:/ $ grep global /etc/vfstab
/dev/md/dsk/d32 /dev/md/rdsk/d32 /global/.devices/node@1 ufs 2 no global
medusa:/ $ df -k | grep global
/dev/md/dsk/d32 493527 4803 439372 2% /global/.devices/node@1
Does anyone have any idea why the machine called ultra10 of node ID 2 is trying to mount the node ID 1 global file system when the correct entry is within the /etc/vfstab file?
Many thanks for any assistance.

Hmm, so for arguments sake, if I tried to mount both /dev/md/dsk/d50 devices to the same point in the filesystem for both nodes, it would mount OK?
I assumed the problem was because the device being used has the same name, and was confusing the Solaris OS when both nodes tried to mount it. Maybe some examples will help...
My cluster consists of two nodes, Helene and Dione. There is fibre-attached storage used for quorum, and website content. The output from scdidadm -L is:
1 helene:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1
2 helene:/dev/rdsk/c0t1d0 /dev/did/rdsk/d2
3 helene:/dev/rdsk/c4t50002AC0001202D9d0 /dev/did/rdsk/d3
3 dione:/dev/rdsk/c4t50002AC0001202D9d0 /dev/did/rdsk/d3
4 dione:/dev/rdsk/c0t0d0 /dev/did/rdsk/d4
5 dione:/dev/rdsk/c0t1d0 /dev/did/rdsk/d5
This allows me to have identical entries in both host's /etc/vfstab files. There are also shared devices under /dev/global that can be accessed by both nodes. But the RAID devices are not referenced by anything from these directories (i.e. there's no /dev/global/md/dsk/50). I just thought it would make sense to have the option of global meta devices, but maybe that's just me!
Thanks again Tim! :D
Pete

After cvfsck can't find some files? What chances of recover them?

Hi all,
so the problem is that in my xsan one of the volumes have restarted 2-3 times in a day. So i did cvfsck -wv. During the chek it reported File System Status as Clean and at the end that F+ile system have been modified+. After that i can not find some of the files. Is this normal behavior of cvfsck? Is there any chances to recover lost files?
Thanks in advance

In the root of the filesystem there normally is a folder "lost+found", in which files with strange names are found. These are the files cvfsck has collected in the recovering of the filesystemnames. It is sometimes not possible to recover the original file name and location. So this is the only way for cvfsck to give them back.
If you think the content of these files is allright, you can rename and relocate them.
Regards
Donald

How do I restore Firefox base after reinstalling Windows , but I have file system safe(all program folders)?

How do I restore Firefox base after I reinstalled Windows , but I have my system and program old folders safe. ( exact Firefox Application and Program Files folders etc)?
== This happened ==
Every time Firefox opened
== I reinstalled Windows

What I mean is I have saved passwords and some website adresses in my Firefox that was on deleted windows ( but I saved the file system so it works from there using another computer) but all I need is passes and saved links . just the complete copy of my old setups and such . is that possible?

RPC Problem while mounting NFS File System

Hi,
We have two servers. ca1 and bench
Currently we moved bench across the firewall in DMZ. Now ca1 and bench are on opposite sides of the firewall. We have made sure that port 111, 2049 and 4045 along with the default telnet and ftp ports are programmed in firewall to provide access.
We can telnet and ftp from bench to ca1.
When we try to NFS mount a ca1 filesystem at bench using following command :
bench:>mount ca1:/u07/export /ca1/u07/export
we get following error :
nfs mount: ca1: : RPC: Timed out
This is happening since we moved the bench server across the firewall.
What could be the problem?
Cheers,
MS

Hi,
Thanks for the help.
It seems like that the nfs service is already started on the server.
Here are the results :
# ps -ef | grep nfsd
root 366 1 0 Jul 12 ? 0:00 /usr/lib/nfs/nfsd -a 16
root 25791 25789 0 16:16:45 pts/5 0:00 grep nfsd
# ps -ef | grep mountd
root 218 1 0 Jul 12 ? 0:05 /usr/lib/autofs/automountd
root 364 1 0 Jul 12 ? 0:00 /usr/lib/nfs/mountd
root 25793 25789 0 16:16:53 pts/5 0:00 grep mountd
# ps -ef | grep statd
root 201 1 0 Jul 12 ? 0:00 /usr/lib/nfs/statd
root 25797 25789 0 16:16:59 pts/5 0:00 grep statd
# ps -ef | grep lockd
root 203 1 0 Jul 12 ? 0:00 /usr/lib/nfs/lockd
root 25799 25789 0 16:17:07 pts/5 0:00 grep lockd
Please let me know what else can be done. This problem started after we moved these machines on different sides of the firewall.
Cheers,
MS

How can I search a file system and only return newer files?

Sorry the title didn't give me much room to work with. I'm writing a tool which needs to track all the files in an OS. What I'd like to do is make it so my program will only return files that have been modified/created since the last search to add to my program. I was wondering if there's an efficient way to do this other than checking each file's timestamps? Also is there a way to tell from a parent directory whether any files in its directory have been modified/created? I'm looking for ways for Windows and Linux.

I have no problem checking timestamps but it can be rather time consuming doing this. I don't know if this is quicker but I'd like to sort by modified date and check the time stamps for newer timestamps than the last time I ran. This way if I hit a time stamp equal to my last run I know to stop there. I checked Windows and the folder does tell you whether any file was created/modified in it's directory. However, if a file is created in one of its children's directories it won't update the time stamp. It's unfortunate because I could've avoided the search at a higher level directory otherwise. Without this I'll have to walk the whole structure one way or another. I can still improve the speed but I can't make it as efficient as I'd like.

Please HELP!!!!!!!! Mount a File System in Sun One Studio

Hi,
I've been trying to get my Java Documentation (on my hard drive...v.1.4.2) to work with Sun One Studio 5 update 1. I have been completely unsuccessful at mounting the documentation so that I could get reference on specific classes. Can somebody PLEASE tell me how I can mount the Javadoc correctly so that it will work and integrate with Sun One Studio 5?!?!?
Thank you very much in advance!!

The JDK documentation is automatically picked up for code completion. For explicit JavaDoc visibility in the Studio, select Tools | JavaDoc Manager and mount the api directory of the JDK documentation root.

2007 iMac Gray Screen After Boot - Can't do anything

Hello,
I have a 2007 iMac. When I turn it on, I hear the boot chime and see the light gray screen, and then it goes to a darker gray screen. It won't get past the dark gray screen, and the screen doesn't show any icons or anything. It's just a solid dark gray. I've tried resetting the NVRAM/PRAM, starting in safe mode, etc., and nothing seems to be making a difference.
Does anyone have any idea what might be causing this, and how I can fix it?
Thanks in advanced!

I've tried all of those things. I don't believe the peripherals are causing the problem. I forgot to mention that I have it connected to a TV via VGA adapter. The iMac's monitor doesn't work.

Cannot mount NTFS file system on USB drive

I plug in external disk via USB drive. I attempt to mount drive. I've downloaded several NTFS rpms.
I believe the issue is that I do not yet have the correct NTFS rpm. Any help?
[root@kclinux1 media]# mount -t ntfs /dev/sdc1 /media/usbdrive/
mount: unknown filesystem type 'ntfs'
[root@kclinux1 media]# cat /proc/filesystems |grep ntf
[root@kclinux1 media]# uname -a
Linux kclinux1 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:41:04 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@kclinux1 media]# rpm -qa|grep ntfs
ntfsprogs-1.9.4-1.2.el4.rf
kernel-module-ntfs-2.6.18-128.1.1.el5xen-2.1.27-0.rr.10.11
kernel-module-ntfs-2.6.18-128.el5xen-2.1.27-0.rr.10.11
[root@kclinux1 media]#

try
step 1)
# Red Hat Enterprise Linux 5 / i386:
rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
# Red Hat Enterprise Linux 5 / x86_64:
rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS//rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm
# Red Hat Enterprise Linux 4 / i386:
rpm -Uhv http://apt.sw.be/redhat/el4/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el4.rf.i386.rpm
# Red Hat Enterprise Linux 4 / x86_64:
rpm -Uhv http://apt.sw.be/redhat/el4/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.el4.rf.x86_64.rpmstep 2)
apt-get updatestep 3)
> yum install ntfs-3g
> ntfs-3g /dev/sdxy /<mount directory>
rgrds

SAP/ORACLE File Systems Disappeared in Local Zone

I created some 20-30 files systems as meta devices for a SAP/Oracle installation on my 6320 SAN for a local zone.
I did a newfs on all of them and then mounted them in the global zone with their appropriate mount points.
I then did a zonecfg with the following input.
zonepath: /export/zones/zsap21
autoboot: true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /opt/sfw
inherit-pkg-dir:
dir: /usr
fs:
dir: /oracle
special: /oracle_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /oracle/stage/920_64
special: /oracle/stage/920_64_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /temp
special: /temp_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /usr/local
special: /usr/local_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /usr/sap
special: /usr/sap_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /usr/sap/install
special: /usr/sap/install_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /usr/sap/trans
special: /usr/sap/trans_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /export/home/zsap21
special: /export/home_zsap21
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1
special: /oracle/FS1
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/920_64
special: /oracle/FS1/920_64
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/mirrlogA
special: /oracle/FS1/mirrlogA
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/oraarch
special: /oracle/FS1/oraarch
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/origlogA
special: /oracle/FS1/origlogA
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/origlogB
special: /oracle/FS1/origlogB
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/saparch
special: /oracle/FS1/saparch
raw not specified
type: lofs
options: []
fs:
dir: /oracle/FS1/sapdata1
special: /oracle/FS1/sapdata1
raw not specified
type: lofs
options: []
***********more available but I truncated it here**********************
I successfully installed and configured the zone.
I then logged into the local zone and installed a new version of Oracle and a working SAP instance. I know that it worked because I was able to log into it.
Upon rebooting the server and the local zone I have lost access to all of my file systems in the Oracle/SAP zone.
It's almost as if the global zone has not mounted its file systems over the local zones mount points. In the local zone I can see no files in the directories where I would expect Oracle or SAP files.
I either mis-configured the zonecfg or missed a step somewhere.
I suspect that my file system contents are still around somewhere waiting to be hooked up with a zone's mount point.
In the local zone a df -k shows all of the file systems (like the local zone knows about what file systems belong) but they all have the same size and free space (probably from the root zone).
Any thoughts appreciated.
Atis

Do you have amount point within the zone path for these oradb mounts?
You have to add a directory entry for /oradb in the zone's root directory, i.e. ``zone_path''/root/oradb

After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md

Similar Messages

Maybe you are looking for