PXI invalid sytem disk

最近PXIシステムを購入したのですが、PXI-8186にWIndows OSをインストールしようとすると、"Invalid system disk"というエラーが出てきてうまくいきません。CD-ROMドライブはNIが推奨しているTEAC社製のものを使用しているので、CD-ROMの相性の悪さが原因とは思えません。どうしたらOSをインストールできるようになるでしょうか。

お世話になっております。
日本ナショナルインスツルメンツ、湯田と申します。
Leorge様
ご返答ありがとうございました。
MNaka様
OSをインストールする際に表示される"PXI Invalid System Disk"の問題についてですが、
ハードドライブよりもCD-ROMが先にブートすることで、
正常にドライブを認識し、CD-ROMからインストールすることができるかと思いますので、
以下の方法で今一度ご確認のほどよろしくお願いします。
１．起動画面にて、"Delete"キーを押し、BIOS画面に入る
２．"Boot"タブに移動し、USB CD-ROMが認識されているか確認する
３．USBデバイスをハイライトし、＋キーでUSBデバイスを一番上に移動する
４．F10キーを押してBIOSでの変更を保存する
上記の設定を行いますと、CD-ROMが一番最初のブートデバイスとして認識されるため
インストールできるかと思います。
以上ご確認よろしくお願いいたします。

Similar Messages

How can I make an invalid dynamic disk Array available to the OS again

Hello Storage Pros
The setup
I have a Promise VTrak E610f head unit with 2 VTrak 610j expansion units attached to it together giving me over 27 TB of usable storage space.
At the hardware level I slip the storage into 6 parts containing 7
1TB disks and had the parts configured into 6 RAID 6 arrays. In the end; each of the 6 arrays gives me 4.6TB of usable storage space.
On the OS level, I have the storage attached to 2 servers: Windows server 2008 and windows server 2008 R2 over a Qlogic fiber channel switch. Each of the 6 arrays are viewable as basic disks of 4,6Tb which I went on to configure as a single RAID 0
spanned volume of 27TB and for that all the disks had to be converted to dynamic.
The problem
Now comes the problem: On my first attempt to do a firmware update on the VTrak E610f storage; all the volumes were rendered foreign and I had to import them to be able to use them. Although the import was successful, I lost all the set NTFS permissions
and SMB share and I had to manually reconfigure them. Upon doing so The OS registered some inconsistencies in the storage and recommended that I ran chkdsk. Since the storage is that big I reluctantly complied and restarted the server.
The first server was restarted BUT chkdsk did not commence as scheduled, the server powered right up. After logging in to inspect; I discovered - to my surprise, that the disks were now shown as invalid in Disk Manager and were no longer visible to
the OS. Assuming that maybe a restart of the other server and the storage would set things right, I went ahead to do so but to no avail. After rebooting the entire system (including the storage), the other server also displayed the disks as invalid and were
no longer visible to the OS as well.
My question is; how can I make the disk available again from this ‘invalid’ state without losing data?
What I tried but did not help:
Taking the disks offline and then online again did not work, after the disks were online again, they still appeared as invalid.
Reactivating the disks threw an error “operation not allowed on an invalid disk pack”
Calling support of the storage manufacturer: they did not find anything wrong with the system, after 5 hours we had to stop.
I fear converting the array from dynamic to basic will destroy all the data.
HxD is showing no errors in the disks
If there is any expert out there with helpful tips; your assistance will be greatly appreciate.
Cheers
John

Hello Shoan
Thanks a lot for your response and tips. Sorry I could not get back to you in good time for I had to run some of the tests you provided, it took some time to
thoroughly re-test the system.
The summary
The initial firmware upgrade attempt forced 3 disks offline and the other 3 became foreign. I had to re-import them to have access again. after re-importing
the disks I realized all NTFS permissions and SMB shares of the folders on the disks had disappeared, but at least the disk was visible and accessible at that point - but not fault free. It was recommened that I let chkdsk run. However rebooting the
system to allow chkdsk to run did not result in chkdsk running, instead chkdsk did not run and after restart, the OS showed the disks as invalid. And that is still the case now.
Response to your questions:
Yes the storage array was (and is still) connected to another server 2008 R2 server when the problem occurred. The second server is also displaying the same problem: the disks are shown as invalid.
The loss of SMB shares and NTFS permissions occurred after the initial firmware upgrade attempt, some disks (3 out of 6 of them) were forcibly offlined and the other 3 were, suddenly, marked as foreign. In the end, and to have access to the disks
I had to online the offlined 3 disks and then reimport the rest of them. From the way I understand it, if the upgrade was not the cause, then at least it was the trigger.
In as far as converting disks from dynamic to basic, I was not in luck so far:
Three of the companies I have contacted (recommended by promise Technology technician) so far only work with smaller disks like 2TB, 27 TB like I have is so
far too big.
I’m not sure converting the disks to basic will help much though, since that would break the single 27 TB volume which the OS was working with into 6 individual
disks of 4.6 TB. Will I be able to get the data back that was written to just one volume from those 6 individual and unrelated disks?
Above all, I have connected the RAID storage system to a newly installed Server 2008 R2, the disks are also shown as invalid.
I have spent more than 17 hours in remote sessions with a Promise Technology technician trying the resolve the issue. From the technician’s side all seems in place with the exception
that the disks are invalid in the OS.
I have contacted Microsoft Customer Support service with the issue. Given that Microsoft did not manufacture the storage unit, can they help at this point – or am I better off
putting my hopes else?
Your help is always appreciated and again, thanks for your response and advice.
JohnV

