"mount point /proc/bus/usb does not exist" -deux

Hi everyone!
I've installed arch 6.0 on a laptop running on the 2.4 SCSI kernel.
Indeed, /proc/bus/usb does not exist. I'm not sure why...
I'm not sure how to get the full directory either.
I've viewed this thread and this thread and followed the advice to change the usb line in my fstab to usbfs /proc/bus/usb usbfs defaults 0 0. I'm not sure what I was expecting, but the problem didn't go away and my /proc/bus/usb did not magically appear afterwards.

ok, I did the update. The usb directory is still not there.
Since I don't have permission to make the directory myself (even as root), I guess I'll call it quits here.
I'm using the arch 7.0 cd now. The problem has gone away.

Similar Messages

Mount point /proc/bus/usb does not exist

Does anybody know why this mount point would not be there? There is indeed a directory at that location...

hi,
kleptophobiac wrote:Does anybody know why this mount point would not be there? There is indeed a directory at that location...
sarah31 wrote:perhaps it is the syntax in your fstab?
Nope, it's a miracle, concerning the scsi kernel only, AFAIK. Some devs have
rebuilt with some module variations but no clue so far where it does come
from.
It goes like that:
usbcore loads usbfs (when it shouldn't), at a time when proc is not mounted.
usbfs tries to create the dir and throws that error. Later on boot process
hotplug corrects that. So it's a kind of annoyance, but it does feel
uncomfortable as long as no one where it does come from :-/
-neri

Initscripts 2012.08.3-1 /proc/bus/usb does not exist

After upgrading initscripts
[2012-08-28 15:26] upgraded initscripts (2012.08.2-1 -> 2012.08.3-1)
boot.log shows the following error message
mount: mount point /proc/bus/usb does not exist
I didn't find any recent post about this issue. I recall that something changed maybe with /proc and /sys some weeks/months ago, but I get this warning message since the initscripts update.
Any idea? Or is it a sign that I should familiarize myself with systemd?
Update:
I missed this thread, same issue, sorry: https://bbs.archlinux.org/viewtopic.php?id=147916
Someone may want to delete this one. Thanks.
Last edited by siriusb (2012-08-30 12:42:38)

After upgrading initscripts
[2012-08-28 15:26] upgraded initscripts (2012.08.2-1 -> 2012.08.3-1)
boot.log shows the following error message
mount: mount point /proc/bus/usb does not exist
I didn't find any recent post about this issue. I recall that something changed maybe with /proc and /sys some weeks/months ago, but I get this warning message since the initscripts update.
Any idea? Or is it a sign that I should familiarize myself with systemd?
Update:
I missed this thread, same issue, sorry: https://bbs.archlinux.org/viewtopic.php?id=147916
Someone may want to delete this one. Thanks.
Last edited by siriusb (2012-08-30 12:42:38)

/proc/acpi/button does not exist.

/proc/acpi/button does not exist. Any ideas?
or, anyone knows which module is the owner of /proc/acpi/button?
Thanks!

I am having the same problem, even with a stock kernel. There is no power button
device and therefore acpi_listen does not detect putton press events. I am on a
Thinkpad T420s, which used to work until a recent reinstall. Here are the
outputs that were originally requested (most of them look quite similar to
enicham's):
% lsmod | grep evdev
evdev 11784 27
% ls /dev/input
by-id event10 event14 event2 event6 mice
by-path event11 event15 event3 event7 mouse0
event0 event12 event16 event4 event8 mouse1
event1 event13 event17 event5 event9 mouse2
% cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech Unifying Device. Wireless PID:101b"
P: Phys=usb-0000:00:1a.0-1.2:1
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004/input/input2
U: Uniq=
H: Handlers=mouse0 event1
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0
B: REL=143
B: MSC=10
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech Unifying Device. Wireless PID:4002"
P: Phys=usb-0000:00:1a.0-1.2:2
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0005/input/input3
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=12001f
B: KEY=837fff072ff32d bf54444600000000 1 30f948b17c007 ffff73fad941dfff febeffdfffefffff fffffffffffffffe
B: REL=40
B: ABS=100000000
B: MSC=10
B: LED=1f
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input5
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=3
B: KEY=4000 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input7
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0019 Vendor=17aa Product=5054 Version=4101
N: Name="ThinkPad Extra Buttons"
P: Phys=thinkpad_acpi/input0
S: Sysfs=/devices/platform/thinkpad_acpi/input/input8
U: Uniq=
H: Handlers=kbd rfkill event7
B: PROP=0
B: EV=33
B: KEY=18040000 0 10000000000000 0 1501b00102004 c000000001104000 e000000000000 0
B: MSC=10
B: SW=8
I: Bus=0003 Vendor=04f2 Product=b221 Version=0752
N: Name="Integrated Camera"
P: Phys=usb-0000:00:1a.0-1.6/button
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/input/input9
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input10
U: Uniq=
H: Handlers=kbd event9
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0001 Vendor=14f1 Product=506e Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input12
U: Uniq=
H: Handlers=kbd event10
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input13
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
U: Uniq=
H: Handlers=event14
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
U: Uniq=
H: Handlers=event15
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input11
U: Uniq=
H: Handlers=mouse1 event16
B: PROP=9
B: EV=b
B: KEY=6420 30000 0 0 0 0
B: ABS=260800011000003
I: Bus=0011 Vendor=0002 Product=000a Version=0000
N: Name="TPPS/2 IBM TrackPoint"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input18
U: Uniq=
H: Handlers=mouse2 event17
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3
% pacman -Qi linux
Name : linux
Version : 3.14.5-1
Description : The Linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2
Groups : base
Provides : kernel26=3.14.5
Depends On : coreutils linux-firmware kmod
mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels
of your country
Required By : nvidia
Optional For : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 71950.00 KiB
Packager : Tobias Powalowski <[email protected]>
Build Date : Sun 01 Jun 2014 01:40:01 AM EDT
Install Date : Sat 07 Jun 2014 02:21:14 PM EDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
% journalctl | grep dev/input
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event6 (Power Button)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event3 (Video Bus)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event4 (Lid Switch)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event5 (Sleep Button)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)

Root device mounted successfully, but /sbin/init does not exist ???

I'm having the issue where when I boot after doing a fresh install, it gives me:
ERROR: Root device mounted successfully, but /sbin/init does not exist
Bailing out, you are on your own. Good luck
sh: can't access tty; job control turned off
[rootfs /]#
My fstab:
# /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1 LABEL=homerroot
UUID=877deab9-624d-4e1d-90a1-ccc1d6ebc0c6 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=homerboot
UUID=77835da5-8a38-44c1-bf27-bb657df4484b /boot ext4 rw,relatime,data=ordered 0 2
# /dev/sda3 LABEL=homeretc
UUID=8a1b5bd8-b147-41e0-87df-70a4a9e12df2 /etc ext4 rw,relatime,data=ordered 0 2
# /dev/sda4 LABEL=homervar
UUID=8eb2e7b1-cdf1-46ce-9dc1-439d002bfae4 /var ext4 rw,relatime,data=ordered 0 2
# /dev/sda5 LABEL=homerusr
UUID=bce162b4-d27f-450c-a0e6-4d3ebc6242dc /usr ext4 rw,relatime,data=ordered 0 2
# /dev/sda6 LABEL=home
UUID=62de76ab-b6d4-4e3d-a423-c287b81813a9 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda7 LABEL=public
UUID=d98a9c8e-2301-4e66-8c7f-26167633a4b0 /public ext4 rw,relatime,data=ordered 0 2
This looks fine to me, but when /dev/sda1 is mounted at /new_root, none of the other devices are mounted....
I don't know if this is what's causing the problem since /etc, and /usr are on separate partitions from root, but
this would be the first time I get a problem dividing things this way (on ubuntu, mint, fedora, et cetera).
So I tried:
https://bbs.archlinux.org/viewtopic.php … 3#p1283343
I get "* is owned by filesystem 2013.05-2" for all three dirs from step three.
None of the other steps have any effect....
I also tried:
https://bbs.archlinux.org/viewtopic.php?id=172943
My /dev/sda1 mounts to new_root, so I don't think I'm having his problem.
And:
https://bbs.archlinux.org/viewtopic.php?id=166423
I reinstalled systemd-sysvcompat, and I'm sure that's not my problem.
Interestingly enough, /usr/lib/systemd/systemd is an elf file on my target hard disk.
Is this an outdated issue or something? Or should /usr/lib/systemd/systemd be a text file?
Thanks in advance for your help guys!

WorMzy wrote:Oh, and /usr/lib/systemd/systemd is supposed to be an ELF binary. Not sure why you think it should be a text file.
I saw another thread saying that adding an entry there would help. I think it was "init=<something>".
WonderWoofy wrote:A separate /etc is not supported whatsoever. There needs to be initial access to a few things there. I'm sure it could be made to work with some initramfs hackery. But it is neither supported or wise to do so IMO.
I'll not do the separate partitions then. Thanks. I'll check back if it works/doesn't-works.

SCCM 2012 R2 - Reporting Services Point installation - "The Datasource does not exist"

Hi all,
Quick bit of background, we have SCCM 2012 R2 installed on a Windows 2012 R2 server. We have the SQL back end off box, configured on a SQL 2012 R2 server running on a Windows Server 2012 R2 cluster. Then there is yet another server which runs the reporting
services. I've just tried installing the Reporting Services Point on the srs server but it doesn't appear to have worked that well. Here's the info i've got back:
A] Site Status > Reporting services point:
SMS_SITE_SYSTEM_STATUS_SUMMERIZER
Site System Status Summarizer detected that the availability of the "Reporting services point" role on server "\\NA-SQLR01.in.tna.local" has changed to Failed.
B] The last message from the SMS_SRS_REPORTING_POINT Component Status is "Site Component Manager successfully installed this component on this site system"
C] Here's the first chunk of info which appears in the srsrp.log file:
SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 4204 (0x106C).
This is a SRS Reporting Point Role as SRSRP registry key exists.
Waiting for changes for 0 minutes
Timed Out...
Set configuration
Check state
Check server health.
Successfully created srsserver SMS_
Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
Reporting Services is running
The DataSource does not exist.
[sqlserver.local\SQL1] [SCCM_XXX] [ConfigMgr_XXX] [sqlreportserver.LOCAL]
[SQL2012] [1] [] [xxx\SCCM2012Server]
Confirmed version [11.0.5058.0] for the Sql Srs Instance.
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
Extract resource language packs if exists
Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
Looking for 'English (United Kingdom)' resources
Looking for 'English' resources
Found resources for 'English'
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
Item, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
Folder, String Parent, Property[] Properties)
(!) SRS root folder was reported missing
STATMSG: ID=7405 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=sqlreportserver.LOCAL SITE=P01 PID=2120 TID=4204 GMTDATE=Wed Apr 08 08:56:05.349 2015 ISTR0="ConfigMgr_XXX" ISTR1="sqlreportserver.LOCAL"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
Registry change
Waiting for changes for 1 minutes
After this point i simply get the following info messages looping endlessly:
Set configuration
Check state
Check server health.
Successfully created srsserver
Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
Reporting Services is running
The DataSource does not exist.
[sqlreportserverlocal\SQL1] [SCCM_XXX] [ConfigMgr_P01] [sqlreportserver.LOCAL]
[SQL2012] [1] [] [XX\SCCM2012Server]
[1] [0]
Confirmed version [11.0.5058.0] for the Sql Srs Instance.
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
Extract resource language packs if exists
Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
Looking for 'English (United Kingdom)' resources
Looking for 'English' resources
Found resources for 'English'
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_P01' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
Item, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
Folder, String Parent, Property[] Properties)
(!) SRS root folder was reported missing
Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
Registry change
Waiting for changes for 1 minutes
Has anyone come across this issue before? Must admit, I'm not too hot on the sql side of things so any advice or suggestions would be greatly appreciated. Thanks in advance!

