January 27, 201313 yr command I used was this : reiserfsck --check /dev/sdc Looks like I must use /dev/md* but what number have my cache drive ? I need some help in the WIKI is stated i need to use --rebuild-sb PLEASE ask for assistance on the unRAID forums My cache drive have been damage ?? can some one help me ? My partition is not change so it's valid. info of cache drive below Drive Partitions - Not In Protected Array Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/sdc ST3500630AS_9QG0V4HA 24°C 500.11G /dev/sdc1 ST3500630AS_9QG0V4HA 24°C result from reiserfsck --check /dev/sdc 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.
January 27, 201313 yr Author opps I doing this right now, so some info the it's need to do this on the partition ;-) reiserfsck --check /dev/sdc1 We will see what the result .... EDIT No corruption found.... The reason was that the cache drive show up as unformatted, but there was a green ball for the disc, now I'm rebooting ....
January 28, 201313 yr Always great when someone requests assistance with a problem, then diagnoses it them self, then fixes it too! So happy we could help!
January 28, 201313 yr opps I doing this right now, so some info the it's need to do this on the partition ;-) reiserfsck --check /dev/sdc1 We will see what the result .... EDIT No corruption found.... The reason was that the cache drive show up as unformatted, but there was a green ball for the disc, now I'm rebooting .... to unRAID, any disk that fails to "mount" is unformatted. Therefore, if you have anything that interferes with the mounting of the cache drive, it will show as "unformatted" (an add-on might be attempting to access a directory on the cache drive before it is mounted, preventing it from being mounted because the mount-point is already in use)
January 14, 201412 yr I just had a similar occurrence, running v5.0.4. System rebooted this morning after a power cut. I noticed, this evening, that my photo-frame wasn't displaying photos. On investigation, I found that my minidlna plugin wasn't running, and refused to start (I tried the emhttp interface, start service and running as a direct command). Everything else appeared to be working correctly - mysql, squeezeboxserver, reading nfs shares etc. On looking at the syslog, I found a number of errors related to sdb, which pointed to my cache drive. I ran reiserfsck on sdb1 which reported an error on block 2. emhttp was showing the cache drive as 'green'. I shut the server down and restarted - everything came up normally. So, something upset my cache drive, preventing it from mounting after the power returned (via APC UPS) this morning. This appeared to interfere with minidlna which, as far as I'm aware, makes no direct reference to the cache. Most odd!
Archived
This topic is now archived and is closed to further replies.