INS-30508 Invalid ASM disks on 11.2.0.3 OL 6.2 grid standalone install

New set of Dell servers R710s running OL 6.2 redhat compatible kernel
$ uname -a
Linux seoltpo-02 2.6.32-220.el6.x86_64
Connected to EMC VNX5500 and using powerpath 5.6.0. Not a rac environment ... doing 11.2.0.3 base install of grid infrastructure for a standalone server.
Not using ASMLIB.
Disk permissions are correct as grid install begins ...
brw-rw---- 1 grid oinstall 120, 704 Jul 26 21:18 emcpoweras
brw-rw---- 1 grid oinstall 120, 720 Jul 26 21:18 emcpowerat
brw-rw---- 1 grid oinstall 120, 736 Jul 26 21:18 emcpowerau
brw-rw---- 1 grid oinstall 120, 752 Jul 26 21:18 emcpowerav
brw-rw---- 1 grid oinstall 120, 768 Jul 26 21:18 emcpoweraw
brw-rw---- 1 grid oinstall 120, 784 Jul 26 21:18 emcpowerax
brw-rw---- 1 grid oinstall 120, 800 Jul 26 21:18 emcpoweray
brw-rw---- 1 grid oinstall 120, 816 Jul 26 21:18 emcpoweraz
GUI installer sees the powerpath LUNs after changing the Disk Discovery path ... for example ....
INFO: ... discoveryString = /dev/emcpower*
INFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpower*']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing 40960 CANDIDATE /dev/emcpoweras grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerat grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerau grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerav grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraw grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerax grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweray grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraz grid oinstall
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweru
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweru"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
*** Of course there are other LUNs not going to be part of ASM disk groups so it cannot read all of them initially.
Somehow after first looking at the disks and seeing them the first time the permissions are changed back on the disks over to root:root as soon as the GUI sees the disks.
You select the disks that you want in the GUI ( but the permissions have been changed already ) so click Next and wham INS 30508 ...
The Install log shows that kfod is apparently scanning the disks a bunch of time ... but before the error appears install log sees that permissions have changed.
Somehow actions caused from running the GUI are changing the permissions? Something is wrong somewhere ... powerpath ? 11.2.0.3 on this kernel version ? Seems very bizarre ...
NFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpoweras','/dev/emcpowerat','/dev/emcpowerau','/dev/emcpowerav','/dev/emcpoweraw','/dev/emcpowerax','/dev/emcpoweray','/dev/emcpoweraz']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraz
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraz"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: The process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweray
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweray"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerax
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerax"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraw
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraw"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerav
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerav"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerau
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerau"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerat
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerat"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweras
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweras"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Output processor threads exited.
SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
CAUSE: The disks [dev/emcpoweras, /dev/emcpowerat, /dev/emcpowerau, /dev/emcpowerav, /dev/emcpoweraw, /dev/emcpowerax, /dev/emcpoweray, /dev/emcpoweraz] were not valid.
ACTION: Please choose or enter valid ASM disks.
INFO: Advice is ABORT
INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
INFO: Completed validating state <CreateASMDiskGroup>
INFO: Terminating all background operations
INFO: Terminated all background operations
INFO: Transition aborted
INFO: Rolled back to state <CreateASMDiskGroup>
Is there some kind of configuration steps I am missing somewhere?
Yeah I know probably going to have to open an SR here but some of you guys around here are pretty sharp. Can I attach the whole install log here somehow?

