RAID1に設定したSR3610-2S-SB2に対して、家庭内サーバからUSB2.0でmountをおこない、データを書き込んだ後にumountし、USBケーブルを抜いた。
その後、USB経由で手元のLinux Note PCに同RAID箱を挿すとこういうログ。
Oct 16 13:26:40 hong kernel: usb 3-3: new high speed USB device using ehci_hcd and address 3
Oct 16 13:26:41 hong kernel: Initializing USB Mass Storage driver...
Oct 16 13:26:41 hong kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Oct 16 13:26:41 hong kernel: usbcore: registered new driver usb-storage
Oct 16 13:26:41 hong kernel: USB Mass Storage support registered.
Oct 16 13:26:41 hong usb.agent[9983]: usb-storage: loaded successfully
Oct 16 13:26:46 hong kernel: Vendor: STARDOM Model: V.36.A03 Rev: 0000
Oct 16 13:26:46 hong kernel: Type: Direct-Access ANSI SCSI revision: 00
Oct 16 13:26:47 hong kernel: SCSI device sda: 976794112 512-byte hdwr sectors (500119 MB)
Oct 16 13:26:47 hong kernel: SCSI device sda: 976794112 512-byte hdwr sectors (500119 MB)
Oct 16 13:26:47 hong scsi.agent[10045]: sd_mod: loaded successfully (for disk)
Oct 16 13:26:47 hong kernel: sda: sda1
Oct 16 13:26:47 hong kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
しかしなぜか
# mount -t ext3 /dev/sda1 /mnt/floppy/
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
と言われ、mount出来ない。
RAID箱のLCD表示もなんだか変わっている。
LCDをよく見ると、RAID0の設定になっているようだ。
また、ログも/dev/sdaが500GBになっている。あれれ?
250GBのHDDでRAID1なので、250GBのはずだが。
とりあえずRAID箱の設定スイッチからRAID1に設定を戻してみる。
「データが壊れるよ!」と警告がでるけど、仕方なく進む。
もう一度Linux Note PCにつなぎ直すが、パーティションテーブルが壊れているので、試しにfdiskとe2fsckをば。
# e2fsck /dev/sda1
e2fsck 1.38 (30-Jun-2005)
e2fsck: そのようなデバイスやアドレスはありません while trying to open /dev/sda1
Possibly non-existent or swap device?
# fdisk /dev/sda
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 30401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): p
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-30401, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-30401, default 30401):
Using default value 30401
Command (m for help): p
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 83 Linux
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
# e2fsck /dev/sda1
e2fsck 1.38 (30-Jun-2005)
/dev/sda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 125/30539776 files (2.4% non-contiguous), 11491010/61049000 blocks
#
安定稼働の道は険しいなぁ。
ps.
その後何度か電源off/onをおこなったり、USBケーブル抜き差ししたけど、
RAIDタイプが変わることはなかった。
シリアル経由で何か悪さをしたことになるのかなぁ。
0 件のコメント:
コメントを投稿