Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Beeker

Pages: 1 ... 3 4 [5] 6 7 ... 18
61
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 05:05:50 am »
No I have 4 x HDD's with one hot spare so it should be b,c,d & e with f as a hot spare so may be either the power or the sata lead may have come out, I will check these when I get home and let you know

62
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 04:43:17 am »
This is what I got

dcerouter_1024641:/home/bruce# mdadm -E /dev/sdd1
mdadm: cannot open /dev/sdd1: No such file or directory

63
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 03:50:08 am »
ok

64
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 03:20:18 am »

Here you go
cat /proc/mdstat   

dcerouter_1024641:/home/bruce# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : inactive sdb1[0](S) sdf[4](S) sde1[3](S) sdc1[1](S)
      5860546304 blocks

mdadm -E /dev/sdb1
dcerouter_1024641:/home/bruce# mdadm -E /dev/sdb1
/dev/sdb1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 5747d0ac:31c15bff:bd9f1658:0a1d2015 (local to host dcerouter)
  Creation Time : Sun Dec 27 10:14:43 2009
     Raid Level : raid5
  Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
     Array Size : 4395407808 (4191.79 GiB 4500.90 GB)
   Raid Devices : 4
  Total Devices : 5
Preferred Minor : 1

    Update Time : Thu Jun 13 09:02:55 2013
          State : clean
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1
       Checksum : ee358c49 - correct
         Events : 1802

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       8       17        0      active sync   /dev/sdb1

   0     0       8       17        0      active sync   /dev/sdb1
   1     1       8       33        1      active sync   /dev/sdc1
   2     2       8       49        2      active sync
   3     3       8       65        3      active sync   /dev/sde1
   4     4       8       80        4      spare   /dev/sdf



mdadm -E /dev/sdc1
dcerouter_1024641:/home/bruce# mdadm -E /dev/sdc1
/dev/sdc1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 5747d0ac:31c15bff:bd9f1658:0a1d2015 (local to host dcerouter)
  Creation Time : Sun Dec 27 10:14:43 2009
     Raid Level : raid5
  Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
     Array Size : 4395407808 (4191.79 GiB 4500.90 GB)
   Raid Devices : 4
  Total Devices : 5
Preferred Minor : 1

    Update Time : Thu Jun 13 09:02:55 2013
          State : clean
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1
       Checksum : ee358c5b - correct
         Events : 1802

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1       8       33        1      active sync   /dev/sdc1

   0     0       8       17        0      active sync   /dev/sdb1
   1     1       8       33        1      active sync   /dev/sdc1
   2     2       8       49        2      active sync
   3     3       8       65        3      active sync   /dev/sde1
   4     4       8       80        4      spare   /dev/sdf


mdadm -E /dev/sde1
dcerouter_1024641:/home/bruce# mdadm -E /dev/sde1
/dev/sde1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 5747d0ac:31c15bff:bd9f1658:0a1d2015 (local to host dcerouter)
  Creation Time : Sun Dec 27 10:14:43 2009
     Raid Level : raid5
  Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
     Array Size : 4395407808 (4191.79 GiB 4500.90 GB)
   Raid Devices : 4
  Total Devices : 5
Preferred Minor : 1

    Update Time : Thu Jun 13 09:02:55 2013
          State : clean
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1
       Checksum : ee358c7f - correct
         Events : 1802

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     3       8       65        3      active sync   /dev/sde1

   0     0       8       17        0      active sync   /dev/sdb1
   1     1       8       33        1      active sync   /dev/sdc1
   2     2       8       49        2      active sync
   3     3       8       65        3      active sync   /dev/sde1
   4     4       8       80        4      spare   /dev/sdf




65
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 02:26:10 am »
I tried
mdadm –detail /dev/md1 and got

dcerouter_1024641:/home/bruce# mdadm -detail /dev/md1
mdadm: -d does not set the mode, and so cannot be the first option.

So than I tried mdadm -D /dev/md1 and got
dcerouter_1024641:/home/bruce# mdadm -D /dev/md1
mdadm: md device /dev/md1 does not appear to be active.


66
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 01:39:32 am »
Hi Crumble

This is what I got from sudo fdisk -l and from memory sdf was always the spare drive

dcerouter_1024641:/home/bruce# sudo fdisk -l

Disk /dev/sda: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x39686ed2

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       90446   726507463+  83  Linux
/dev/sda2           90447       91201     6064537+   5  Extended
/dev/sda5           90447       91201     6064506   82  Linux swap / Solaris

Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0006a5c8

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      182401  1465136001   83  Linux

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb217d64b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      182401  1465136001   83  Linux

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x43b7a284

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1      182401  1465136001   83  Linux