Well I am not exactly opposed to udev rules for the powerpath devices ... not that I know what that is exactly ... if this can fix my problem.
I found an example or two from google ...
It looks like on my OL 6.2 system there is a difference in the files ( rules I guess ) under /etc/udev/rules.d
# *** OL 5.7 system below
$ ls -ltr
total 232
-rw-r--r-- 1 root root 1088 Jun 6 2007 60-pcmcia.rules
-rw-r--r-- 1 root root 58016 Jun 6 2007 60-libsane.rules
-rw-r--r-- 1 root root 2319 Jul 14 2008 bluetooth.rules
-rw-r--r-- 1 root root 114 Nov 5 2008 90-alsa.rules
-rw-r--r-- 1 root root 1823 Nov 5 2008 85-pcscd_ccid.rules
-rw-r--r-- 1 root root 316 Dec 8 2010 60-raw.rules
-rw-r--r-- 1 root root 82 Jan 13 2011 90-hal.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r-- 1 root root 292 May 11 2011 98-kexec.rules
-rw-r--r-- 1 root root 143 Jun 7 2011 60-net.rules
-rw-r--r-- 1 root root 331 Jun 9 2011 90-ib.rules
-rw-r--r-- 1 root root 992 Jul 8 2011 40-multipath.rules
-rw-r--r-- 1 root root 9366 Jul 22 2011 60-wacom.rules
-rw-r--r-- 1 root root 107 Jul 22 2011 95-pam-console.rules
-rw-r--r-- 1 root root 61 Jul 22 2011 90-dm.rules
-rw-r--r-- 1 root root 471 Jul 22 2011 51-hotplug.rules
-rw-r--r-- 1 root root 16732 Jul 22 2011 50-udev.rules
-rw-r--r-- 1 root root 515 Jul 22 2011 05-udev-early.rules
-rw-r--r-- 1 root root 175 Jul 22 2011 88-clock.rules
# *** OL 6.2 system below
$ ls -ltr
total 64
# *** OL 6.2 system below
$ ls -ltr
total 64
-rw-r--r--. 1 root root 1914 Apr 27 2010 85-pcscd_ccid.rules
-rw-r--r--. 1 root root 320 Jul 2 2010 90-alsa.rules
-rw-r--r--. 1 root root 1060 Jul 24 2010 60-pcmcia.rules
-rw-r--r--. 1 root root 1652 Nov 20 2010 60-fprint-autosuspend.rules
-rw-r--r--. 1 root root 2486 Dec 23 2010 97-bluetooth-serial.rules
-rw-r--r-- 1 root root 935 Mar 7 2011 95-dataeng-udev.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r--. 1 root root 706 Mar 29 2011 56-hpmud_support.rules
-rw-r--r--. 1 root root 6858 Mar 29 2011 40-hplip.rules
-rw-r--r--. 1 root root 83 May 20 2011 90-hal.rules
-rw-r--r--. 1 root root 316 Oct 13 2011 60-raw.rules
-rw-r--r--. 1 root root 54 Dec 7 2011 99-fuse.rules
-rw-r--r--. 1 root root 292 Dec 7 2011 98-kexec.rules
-rw-r--r--. 1 root root 53 Dec 7 2011 91-drm-modeset.rules
-rw-r--r--. 1 root root 789 Jul 19 07:28 70-persistent-cd.rules
??? So no file 50-udev.rules ... in the 6.2 system ??? But tons of stuff in the 5.7 system ...

[FATAL] [INS-30508] Invalid ASM disks.

Dear Gurus
please help for troubleshoot the Invalid asm disk error on solaris
Oracle Grid 11.2.0.3.0
Solaris10 with EMC Powerpath Partition
-bash-3.2$ ./runInstaller -silent -responseFile /aaa/Oracle11g_SunSPARC_64bit/grid/response/grid_install.rsp
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 180 MB.   Actual 90571 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 90667 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-09-15_12-17-47PM. Please wait ...-bash-3.2$ [FATAL] [INS-30508] Invalid ASM disks.
   CAUSE: The disks [/dev/rdsk/emcpower2a, /dev/rdsk/emcpower6a, /dev/rdsk/emcpower8a] were not valid.
   ACTION: Please choose or enter valid ASM disks.
A log of this session is currently saved as: /tmp/OraInstall2013-09-15_12-17-47PM/installActions2013-09-15_12-17-47PM.log. Oracle recommends that if you want to keep this log, you should move it from the temporary location to a more permanent location.

