How to replace a failed HD?

StorCenter ix2-200 Network Storage
eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

How to replace a failed HD?

Post by eyp » Mon Mar 31, 2014 8:19 pm

Hi, one of the 2TB drives failed so I've purchased a new one.

Now I've put it into the device and a /dev/md0 20GB mirror has been created automatically, but the other (1.8TB) one not.
What must I do?, I've tried to recreate the mirror device, but it gives me errors:

Code: Select all

root@ix2-200-D8S0EN:/# mdadm --create --verbose /dev/md1 --metadata 1 --level=mirror --raid-devices=2 /dev/sda2 /dev/sdb2
mdadm: /dev/sda2 appears to be part of a raid array:
    level=raid1 devices=2 ctime=Tue Jan 21 21:37:30 2014
mdadm: Cannot open /dev/sdb2: No such device or address
mdadm: create aborted
How I should create the /dev/sdb2 partition? Why it not created the partition automatically as the /dev/sdb1?

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: How to replace a failed HD?

Post by Mijzelf » Tue Apr 01, 2014 6:46 pm

Can you post the output of

Code: Select all

cat /proc/partitions
I wonder if you new disk is a little bit too small.

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Tue Apr 01, 2014 7:36 pm

No, it isn't, but there isn't a sdb2 partition. Must I create a partition myself?

Code: Select all

cat /proc/partitions
major minor  #blocks  name

   7        0     604505 loop0
   7        1       8192 loop1
   7        2        204 loop2
   8        0 1953514584 sda
   8        1   20980888 sda1
   8        2 1932533625 sda2
   8       16 1953514584 sdb
   8       17   20980888 sdb1
  31        0        768 mtdblock0
  31        1         16 mtdblock1
  31        2       3072 mtdblock2
  31        3       3072 mtdblock3
  31        4      32768 mtdblock4
   9        0   20980800 md0
 253        0    4194304 dm-0
 253        1   16785408 dm-1

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: How to replace a failed HD?

Post by Mijzelf » Wed Apr 02, 2014 7:28 am

It won't hurt, although the firmware sshould do it. And then you can add the partition to your existing array:

Code: Select all

mdadm --add /dev/md1 /dev/sdb2

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Wed Apr 02, 2014 8:29 am

Mijzelf wrote:It won't hurt, although the firmware sshould do it. And then you can add the partition to your existing array:

Code: Select all

mdadm --add /dev/md1 /dev/sdb2
I'm wondering why there is an sdb1 partition but not an sdb2, so why the firmware didn't create it? which could be the reason for that?

As it looks like that the firmware hasn't created the partition, how must I create it?, must I use lvm?, how is the best way to do it?. I don't want to plug the HD in another computer, I'd like to
do it in the NAS itself.

Thanks in advance.

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: How to replace a failed HD?

Post by Mijzelf » Wed Apr 02, 2014 10:38 am

Don't know why the firmware failed to do so. My first guess was a slightly too small disk, but that's not true.

You'll need to use parted to create that partition. You can also use it to look a the partition table of the old disk:

Code: Select all

parted /dev/sda unit s print
And then you can just add it to the current raid array. In that case you don't need to worry about LVM, as that is inside the raidarray.

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Wed Apr 02, 2014 10:39 am

Ok, thank you. I'll try it when I am at home this afternoon.

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Thu Apr 03, 2014 7:53 am

Mijzelf wrote:Don't know why the firmware failed to do so. My first guess was a slightly too small disk, but that's not true.

You'll need to use parted to create that partition. You can also use it to look a the partition table of the old disk:

Code: Select all

parted /dev/sda unit s print
And then you can just add it to the current raid array. In that case you don't need to worry about LVM, as that is inside the raidarray.
Yesterday I created the new partition /dev/sdb2 with parted command and added the new partition to the RAID array.
Everything went right, the array was rebuilt and the data is accesible. BUT... there's still a red light blinking.

Before I put the new HD in the red light was already blinking, but I thought it was because it noticed that an HD was missing, but now that the new HD is in and
configured I can't imagine what the problem is :?:

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: How to replace a failed HD?

