31
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:58:11 am »
no did you want me to try and restore a super block on sdc & sde as well
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
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.
32
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:50:14 am »
Sorry to be a pain in the you know where..........I have tried a number of the superblocks and I am getting the same error as per below and I tried e3fsck and that didn't work either as it came back as command not found
dcerouter_1024641:/home/bruce# e2fsck -b 32768 /dev/sdb
e2fsck 1.41.3 (12-Oct-2008)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
dcerouter_1024641:/home/bruce# e2fsck -b 32768 /dev/sdb
e2fsck 1.41.3 (12-Oct-2008)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
33
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:31:42 am »
This is what I get for sdb, sdc,sde
dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdb
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdb
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
34
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:29:49 am »
This is what I got below from sdd so now I am going to check sdb
dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdd
e2fsck 1.41.3 (12-Oct-2008)
/dev/sdd has gone 1270 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
11 inodes used (0.00%)
0 non-contiguous inodes (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
5798288 blocks used (1.58%)
0 bad blocks
1 large file
0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
dcerouter_1024641:/home/bruce#
dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdd
e2fsck 1.41.3 (12-Oct-2008)
/dev/sdd has gone 1270 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
11 inodes used (0.00%)
0 non-contiguous inodes (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
5798288 blocks used (1.58%)
0 bad blocks
1 large file
0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
dcerouter_1024641:/home/bruce#
35
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:26:20 am »
Thanks so do you think sdb will have bad superblock even though sdd was the faulty HDD
36
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:21:06 am »
I started checking sdd and currently it says this
dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdd
e2fsck 1.41.3 (12-Oct-2008)
/dev/sdd has gone 1270 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Should I cancel it and check sdb
dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdd
e2fsck 1.41.3 (12-Oct-2008)
/dev/sdd has gone 1270 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Should I cancel it and check sdb
37
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:14:18 am »
I have stopped it already and I am sure it was sdd as that was the HDD I replaced so I assume it wont hurt if it the wrong HDD and if it comes back ok then I will check sdb
38
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 11:07:24 am »
Hey Crumble,
Reading the wordpress documentation it says to run
sudo fsck.ext3 -v /dev/sdd
Is it ok to run this cmd ?
Regards
Beeker
Reading the wordpress documentation it says to run
sudo fsck.ext3 -v /dev/sdd
Is it ok to run this cmd ?
Regards
Beeker
39
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 16, 2013, 09:45:05 am »
Thanks Crumble,
Just in the car stuck in traffic and will be home
in about 40mins so I will let you know how it
goes and thanks again:)
Just in the car stuck in traffic and will be home
in about 40mins so I will let you know how it
goes and thanks again:)
40
Users / Re: QNAP NAS in 810
« on: July 13, 2013, 01:01:58 am »
Hi All,
I had 810 working with a QNAP TS-869L NAS and I had to reset the QNAP TS-869L NAS back to factory defaults due to a firmware issues, I have it set up for DHCP and I have tried everything I can to get 810 to find it and I have been searching for hours in the forums but still no luck.
I have added a file server device 1837 and even fired P&P events still no joy, if anyone has any ideas that would be much appreciated and just an FYI l can work with the command line but no way am I experienced
Thanks
Beeker
I had 810 working with a QNAP TS-869L NAS and I had to reset the QNAP TS-869L NAS back to factory defaults due to a firmware issues, I have it set up for DHCP and I have tried everything I can to get 810 to find it and I have been searching for hours in the forums but still no luck.
I have added a file server device 1837 and even fired P&P events still no joy, if anyone has any ideas that would be much appreciated and just an FYI l can work with the command line but no way am I experienced
Thanks
Beeker
41
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 09, 2013, 11:38:53 am »
Thanks much appreciated 
42
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 09, 2013, 11:30:33 am »
Phew sdd1 is definitely the replacement HDD that is currently showing no valid partition
43
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 09, 2013, 11:23:06 am »
Here you go after formatting sdd1 with ext3
dcerouter_1024641:/home/bruce# 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/sdd: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc8efaf55
Disk /dev/sdd doesn't contain a valid partition table
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: 0x2848762e
Device Boot Start End Blocks Id System
/dev/sdf1 1 182401 1465134080 83 Linux
dcerouter_1024641:/home/bruce#
dcerouter_1024641:/home/bruce# 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/sdd: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc8efaf55
Disk /dev/sdd doesn't contain a valid partition table
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: 0x2848762e
Device Boot Start End Blocks Id System
/dev/sdf1 1 182401 1465134080 83 Linux
dcerouter_1024641:/home/bruce#
44
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 09, 2013, 11:05:05 am »
Have I stuffed things ?
45
Users / Re: URGENT 810 Software RAID failed after power outage
« on: July 09, 2013, 11:01:32 am »
Sorry oops to late as that was the replacement HDD that was showing as no valid partition so I figured it needed to be formatted as ext3