I'm grateful for your response and your time
We had resolve the issue our self
[/dev/rdsk/emcpower2a, /dev/rdsk/emcpower6a, /dev/rdsk/emcpower8a]
above partition by default take the slice 0
we had refer below link
ASM Create Partitions in Solaris and add them as disks in AS
In Sparc architecture, the solaris disk is subdivided into 8 slices.
Below is the common configuration of these eight slices:
slice 0: Holds files and directories that make up the operating
system.*
slice 1: Swap, Provides virtual memory, or swap space.
slice 2: Refers to the entire disk, by convention. The size of this
slice should not be changed.**
slice 3: /export, Holds alternative versions of the operating system.
slice 4: /export/swap. Provides virtual memory space for client
systems. ***
slice 5: /opt. Holds application software added to a system.
slice 6: /usr. Holds operating system commands--also known as
executables-- designed to be run by users.
slice 7: /home. Holds files created by users.
* Cannot be used as ASM disk. Using this slice causes disk corruption
and may render the disk as unusable.
** Should not be used as ASM Disk, as slice refers to the entire disk
(Including partition tables).
*** Is the recommended slice to be used for ASM disk.
as per asm recommendation we had used slice 4 the same
so we had detail diagnose and came to know that we have to use
[/dev/rdsk/emcpower2e, /dev/rdsk/emcpower6e, /dev/rdsk/emcpower8e]
here e refer the slice 4
we had use below changes in silent file and it's working fine
oracle.install.asm.diskGroup.disks=/dev/rdsk/emcpower2e,/dev/rdsk/emcpower6e,/dev/rdsk/emcpower8e
sample logs
INFO: Starting Output Reader Threads for process /tmp/OraInstall2013-09-17_05-03-21PM/ext/bin/kfod
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower2e oracle oinstall
INFO: The process /tmp/OraInstall2013-09-17_05-03-21PM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower6e oracle oinstall
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower8e oracle oinstall

Portege 660CDT "Invalid System Disk Error"!!!

I just purchased a Used 660CDT and placed a new hard drive in it. Now I can not load an OS Due to This Error "Invalid System Disk". I have tried to Boot from my XP Cd but just the same. I have attempted to boot from a Norton Disk and nothing as well.. I have no clue what is wrong..
I have made sure that the Bios is set to start with the Drive first and not the HDD.
I would like to use this system someday, but right now I dont see it happening.
If anyone can help I would thank you greatly.
Thank you
Robert
Houston, Texas

Hi Robert
As far as I know this oldie can handle just with 1,3 GB HDD. How much capacity has a new HDD?
Unfortunately it is not easy to say what the problem is because who knows what you do exactly and which OS you want to use. Just for info. This old Portege is delivered with W95 and you should try to use the same OS.
"Invalid System Disk error means that the Windows Setup was unable to copy the system files to the hard disk.
By the way, check Toshiba download page under http://eu.computers.toshiba-europe.com/cgi-bin/ToshibaCSG/download_drivers_bios.jsp?service=EU and under archive you will find lot useful stuff for this old notebook.
Good luck!

Why quality sytem disk space should be the same as Production disk space

Hi All,
Why quality sytem disk space should be the same as Production system disk space. Please give few points and also the impact if the disk spaces are not same. Its URGENT.

Karunakar,
It all depends on what you do with your QA system. I personally don't think QA and Prod should be of the same size.
QA is your testing environment, the one where you perform the final tests and validations before going to Prod.
In my personal experience and practice, for QA:
- Daily loads of Master Data - Master Data is good to keep it updated, for obvious reasons
- No daily transactions loads - You can load your transaction data on demand, depending on the specific area you need to test. You can initialize and load sample periods or sets of data. Once you're done, that's it.
- No copy from BW Prod to QA - You really don't need to. As far as they do "refresh" from R/3 Prod to R/3 QA, you'll have data in QA good enough to test. Also, copying Prod to QA in BW can mess your transports sequence and put the systems out of sync or make you re-transport requests that were already in QA but not in Prod. Also, by doing those copies, it's like having two Production systems to maintain... Your landscape and maintenance costs will grow much faster
In my opinion, Development and QA have a controlled growing, following those guidelines. Only Prod will keep growing during time, which makes sense.
My 2 cents...
Regards,
Luis

Invalid system disk

I
bought a used toshiba satillite a10-s127, with no hard drive or operating system. I bought
a hard drive, and I want to install Ubuntu on it. but when it boots all I get is a message that says Invalid system disk. I can get to bios but that is all. Any suggestion?

Assuming that you bought a compatible hard drive and that it is jumpered as Master (cable select drives do not work), then it sounds like the system is trying to boot from the hard drive rather than the CD. It is also possible the the system doesn't have the capability of booting from CD, in which case you would have to boot from a floppy with CD drivers and install from there.

