Error with "File System" destination only in a Publication

Hello,
I am able to have individual reports run & refresh to a File System destination, but when I attempt to have the same reports, as part of a Publication, save to a File System destination, I receive this error in the log:
ERROR PublishingService:HandlerPool-32 BusinessObjects_PublicationAdminLog_Instance_15516 - Publication ID # 15516 - Distribution to destination CrystalEnterprise.DiskUnmanaged ... destination DLL disabled. [http://CrystalEnterprise.DiskUnmanaged ([1]/1])]: [ (FBE60013)
If I use Email instead of File System in this Publication, the Publication runs fine, no issues.
Thanks for any help.

Let's start with proper terminology
You're not sending report to unmanaged disk, you're scheduling it there.
When you use publication - you're publising it there.
2 different worflows, that use 2 different servers. Each server has to be configured for this functionality.
It is done in CMC in servers properties.
Admin guide will give you information on what each server in BO architecture is responcible for and what are the parameters that needs to be set for various workflows.

Similar Messages

OVM Manager 2.2.2: server pool error with file system type

I'm just getting started with OVM. I've installed OVM on one machine and the manager on another.
I created a server pool, which seemed to work OK but shows "Error" in the table under the "Server Pools" tab in the manager interface
When I edit it I see
Error: OVM-1011 OVM Manager communication with NNN.NNN.NN.NNN for operation Pre-check cluster root for Server Pool failed: <Exception: SR '/dev/sda3' not supported: type 'ocfs2.local' not in ['nfs', 'ocfs2.cluster']>
Can anyone explain this? Does this mean I can't use a local file system in OVM 2.2.2? I understood this was the case with OVM 3, which is why I went with 2.2.2.
Thanks.

Roger Ford wrote:
Error: OVM-1011 OVM Manager communication with NNN.NNN.NN.NNN for operation Pre-check cluster root for Server Pool failed: <Exception: SR '/dev/sda3' not supported: type 'ocfs2.local' not in ['nfs', 'ocfs2.cluster']>
Can anyone explain this? Does this mean I can't use a local file system in OVM 2.2.2? I understood this was the case with OVM 3, which is why I went with 2.2.2.You can't created a clustered pool with a local filesystem. You need to format the filesystem with ocfs2 in clustered mode.

1)Could not start up os x 2)Only could start bootcamp 3)Tried resetting nvram 4)Could not start even in bootcamp 5)Verify disk says -. Verifying volume "Macintosh HD" Error: Live file system repair is not supported 6)Installed maverick on USB d

1) Could not start up os x
2) Only could start bootcamp
3) Tried resetting nvram
4) Could not start even in bootcamp
5) Verify disk says …. Verifying volume “Macintosh HD”
Error: Live file system repair is not supported
6) Installed maverick on USB drive
7) Boot from USB drive. Tried verifying HD: Volume header needs minor repair. The volume Recovery HD was found corrupt and needs to be repaired. Verifying volume “Macintosh HD”: Error: live file system repair is not supported.
8) The terminal code says
9) Last login: Wed Feb 11 14:09:47 on console
10) xxxx-MacBook:~ xxxx$ diskutil list
11) /dev/disk0
12) #: TYPE NAME SIZE       IDENTIFIER
13) 0:      GUID_partition_scheme *160.0 GB   disk0
14) 1: EFI EFI 209.7 MB   disk0s1
15) 2:                  Apple_HFS Macintosh HD            80.1 GB disk0s2
16) 3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
17) 4:       Microsoft Basic Data 50.0 GB    disk0s4
18) /dev/disk1
19) #: TYPE NAME SIZE       IDENTIFIER
20) 0:      GUID_partition_scheme *15.6 GB    disk1
21) 1: EFI EFI 209.7 MB   disk1s1
22) 2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
23) 3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
24) Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
25) No CoreStorage logical volume groups found
26) Saeedehs-MacBook:~ saeedehmirbagheri$ sudo gpt -vv -r show /dev/disk0
27) Password:
28) gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
29) gpt show: /dev/disk0: PMBR at sector 0
30) gpt show: /dev/disk0: Pri GPT at sector 1
31) gpt show: /dev/disk0: Sec GPT at sector 312581807
32) start       size index contents
33) 0          1 PMBR
34) 1          1 Pri GPT header
35) 2         32 Pri GPT table
36) 34          6
37) 40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
38) 409640 156394528      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
39) 156804168    1269544      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
40) 158073712   56853648
41) 214927360   97652736      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
42) 312580096       1679
43) 312581775         32         Sec GPT table
44) 312581807          1         Sec GPT header
45) xxxx-MacBook:~ xxxx$ sudo fdisk /dev/disk0
46) Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
47) Signature: 0xAA55
48) Starting       Ending
49) #: id cyl hd sec - cyl hd sec [     start - size]
50) ------------------------------------------------------------------------

