rdenney Posted November 19, 2012 Share Posted November 19, 2012 I just upgraded to the Plus version and added a drive, following the instructions in the user manual. The user manual says to stop the array, do a clean powerdown, add the drive, restart the system, and assign the drive to the array. The drive was actually already in the system, but the Plus registration key just made it possible to add it to the array. When I did that, it started an extensive preclear process. I then went out of town on business. Sometime much later, I received an email notification that the array was up, so I assumed I was in business. Looking at it today, a week after the above, the drive shows a green ball, but the "used" column on the Main tab shows "unformatted". I gather this merely means it does not contain the Reiser filesystem. Perhaps it has an NTFS filesystem--I might have checked this drive out under Windows, including a format. I know I checked one of the two Seagate drives in my array (the other one is mounted normally and works fine--it was part of the Basic array before upgrading to Plus), but one is never exactly sure which disk is which. This newly added Seagate disk is shown as Disk 3 in the Main tab. Linux and UNRAID both show the physical drive as /dev/sde. (sda is a Windows drive that I'm ignoring in UNRAID--to boot the machine when I pull the flash drive if needed. sdb through sde are the four drives in the array, including the parity drive.) I followed the instructions in "Check Disk Filesystems" on the Wiki. I stopped the array, and restarted it in Maintenance Mode, as instructed. I then ran reiserfsck as instructed, as follows: root@Tower:~# reiserfsck --check /dev/md3 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/md3. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. reiserfsck reports expected things ("Replaying journal: Done", etc.) for /dev/md1 and /dev/md2, which I assume (because God knows I don't know how to know for sure) are Disk1 and Disk2 in the array, with the parity drive, /dev/sdb, not being mounted per se. I do at least know that the new disk is /dev/sde. In this post: http://lime-technology.com/forum/index.php?topic=23588.msg208032#msg208032, Joe gave the advice to do the following: root@Tower:~# fdisk -l /dev/sde Disk /dev/sde: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. I gather this is normal partition information, showing /dev/sde1 as a normal partition. Other disks read the same. I then followed the next instruction, which was the following: root@Tower:~# dd if=/dev/sde count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00655669 s, 15.2 MB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 p 210 340 350 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0032256 353 R 220 N T F S \0 002 001 \0 \0 0032272 \0 \0 \0 \0 \0 370 \0 \0 ? \0 377 \0 ? \0 \0 \0 0032288 \0 \0 \0 \0 200 \0 200 \0 201 > \0 \0 \0 \0 \0 \0 0032304 326 024 \0 \0 \0 \0 \0 \0 @ 037 \0 \0 \0 \0 \0 \0 0032320 002 \0 \0 \0 \b \0 \0 \0 247 030 271 250 9 271 250 226 0032336 \0 \0 \0 \0 372 3 300 216 320 274 \0 | 373 270 300 \a 0032352 216 330 350 026 \0 270 \0 \r 216 300 3 333 306 006 016 \0 0032368 020 350 S \0 h \0 \r h j 002 313 212 026 $ \0 264 0032384 \b 315 023 s 005 271 377 377 212 361 f 017 266 306 @ f 0032400 017 266 321 200 342 ? 367 342 206 315 300 355 006 A f 017 0032416 267 311 f 367 341 f 243 \0 303 264 A 273 252 U 212 0032432 026 $ \0 315 023 r 017 201 373 U 252 u \t 366 301 001 0032448 t 004 376 006 024 \0 303 f ` 036 006 f 241 020 \0 f 0032464 003 006 034 \0 f ; 006 \0 017 202 : \0 036 f j 0032480 \0 f P 006 S f h 020 \0 001 \0 200 > 024 \0 \0 0032496 017 205 \f \0 350 263 377 200 > 024 \0 \0 017 204 a \0 0032512 264 B 212 026 $ \0 026 037 213 364 315 023 f X [ \a 0032528 f X f X 037 353 - f 3 322 f 017 267 016 030 \0 0032544 f 367 361 376 302 212 312 f 213 320 f 301 352 020 367 6 0032560 032 \0 206 326 212 026 $ \0 212 350 300 344 006 \n 314 270 0032576 001 002 315 023 017 202 031 \0 214 300 005 \0 216 300 f 0032592 377 006 020 \0 377 016 016 \0 017 205 o 377 \a 037 f a That and the next instruction, which I also followed, finds nothing on the device that reads "R e I s E r...". I do see a mention in the above of "NTFS", which suggests to me that this partition was formatted for NTFS and UNRAID did not reorganize it as with the Reiser filesystem when it set up the disk for use in UNRAID. I'm warned in many places not to attempt to create a Reiser filesystem without expert help, and I take that advice very seriously. That's the reason for this post. There is no data on the new drive that I care about, and I just want to start over with it. I was tempted to repartition it, but that apparently requires a special script, and that's probably the script that failed to redefine this partition as a Reiser filesystem. Frankly, I wouldn't have thought this would be so difficult--I expect many people are repurposing old PC's for use with UNRAID, and would be attaching old NTFS-formatted drives. But the manual's big weakness is that (like the manuals I usually write), it says what should happen, but provides no explanation or course of action if what actually happens is something different. I sympathize--I wouldn't even know where to begin. I do not want to ruin this hard disk before even having a chance to use it. Advice on how to proceed respectfully requested. Rick "running UNRAID 5.0-rc8a, as required to get the LSI9210 card working, but with a modification from another user to provide support for a Realtek 8169 ethernet card" Denney Link to comment
lionelhutz Posted November 19, 2012 Share Posted November 19, 2012 Adding a drive to the array won't format it. You have to do that youself using the web interface. Link to comment
rdenney Posted November 19, 2012 Author Share Posted November 19, 2012 Adding a drive to the array won't format it. You have to do that youself using the web interface. Could you give me a clue as to where and how to do that? I find nothing in the Web GUI that formats a disk, and I've searched, read the FAQ, and read the manual, ad infinitum. I'm sure it's in some obvious place, but so far I've looked right over it. The unofficial version of the user manual says the same thing, but I'll be damned if I can find the "format" button on the user interface. And which user interface? There are several, and they differ by version of the software, too. I've added the Simple-Features, but my understanding was that it did not block any of the functionality of the web GUI. I could not find it in the UnMENU, either, despite that I suspect that menu system is somewhat out of date. The "official" version of the manual, and also the "UnRAID Manual 5" version on the Wiki, say this: When you Start the array, the system will first format the new disk(s). When this operation finishes, all the data disks, including the new one(s), will be exported and be available for use. Rick "who does try to answer questions on his own before asking" Denney Link to comment
Joe L. Posted November 19, 2012 Share Posted November 19, 2012 A screen shot and a copy of your syslog is in order. Have you started the array? (Check the I'm sure box below the button and then click "Start") The "Format" button should then be present. If not, the screen shot and syslog should yield clues. It does not appear the disk was cleared (or else the NTFS string would have been gone, but it is at a low address on the disk, possibly prior to the normal start of the reiser File System at sector 63. If you've not formatted the disk, I would not expect any reiserfs string at all. Joe L. Link to comment
rdenney Posted November 19, 2012 Author Share Posted November 19, 2012 A screen shot and a copy of your syslog is in order. Have you started the array? (Check the I'm sure box below the button and then click "Start") The "Format" button should then be present. If not, the screen shot and syslog should yield clues. It does not appear the disk was cleared (or else the NTFS string would have been gone, but it is at a low address on the disk, possibly prior to the normal start of the reiser File System at sector 63. If you've not formatted the disk, I would not expect any reiserfs string at all. Joe L. Yes, the array was started. I've started it in maintenance mode, stopped it, and started it in regular mode. Several times. I've even unassigned that disk from the array and reassigned it. Could I impose on you to provide a screen shot showing where the format button is, so that I'll know where to look for it? Maybe it's hiding in plain sight and I've just missed it. Under what conditions does that button appear or not appear? I can provide a screenshot of the syslog tonight when I'm back home. But I would hope that this doesn't require that much depth to solve the mystery. Rick "fully capable of missing the obvious" Denney Link to comment
rdenney Posted November 19, 2012 Author Share Posted November 19, 2012 Okay, I saw in another thread where the Format button is supposed to be. I have not seen it there, but will confirm and then I'll know that whatever switch causes it to appear isn't doing so. Rick "syslog and screenshot forthcoming" Denney Link to comment
rdenney Posted November 20, 2012 Author Share Posted November 20, 2012 Okay, so I'm freaking blind. Right there on the Main page was the check box to allow me to press the format button. Sheesh. I must have truly been non compos mentis last night. The format took only a few minutes and now I'm doing a full parity check. Moving about 110MB/s, which seems fast enough. Thanks for putting up with me. Rick "in business for now" Denney Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.