Thinkpad T440s BIOS update via PXE fails with "invalid system disk"

Hi,
I'm trying to boot via PXE to the BIOS 2.24 update ISO image because the T440s comes without a DVD drive. The Thinkpads are running RHEL 6.5 workstation installed. I'm using syslinux 6.02 and the following menu entry:
label lenovo_t440s
    menu label Lenovo Thinkpad T440s BIOS 2.24 Update
    kernel memdisk
    append initrd=lenovo/t440s/gjuj11us.iso iso
The ISO gets loaded via TFTP and seems to boot, but then an error message appears:
Loading boot sector... booting...
Lenovo Group Limited
Invalid system disk
Replace the disk, and then press any key.
The Thinkpads come with the following SSD drive: SAMSUNG MZ7TD256HAFV-000L9.
Anyone had luck with updating BIOS via PXE boot?
We also have Thinkpads T430s. There the BIOS update ISO image loads, displays the menu, but when one presses "update firmware" then it freezes.
Regards,
Bernd

Same behaviour when I try without PXE and load memdisk and ISO file directly via GRUB using this entry in /boot/grub/grub.conf:
title ThinkPad BIOS Update
root (hd0,1)
kernel /memdisk iso
initrd /gjuj11us.iso

PXIe acquiring and disk streaming speed

Good evening,
I need to acquire and stream to disk the status of N.8 digital lines at 100 MHz clock, idest 100MBytes/sec data rate, in continuously mode (without data loss) for five minutes.
I've thought to a PXIe configuration with:
PXIe 6544 High speed DIO,
PXIe 1071 Chassis,
PXIe Controller with solid state H.D. option.
Is that configuration enough?
Thanks.
Natalino Roberto

Hello Roberto,
According to NI PXIe-6544 specifications, you should be able to achieve typical data streaming rates 400 MB/s for acquisition and 400 MB/s for generation. So, you shouldn't face with any issue from this side.
Does your application provide an host interface communicating with embedded application? If doing so, you may need to design your application according real time guidelines.
Let me know if you need help or additional assistance.
Have a nice day.
Matteo C. - Test Engineer

URGENT!!!!- INTEL MAC "INVALID SIBLING DISK" error when run disk utility

I am very upset, I ran my verify disk permissions, everything fine, repair disk permissions, everything fine, do t periodically just to mae sure all my stuff is in order,,,, then I decided to run te VERIFY DISK, because do not do it as much and want to mae sure my macbook pro is running fine, and I get:
Verifying volume “minimal minimal”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid sibling link
The volume minimal minimal needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
!!!!!!!!!!!!!!! ***?!!!!!!!!!!!!!!!!! there is no way of repairing the disk, and when I search for possible solutons it says I need to run it from the original osx installer disk, and even when it does not necessarily repir this error. besides the fact that the original cd is in atlanta and I am currently in barcelona, some say that I would need to reformat my drive and either way this might not solve the problem. I HAVE WAY TOO MUCH IMPORTANT INFORMATION on my macbook pro to reformat, and i do not have the money to buy an external hardrive, I A VERY UPSET, A BRAND NEW COMPUTER, LESS THAN TWO MONTHS OLD, AND ALREADY I HAVE THESE KIND OF PROBLEMS WITH IT, WHERE IS MY SUPPORT?! please tell me, what do i do? I expect a decent, viable slution to the problem. I need my computer ad the information in it, I work from it and also use it to produce music. why would I have this kind of problem, when I search for answers, everything relates to external hardrives, ..... this is my internal hard drive that I am talking about--- WHAT DO I DO?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