Hi guys, cheers for the swift response.
Garth, i can access SSRS in IE from the SCCM box and it looks a-ok.
Paul, nope can't say I've done any configuration of reporting services - the whole thing has been set up by the database team. Having had a trundle through Reporting Services Configuration Manager, it seems the Database team have set up SSRS in line with
the walkthrough you posted.
Since i'm not seeing the ConfigMgr_XXX folder appear in SSRS I'm wondering if there's something preventing SCCM from being able to create it. The message
"Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions
granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation" sounds like the account SCCM is leveraging to perform the install might not have the right permissions in SSRS. Do i need to delegate specific rights to the NT
AUTHORITY\SYSTEM account in SRS perhaps?

Asm diskgroup does not exist or not mounted

Hi,
iam have configured a 2 node cluster and now when i rebooted and again started my rac database so all the applications are offline so i stop them with crs_stop and then restarted but my databases asm and instance service is not up so in that case i tried to connect to database or to instance but i was not able to so then i thought of connecting to asm instance and then the status is as follows
SQL> select name ,state ,mount_status from v$asm_disk ;
NAME STATE MOUNT_S
NORMAL CLOSED
NORMAL CLOSED
FG_0000 NORMAL CACHED
SQL> alter database open ;
alter database open
ERROR at line 1:
ORA-15000: command disallowed by current instance type
SQL> alter diskgroup all mount ;
alter diskgroup all mount
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DG1" is being dismounted
ORA-15066: offlining disk "DG1_0001" may result in a data loss
SQL>
SQL>
so in that cse the contents are as follows
on Jul 11 21:58:46 2011
Dirty detach reconfiguration started (old inc 2, new inc 2)
List of nodes:
0 1
Global Resource Directory partially frozen for dirty detach
* dirty detach - domain 1 invalid = TRUE
0 GCS resources traversed, 0 cancelled
Dirty Detach Reconfiguration complete
Mon Jul 11 21:58:46 2011
freeing rdom 1
Mon Jul 11 21:58:47 2011
WARNING: dirty detached from domain 1
Mon Jul 11 21:58:47 2011
ERROR: diskgroup DG1 was not mounted
Mon Jul 11 21:58:47 2011
WARNING: PST-initiated MANDATORY DISMOUNT of group DG1 not performed - group not mounted
Mon Jul 11 21:58:47 2011
Errors in file /u01/app/oracle/admin/+ASM/bdump/+asm1_b000_18030.trc:
ORA-15001: diskgroup "DG1" does not exist or is not mounted
ORA-15001: diskgroup "DG1" does not exist or is not mounted
so iam not able to figure out please help me in solving this
Thanks in Advance
Regards
Kavita

