November 11, 200916 yr I went to add two more drives to my configuration last night and added another 2 port Via SATA card. But to keep the drives and cards physically aligned I moved the cards down the motherboard. When I brought the machine up I had a message that I had an invalid configuration - understandable as drive mount points had changed. The screen was actually quite helpful in letting me know what it expected so I printed that page and went and re-selected the original array drives in the correct order) and left the new drives out of it for the moment. When I did this I got a green configuration. At this point I started the array and it commenced a parity check which completed without problem (that I remember). One thing I did note is that unlike usual the samba mounts did not come online during that parity check. So, this morning when the check was complete, I shut down the array and added the two drives (These are two drives that were in my old WD World Book so they are previously linux formatted drives) but when I went back to the main page I find that all drives are reporting blue - Initial configuration. I quickly jumped back to devices, re-removed the new disks and the remaining drives are still showing blue - Initial Configuration. Any recommendations about where to go in this? (attached is my syslog) Syslog Notes: I did have some issues trying to get unmenu running. I was getting a nearly blank page from myMenu on unmenu (e<body></body>o - or something similar - I tried to update the files through sftp but there were write problems) The fat write failures in the log I guess are those attempts. There are two fat formatted volumes, one being an old 40G I use to boot PLoP to boot from USB, which is the other fat volume. Only the USB key is mounted. Why it couldn't write, I cannot tell you. I did stop messing with it while the parity was running as I had intended to submit this for level 1 motherboard certification. I'm actually starting to think that the issues writing to the fat for some reason is the cause for these drives now appearing as new. I'd just like to get your comments before I do anything terribly drastic. (grin) Thanks all! (Updated attachment - Was syslinux.exe, now actual syslog)
November 11, 200916 yr Author I did find that logged in as root I cannot create a file on the /boot folder. Despite my usb key not having a write protect switch, I'm at a bit of a loss as to how that happened. But it's certainly my bet for the root of my problem. I look forward to some input before I proceed. I expect that I'll shut things down, check out my usb key's file system, possibly reformatting it and reinstalling unraid and restoring my configuration folder and setting up the drives again to match my last previous good configuration. Thanks again for your time. Rob
November 11, 200916 yr I kinda sounds like your flash drive is not allowing writes to it. So what might have happened is that when the parity check completed it tried to write the info to the super.dat file and could not. From there it seems to think the super.dat is bad and that you have a new config. A restart of the server might fix it, but I would probably shut it down and place the drive in a windows computer and run chkdisk on it to see if it finds anything wrong.
November 11, 200916 yr Author It was too late to do anything drastic earlier so posting this thread was my way of stopping myself. I rebuilt my usb key - using a non-quick format to ensure that the OS thought it was a reliable disk and restarted and my array came up active and rescanning parity on reboot. Whew. I'm not a huge fan of "new" when they're disks with info. Thanks for the second set of eyes. Rob
November 12, 200916 yr I'm sure it could be helpful to somebody, but did you really mean to attach a copy of syslinux.exe?
November 12, 200916 yr Author At 3am you're luck you didn't get my whole drive. Fixed. Rob (That is funny though)
Archived
This topic is now archived and is closed to further replies.