The available Apple centers in Spain are:
ADEMAC
C Castelló, 109
28006 Madrid
Tel 91 562 11 00
BANANA COMPUTER
C Leon and Castillo, 88
The 35004 Palms of Great Canary
Tel: 928 24 28 28
Fax: 928 24 82 31
BANANA COMPUTER
General boulevard Franco, 141
38001. - Santa Cruz de Tenerife
Tlf.: 922882126
Fax.: 922206782
BENOTAC
C Doctor Castelo, 35
28009 Madrid
Tel 91 308 43 63
BENOTAC
C Babel Nº1, the Premises
29006 Malaga
Tel: 952 04 09 55
Fax: 952 04 13 58
BILBOMICRO
Stolen c of Amezaga, nº 7 low
48008 Bilbao (Biscay)
Tel 94 423 02 13
BILBOMICRO
C Abendaño, 52
01008 Vitoria
Tel 945 28 41 33
BUS Solutions
C Cabrales, 100
33201 Gijón - Asturias
Tel: 985 35 90 85
CTA Serveis
C Consell de Cent, 382
08009 Barcelona
Tel 93 24 40 350
GOLDENMAC
C Bolt, 48
29007 Malaga
Tel 952 42 97 12
GOLDENMAC
Avda. White Carrero, 2
41011 Seville
Tel 95 427 12 13
K-TUIN
C Luis You live 8
50006 Zaragoza
Tel 976 56 72 27
K-TUIN
C Hernandez Lazaro 14
46015 Valencia
Tel 96 385 36 74
K-TUIN
C Muntaner 537 - 541
08022 Barcelona
Tel 93 418 02 03
K-TUIN
C Orense, 52
28020 Madrid
Tel 91 55 56 798
K-TUIN
C Aureliano Valle, 4
48010 Bilbao
Tel 94 410 07 77
Microgestio, LIMITED LIABILITY COMPANY.
C Valencia, 87-89
08029 Barcelona
Tel 93 454 63 63
Rossellimac.
C Painter Lopez Mosque, 12
18002 Granada
Tel 95 829 13 24
SICOS
Pza of Good Shepherd 6
20005 San Sebastián (Guipuzcoa)
Tel 94 344 12 79
Valles Tecnologic, S.A.
Plza. Of the Unio, 3 the Premises 1º
08190 Sant Cugat of Valleys (Barcelona)
Tel 93 590 80 60
Perhaps, since you are under warranty, they may have a boot disk to attempt to run disk utility and see if the problem can be repaired before resorting to reformatting. Disk error may occur because of a number of issues (installed software, crashes, shutdowns, physical movement of the drive while disks spinning, etc.)
In addition you may want to boot in the single user mode to access the FSCK command as follows: The following is from the Apple support site
Mac OS X: How to Start up in Single-User or Verbose Mode
You may use a key combination when starting up the computer to enter single-user mode or verbose mode, either of which can be used for troubleshooting and in software development. This document applies to Mac OS X and Mac OS X Server versions 10.0 and later.
Steps to Enter Single-User or Verbose Mode
1. Shut down the computer if it is on.
2. Press the power button to start the computer.
3. Immediately press and hold the Command (Apple) key and one of the following:
the "s" key for single-user mode.
the "v" key for verbose mode.
4. To exit single-user mode type: reboot
5. Press Return.
You have successfully entered single-user or verbose mode when you see white text appear on the screen.
Then you may try to repair as follows using the FSCK
fsck is a command-line utility that may be able to verify and repair a disk. If you can successfully start up in Safe Mode or use Disk Utility while started up from a disc, you don't need to use fsck. However, here are some situations in which fsck may be necessary.
Your Mac OS X disc isn't available.
Your optical drive isn't available.
You can't start with a Safe Boot.
Tip: If you use a Mac OS X Extended (Journaled) formatted volume, such as with Mac OS X 10.3 or later, you probably won't need to use fsck. If you do use it for any reason, please be aware that benign error messages can appear.
If you're not sure how your volume is formatted and you can't start up from your Mac OS X volume to find out, type the following command in a command-line interface and then press Return: diskutil info /
If you see "File System: Journaled HFS+" returned, you have a Journaled volume.
To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
Start up your computer in single-user mode to reach the command line.
Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
At the command-line prompt, type /sbin/fsck -fy
Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
** The volume (nameofvolume) appears to be OK
If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
*** FILE SYSTEM WAS MODIFIED ***
Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
Your computer should start up normally and allow you to log in.
About live verification in Mac OS X 10.4.3 or later
In Mac OS X 10.4.3 or later, you can verify your Mac OS X volume while started from it. This is known as live verification, and can be used in three different ways.
Option 1: Verify your disk using Disk Utility while started from the startup disk. To find out how to do this, see this article. Please note that live verification does not involve any disk repair, so if verification finds something that should be repaired, start up from your Mac OS X Install disc and use Disk Utility as described above in "Try Disk Utility."
Option 2 (advanced): Use the command line and the command-line utility, diskutil.
Start up your computer and log in as an administrator.
Open Terminal (/Applications/Utilities).
At the prompt, type the following command and then press Return:
diskutil verify /
Note: Don't use this method to check non-startup volumes.
You should see messages such as the following during the disk check:
Could not unmount disk for verification, attempting live verify
Started verify/repair on volume disk0s3 Macintosh HD
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
The volume Macintosh HD appears to be OK.
Mounting Disk
Verify/repair finished on volume disk0s3 Macintosh HD
Option 3 (advanced): Use the command line and the fsck_hfs -l command.
Start up your computer and log in as an administrator.
Open Terminal (/Applications/Utilities).
At the prompt, type the following command and then press Return to determine your filesytem ID:
df -hl
Look for some lines of text that look like this:
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s3 37G 20G 17G 55% /
/dev/disk0s5 37G 37G 641M 98% /Volumes/Storage
Make a note of the first "disk" name that appears after /dev/, such as "disk0s3." This is your filesystem ID for your startup volume.
At the prompt, type the following command and then press Return:
df -hl
Then type the following command, where "disk0s3" is your filesystem ID you noted in step 4, then press Return:
sudo fsck_hfs -l /dev/disk0s3
When prompted, enter your admin password, then press Return to begin the verification.
You should see messages like these during the disk check:
** /dev/rdisk0s3 (NO WRITE)
** Root file system
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume Macintosh HD appears to be OK.
Additional Information
If you're interested in UNIX-style command-line syntax, here's a look at how a couple of flags used in our instruction can influence fsck:
The -y flag: Tells fsck that you want to answer "yes" to all questions about fixing, repairing, or salvaging information. This is the optimal approach, as answering "no" to any question causes fsck to stop. You cannot determine that all necessary repairs have been made until fsck completes and gives its final report.
The -f flag: Forces fsck to check "clean" filesystems when preening.
Macbook Pro 17" 7200 HD 1GB Powerbook G4 (15 inch FW 800) Mac OS X (10.4.6)
Macbook Pro 17" 7200 HD 1GB Powerbook G4 (15 inch FW 800) Mac OS X (10.4.6)
Macbook Pro 17" 7200 HD 1GB Powerbook G4 (15 inch FW 800) Mac OS X (10.4.6)