Hi,
Sir i wait for many times but the major issue is iam facing that all aplications when i start my machine are offline or unknown........ then when i exec crsctl stop crs and crsctl start crs i wait a lot and then i exec crrs_stat t that time all applications are either unknown or offline............ then i stop forcily all applications which are unknown finally bring all to offline status and then restart but in this case i exec srvctl start nodeapps - n rac1 and nrac2 these things work but tried with database or service or instnace that ownt work it give me the following error
and then i sart instance or database through sqlplus and if i do any transcations then i get the follwoing error .........
PRKP-1001 : Error starting instance devdb1 on node rac1
CRS-0215: Could not start resource 'ora.devdb.devdb1.inst'
and now if iam trying to start my asm instance iam have already posted through what iam getting and this i have tried for 2 diffemt 2 node cluster but facing the same issue
2011-07-12 22:02:02.500: [ CRSRES][3772144560]0startRunnable: setting CLI values
2011-07-12 22:02:03.235: [ CRSRES][3772144560]0Attempting to start `ora.prod1.LISTENER_PROD1.lsnr` on member `prod1`
2011-07-12 22:02:06.197: [ CRSRES][3772144560]0Start of `ora.prod1.LISTENER_PROD1.lsnr` on member `prod1` succeeded.
Sir this from
(0x8364680) pid() proto(10:2:1:1)
[    CSSD]2011-07-12 22:46:09.669 [91069360] >TRACE: clssgmClientConnectMsg: Connect from con(0x8350880) proc(0x8364680) pid() proto(10:2:1:1)
[    CSSD]2011-07-12 22:47:03.826 [91069360] >TRACE: clssgmClientConnectMsg: Connect from con(0x8352a08) proc(0x8364680) pid() proto(10:2:1:1)
[    CSSD]2011-07-12 22:47:04.385 [91069360] >TRACE: clssgmClientConnectMsg: Connect from con(0x835bf18) proc(0x835ed88) pid() proto(10:2:1:1)
[    CSSD]2011-07-12 22:47:17.938 [91069360] >TRACE: clssgmClientConnectMsg: Connect from con(0x835bf18) proc(0x8364680) pid() proto(10:2:1:1)
[    CSSD]2011-07-12 22:48:27.641 [91069360] >TRACE: clssgmClientConnectMsg: Connect from con(0x8350880) proc(0x8364680) pid() proto(10:2:1:1)
Thanks in Advance
Regards
Kavita