Post by Mijzelf » Thu Apr 03, 2014 10:19 am

Did you already reboot the box, after the rebuild finished?

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Thu Apr 03, 2014 10:21 am

Mijzelf wrote:Did you already reboot the box, after the rebuild finished?
Nop, I only verified that the data was there and I was happy with that LOL.

Ok, I'll do it today. Why should I reboot it?

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: How to replace a failed HD?

Post by Mijzelf » Thu Apr 03, 2014 10:52 am

The box has detected a degraded array, and for that reason the red led is flashing (I guess). Now you have repaired the array behind the back of the firmware. I can imagine it didn't notice.

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Thu Apr 03, 2014 5:56 pm

Mijzelf wrote:The box has detected a degraded array, and for that reason the red led is flashing (I guess). Now you have repaired the array behind the back of the firmware. I can imagine it didn't notice.
I don't understand anything. I've restarted the device through the web interface.
After being restarted the /dev/md1 (data array) is not assembled :?:

Code: Select all

cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
md0 : active raid1 sda1[0] sdb1[1]
      20980800 blocks [2/2] [UU]

unused devices: <none>
root@ix2-200-D8S0EN:/# cat /proc/partitions
major minor  #blocks  name

   7        0     604505 loop0
   7        1       8192 loop1
   7        2        204 loop2
   8        0 1953514584 sda
   8        1   20980888 sda1
   8        2 1932533625 sda2
   8       16 1953514584 sdb
   8       17   20980888 sdb1
   8       18 1932533625 sdb2
  31        0        768 mtdblock0
  31        1         16 mtdblock1
  31        2       3072 mtdblock2
  31        3       3072 mtdblock3
  31        4      32768 mtdblock4
   9        0   20980800 md0
 253        0    4194304 dm-0
 253        1   16785408 dm-1
I've assembled the other array again, but I supose it'll fail when I restart the NAS... Furthermore, the data that was before restarting is not there...
I don't know if it'll appear after a while.

Code: Select all

mdadm --assemble --scan
/dev/md1: File exists
mdadm: /dev/md/1 has been started with 2 drives.
And this is the dmesg output:

Code: Select all

   32regs    :   668.800 MB/sec
xor: using function: arm4regs (870.800 MB/sec)
NET: Registered protocol family 16
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
PEX1_MEM ....no such
PEX1_IO ....no such
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6281A  Soc: 88F6281 A0 LE

 Detected Tclk 200000000 and SysClk 333333333
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c8040740
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
mvPexLocalBusNumSet: ERR. Invalid PEX interface 1
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
raid6: int32x1     76 MB/s
raid6: int32x2     91 MB/s
raid6: int32x4    100 MB/s
raid6: int32x8     78 MB/s
raid6: using algorithm int32x4 (100 MB/s)
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 2724K
rtc mv_rtc: rtc core: registered kw-rtc as rtc0
RTC registered
mp_lm63: device lm63 found
mp_lm63: Alert/tach pin configured for tachometer input
mp_lm63: PWM clock 1.4 kHz, output frequency 22 Hz
mp_lm63: PWM output active high, auto mode
mp_lm63: Module loaded.
cpufreq: Init kirkwood cpufreq driver
cpufreq: High frequency: 1000000KHz - Low frequency: 333333KHz
cpufreq: Setting CPU Frequency to 1000000 KHz
cpufreq: Setting PowerSaveState to off
cpufreq: Setting CPU Frequency to 1000000 KHz
cpufreq: Setting PowerSaveState to off
XOR registered 4 channels
XOR 2nd invalidate WA enabled
cesadev_init(c000ed48)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
MV Buttons Driver Load
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 485
alg: No test for cipher_null (cipher_null-generic)
alg: No test for ecb(cipher_null) (ecb-cipher_null)
alg: No test for digest_null (digest_null-generic)
alg: No test for compress_null (compress_null-generic)
alg: No test for stdrng (krng)
alg: No test for hmac(digest_null) (hmac(digest_null-generic))
async_tx: api initialized (sync-only)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
Integrated Sata device found
IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
[0 0]: SATA disk found
[0 0]: Disk ready
[0 0]: Sata device ready
[0 1]: SATA disk found
[0 1]: Disk ready
[0 1]: Sata device ready
scsi 0:0:0:0: Direct-Access     Seagate  ST2000DM001-9YN1 CC4B PQ: 0 ANSI: 5
Linux IAL (ERROR) [0 0 0]: set device max sectors to 2048
scsi 1:0:0:0: Direct-Access     Seagate  ST2000DM001-1CH1 CC27 PQ: 0 ANSI: 5
Linux IAL (ERROR) [0 1 0]: set device max sectors to 2048
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sda] 0-byte physical blocks
SAL (ERROR)  0 0 0 :Scsi command completed. pScb c44d3de0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
SAL (ERROR)  0 0 0 :Scsi command completed. pScb c44d3de0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] 0-byte physical blocks
SAL (ERROR)  0 1 0 :Scsi command completed. pScb c44d3de0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
SAL (ERROR)  0 0 0 :Scsi command completed. pScb c44d3de0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
SAL (ERROR)  0 0 0 :Scsi command completed. pScb c44d3de0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o 2 Giga ports supported
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload (TSO) supported
  o Receive checksum offload supported
  o Transmit checksum offload supported
  o Network Fast Processing (Routing) supported - (Disabled)
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o SKB Reuse supported - (Disabled)
  o SKB Recycle supported - (Disabled)
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
     o register under mv88fx_eth platform
 sda:SAL (ERROR)  0 1 0 :Scsi command completed. pScb c8589f60, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
     o eth0, ifindex = 2, GbE port = 0
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 23 00 10 00
     o eth1, ifindex = 3, GbE port = 1

