May 12, 200818 yr Hi all, I upgraded from 4.2.1 to 4.3-beta6 tonight, and afterwards on of my drives was marked as missing. At first I thought it was just an issue with a recent replacement of a bad data drive. So I went to the devices pane, and selected the only remaining drive. Then I went back to the main page and tried to start the array. It won't start, even though the configuration is valid. Here's what the system log says: May 11 21:02:08 storage kernel: md3: wrong May 11 21:02:09 storage emhttp: shcmd (15): killall -w smbd nmbd May 11 21:02:10 storage emhttp: shcmd (16): /usr/sbin/nmbd -D May 11 21:02:10 storage emhttp: shcmd (17): /usr/sbin/smbd -D May 11 21:02:10 storage emhttp: writing mbr on disk 3 (/dev/hdc) May 11 21:02:10 storage kernel: hdc: unknown partition table May 11 21:02:11 storage kernel: md3: wrong May 11 21:02:11 storage kernel: mdcmd (6): start May 11 21:02:11 storage kernel: md3: wrong May 11 21:02:11 storage kernel: md: do_run: lock_rdev error: -6 May 11 21:02:11 storage kernel: md0: stopping May 11 21:02:11 storage kernel: md1: stopping May 11 21:02:11 storage kernel: md2: stopping May 11 21:02:11 storage kernel: md3: stopping May 11 21:02:11 storage kernel: md4: stopping May 11 21:02:11 storage kernel: md5: stopping May 11 21:02:11 storage emhttp: shcmd (18): killall -HUP smbd I downgraded to 4.2.4 and everything is well again. Here's the ID of the "missing" drive: WDC WD2500JB-00GVA0/WD-WCAL71039581. The device page had an ID with "%" in it, which seemed odd to me. Actually, check that... I clicked start several times and it refused to start. I'm trying a restore now. 3 of my 5 disks are taking a while to mount. Is this standard procedure after an upgrade? I don't remember doing it before. Gah! Now disk3 is coming up unformatted! Hm... I'm going to try reverting to 4.2.1. I'll also do some research on the forums. Thanks, David
Archived
This topic is now archived and is closed to further replies.