April 15, 201115 yr Author root@Storage:~# fdisk -l /dev/sda Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2 62016336 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Storage:~# fdisk -l /dev/sdb Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Storage:~# fdisk -l /dev/sdc Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 2 62016336 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Storage:~# fdisk -l /dev/sdd Disk /dev/sdd: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 2 62016336 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Storage:~# fdisk -l /dev/sde Disk /dev/sde: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/sde doesn't contain a valid partition table root@Storage:~# fdisk -l /dev/sdf Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdf1 1 243202 1953514552+ 0 Empty Partition 1 does not end on cylinder boundary. root@Storage:~# fdisk -l /dev/sdg Disk /dev/sdg: 4022 MB, 4022337024 bytes 255 heads, 63 sectors/track, 489 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdg1 * 1 488 3919841 b W95 FAT32 root@Storage:~# fdisk -l /dev/sdh Disk /dev/sdh: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdh1 2 62016336 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary.
April 15, 201115 yr Author root@Storage:~# fdisk -l /dev/sde Disk /dev/sde: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/sde doesn't contain a valid partition table This looks bad to me? But what do I know?
April 15, 201115 yr Your parity drive will not have a partition table, so if SDE is your parity drive then that is normal.
April 15, 201115 yr Take the cues from this thread and try removing SDE and starting the array without it. If that works, then we've identified the problem . WARNING: YOU WILL HAVE NO PARITY PROTECTION WHILE RUNNING WITH SDE REMOVED.
April 16, 201115 yr Author Apr 15 20:01:54 Storage logger: mount: wrong fs type, bad option, bad superblock on /dev/md5, Apr 15 20:01:54 Storage logger: missing codepage or helper program, or other error (Errors) Apr 15 20:01:54 Storage logger: In some cases useful info is found in syslog - try Apr 15 20:01:54 Storage logger: dmesg | tail or so Apr 15 20:01:54 Storage logger: Apr 15 20:01:54 Storage logger: mount: wrong fs type, bad option, bad superblock on /dev/md4, Apr 15 20:01:54 Storage logger: missing codepage or helper program, or other error (Errors) Apr 15 20:01:54 Storage logger: In some cases useful info is found in syslog - try Apr 15 20:01:54 Storage emhttp: _shcmd: shcmd (45): exit status: 32 (Other emhttp) Apr 15 20:01:54 Storage emhttp: disk5 mount error: 32 (Errors) Apr 15 20:01:54 Storage emhttp: shcmd (46): rmdir /mnt/disk5 (Other emhttp) Apr 15 20:01:54 Storage logger: dmesg | tail or so Apr 15 20:01:54 Storage logger: Apr 15 20:01:54 Storage emhttp: _shcmd: shcmd (46): exit status: 32 (Other emhttp) Apr 15 20:01:54 Storage emhttp: disk4 mount error: 32 (Errors) Apr 15 20:01:54 Storage emhttp: shcmd (47): rmdir /mnt/disk4 (Other emhttp)
April 16, 201115 yr Author Model / Serial No. Temperature Size Free Reads Writes Errors parity ST32000542AS_5XW1D19C 26°C 1,953,514,552 - 162 230 0 disk1 ST32000542AS_5XW18K0D 27°C 1,953,514,552 489,505,348 210 5 0 disk2 ST32000542AS_5XW2061D 29°C 1,953,514,552 474,753,588 299 5 0 disk3 ST32000542AS_5XW1BAFV 26°C 1,953,514,552 495,209,228 3,216 118 0 disk4 Not installed - 1,953,514,552 Mounting - - - disk5 WDC_WD20EARS-00M_WD-WCAZA1055519 26°C 1,953,514,552 Mounting 52 0 0 disk6 WDC_WD20EARS-00M_WD-WCAZA1055748 27°C 1,953,514,552 972,962,028 657 105 0 Server is stuck in starting and not working?! I can't stop it or reboot. Any other ideas? Getting very very frustrated
April 16, 201115 yr Don't get. frustrated, you're at least getting somewhere here. Is there anything odd about this hardware that could be related to these drives acting up, such as these drives being on a different disk controller? Was that the only errors or odd parts you saw in the syslog? You didn't include the whole thing so it's hard to know what's happening. I don't get what happened that buggered up your disks unless you have a new bad component there. unRAID will generally not do anything to a disk unless you let it. I'm sure you've seen the "expand the array" or "rebuild a drive" with the "are you sure"checkbox before. On a normal start it just uses the drives as they are. FYI, the parity drive does have a partition, it just does not have a filesystem (ie reiserfs) on it. Raw data is stored on the partition. At this point, I think you are going to have to attempt a repair on disk5 (md5) and then recover disk4 by rebuilding. First use reiserfsck to check disk5 as specified in the wiki. You don't have to stop samba or unmount it (it never mounted) but check md5 and see what it says. http://www.lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems One last thing. Do you have any extra spare drives just in case you need/want to make a copy of disk5 before attempting repairs on it? Peter
April 16, 201115 yr Author Rebooted and now I get: disk4 Not installed - 1,953,514,552 Unformatted - - - disk5 WDC_WD20EARS-00M_WD-WCAZA1055519 27°C 1,953,514,552 Unformatted 36 0 0 Unformatted! Gulp help!
April 16, 201115 yr Author Will read-only check consistency of the filesystem on /dev/sdf 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/sdf. 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.
April 16, 201115 yr You have 2 option. Option #1: Stop the array reassign disk4 Check if unRAID says that it will rebuild disk4. If this is true, then check the "are you sure box" Press the start button. Wait for the rebuild to complete. Then, you will have 2 drives that you can attempt to rebuild/repair. It is very possible that disk4 will rebuild and be fully restored based on the parity and disk5, even though it is bad. The truely best would be to rebuild disk4 onto a new disk if you had one. Option #2: Attempt to rebuild disk5 right now. Working on md5 means the parity should be adjusted and disk4 will remain just as rebuildable into the future as now. You would first run the --rebuild-sb option and then a rebuild tree or scan whole partition after. For the rebuild-sb I'm quite sure you use version = 3.6, block size = 4096, journaling = yes and rebuild header = no. Hopefully, someone else can confirm this. You could also attempt to create a new mbr on the disk4 at the same time. In the 5.0b6a thread is a utility that will re-create the mbr. You could try that and see what happens. After creating the mbr I would either use unMENU to mount the drive or assign the drive as the cache to see what is on it. It will be rebuilt if you assign it back to the disk4 slot. Peter
April 16, 201115 yr Author ARG how in the world did this all go wrong?! I picked up the disk and moved them to a new machine. This was supposed to be simple. I saw people say NO to journaling! I have to re-read the thread in the wiki. Im starting to evaluate more commercial style raid arrays. I don't want to but im at a loss. I really do not want to to lose this data... Neil
April 16, 201115 yr Author It doesn't look like I can do what you suggested in option 1. It shows it as unformatted and my only option is to format and if I check that I lose both drives....
April 16, 201115 yr Author I quit. Will read-only check consistency of the filesystem on /dev/sdf Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Fri Apr 15 22:08:08 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/sdf' in blocks [18..8211]: 0 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Donzo
April 16, 201115 yr Well, quitting 100% won't get your data back and unRAID, like any RAID, IS NOT a backup. The upgrade you did should have been easy but shit happens. Disk4 which is not installed says it is unformatted. So, I'm thinking that means the simulated disk is not valid and the rebuild will end up the same. I have no idea what you did or didn't do. You're posting a little output snippet with no explanation. It appears you possibly ran the rebuild-tree?? and it failed, likely due to there being no superblock and also possibly because it appears you ran it on device /dev/sdf instead of the partition /dev/sdf1 or the device /dev/md5. You have to use the /dev/mdX device or the /dev/sdX1 device for the reiserfsck commands (eg md1 and sda1 both refer to the partition but sda refers to the whole drive). Using the md device will keep the parity in sync and is only available when the array is started so it's the preferred way to fix disk5. If you are not 100% sure what you are doing then don't do it. I believe you used md5 because I posted md5 and the wiki says to use the mdX device. So, what did you actually do? Disk5 I did more searching and the answers are 3.6.x, 4096, y, n. Get the superblock created then run the check again and report back. reiserfsck --rebuild-sb /dev/md5 reiserfsck /dev/md5 Disk4 Try first creating the partition again. This post has some details on how to do that; http://lime-technology.com/forum/index.php?topic=5072.msg47122#msg47122 Only do this part of the commands and see what you get; unraid_partition_disk.sh /dev/sdX It should complain the partition is not correct. Then: unraid_partition_disk.sh -p /dev/sdX reiserfsck /dev/sdX1 You will have to figure out what device (what X stands for) the disk4 is. You can check the dropdown on the devices page with the array stopped to see what it. Make sure it is unassigned before trying to start the array again. Peter
April 16, 201115 yr Author Disk5 I did more searching and the answers are 3.6.x, 4096, y, n. Get the superblock created then run the check again and report back. reiserfsck --rebuild-sb /dev/md5 reiserfsck /dev/md5 Didn't work see below: Will read-only check consistency of the filesystem on /dev/md5 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sat Apr 16 08:48:14 2011 ########### Replaying journal: No transactions found Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) partition_disk.sh -p /dev/sdX reiserfsck /dev/sdX1 You will have to figure out what device (what X stands for) the disk4 is. You can check the dropdown on the devices page with the array stopped to see what it. Make sure it is unassigned before trying to start the array again. Peter
April 16, 201115 yr Author Disk 4 root@Storage:/boot# reiserfsck --rebuild-sb /dev/sde1 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 check superblock and rebuild it if needed 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/sde1. what the version of ReiserFS do you use[1-4] (1) 3.6.x (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, choose this one) (3) < 3.5.9 converted to new format (don't choose if unsure) (4) < 3.5.9 (this is very old format, don't choose if unsure) (X) exit 1 Enter block size [4096]: No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified). Is journal default? (y/n)[y]: y Did you use resizer(y/n)[n]: n rebuild-sb: no uuid found, a new uuid was generated (689282ab-b4d3-444a-9166-88dcd9b381c5) rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header? (y/n)[n]: y Reiserfs super block in block 16 on 0x841 of format 3.6 with standard journal Count of blocks on the device: 488378624 Number of bitmaps: 14905 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is NOT clean Tree height: 0 Hash function used to sort names: not set Objectid map size 0, max 972 Journal parameters: Device [0x0] Magic [0x0] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x1: some corruptions exist. sb_version: 2 inode generation number: 0 UUID: 689282ab-b4d3-444a-9166-88dcd9b381c5 LABEL: Set flags in SB: Mount count: 1 Maximum mount count: 30 Last fsck run: Sat Apr 16 08:57:07 2011 Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check. root@Storage:/boot# reiserfsck --check /dev/sde1 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/sde1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sat Apr 16 08:59:29 2011 ########### Replaying journal: No transactions found Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted
April 16, 201115 yr Author I don't mean to send snippets I thought it was clear I was trying what I have been told to do? Im running a host of commands but ultimately I think these drives are fubared for some reason?! I wonder if I can read them so I can get the data off them. I realize unraid isn't a backup. I have a second unraid server to backup this one, but with everything being in flux the rsync is far behind... At this point I am hoping for a small miracle. Neil
April 16, 201115 yr Author Disk 4 when I click on it in unraid says: Partition format: MBR: unaligned Great.
April 16, 201115 yr OK, you have a valid partition and the check says that --rebuild-tree didn't complete so that appears to be the right thing to do. If the filesystem checks out OK after your are done then you may also have to run with the --scan-whole-partition option to recover files, which will then be recovered into a lost+found directory. Did you assign disk4 back to the array? Did you create a partition on disk4? How did it get have a valid partition again? I would personally do a fdisk -l /dev/sde just to make sure the partition appears valid compared to your other disks. Peter
April 17, 201115 yr Author I think getting disk5 that is showing a green ball but unformatted is my best bet. If I can get that drive back in the array and rebuild from the parity drive with disk 4 I am good (I think?) I ran reiserfsck --rebuild-tree /dev/sde1 this is disk5 and it seemed to be an encouraging results. But I rebooted and it still shows unformatted . Im not sure what else to do at this point. Disk /dev/sde: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 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. Still shows unformatted? How do I fix that problem?
April 17, 201115 yr Author reiserfs_open: the reiserfs superblock cannot be found on /dev/sde1. Failed to open the filesystem.
April 17, 201115 yr Reply 42 - you put Disk4 and sde1 together. At this point I have no idea what you are doing and you're still just off doing your own thing so I really have nothing more to add. I posted what to do but it wasn't followed so it appears I'm just wasting my time. Good luck. Peter
Archived
This topic is now archived and is closed to further replies.