HP boot up fails when checking file systems Due to Corrupted Software.
Symptom
HP boot up fails when checking file systems See long description The screen displays the following: Checking filesystems Fsck.ext2: /dev/sda1: The super block could not be read or does not describe a correct ext2 file systems. If the device is valid and it really contains an ext2 file system (and not swap or ufs or something else), then the super block is corrupt, and you might try running e2fsck with an alternate super block: E2fsck –b 8193 <device> No medium found while trying to open /dev/sda1 [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell: the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue):
Error message
The super block could not be read or does not describe a correct ext2 file system.
Applies to
- Models
- Excite
- Product
- Excite Includes Excite 1 and Excite 2, 10.0, 11.0 and 11.1 Software.
- Software
- 11.0 Only for 1.5T Excite product. 12.0 is Excite HD and 14.0 is Excite HDx. 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.