System Forgets DASM Setup on Every System Reboot Since 11.1 Software Upgrade FMI 60747 Installation due to Software Bug…
System Forgets DASM Setup on Every System Reboot Since 11.1 Software Upgrade FMI 60747 Installation due to Software Bug in 11.1 M4 Software.
Symptom
System Forgets DASM Setup on Every System Reboot Since 11.1 Software Upgrade FMI 60747 Installation See Long Description Since FMI 60747 "11.1 M4 Release with Customer Letter" was installed to upgrade the system from 11.0 to 11.1 software, the customer reports they are unable to film following a system reboot. The FE has to go to the site and reinstall the DASM in software to get it working again. Then, on the next system reboot, the system "forgets" the DASM again and the process repeats. The customer sees a message, which is not logged, in the /usr/g/service/log/gesys*log, as follows: Unable to communicate with camera . If you view the /export/home/sdc/logfiles/prslog (print server log), you will see a series of entries as shown in this example: MESSAGE from Process 15012>> Wed Nov 19 18:57:20 2008 (prscommon.c:54) [PRSserver]> Print job started MESSAGE from Process 15012>> Wed Nov 19 18:57:21 2008 (prsjob.c:436) [PRSserver]> The printer interface was unable to open the SCSI device driver. Please resume the print job in the Film Queue. MESSAGE from Process 15012>> Wed Nov 19 18:57:21 2008 (prsjob.c:438) [PRSserver]> Unable to communicate with camera. MESSAGE from Process 15012>> Wed Nov 19 18:57:21 2008 (prscommand.c:675) Paused Ex: 1000 Se: 1 Im: 1 Laser Camera MESSAGE from Process 15012>> Wed Nov 19 18:57:21 2008 (prscommand.c:676) [PRSserver]> Paused print job: Ex: 1000 Se: 1 Im: 1 Laser Camera MESSAGE from Process 18220>> Wed Nov 19 18:58:29 2008 (prscommon.c:54) [PRSserver]> Print job started MESSAGE from Process 18220>> Wed Nov 19 18:58:34 2008 (prsjob.c:298) [PRSserver]> Failure opening or reading film file /export/home/sdc/film/job0XCQ84R MESSAGE from Process 18220>> Wed Nov 19 18:58:34 2008 (prscommand.c:683) Aborted Ex: 1000 Se: 1 Im: 1 Laser Camera Without doing anything else, on a reboot: if you go to a C Shell and type showdasm you see the following error which means the DASM is not installed or not configured in software: scsi_open: /dev/dasm1 open failed - errno 2 Could not initialize_scsi status = ffffffff iTraks # 13227519 and # 13227554 have been submitted for this problem.
Error message
Unable to Communicate with the Camera Could not initialize_scsi status = ffffffff See Long Description Error occurs when running showdasm command. See typical session below from a 9.1 M4 system and the resulting error in red. lx-mr# su root [Enter] [enter root password] lx-mr# showdasm [Enter] set environment variable FILM_DASM_DEV appropriately lx-mr# setenv FILM_DASM_DEV /dev/dasm1 [Enter] lx-mr# ./showdasm [Enter] Could not initialize_scsi status = ffffffff
Applies to
- Models
- Excite
- Product
- Excite Includes Excite 1 and Excite 2, 10.0, 11.0 and 11.1 Software.
- Software
- 11.1 For product 1.5T Excite only. Note, 3T Excite goes with software G3, not 11.0 or 11.1.
- Area
- MR
Full cause & step-by-step resolution
The complete cause analysis, the step-by-step remedy for this GE Healthcare MR issue are available to FSELIB subscribers — re-authored, web-first, searchable.
7-day free trial · no credit card required
Related GE Healthcare MR issues
- TPS/MGD fails to download or reset. mgd_term windows fail to mount file system.
- The Carriage Fails to Advance to Latch to the Table and to Retract When it is Raised, Undocked or Lowered.
- Unable to Load Applications Software during restoreinfo Due to Corrupt saveinfo Disk.
- CWA ID100315. Auto and Manual Prescan Fails.
- Ghosted or Smeared Head Images Using Head Coil due to Head TR Assembly.
- A Copper Coolant Line or Pipe Internal to the MCS Cabinet Chiller Burst due to Water Remaining in Unit Freezing During Shipment.