WS2008 R2 - Invalid dynamic disk

I have a software RAID5 array in Windows Server 2008 R2. 5x4TB drives. After clean shutdown all the disks in disk management are listed as invalid. When I try to reactivate any of them I get this error message: This operation is not allowed
on the invalid disk pack.
What can I do? I've searched high and low and can't find a solution.

Hi,
Based on research, it seems a bug that Dynamic disk(s) comes back as INVALID after taking offline, or following reboot.
This bug surfaces when the size of a record in the LDM matches exactly the size of a block on disk. In this situation, volmgrx incorrectly flags the record as incomplete. After reading the whole database, volmgrx will clean all incomplete records. That’s why
we end up with an empty volume record and with a plex that’s not referenced by a volume.
In this repro, we have a record for a volume that’s bigger than 2TB, has a 3 digit number and has no drive letter (which means attributes are stored in the record). Because of this, the record size was exactly 68 bytes, which is the size available in the block
after all the headers.
If the effected Windows 2008 R2 server is Non-DPM server, we must re-create the volumes manually and restore from backup.
If the server is a DPM 2007 server, all of the dynamic disks in the DPM storage pool will be inaccessible. To avoid having to rebuild the DPM server from scratch, you can use the following procedure to clean (wipe out) the dynamic disks and recreate the DPM
replica and recovery point volumes while maintaining the rest of the DPM 2007 configuration.
WARNING: This procedure is non-reversible, and will result in ALL replica and recovery point volumes to be permanently lost. Verify with the customer that he has a >2TB volume configured before proceeding.
1) Run diskpart.exe - and issue a "list disk" command - and see which disks show the status of INVALID
2) Select one invalid disk at a time and issue a CLEAN command to wipe it out and make it a RAW disk again.
3) Select one disk at a time and convert to GPT, then Dynamic.
4) Exit diskpart.exe
5)Now add the same disks to the DPM storage pool under the management tab - disk tab.
6) From command prompt - run the following command to remake the DPM volumes - this may take hours...
dpmsync -reallocatereplica
7) AFTER Dpmsync completes, re-run diskpart.exe and save the output of the "list volume" command.
NOTE: Make the DOS window so if has a height of 9999 before running list volume - then copy the contents of the window to notepad.
8) Search the output of list volume and locate any volumes are larger than 2000 GB (2TB) - note the mountpoint path.
9) From command prompt - run mountvol.exe >mountvol.txt - then open the mountpoint.txt using notepad. Search for the path for the >2GB volumes to get the volume {Guid}
10) Use mountvol.exe to assign a drive letter to that volume.
mountvol E: \\?\Volume{bf14e9ca-d929-11dd-8f76-806e6f6e6963}
11) Repeat steps 7-9 for ANY and ALL volumes that have a volume numbers above 99, and exceed the 2TB size.
It is now safe to reboot and not experience the dynamic Invalid status for the dynamic disks. If the customer creates any more dynamic volumes that exceed 2TB - they MUST assign a drive letter or they will experience the same issue.
12) Run Consistency checks for all the data sources to get the DPM server back into a consistent state and continue protectecting the production servers.
I hope this helps.
Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Invalid system disk when recovering from USB system image