ORA-15001: diskgroup "FRA" does not exist or is not mounted

Dear Experts,
We noticed the error "ORA-15001: diskgroup "FRA" does not exist or is not mounted" on the 2nd node of our 4 nodes RAC database system.
During this weekend, we moved our system to a new data center. After the move was done, we were able to bring up the 4 instances around 3:00 AM. However, 4 hours later (7:00 AM), OEM Grid control alerted us with "archival error" on the 2nd instance. From our investigating, we saw the FRA was dismounted. Below is the oracle alert log file (For secuirty reson, the SID is modified):
Sat Feb 7 03:46:03 2009
Completed: ALTER DATABASE OPEN
Sat Feb 7 03:50:18 2009
Sat Feb 7 07:01:36 2009
Thread 2 advanced to log sequence 8534
Current log# 3 seq# 8534 mem# 0: +REDOGRPA/xyz/onlinelog/redo_03.log
Current log# 3 seq# 8534 mem# 1: +REDOGRPB/xyz/onlinelog/redo_03b.log
Sat Feb 7 07:01:39 2009
ARCH: Archival stopped, error occurred. Will continue retrying
Sat Feb 7 07:01:39 2009
ORACLE Instance XYZ2 - Archival Error
Sat Feb 7 07:01:39 2009
ORA-16038: log 11 sequence# 8533 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 11 thread 2: '+REDOGRPA/xyz/onlinelog/redo_11.log'
ORA-00312: online log 11 thread 2: '+REDOGRPB/xyz/onlinelog/redo_11b.log'
ORA-15001: diskgroup "FRA" does not exist or is not mounted
ORA-15001: diskgroup "FRA" does not exist or is not mounted It is my understanding, that Oracle will automatically mount the diskgroups on the ASM when the instances are started. In our case, all other diskgroups are started OK but not the FRA diskgroup. Is this a bug with FRA where FRA can not be automatically started up after recycling the instance? Did anyone experience the same situation? Can someone advice?
Thanks!