Disk /dev/sdf: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc8efaf55

Disk /dev/sdf doesn't contain a valid partition table


I also tried

dcerouter_1024641:/home/bruce# mdadm -E /dev/md1
mdadm: No md superblock detected on /dev/md1.

Any help on how to proceed would be greatly appreciated I wasn't sure where to go from here

Regards
Beeker

67
Users / Re: URGENT 810 Software RAID failed after power outage
« on: June 17, 2013, 01:20:26 am »
Thanks very much for the info I will try it now and report back and sorry its a software RAID5 in LMCE

Kind regards
Beeker

68
Users / [SOLVED]: URGENT 810 Software RAID failed after power outage
« on: June 14, 2013, 10:50:26 pm »
Hi All,
We had a power failure at home and my system with 810 and when the power came back and it booted back up now the LMCE software RAID is showing all the drives as removed I have tried su mdadm -D /dev/md1 and it comes back with mdadm: md device /dev/md1 does not appear to be active.

I have very limited cmd line knowledge so any help would be appreciated to see if there is anything I can try to recover the RAID and data as all our family photos are on it and I am currently building up a new QNAP NAS with RAID6 as I was advised to do

I have attached a photo from LMCE of the RAID

Kind regards
Beeker

69
Installation issues / Re: 1004 - QNAP NAS - AXIS CAMERA - ATOM n330i
« on: March 07, 2013, 06:30:06 am »
Apologies to all that replied I am traveling at the moment so I will respond to all the posts this weekend, though I did manage to get the Qnap to be recognised by 810 after finding a previous post of how to get it to rescan 

70
Installation issues / 1004 - QNAP NAS - AXIS CAMERA - ATOM n330i
« on: March 02, 2013, 10:12:29 am »
Hi All,
I know I am trouble for combining multiple issues in the one thread though I thought it all relates to the same thing 1004

As per tschak909 Tom's suggestion in one my previous posts to move to 1004 I bit the bullet and downloaded 1004 final and installed it on a standalone network with internet so it did not upset my existing 810 setup and below are the results and I am interested in any feedback or suggestions


 1 . After installing 1004 successfully (Great work from everyone much slicker) I moved my QNAP TS-869 over to the test environment and 1004 found it straight away so I added all the shares and made them public as they were discovered though when I click on any of them in an orbiter no files are present despite doing a resync in the media browser.

2. My AXIS IP M1011 cameras that worked under motion wrapper perfectly in 810 now do not work in 1004 despite being set up exactly the same s in 810. I even tried the Advanced IP device template though both the motion wrapper and the advanced IP gave the same result of no image

3. I had limited success with the Atom n330i as a MD whilst it now does not have the kernel panic issue it take ages to boot up. In one of the reboots it did an update of nVidia graphics by itself and now when it finally boots up as a MD it has strange coloured blocks across the screen...........it was working until it did that update during one of the reboots

4. I need to use the QNAP for the future though before I move all my data off the 810 software RAID I want to make sure the QNAP works in 1004 and I have the right structure before I move the 5TB of content over to the QNAP so any help here would be much appreciated.

5. Finally if anybody can suggest how to make 810 find my QNAP as I changed it to DHCP as recommended and plugged it back into my 810 network and LMCE has yet to find it after 2 days

Regards
Beeker


71
Users / Re: QNAP NAS
« on: February 28, 2013, 07:58:10 pm »
That's great news about the Atom  :)

72
Users / Re: QNAP NAS
« on: February 28, 2013, 07:04:38 pm »
Thanks guys much appreciated been waiting
for 1004 so I can use my Ion Atom as MD

73
Users / QNAP NAS
« on: February 28, 2013, 06:19:08 pm »
Hi All,
Running 810 Final release with a software RAID and have brought a new Qnap TS869L NAS and its on the internal network and have set a static IP on it within the range for the core and I am having difficulty with the fact the Core is not automatically recogonising it, I know there is a way to get the core to search for it can anybody help...........only have limited cmd line experience

Thanks
Beeker

74
Installation issues / RESOLVED Re: Axis M1011 IP Camera
« on: February 17, 2013, 09:07:32 pm »
Thank you very much for the tip and screenshot..............after entering the user name and password in the config area it worked perfectly and I have tested it with both of these and they both work

/axis-cgi/jpg/image.cgi
/mjpg/video.mjpg

Kind regards
Beeker

75
Installation issues / Re: Axis M1011 IP Camera
« on: February 16, 2013, 09:33:55 pm »
Further to that here is a screenshot of the axis device in LMCE

Pages: 1 ... 3 4 [5] 6 7 ... 18