October 4, 201015 yr I had finished my pre clear and was in the middle of the format (I think... It had been a while since I checked) on my new rig with 5 2tb drives and the transformer blew outside. Sooo... How screwed am I? Do I need to reformat only? Or start all over again? Preclear took 28 hours... Formatting was on like hour 6.
October 4, 201015 yr I had finished my pre clear and was in the middle of the format (I think... It had been a while since I checked) on my new rig with 5 2tb drives and the transformer blew outside. Sooo... How screwed am I? Do I need to reformat only? Or start all over again? Preclear took 28 hours... Formatting was on like hour 6. Formatting ANY drive should only take a minute or two. Something else was going on. You probably just need to re-format. Make sure you are NOT on version 4.5.3 of unRAID. It had a format related bug where all the drives would show as unformatted, and all would be formatted when you press "Format", even those with data. Joe L.
October 4, 201015 yr Author Errr... Crap. Is it because it was trying to format and build parity at the same time?
October 4, 201015 yr Errr... Crap. Is it because it was trying to format and build parity at the same time? Don't know... It should not have bothered it at all. We've seen a number of kernel Oops lately. It might have been one of those. No way to know without looking at a syslog. If you want, you can run the "format" program on the command line, one disk at a time You just need to use the correct "md" device. disk1= /dev/md1, disk2 = /dev/md2, disk3 = /dev/md3, etc. So, to format disk2, as an example, type: mkreiserfs /dev/md2 after logging in as root.
October 4, 201015 yr So it's not sdx like with pre clear? No, it is not. It must be done on the "/dev/mdX" device so that parity is calculated on it. It must therefore also be done after being added (assigned to a slot) to the array and the array must be started. The disk will show as unformatted in the management web-page.
October 4, 201015 yr Author So I started the format from the GUI again and I'm still seeing it more than a minute. The Reads keep going up on my HD, the writes keep going up on my Parity, but the format goes on... here's a chunk of the syslog: Oct 4 17:26:32 Tower kernel: md: recovery thread woken up ... Oct 4 17:26:32 Tower kernel: md: recovery thread syncing parity disk ... Oct 4 17:26:32 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md4, Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md3, Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (18): exit status: 32 Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (18): exit status: 32 Oct 4 17:26:32 Tower emhttp: disk3 mount error: 32 Oct 4 17:26:32 Tower emhttp: disk4 mount error: 32 Oct 4 17:26:32 Tower emhttp: shcmd (20): rmdir /mnt/disk3 Oct 4 17:26:32 Tower emhttp: shcmd (20): rmdir /mnt/disk4 Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md2, Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md1, Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (20): exit status: 32 Oct 4 17:26:32 Tower emhttp: disk1 mount error: 32 Oct 4 17:26:32 Tower emhttp: shcmd (21): rmdir /mnt/disk1 Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (21): exit status: 32 Oct 4 17:26:32 Tower emhttp: disk2 mount error: 32 Oct 4 17:26:32 Tower emhttp: shcmd (22): rmdir /mnt/disk2 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md2): sh-2021 reiserfs_fill_super: can not find reiserfs on md2 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md1): sh-2021 reiserfs_fill_super: can not find reiserfs on md1 Oct 4 17:26:33 Tower emhttp: shcmd (26): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Oct 4 17:26:33 Tower emhttp: _shcmd: shcmd (26): exit status: 1 Oct 4 17:26:33 Tower emhttp: shcmd (27): cp /etc/exports- /etc/exports Oct 4 17:26:33 Tower emhttp: shcmd (28): killall -HUP smbd Oct 4 17:26:33 Tower emhttp: shcmd (29): /etc/rc.d/rc.nfsd restart | logger Oct 4 17:26:38 Tower ntpd[1497]: synchronized to 169.229.70.201, stratum 3 Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md1 2>&1 | logger Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md2 2>&1 | logger Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md4 2>&1 | logger Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md3 2>&1 | logger Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger:
October 4, 201015 yr So I started the format from the GUI again and I'm still seeing it more than a minute. The Reads keep going up on my HD, the writes keep going up on my Parity, but the format goes on... here's a chunk of the syslog: Oct 4 17:26:32 Tower kernel: md: recovery thread woken up ... Oct 4 17:26:32 Tower kernel: md: recovery thread syncing parity disk ... Oct 4 17:26:32 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md4, Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md3, Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (18): exit status: 32 Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (18): exit status: 32 Oct 4 17:26:32 Tower emhttp: disk3 mount error: 32 Oct 4 17:26:32 Tower emhttp: disk4 mount error: 32 Oct 4 17:26:32 Tower emhttp: shcmd (20): rmdir /mnt/disk3 Oct 4 17:26:32 Tower emhttp: shcmd (20): rmdir /mnt/disk4 Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md2, Oct 4 17:26:32 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md1, Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower logger: missing codepage or helper program, or other error Oct 4 17:26:32 Tower logger: In some cases useful info is found in syslog - try Oct 4 17:26:32 Tower logger: dmesg | tail or so Oct 4 17:26:32 Tower logger: Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (20): exit status: 32 Oct 4 17:26:32 Tower emhttp: disk1 mount error: 32 Oct 4 17:26:32 Tower emhttp: shcmd (21): rmdir /mnt/disk1 Oct 4 17:26:32 Tower emhttp: _shcmd: shcmd (21): exit status: 32 Oct 4 17:26:32 Tower emhttp: disk2 mount error: 32 Oct 4 17:26:32 Tower emhttp: shcmd (22): rmdir /mnt/disk2 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md2): sh-2021 reiserfs_fill_super: can not find reiserfs on md2 Oct 4 17:26:32 Tower kernel: REISERFS warning (device md1): sh-2021 reiserfs_fill_super: can not find reiserfs on md1 Oct 4 17:26:33 Tower emhttp: shcmd (26): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Oct 4 17:26:33 Tower emhttp: _shcmd: shcmd (26): exit status: 1 Oct 4 17:26:33 Tower emhttp: shcmd (27): cp /etc/exports- /etc/exports Oct 4 17:26:33 Tower emhttp: shcmd (28): killall -HUP smbd Oct 4 17:26:33 Tower emhttp: shcmd (29): /etc/rc.d/rc.nfsd restart | logger Oct 4 17:26:38 Tower ntpd[1497]: synchronized to 169.229.70.201, stratum 3 Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md1 2>&1 | logger Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md2 2>&1 | logger Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md4 2>&1 | logger Oct 4 17:31:09 Tower emhttp: shcmd (30): mkreiserfs -q /dev/md3 2>&1 | logger Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: Oct 4 17:31:09 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Oct 4 17:31:09 Tower logger: looks good so far. I've never tried to do more than one disk at a time. It should not take to much longer. You can see the 4 mkreiserfs commands it executed.
October 5, 201015 yr I'll bet the reads and wries have stopped incrimenting. If so, it has probably deadlocked. If deadlocked, I'd proceed like this. I'd kill the existing processes, then invoke them one at a time on the command line. To kill them type killall mkreiserfs To do each, one at a time type: mkreiserfs /dev/md1 then, when it is finished mkreiserfs /dev/md2 then, when finished mkreiserfs /dev/md3 then one last time mkreiserfs /dev/md4
October 5, 201015 yr Author No... they are slowly still going up. But I'm starting to think I need to do what you suggested.
October 5, 201015 yr No... they are slowly still going up. But I'm starting to think I need to do what you suggested. Then they are probably fighting each other for some resource. If the reads and writes are still incrementing I'd probably just let them run and sleep on it. Joe L.
October 5, 201015 yr Author Guess I should have had more patience I killed the processes and am trying them one at a time. This is what I have so far... it seems stuck right there. Guessing about desired format.. Kernel 2.6.32.9-unRAID is running. Format 3.6 with standard journal Count of blocks on the device: 488378624 Number of blocks consumed by mkreiserfs formatting process: 23116 Blocksize: 4096 Hash function used to sort names: "r5" Journal Size 8193 blocks (first block 18) Journal Max transaction length 1024 inode generation number: 0 UUID: 114df93e-4d61-4851-82d2-1544f7f66e51 ATTENTION: YOU SHOULD REBOOT AFTER FDISK! ALL DATA WILL BE LOST ON '/dev/md1'! Continue (y/n):y Initializing journal - 0%....20%....40%....60%....80%....100%
October 5, 201015 yr Well... it popped this then quit. -bash: Initializing: command not found You probably cut and pasted the "Initializing" text from the output. In putty, highlighting text automatically copies it to the clipboard. Right-click pastes it. you probably pasted it. Joe L.
October 5, 201015 yr Author Not sure... it still showed as unformatted this morning. So I pulled all the drives and re-started preclear so I can take another look at those results. So many issues I'm getting kind of worried.
Archived
This topic is now archived and is closed to further replies.