I have a Toshiba L650 running win7. The internal disk failed recently so I replaced it with one I bought locally. I successfully recovered the DVD based system image I took soon after purchasing the laptop. I am now trying to
recover later system images I made to an attached USB drive. I am using a system recovery disk to boot into the recovery process and am successfully finding the USB based system images. However soon after the recovery process begins I get an eror like "Cannot recover to system disk". There are 3 reasons provided
a. system disk is in the exclusion list - no I checked
b. system disk is a USB disk - no the system image is on the USB drive but the system disk is the internal HDD
c. system disk is invalid - no I just installed a system image from DVD onto it - no problems
How do I proceed? There is obviously a valid system image but I just can't get iti nto the machine.
cheers,

Usually such message appears if you try to boot from CD which is no bootable.
Possibly the BIOS cannot boot up from the PCMCIA drive and tries to boot from the HDD.
But on the HDD the OS is missing and therefore the message appears.
Did you try to force the booting manually?
You could try to press the C button immediately after the notebook starting for booting from PCMCIA drive.
Please read also this Toshiba knowledge article:
Portg R100 supported Recovery Drives
http://support.toshiba-tro.de/kb0/TSB5100S70004R01.htm

RF acquisition stream PXIe 5663 et disk RAID

Bonsoir
j'essaie de réaliser un enregistreur large bande !!! Je dispose d'une carte PXIe 5663 et de disques RAID à 200Mo/s (je ne me rappelle plus de la réference mais il y a 4 disques de 250Go sur un U)
J'utilise les drivers RFSA configurés en IQ pour réaliser une acquisition continue et j'écris directement les données sur le disque au format I16.
Mais je n'arrive pas à enregistrer en continue j'ai le message d'erreur qui me dit que les données ont été écrasées dans le numériseur !!!
Pourquoi est ce que ça ne tient pas le débit??? que je mette 50MHz ou 20MHz de sampling rate j'ai le même message!!!
A 50MSPS en IQ je suis pourtant théoriquement à 200Mo par seconde, non?????Je ne comprend pas !!!
Help

Bonjour Romain,
Bon dans ce cas là ce qui relentie l'écriture ce serait l'accés au disques.
Déjà vérifie que les disques sont bien configurés en RAID 0 (striped) pour avoir les 200Mo/s en lecture/écriture (conf. INSTALLATION GUIDE NI 8260).
Aussi je te renvoie vers ce doument Stream to Disk Using Win32 File IO qui explique avec des examples comment faire des accés fichiers non bufferisés (donc plus rapides) sous windows en LabVIEW.
Pour répondre à ta dernière question: Le "fetch" va chercher les données dans le mémoire de la carte et les met en RAM (du PC). Donc tout ce qui se passe aprés se passe en RAM.
Cordialement,
Ludovic R.

Toshiba Satellite A205- Invalid system disk.... please help!

my pc is running on Windows Vista and it needs to be reinstalled/restore(been very slow),
i've got a big problem because my optical drive won't read DVD's including it's recovery
disc... So i've finally decided to downgrade my OS to Windows XP since my optical drive has
no problem on reading/accessing CD's. i just formatted my hard drive and ready to install
windows xp but there was an error when already on the " preparing for setup" part.... It says
" Setup did not find any hard disk drives installed in your computer. Make sure any hard disk
drives are powered on and properly connected to your computer and that any disk-related
hardware configuration is correct. This may involve running a manufacturer supplied
diagnostic or setup program... setup cannot continue.
PLEASE HELP!!! i really need your help....THANK YOU!!!

Satellite L305-S5955
See the section Hard Drive Recovery Utilities, beginning on p. 60 of the User's Guide.
Satellite L300 Series User’s Guide
-Jerry

How to erase Mountain tiger sytem disk

Big problems with mountain tiger. Can't burn a Blu ray from FCPX on my Pioneer BD-RW BDR-206M witch working right on Lion.
So I want to get back to Lion and with those downloadable software I can't erase my startup disk.
Please help

You have found the forums for pre-2006 Mac tower computers that cannot run OS 10.7. Can you further identify your model so we can get the hosts to move your question to a more appropriate forum?
And there is no such thing as "Mountain Tiger." There is "Lion" and "Mountain Lion," but no such alpine modifiers for "Tiger" (Mac OS 10.4.11)

PXI invalid sytem disk

Similar Messages

Maybe you are looking for