January 25, 201115 yr Array will boot, but immediately gets a kernel panic once login screen is displayed. Since kernel is down, can't get to syslog. Took picture and attached. Was having some issues with my media center memory maxing out during library build, and moved about 300 files out of one folder to a temp folder. This operation was successful, I started to move some files back over to the main directory, and window locked up. I rebooted my media server, then tried to connect to unraid, and couldn't. Forced a hard reboot, and file system was mounting, but have been recieving this error ever since. Am in process of running a mem-test right now, but I do believe this is a file system issue. Tried to find some similar information on forum, but haven't seen anything like this yet. Waiting for guidance on next step. Thanks in advance.
January 25, 201115 yr Author I was running 4.5.6 (I'm pretty sure, but not 100%), but I upgraded to 4.7 to determine if this would fix things. My upgrade to 4.5.6 was on 10-28-2010, and I would have taken whatever build was in final release. By upgrading, all I did was copy bzroot, bzimage, and memtest.
January 25, 201115 yr I'd say boot with a non-configured flash drive. (Or move your config folder to a different name for the short term) If it is a reiserfs error, then don't let it try to mount it. Then once booted, you can run reiserfsck on each drive in turn. Yes, you'll need to re-compute parity, but it might get you up and running. Joe L.
January 25, 201115 yr Author Have checked 3 drives so far, 2 have superblock issues that it wants me to run the -SB option on. Is this safe, or should I run --rebuild-tree instead?
January 25, 201115 yr Have checked 3 drives so far, 2 have superblock issues that it wants me to run the -SB option on. Is this safe, or should I run --rebuild-tree instead? Are you running it on the correct device? Or, better asked: What command are you using to check them? (Be very specific and list the exact command including the "device") There is no file system on the parity drive, so you can skip that one. Typically you never run a command that is not suggested by a prior reiserfsck. so no, a rebuild-tree is not in order unless it requested it. Joe L.
January 25, 201115 yr Author I have 8 disks currently in array: 5 data, 1 cache, 1 parity, and 1 backup (pre-clear is run on it). I ran reiserfsck /dev/sd* on each disk Data disks : SBB - Superblock cannot be found. Suggest running rebuild-sb. SDC - Superblock cannot be found. Suggest running rebuild-sb. SDI - Superblock cannot be found. Suggest running rebuild-sb. SDH - Superblock cannot be found. Suggest running rebuild-sb. one of the below is the data disk, the other is the backup: SDD - Bad root block. Superblock can't be found. SDE - Bad root block. Superblock can't be found. Cache drive - SDG - Superblock cannot be found. Suggest running rebuild-sb. Parity (I know I don't need to run anything on it, just checked it to be thorough) - SDF - Superblock cannot be found. Suggest running rebuild-sb. Plan is to start with the SDB data disk and run: reiserfsck --rebuild-sb /dev/sdb Am not sure of the answers to all the options. Any help would be appreciated.
January 26, 201115 yr I have 8 disks currently in array: 5 data, 1 cache, 1 parity, and 1 backup (pre-clear is run on it). I ran reiserfsck /dev/sd* on each disk Data disks : SBB - Superblock cannot be found. Suggest running rebuild-sb. SDC - Superblock cannot be found. Suggest running rebuild-sb. SDI - Superblock cannot be found. Suggest running rebuild-sb. SDH - Superblock cannot be found. Suggest running rebuild-sb. one of the below is the data disk, the other is the backup: SDD - Bad root block. Superblock can't be found. SDE - Bad root block. Superblock can't be found. Cache drive - SDG - Superblock cannot be found. Suggest running rebuild-sb. Parity (I know I don't need to run anything on it, just checked it to be thorough) - SDF - Superblock cannot be found. Suggest running rebuild-sb. Plan is to start with the SDB data disk and run: reiserfsck --rebuild-sb /dev/sdb Am not sure of the answers to all the options. Any help would be appreciated. you are doing it WRONG. The file system is on the first partition, so the correct syntax would be: reiserfsck --check /dev/sdb1 and then go from there based on its feedback. (Note the trailing "1" on the end of the device name indicating the first partition) Joe L.
January 26, 201115 yr Author Whew, I'm glad I double checked. Not 100% on file system stuff, I'm more of a DB guy. Running check on SDB1 now. So far, so good. Will reort results when done. Thanks again!!
Archived
This topic is now archived and is closed to further replies.