Thank you -
I booted from external USB. The diskutil list output is from OS x booting from the USB, which shows the following:
Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *160.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            80.1 GB    disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data                         50.0 GB    disk0s4
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.6 GB    disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
No CoreStorage logical volume groups found
I am not able to use target disk mode because I don't have firewire/thunderbolt ports.

Boot up - Error Message: "File System not clean"

<blockquote>Locked by Moderator as a duplicate/re-post.
Please continue the discussion in this thread: [tiki-view_forum_thread.php?locale=en-US&comments_parentId=667528&forumId=1]
Thanks - c</blockquote>
== Issue
==
I have another kind of problem with Firefox
== Description
==
At start up displays error message: File System not Clean"
== start up computer
==
== Troubleshooting information
==
WebOfTrust, AdBlock Plus 1.2, Ubuntu Firefox Modifications 0.7, Firefox Universal Uploader (fireuploader) 0.4.1, Foxytunes 4.0.6
== Firefox version
==
3.0.19
== Operating system
==
Linux
== User Agent
==
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.19) Gecko/2010040116 Ubuntu/9.04 (jaunty) Firefox/3.0.19 GTB7.0
== Plugins installed
==
*-The default plugin handles plugin data for mimetypes and extensions that are not specified and facilitates downloading of new plugins.
*The demo print plugin for unix.
*Shockwave Flash 10.0 r45
*DivX Web Player version 1.4.0.233
*The Totem 2.26.1 plugin handles video and audio streams.

http://ubuntuforums.org/

How to work with file system in linux within a JSF app?

I use this line in my backing bean to log some events:
FileHandler fhxml = new FileHandler("../webapps/MyWebApp/Log/MyWebAppLog.xml", append);
fhxml.setFormatter(new XMLFormatter());That works fine in windows but when I deploy it in my Tomcat 6 in linux It doesn't work. How can I work with file system in linux?

You should never use relative paths to access the filesystem. The path would be relative to the current working directory which is not per se the same in all environments. To convert a relative web path to an absolute file system path, you need ServletContext#getRealPath(). Use this absolute file system path in the java.io stuff. In a JSF application on top of Servlet API you can get the underlying ServletContext by ExternalContext#getContext().
Alternatively, if the file is located in one of the default paths of the classpath or if its path is added to the classpath, you can also just use ExternalContext#getResource() or even #getResourceAsStream() using just the file name.

Sign on problems within Elements 10; plus cannot backup writing files error with file catalog.pse10db. No indication what the problem is. How do I get adobe help with these problems?

Sign on problems within Elements 10; plus cannot backup, writing files error with file catalog.pse10db. No indication what the problem is. How do I get adobe help with these problems?

Sign on problems within Elements 10; plus cannot backup, writing files error with file catalog.pse10db. No indication what the problem is. How do I get adobe help with these problems?

Communication error with external system ( VERTEX )

Hi Folks,
While creation the Credit memo request or Sales order /invoice system giving the error message " COmmunication error with external system ( VERTEX ) " and stopping to proceed further and even not able to post the accounting document.
Please help me out here.
Answers will be appreciated and rewared.
Regards,
Ram.

Hi,
check this below thread
Communication error with the external tax system (VERTEX_MS0018)
OR
Remove V from the Extrernal System at the location IMG->financial Accounting->Financial Accounting Global Settings->Tax on Sales/Purchases->Basic Settings->External Tax Calculation->Activate External Tax Calculation
Reg,
JJ
Edited by: Jagsap on Mar 5, 2010 1:15 PM

Moving files to another directory got an error message [File System Task] Error: An error occurred with the following error message: "Could not find a part of the path.".