mvFpRuleDb (c8596000): 2048 entries, 8192 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
SAL (ERROR)  0 1 0 :Scsi command completed. pScb c851d3c0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
SAL (ERROR)  0 1 0 :Scsi command completed. pScb c852b0c0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
GPT:disk_guids don't match.
GPT:partition_entry_array_crc32 values don't match: 0xb40a6566 != 0x9d7ce8a2
GPT: Use GNU Parted to correct GPT errors.
 sda1 sda2
 sdb:
NAND device: Manufacturer ID: 0xad, Chip ID: 0x75 (Hynix NAND 32MiB 3,3V 8-bit)
Scanning device for bad blocks
5 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 5 MTD partitions on "nand_mtd":
0x000000000000-0x0000000c0000 : "uboot"
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
SAL (ERROR)  0 0 0 :Scsi command completed. pScb c852b0c0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
SAL (ERROR)  0 0 0 :Scsi command completed. pScb c851d3c0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
0x000000084000-0x000000088000 : "env"
sd 0:0:0:0: [sda] Attached SCSI disk
0x000000100000-0x000000400000 : "zImage"
0x000000540000-0x000000840000 : "initrd"
0x000000000000-0x000002000000 : "flash"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
 sdb1 sdb2
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
SAL (ERROR)  0 1 0 :Scsi command completed. pScb c852b0c0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
SAL (ERROR)  0 1 0 :Scsi command completed. pScb c852b0c0, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_BAD_SCSI_COMMAND
SAL (ERROR) CDB:12 1 0 0 ff 0
SAL (ERROR) Sense Data:72 5 24 0 0 0 0 c 0 0 0 0 0 0 0 0 0 0 0 0
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
sd 1:0:0:0: [sdb] Attached SCSI disk
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
cpufreq: Setting CPU Frequency to 1000000 KHz
cpufreq: Setting PowerSaveState to off
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc mv_rtc: setting system clock to 2014-04-03 17:51:05 UTC (1396547465)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
RAMDISK: gzip image found at block 0
usb 1-1: new high speed USB device using ehci_marvell and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 1:0.
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 21484339200
 md0: unknown partition table
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Bluetooth: L2CAP ver 2.13
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
ufsd: driver 8.5 (Apr 16 2012 15:00:27) LBD=ON with delayalloc with ioctl loaded at bf0ae000
NTFS support included
Hfs+/HfsX support included
Built for: EMC_ix2_2
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
Freeing init memory: 136K
eth1: link up, full duplex, speed 100 Mbps
eth1: started
eth1: stopped
eth1: link up, full duplex, speed 100 Mbps
eth1: started
eth1: change mtu 1500 (buffer-size 1536) to 9000 (buffer-size 9024)
XFS mounting filesystem dm-1
Ending clean XFS mount for filesystem: dm-1
Adding 524280k swap on /mnt/system/swapfile.  Priority:-1 extents:5 across:4626708k
Uncached vma cef6e288 (addr 4842b000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c746e5f8 (addr 405c6000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c21523e8 (addr 405f2000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c3902a70 (addr 4bb83000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c215c230 (addr 40c28000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c21df288 (addr 40637000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c7df1a18 (addr 40b7f000 flags 080000d5 phy 0dd45000) from pid 2939
Uncached vma c215c910 (addr 404c7000 flags 080000d5 phy 0dd45000) from pid 2940
Uncached vma c2009c28 (addr 40637000 flags 080000d5 phy 0dd45000) from pid 2941
Uncached vma c98b1808 (addr 40b7f000 flags 080000d5 phy 0dd45000) from pid 2941
Uncached vma c215c700 (addr 404c7000 flags 080000d5 phy 0dd45000) from pid 2942
Uncached vma c7df1650 (addr 40637000 flags 080000d5 phy 0dd45000) from pid 2943
Uncached vma c75519c0 (addr 405f2000 flags 080000d5 phy 0dd45000) from pid 2944
Uncached vma c9bd3d88 (addr 405f2000 flags 080000d5 phy 0dd45000) from pid 2945
Uncached vma c6af4a18 (addr 404c7000 flags 080000d5 phy 0dd45000) from pid 2948
Uncached vma c9b6ee90 (addr 404c7000 flags 080000d5 phy 0dd45000) from pid 2949
Uncached vma c2bd1ac8 (addr 40637000 flags 080000d5 phy 0dd45000) from pid 2950
Uncached vma cc0a6b20 (addr 405f2000 flags 080000d5 phy 0dd45000) from pid 2951
Uncached vma c865ba70 (addr 405f2000 flags 080000d5 phy 0dd45000) from pid 2952
Uncached vma c98b17b0 (addr 404c7000 flags 080000d5 phy 0dd45000) from pid 2953
Uncached vma c595a968 (addr 40637000 flags 080000d5 phy 0dd45000) from pid 2954
Uncached vma c9bd3128 (addr 40c28000 flags 080000d5 phy 0dd45000) from pid 2955
Uncached vma c9b6e700 (addr 40c28000 flags 080000d5 phy 0dd45000) from pid 2966
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md1 active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 1978914291712
 md1: unknown partition table
It says md1: unknown partition table

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Fri Apr 04, 2014 6:22 am

Well, this morning all the data is again accesible in /dev/md1 but the red light is still blinking.
If I restart the NAS I'm sure it won't assemble the raid array again.

In the web admin it says the same it was saying yesterday:
There are 2 drives with existing data on your Iomega StorCenter ix2-200.
So the main problem now is knowing how must I change in order to have assembled the raid array after restarting the device.
Any ideas?

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: How to replace a failed HD?

Post by Mijzelf » Fri Apr 04, 2014 7:37 am

It says md1: unknown partition table
That is normal. The array doesn't have a partition table, it only contains an LVM

The lines 'SAL (ERROR)' are alarming. I think they point to a hardware error. Your new disk was new, I guess? Can you connect sda to a PC and let it examine by (disk) vendor diagnostic software?

/Edit: Do NOT take up a 'helpful' offer of the PC OS to 'initialize' that disk!

eyp
Posts: 44
Joined: Thu Aug 09, 2012 11:15 am

Re: How to replace a failed HD?

Post by eyp » Fri Apr 04, 2014 8:04 am

How is the best safe way to remove a drive from the NAS. Should I remove it first from the array (mdadm --remove)? Should I run any commands before
shutting down the device and extract the disk?

About eximining the disk, do you mean checking it for bad sectors?

Post Reply