Hello,
We are running oracle 10.2.0.2.
Which section of the alert log file for +ASM2 we need here? I will paste it here the ones when "alter diskgroup all mounted" started at 3:00 AM all the way upto 4:00 AM on Saturday, Feb 7:
SQL> ALTER DISKGROUP ALL MOUNT
Sat Feb 7 03:44:15 2009
NOTE: cache registered group FRA' number=1 incarn=0x1e5bf0d2
NOTE: cache registered group DATAX number=2 incarn=0xbcabf0d1
NOTE: cache registered group REDO2 number=4 incarn=0x1e5bf0d3
NOTE: cache registered group REDOGRPA number=5 incarn=0xbcbbf0d4
NOTE: cache registered group REDOGRPB number=6 incarn=0xbcbbf0d5
NOTE: cache registered group TEMPX number=7 incarn=0xbcbbf0d6
NOTE: cache registered group TEMP number=8 incarn=0x1e6bf0d7
NOTE: cache registered group TIBDATA number=9 incarn=0xbcbbf0d8
NOTE: cache registered group TIBREDO number=10 incarn=0xbcbbf0d9
NOTE: cache registered group TIBTEMP number=11 incarn=0x1ebbf0da
Sat Feb 7 03:44:15 2009
ERROR: no PST quorum in group 1: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 1/0x1E5BF0D2 (FRA')
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup FRA' was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 2)
ERROR: no PST quorum in group 4: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 4/0x1E5BF0D3 (REDO2)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup REDO2 was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 5)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 6)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 7)
ERROR: no PST quorum in group 8: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 8/0x1E6BF0D7 (TEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TEMP was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 9)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 10)
ERROR: no PST quorum in group 11: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 11/0x1EBBF0DA (TIBTEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TIBTEMP was not mounted
NOTE: cache opening disk 0 of grp 2: DATAX_0000 path:/dev/raw/raw61
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 2/0xBCABF0D1 (DATAX)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 2
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.1158090 ABA
NOTE: seq=54 blk=4821
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 2/0xBCABF0D1 (DATAX) succeeded
SUCCESS: diskgroup DATAX was mounted
NOTE: cache opening disk 0 of grp 5: REDOGRPA_0000 path:/dev/raw/raw20
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 5/0xBCBBF0D4 (REDOGRPA)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: recovering COD for group 2/0xbcabf0d1 (DATAX)
SUCCESS: completed COD recovery for group 2/0xbcabf0d1 (DATAX)
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 5
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.103802 ABA
NOTE: seq=43 blk=2123
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 5/0xBCBBF0D4 (REDOGRPA) succeeded
SUCCESS: diskgroup REDOGRPA was mounted
NOTE: cache opening disk 0 of grp 6: REDOGRPB_0000 path:/dev/raw/raw12
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 6/0xBCBBF0D5 (REDOGRPB)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 6
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.75866 ABA
NOTE: seq=20 blk=1704
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 6/0xBCBBF0D5 (REDOGRPB) succeeded
SUCCESS: diskgroup REDOGRPB was mounted
NOTE: cache opening disk 0 of grp 7: TEMPX_0000 path:/dev/raw/raw71
NOTE: F1X0 found on disk 0 fcn 0.25328
NOTE: cache opening disk 1 of grp 7: TEMPX_0001 path:/dev/raw/raw7
NOTE: cache mounting (not first) group 7/0xBCBBF0D6 (TEMPX)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 7
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.69473 ABA
NOTE: seq=42 blk=432
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 7/0xBCBBF0D6 (TEMPX) succeeded
SUCCESS: diskgroup TEMPX was mounted
NOTE: cache opening disk 0 of grp 9: TIBDATA path:/dev/raw/raw86
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 9/0xBCBBF0D8 (TIBDATA)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 9
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.102912 ABA
NOTE: seq=12 blk=2050
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 9/0xBCBBF0D8 (TIBDATA) succeeded
SUCCESS: diskgroup TIBDATA was mounted
NOTE: cache opening disk 0 of grp 10: TIBREDO path:/dev/raw/raw87
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 10/0xBCBBF0D9 (TIBREDO)
Sat Feb 7 03:44:18 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:18 2009
NOTE: attached to recovery domain 10
Sat Feb 7 03:44:18 2009
NOTE: opening chunk 4 at fcn 0.18970 ABA
NOTE: seq=12 blk=6577
Sat Feb 7 03:44:18 2009
NOTE: cache mounting group 10/0xBCBBF0D9 (TIBREDO) succeeded
SUCCESS: diskgroup TIBREDO was mounted
Sat Feb 7 03:44:19 2009
NOTE: recovering COD for group 5/0xbcbbf0d4 (REDOGRPA)
SUCCESS: completed COD recovery for group 5/0xbcbbf0d4 (REDOGRPA)
NOTE: recovering COD for group 6/0xbcbbf0d5 (REDOGRPB)
SUCCESS: completed COD recovery for group 6/0xbcbbf0d5 (REDOGRPB)
NOTE: recovering COD for group 7/0xbcbbf0d6 (TEMPX)
SUCCESS: completed COD recovery for group 7/0xbcbbf0d6 (TEMPX)
NOTE: recovering COD for group 9/0xbcbbf0d8 (TIBDATA)
SUCCESS: completed COD recovery for group 9/0xbcbbf0d8 (TIBDATA)
NOTE: recovering COD for group 10/0xbcbbf0d9 (TIBREDO)
SUCCESS: completed COD recovery for group 10/0xbcbbf0d9 (TIBREDO)
Sat Feb 7 03:45:18 2009
Starting background process ASMB
ASMB started with pid=17, OS id=16122
Sat Feb 7 03:49:35 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=18, OS id=25963
Sat Feb 7 03:54:34 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 03:54:50 2009
Starting background process ASMB
ASMB started with pid=18, OS id=913
Sat Feb 7 03:57:55 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 04:07:26 2009
Starting background process ASMB
ASMB started with pid=21, OS id=23012
Sat Feb 7 04:13:59 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=22, OS id=31320
Sat Feb 7 04:36:43 2009
NOTE: ASMB process exiting due to lack of ASM file activity

[Solved]Unable to boot /sbin/init does not exist.

When I boot, I get this message: ERROR: Root device mounted successfully, but /shin/init does not exist. This is an installation that was working fine for me before. I went into Windows to free up disk space, and when I booted Arch later, this is what came up. I have already tried using the live disk as a rescue, but I am unable to chroot into it. I have checked my partitions with a live disk and my files are still there. Is there any way that I can fix this without reinstalling Arch? I have a lot of things that I cannot reinstall right now as I don't have access to the internet currently, and I am using my phone to access the forum.
Last edited by LGG42 (2013-11-27 02:43:47)

My bootloader is Syslinux. Yes, I am able to mount the file systems. The partitions are in ext4 format. I boot from legacy BIOS, as I have had EFI problems in the past. arch-chroot gives me this: ==> ERROR: failed to setup API filesystems in chroot /mnt. I should have been clear about what I did in Windows. I was running out of space in Windows, and I had some unallocated disk space, and so I extended my Windows partition.
The output of frisk -l is:
Disk /dev/sda: 500.1 GB, 500107862016 sectors
Units = sectors of 1* 512
I/O size (minimum/optimal): 4096 Bytes/4096 bytes
disk label type: got
#1 start: 2048 End 821247 size 400M type windows recovery 2 start 821248 End 1353727 Size 260M type ms basic 3 start 874614784 End 916559871 Size 128M ms reserved 4 start 1615872 End 874614783 Size 416G ms basic. 5 start 874614784 End 91655781 Size 20G ms basic. 6 start 916561920 End 916756479 Size 95M type EFI system. 7 start 916758528 End 928495615 8 start 928495616 end 928499711 Size 2M type ms basic. 9 start 928499712 End 976773119 size 23G type ms basic. Sorry about the mess that is in. As a note, my / partition is #5, and my home is #9. Thank you for helping.

Build Question: error 7 occurred at source does not exist

I have VIs built in LabVIEW 6.1. It works and built well. In LabVIEW
7, It works well. But when I try to build it. I got error.
I first use the mass conpile to compile VIs and then build the exe
with default settings. I got:
Error 7 occurred at source does not exist
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted,
or the file path might be incorrectly formatted for the operating
system. For example, use \ as path separators on Windows, : on Mac OS,
and / on UNIX.
NI-488: Non-existent board.
But It does not point out which file does not exist.
Anyone can help me out?

Hello yqin,
Here are some more KnowledgeBases that may pertain to your issue.
Error 7 When Building Applications and DLLs That Use the LabVIEW Report Generation Toolkit
Why Do I Get Error 7 When Building an Executable from a Build Script?
Error 7 at Invoke Node When Building a LabVIEW Executable
If the above KnowledgeBases do not work, we will want to try the following procedure.
1. Open your Main VI.
2. Hold + a
nd click the run arrow (forces recompile).
3. Close the VI and mass compile it.
4. Keep the VI closed and build the application from scratch (do not use a script).
5. Ensure that all VIs called dynamically are included as support files before building.
Please let me know if you have any questions,
Matt
Keep up to date on the latest PXI news at twitter.com/pxi

[SOLVED] after upgrade : /sbin/init does not exist. Bailing out, ...

hi, after having upgraded today my archlinux, I cannot boot it. I get the following message : "ERROR: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on you own. Good luck."
The last time the system was upgraded was in june 2013, before the "Binaries move to /usr/bin requiring update intervention" advisory (https://www.archlinux.org/news/binaries … ervention/). So before upgrading I followed the instructions given in this article and was able to upgrade. But after reboot I got the error message I'm reporting here.
Here is a copy of the config I'm using to boot arch in grub:
menuentry "Archlinux" {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos7'
echo 'Loading of Archlinux, kernel v.3.xx.xx ...'
linux /boot/vmlinuz-linux root=/dev/sda7 ro
initrd /boot/initramfs-linux.img
Last edited by heavytull (2014-03-06 21:24:48)

karol wrote:
There have been quite a few changes since you last updated e.g. we're using 'rw' instead of 'ro'. Try
linux /boot/vmlinuz-linux root=/dev/sda7 rw init=/usr/lib/systemd/systemd
It's now much better. But a lot of errors are reported and the system hangs, but still rebootable with Ctrl + Alt + Del.
Here are the error messages:
[FAILED] Failed to mount Configuration File System.
See 'systemctl status sys-kernel-config.mount' for details.
[FAILED] Failed to mount Huge Pages File System.
See 'systemctl status dev-hugepages.mount' for details.
[FAILED] Failed to mount POSIX Message Queue File System.
See 'systemctl status dev-mqueue.mount' for details.
[FAILED] Failed to mount Temporary Directory.
See 'systemctl status tmp.mount' for details.
[FAILED] Failed to start Remount Root and Kernel File System.
See 'systemctl status systemd-remount-fs.service' for details.

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

Nvidia module does not exist in /proc/modules

Hi!
I compiled kernel with grsecurity from AUR. everything goes fine, and my system boot with a new kernel.
Only thing i have a problem with, is nvidia module.
I'm tried to makepkg nvidia with ABS way, but i get errors:
ERROR: Module nvidia does not exist in /proc/modules
In order to use the new nvidia module, exit Xserver and unload it manualy.
I"m trying to do:
modprobe nvidia
but i get:
FATAL: Error inserting nvidia (/lib/modules/2.6.32-grsec-ARCH/kernel/drivers/video/nvidia.ko): Cannot allocate memory
When i write :find /lib/modules -name nvidia.ko
I get: lib/modules/2.6.32-grsec-ARCH/kernel/drivers/video/nvidia.ko
When i write: uname -r
I get: 2.6.32-grsec-ARCH
Any help please..

you have to reboot after installing nvidia because the > 2.6.34 kernel has nouveau and is using the card.

Error creating sdo_pc point cloud: "ORA-02289: sequence does not exist"

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0
I've come across a problem when creating point clouds - every so often I'll get an error about a sequence not existing.
ERROR at line 1:
ORA-13199: Invalid Parameters for Partition_Table
ORA-13199: Invalid Parameters for Partition_Table
ORA-13249: Stmt-Execute Failure: DROP SEQUENCE "MDPCS_a_17745$$$"
ORA-29400: data cartridge error
ORA-02289: sequence does not exist
ORA-06512: at "MDSYS.PRVT_PC", line 3
ORA-06512: at "MDSYS.PRVT_PC", line 171
ORA-06512: at "MDSYS.SDO_PC_PKG", line 179
ORA-06512: at line 17
I've got a test case which creates a table where we'll put a sdo_pc, a block table and then a loading XYZ table. We then loop a bunch of times and create a PC for each.
Test case setup:
create table pc_test (
    id integer primary key,
    pc sdo_pc);
create sequence pc_test_id;
create table pc_test_blocks as select * from mdsys.sdo_pc_blk_table;
create table xyz (
    rid number,
    val_d1 number,
    val_d2 number,
    val_d3 number);
insert /*+ append */ into xyz (
    select
        rownum,
        round(dbms_random.value(1,10000),2),
        round(dbms_random.value(1,10000),2),
        round(dbms_random.value(20,50),2)
    from dual
    connect by level <= 1000);
commit;
Run test case:
declare
l_pc sdo_pc;
    l_id pls_integer;
begin
    for i in 1..50 loop
        l_pc := sdo_pc_pkg.init(
            'PC_TEST', 'PC', 'PC_TEST_BLOCKS', 'blk_capacity=500',
            sdo_geometry(2003, 2157, NULL, sdo_elem_info_array(1,1003,3), sdo_ordinate_array(400000, 500000, 800000, 1000000)),
            0.005, 3, null);
        l_id := pc_test_id.nextval;
        dbms_output.put_line('PC_TEST id=' || l_id);
        insert into pc_test (id, pc) values (l_id, l_pc);
        sdo_pc_pkg.create_pc(l_pc, 'XYZ');
    end loop;
end;
Some of the PCs will create, but eventually it'll blow up with
ORA-02289: sequence does not exist
In so far as I can tell, once I call sdo_pc_pkg.create_pc(), Oracle is creating a sequence with a name such as MDPCS_a_1751F$$$. When it is done creating the blocks, it then tries to drop the sequence. However the statement to drop the sequence is wrapped in double quotes - so if the sequence name contained any lowercase letters then it will error out when trying to drop it. The values used between the underscores seem to be hexadecimal - sometimes they're numbers only, sometimes numbers and uppercase letters, sometimes numbers and lowercase letters.
Has anybody else come across this issue?
The issue isn't critical as the PC blocks do seem to be created correctly, so the issues are: (a) my pl/sql block errors out and (b) I'm left with sequences lying around.
For the former I'll catch the exception and ignore it, for the latter I'll just drop the sequences myself afterwards.

I tried the test on 11.2.0.4. On that release I get an error during a rename:
ERROR at line 1:
ORA-13199: Invalid Parameters for Partition_Table
ORA-13199: Invalid Parameters for Partition_Table
ORA-13249: Stmt-Execute Failure: RENAME "MDPCI_a_26062$$$" TO "M3_A_26062$$"
ORA-29400: data cartridge error
ORA-04043: object MDPCI_a_26062$$$ does not exist
ORA-06512: at "MDSYS.PRVT_PC", line 3
ORA-06512: at "MDSYS.PRVT_PC", line 157
ORA-06512: at "MDSYS.SDO_PC_PKG", line 74
ORA-06512: at line 17

ORA-15001: diskgroup "DATA" does not exist or is not mounted in 11gR2

Dear all,
the system is HP-UX 11.31
the new RAC infrastructure is 11gR2 11.2.0.2 (2nodes using ASM)
i am restoring the 10G 10.2.0.4 database to this infrastructure
copy binary files over to new oracle home,
relink all binaries with option rac_off
--startup nomount
--restore controlfile
--mount database
--catalog the restore files
then run restore
run {
restore database ;
recover database;
i always get this error, i did not see this error in 11gR1( restore few times to 11gR1)
verified the diskgroup DATA and i was mounted
ORA-19504: failed to create file "+DATA/OCP/data1.dbf"
ORA-17502: ksfdcre:3 Failed to create file +DATA/OCP/data1.dbf
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
Please give me an advice.
Thanks,

found this note in Metalink and it had solved my issue.
Unable To Create 10.1 or 10.2 or 11.1(< 11gR2) ASM RAC Databases (ORA-29702) Using Brand New 11gR2 Grid Infrastructure Installation . [ID 946332.1]

"mount point /proc/bus/usb does not exist" -deux

Similar Messages

Maybe you are looking for