Hi all,
I am having a list of files in a folder named datafiles and I am processing them one by one when I finish each one I want to move the file into a folder archive.
I am having a variable named filename and archivefilename and two fileconnections one is originalfiles and archivefiles
archivefilename=replace( @[User::filename],"datafiles","archive")
orginalfiles connection is an expression =@user:filename
archivefies connection is an expression=@user:archivefilename
the filename comes from reading the folder that contains those files
public void Main()
            string[] filenames;
            filenames = Directory.GetFiles(@"C:\luminis\datafiles\");
            Array.Sort(filenames);
            Dts.Variables["filelist"].Value = filenames;
            Dts.TaskResult = (int)ScriptResults.Success;
The folder c:\luminis\archive\ exists
why I am getting this error
My filesystem task : destinationpathvariable =false
destinationconnection:archivefile
overwrite=true
operation=movefile
issourcepathvariable=false
sourceconnection=original file
why am i getting this error[File System Task] Error: An error occurred with the following error message: "Could not find a part of the path.".
sohairzaki

there may be 2 problem...
1> specify a target directory only, not with the file name.
OR
2> Try using the unc,path format \\computername\sharename\
let us know your observation...
Let us TRY this | Mail me
My Blog :: http://quest4gen.blogspot.com/

SQL Server not Starting Up - Could not open error log file system error = 5(Access is denied.)

Hi guys,
I am working on issue with SQL Server 2008 R2 .. we rebooted the server and after that all SQL services is not coming up. below is the error from eventlog...
SQL Server running under NetworkService account and has full control on this files..
from Config Manager ....
The request failed or the service did not respond in a timely fashion....
From Event log..
initerrlog: Could not open error log file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 5(Access is denied.).
Any idea or workaround..?
Thanks..
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Finally I found solution and was able to bring back online the SQL Services...
I had a very similar issue with the following error (event log):
Description:
The SQL Server (MSSQLSERVER) service terminated with service-specific error 17058 (0x42A2).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17058
Date: 19/05/2012
Time: 10:20:14
User: N/A
Computer: NSQLXX
Description:
initerrlog: Could not open error log file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
Operating system error = 5(error not found).
In this case the ERRORLOG file had been marked as read only. This was following a scheduled automated boot. -This
was culprit
MSSQL wouldn't not start until this file had been changed.
http://www.experts-exchange.com/Database/MS-SQL-Server/Q_23951723.html
Thanks everyone for your kind replies and time...
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

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)

JFS root file system will only mount read-only

Hi, everybody!
I have been running this filesystem for months with no issues. The only thing I can think of that I changed recently was that I ran pacman -Syu.
When I boot there is no indication that there are errors with the file system. It simply mounts as read-only.
I have tried running
mount -n -o remount,rw /
, and it says "mount: / not mounted already, or bad option".
When I run just
mount -n -o rw /
it appears to work, in that there is no error message, but the file system is still read-only.
I have been able to mount it read-write successfully with the install disc, but only after I ran a fsck on it, also from the install disc. However, each time I have run fsck, it has reported no errors. I also tried forcing the check, with the same result.
Even after mounting it successfully with the install disc, it still will not mount read-write from my hard-disk install.
My DE (gnome) locked up a few days ago and I had to do a hard reboot, but it still functioned fine after that, so it doesn't seem related.
I would like to not have to reinstall, but I can if I need to. I would also like to find out how this happened, so that it does not happen again.
Any suggestions would be greatly appreciated.
Thanks for your help,
Jefferson

I got it working. I was running the fsck on the wrong partition. I am still curious as to why it happened, though.
@Marcel-: I don't think there was anything strange in my logs, but I'm not sure. I will look them over some more. Is there a particular one I should be looking in?
@seiichiro0185: Yes, the passno-flag is set to 1 for my rootfs.
Thank you both very much for helping me!

Intermedia text search error for file system

I would like to search a text from a file. store in the file system. I have done the following procedures but when i create i get error.
BEGIN
CTX_DDL.CREATE_PREFERENCE('search_docroot_pref','FILE_DATASTORE');
CTX_DDL.SET_ATTRIBUTE('search_docroot_pref','path','c:/temp/abc');
END;
Now when i create INDEX with following syntex
CREATE INDEX mysearch_ind ON mytable(mycolumn) INDEXTYPE IS
CTXSYS.context parameters('datastore search_docroot_pref');
I get the following errors.
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: interMedia Text error:
DRG-50704: Net8 listener is not running or cannot start external procedures
ORA-28575: unable to open RPC connection to external procedure agent
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
ORA-06512: at line 1
Can any body tell me where i am wrong.
Thanks,

Hi
I was aslo facing same problem.My net8 connection and listner is aslo ok. but getting same errors.
Raju

Problem withe file system repository

I configured a windows file system to the portal.
And the folder is showing well in the KM content.(along with its content) which is fine.
Now when i am trying to edit the file (by clicking on the 'Edit Locally' ) it is not responding and a message like operation failed is appearing.
NOTE: The Windows folder has given the full permissions.
The folder in theKM was also given full permissions to user.
can any one help me.
Thanks in advance,
Mr.Chowday

Hi
check this
Internet Explorer settings:
Regardless of whether you are using ActiveX or the Applet, you have to make ActiveX settings in the browser (Internet Explorer) in order to use the Edit Locally function.
Call up the security settings for the browser: Choose Tools ® Internet Options ® Security ® Custom Level in the menu bar. Make the following settings
Download signed ActiveX controls = Enable
Download unsigned ActiveX controls = Disable
Initialize and script ActiveX controls not marked as safe = Disable
Run ActiveX controls and plug-ins = Enable
Script ActiveX controls marked safe for scripting = Enable
and also If you are using the repository in read-only mode, the creating, changing, renaming, and deleting of files and directories is not supported.
http://help.sap.com/saphelp_nw04/helpdata/en/a6/181b09bcc7fe4389c8c17d2ad849cc/content.htm
Regards
Krishna.

