03-09-2009
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
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi, I'm stuck in an awkward situation please help :)
I have two identical Seagate 80GB harddrives.
My objective is a bit strange.
1.I want to have a cloned disk as bootable backup
2.When booting using the master drive, I also want to mount the cloned backup disk so I can do incremental... (6 Replies)
Discussion started by: onthetopo
6 Replies
2. Solaris
Hi All,
I need help on this issue and it is a production server.
/usr is unable to mount and make system can't even type any commands.
Only this show and no changes makes to the system.
ERROR: svc:/system/filesystem/root:default failed to mount /usr (see 'svcs -x'
for details) ... (3 Replies)
Discussion started by: mailbox80
3 Replies
3. Solaris
Hi,
I am running Solaris 8 on a V880 which has recently crashed. It has got a fibre connection to a StorageTrek array containing my database info. Since the crash I have been unable to mount the 2 metadevices which correspond to /spool & /apps - these FS's contain my db info and theredore I... (20 Replies)
Discussion started by: Duffs
20 Replies
4. Fedora
Hi,
I'm new for unix. I tried to mount windows NTFS partition in Fedora unix, but it is saying ntfs not found. The command i used is
mount /dev/sdb1 -t ntfs /mnt/drive1
and how to find the available filesystem type?. (1 Reply)
Discussion started by: gwgreen1
1 Replies
5. Shell Programming and Scripting
Hi there
i need a way ( some sort of script maybe) to check if a mont point exist when but the physical drive does not
for example if i look in / and see that user_data2 directory exist but there is no user_data2 drive.
another hurdle would be that some of the machines have raided drives... (3 Replies)
Discussion started by: ab52
3 Replies
6. Solaris
had a D1000 connected to this Solaris10 server, for a while, everything worked good ..until today..
it can't find the other half of D1000 disks at all..all LEDs on the D1000 are in green..kept getting the below:
Dec 19 17:10:34 tocbs103 glm: WARNING: ID
Dec 19 17:10:34 tocbs103 scsi: ... (2 Replies)
Discussion started by: ppchu99
2 Replies
7. UNIX for Dummies Questions & Answers
Hi
I have created a RHEL6 machine that is hosted on VMWare player that in turn runs off my Windows 7 PC.
When I try and mount the CDROM on the RHEL6 box I get the following output:
$ mount /dev/cdrom/media
mount: can't find /dev/cdrom/media in /etc/fstab or /etc/mtab
$
Here is the... (3 Replies)
Discussion started by: accipiter1
3 Replies
8. UNIX for Dummies Questions & Answers
hi
Am trying to mount a cdrom which has a blank cd into it, using the command:
mount -v cdrfs -o ro /dev/cd0 /mnt
Am getting this error:
# df -Ig
Filesystem GB blocks Used Free %Used Mounted on
/dev/hd4 0.50 0.19 0.31 38% /
/dev/hd2 ... (1 Reply)
Discussion started by: kamaldev
1 Replies
9. Red Hat
Hi,
I am unable to mount the AIX share on Red Hat Linux 5.5
getting below error on linux server while mounting.
reason given by server: unknown nfs status return value: -1
I have checked on AIX side.
lssrc -g nfs showing below output.
bash-3.00# lssrc -g nfs
Subsystem ... (2 Replies)
Discussion started by: manoj.solaris
2 Replies
10. UNIX for Dummies Questions & Answers
Hello,
While mounting NFS below error is coming:
# mount -t nfs 10.65.150.69:/lvsnap /lvsnap
mount: mount to NFS server '10.65.150.69' failed: RPC Error: Program not registered.
Please advise.
Best regards,
Vishal (2 Replies)
Discussion started by: admin_db
2 Replies
IOSTAT(1) General Commands Manual IOSTAT(1)
NAME
iostat - report I/O statistics
SYNOPSIS
iostat [ drives ] [ interval [ count ] ]
DESCRIPTION
Iostat iteratively reports the number of characters read and written to terminals per second, and, for each disk, the number of transfers
per second, kilobytes transferred per second, and the milliseconds per average seek. It also gives the percentage of time the system has
spent in user mode, in user mode running low priority (niced) processes, in system mode, and idling.
To compute this information, for each disk, seeks and data transfer completions and number of words transferred are counted; for terminals
collectively, the number of input and output characters are counted. Also, each sixtieth of a second, the state of each disk is examined
and a tally is made if the disk is active. From these numbers and given the transfer rates of the devices it is possible to determine
average seek times for each device.
The optional interval argument causes iostat to report once each interval seconds. The first report is for all time since a reboot and
each subsequent report is for the last interval only.
The optional count argument restricts the number of reports.
If more than 4 disk drives are configured in the system, iostat displays only the first 4 drives, with priority given to Massbus disk
drives (i.e. if both Unibus and Massbus drives are present and the total number of drives exceeds 4, then some number of Unibus drives will
not be displayed in favor of the Massbus drives). To force iostat to display specific drives, their names may be supplied on the command
line.
FILES
/dev/kmem
/vmunix
SEE ALSO
vmstat(1)
4th Berkeley Distribution April 29, 1985 IOSTAT(1)