The UNIX and Linux Forums  
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.

Go Back   The UNIX and Linux Forums > Special Forums > Hardware > Filesystems, Disks and Memory
.
google unix.com



Filesystems, Disks and Memory Discuss NAS, SAN, RAID, Robotic Libraries, backup devices, RAM, DRAM, SCSI, IDE, EIDE topics here.

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
/usr unable to mount mailbox80 SUN Solaris 3 10-14-2008 11:36 PM
mount LVM duplication drives onthetopo UNIX for Advanced & Expert Users 6 08-30-2008 02:13 PM
AIX 4.3 - unable to mount one of our VG's pmcopoc AIX 0 04-15-2008 03:02 PM
USB drives find malware favour - Australian IT iBot UNIX and Linux RSS News 0 07-26-2007 12:00 AM
Unable to mount NFS share during boot jlslhills AIX 0 08-09-2005 02:55 PM

Closed Thread
English Japanese Spanish French German Portuguese Italian Dutch Swedish Russian Norwegian Hungarian Hebrew Danish Powered by Powered by Google
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old 03-09-2009
shamrocks shamrocks is offline
Registered User
  
 

Join Date: Jan 2008
Posts: 5
Unable to mount/find new drives

Hi, I work offshore and we have a system that records excessive amounts of data (Terabytes), therefore we changed the 16 x 400GB drives to 16 x 1TB drives. However, since doing this, upon bootup, the system does not recognize the new drives. These drives are external drives in a chassis which is connected to the computer via SCSI lead. See quote below email to IT assistant:

Quote:
Yesterday we switched the drive chassis off and changed the hard drives from 400 GB to 1 TB. We then switched the chassis back on and it initialized itself which took 6 hours. We did not switch off the computer at all.

We then tried to reboot the computer and the following message keeps coming up

Quote:
No such file or directory while trying to open / dev/vol1/raid1

/dev/vol1/raid1:

The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and it really contains an ext2 file system (and not swop or ufs or something else), then the superblock is corrupt and you might try running e2fsck with an alternate superblock

e2fsck –b 8193 <device> [ failed ]

it then come up with alt d for maintenance menu or enter to re-boot
Any help would be appreciated,
Kind regards
Russ
  #2 (permalink)  
Old 03-10-2009
mark54g mark54g is offline
Registered User
  
 

Join Date: May 2008
Posts: 363
google for rescan-scsi-bus.sh

run this script, then run lvmdiskscan
you should see your new drives

Otherwise, the cable is not attached/terminated properly
  #3 (permalink)  
Old 03-10-2009
shamrocks shamrocks is offline
Registered User
  
 

Join Date: Jan 2008
Posts: 5
Quote:
Originally Posted by mark54g View Post
google for rescan-scsi-bus.sh

run this script, then run lvmdiskscan
you should see your new drives

Otherwise, the cable is not attached/terminated properly

Thanks for your reply, however what I've been told, is that we can see the drives but on intial boot up reporting, it sees the SCSI and two RAID arrays connected and the first two TB slices of each array. However, we had not unmounted the old array before creating the new one. Now on boot up, the servers operating system crashes when trying to mount the new device. We can not get into a command prompt to edit the boot config file.

Any ideas?
  #4 (permalink)  
Old 03-10-2009
Radar's Avatar
Radar Radar is offline
Registered User
  
 

Join Date: Dec 2006
Location: Clifton Park, NY
Posts: 86
When you get the maintenance notification, are you able to log in with the root password?
  #5 (permalink)  
Old 03-10-2009
shamrocks shamrocks is offline
Registered User
  
 

Join Date: Jan 2008
Posts: 5
Quote:
Originally Posted by Radar View Post
When you get the maintenance notification, are you able to log in with the root password?
Upon boot up this is what they get:

Quote:
***error occurred during the file system check
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Press enter for maintenance
(or type Control-D to continue): _
When enter is pressed, a message similiar to the following appears:
Quote:
repair filesystem 1 #
if Y is entered it goes to:
Quote:
repair filesystem 2 #
if Y is entered it goes to repair filesystem 3 # and just keeps incrementing.

If N is entered it does the same thing.

What are you suppose to enter at this stage?
Kind regards
Russ

Last edited by shamrocks; 03-10-2009 at 08:06 PM..
  #6 (permalink)  
Old 03-12-2009
mark54g mark54g is offline
Registered User
  
 

Join Date: May 2008
Posts: 363
at the prompt when you boot to choose your kernel type "linux 1" and then you should be in single user mode.

Then, edit the /etc/fstab and remove the entries for the other array. You may also need to run a vgscan and do any lvremoves and vgremoves that you need to do.
Closed Thread

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT -4. The time now is 10:06 PM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited. Language Translations Powered by .
vBCredits v1.4 Copyright ©2007 - 2008, PixelFX Studios
The UNIX and Linux Forums Content Copyright ©1993-2009. All Rights Reserved.Ad Management by RedTyger

Content Relevant URLs by vBSEO 3.2.0