Problem with File System Repository after release change

Hello,
we have been changing the Portal release from EP 6.0 to SAP NetWeaver Portal 7.0 SP17. The OS of the host is Windows 2003 Server.
If I open the component monitor to watch the repostitories, the state of the file system repositories are red and a error message occurred:
Startup Error: getting mapped math - Logon failure: unknown user name or bad password
I checked the logon credentials....they are ok. Also I checked the access from the Portalhost to the Windows File System....it´s ok too.
In our previous portal release the FSR were ok!!
Is there a difference between the file system repository configuration in portal 6.0 and portal 7.0?
Thanks and regards
Tom

Hello Hussain,
I have checked the username and the password of the user who have full access on the Windows file system, but the same error occurred. In the Network Path we have configured a domain user for the file system access. Here is the configuration of the network path:
Name: Test
Description: Test
Networkpath:
Host\share
Password: ****
Re-enter Password: ****
User: domain\user
Here the configuration of the repository:
Name: Test
Description: Test
Prefix: /Test
Lookup Mode: caseless
Root Directory:
Host\share
Repository Services: Nothing
Property Search Manager: com.sapportals.wcm.repository.manager.generic.search.SimpleManagerSearchManager
Security Manager: AclSecurityManager
ACL Manager Cache: ca_cm_rep_acl
Windows Landscape System: Microsoft_Windows_KM
Read only: unchecked
Could it be that I need a user mapping for the access of the windows file system?
Perhaps the configuration of the Windows Landscape System is wrong?
regards
Tom

DNFS with ASM over dNFS with file system - advantages and disadvantages.

Hello Experts,
We are creating a 2-node RAC. There will be 3-4 DBs whose instances will be across these nodes.
For storage we have 2 options - dNFS with ASM and dNFS without ASM.
The advantages of ASM are well known --
1. Easier administration for DBA, as using this 'layer', we know the storage very well.
2. automatic re-balancing and dynamic reconfiguration.
3. Stripping and mirroring (though we are not using this option in our env, external redundancy is provided at storage level).
4. Less (or no) dependency on storage admin for DB file related tasks.
5. Oracle also recommends to use ASM rather than file system storage.
Advantages of DNFS(Direct Network File System) ---
1. Oracle bypasses the OS layer, directly connects to storage.
2. Better performance as user's data need not to be loaded in OS's kernel.
3. It load balances across multiple network interfaces in a similar fashion to how ASM operates in SAN environments.
Now if we combine these 2 options , how will be that configuration in terms of administration/manageability/performance/downtime in future in case of migration.
I have collected some points.
In favor of 'NOT' HAVING ASM--
1. ASM is an extra layer on top of storage so if using dNFS ,this layer should be removed as there are no performance benefits.
2. store the data in file system rather than ASM.
3. Stripping will be provided at storage level (not very much sure about this).
4. External redundancy is being used at storage level so its better to remove ASM.
points for 'HAVING' ASM with dNFS --
1. If we remove ASM then DBA has no or very less control over storage. He can't even see how much is the free space left as physical level.
2. Stripping option is there to gain performance benefits
3. Multiplexing has benefits over mirroring when it comes to recovery.
(e.g, suppose a database is created with only 1 controlfile as external mirroring is in place at storage level , and another database is created with 2 copies (multiplexed within Oracle level), and an rm command was issued to remove that file then definitely there will be a time difference between restoring the file back.)
4. Now familiar and comfortable with ASM.
I have checked MOS also but could not come to any conclusion, Oracle says --
"Please also note that ASM is not required for using Direct NFS and NAS. ASM can be used if customers feel that ASM functionality is a value-add in their environment. " ------How to configure ASM on top of dNFS disks in 11gR2 (Doc ID 1570073.1)
Kindly advise which one I should go with. I would love to go with ASM but If this turned out to be a wrong design in future, I want to make sure it is corrected in the first place itself.
Regards,
Hemant

I agree, having ASM on NFS is going to give little benefit whilst adding complexity. NAS will carrying out mirroring and stripping through hardware where as ASM using software.
I would recommend DNFS only if NFS performance isn't acceptable as DNFS introduce an additional layer with potential bugs! When I first used DNFS in 11gR1, I came across lots of bugs and worked with Oracle Support to have them all resolved. I recommend having read of this metalink note:
Required Diagnostic for Direct NFS Issues and Recommended Patches for 11.1.0.7 Version (Doc ID 840059.1)
Most of the fixes have been rolled into 11gR2 and I'm not sure what the state of play is on 12c.
Hope this helps
ZedDBA

Error with "File System" destination only in a Publication

Similar Messages

Maybe you are looking for