impossible to get access to nas disk (raid-1 xfs) with live Ubuntu cd: you have no rights...

Toggle sidebar Toggle sidebar
J

JustTrying

Reputable
Feb 14, 2016
23
0
4,510
Hi everyone,
found a possible solution here to gain access to my former nas-drive (the nas obviously died) by using an Ubuntu live cd. Tried to do so, but when accessing the drive I get the message: "You have no rights to access this drive..."
(Using the nas I can still see the users, but not the folders anymore, so I expect the nas is gone.)
No repair utility or something of the kind.
Does anyone have one or more ideas how to get access to the drive again and get to the data?
Hard to get info about 'the day after....' the nas died.
Thank you for any help in advance.
 
Sort by date Sort by votes
Thank you for your assistance - will try to find more answers.
Here is what I can say now:
Dual Bay Nas-server. Brand unknown. The service doesn't exist anymore (unisupport.net in Denmark), the website is for sale.
Had three years of garantee, this is year # 4.
The tool to access the nas is NetTool.exe.
The 2 drives have been formatted to XFS.
Set up via web-based management.
Did use the nas under a win2k pc and an old laptop. That w2k-machine died two months ago, so I have built a new pc with legal win7.
The laptop was that old and having so many problems that I have bought me a simple new one, with win8 pre-installed.
Cannot see anything on the raid-disks (connected via sata inside the new pc) with win7.
Following the suggestion somewhere here, I did create an iso disk with Ubuntu 14.04.3.
I am not (yet) a Linux experienced person, so ran the live cd and tried to get to the files on the disk.
In Ubuntu I could see the disk and a few directories. Entering any of them gave me the info that I had no rights to get in.
Not sure if I ran Ubuntu as root. No idea if a simple user of a live cd has any admin rights or not.
The problem is I do not know which program/system stopped me.
Was it Ubuntu? Was is the nas-drive?
Can I make a user with admin rights when running a live cd?
I do know the user name and the password for the nas.
If Ubuntu allows me to, I can create a user with the name of the administrator and give that user the password that I used for the nas.

I do have a backup of the nas from one week before the nas stopped working.
Created that backup with win7, via the network. Just copying all the stuf.
The basic problem is that my administration data (I am a small trader -an artist- and need that administration for the tax submittance) from the moment between the backup and the end of the nas-life is not on a backup. Could enter the data once more, but then a bunch of administration numbers will be gone. Not funny for tax employees...

Will try to run the live cd once more shortly.
Suggestions on what to try by then are much appreciated. Will look for cat/ proc/mdstat, whatever that may be. I will find it.
Thank you in advance.
 
Upvote 0 Downvote
Just an extra bit of info: the nas was a stand-alone machine, stored far away from the pc's at home, for safety reasons.
Connected via network cable.
It was not a built-in nas, inside my pc.
Excuse me for not mentioning.
 
Upvote 0 Downvote
Username root is the super user and gives you full permissions. See commands id and sudo. Note best practice is to make drive images and execute recovery operations on the images to guard against mistakes. See command ddrescue. As the filesystem is XFS it's likely that Linux Software RAID was used by your NAS. See command mdadm. When you run command "cat /proc/mdstat" it shows the status of your mdadm RAID. But without a basic understanding of Linux it will be a challenge for you to recover the Linux way. I suggest you first try Windows recovery tools such as R-Studio or UFSexplorer which will be safer and easier for you to use.
 
Upvote 0 Downvote
@ S Haran - Yes, understand what you are saying. But I do want to go for the linux way. It will take a couple of days for me to get into this stuff. Already studied basic info. Not afraid of a command line, that's the way I started in 1985 🙂 Windows had to be invented at that time I think. Norton Commander, lots of printer problems and that kind of stuf.

Like to install an extra drive (for 64bit o/s and for linux installation) and rebuild the nas; the nas-drives are out now.
Are both drives of a raid-1 absolutely completely identic, or has one of the two some kind of database/fat/whatsoever?
I mean, does it make a difference the way I put both drives back into the nas? Both drives are identical and I haven't found any identification which one of them should be placed in which slot. Well, may as well try and see what happens.
Try to create an iso of both drives; sounds a good idea.
You will hear from me in a few days; after the weekend I hope.
Enjoy life.
 
Upvote 0 Downvote
Still busy trying to have Ubuntu do what I like it to do.
Can still access the nas via http://ip-address.
Seems to be a chance to make a backup, but not clear yet how to deal with that in Ubuntu - having problems with user rights.
Will be back - thank you for your patience.
 
Upvote 0 Downvote
Back once again. Studying the man pages especially for the commands mentioned here.
It is a pity I have not been able to find more info (yet) about dealing with a harddrive that comes out of an external nas. Many time I read about files on the local disk where ubuntu resides. These files do not exist in my case, which makes understanding a bit confusing.
result for the question earlier:

joes@film16-linux:~$ sudo cat /proc/mdstat
[sudo] password for joes:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sda3[0](S)
976486848 blocks

Working on creating a backup. Fear to have written anything to disk, so studying many man pages. What a pleasure to get that much basic info. Not easy to grow in, but not impossible either.

Double Commander shows the drive with 'md127' and states 'disk is not available'.
It shows a partition as sda2 after the md127.
In sda2 there is a raidconf file stating:

[RAID]
raid_enable = 1
raid_mode = 1
disk_num = 2
disk1 = "/dev/sda"
disk2 = "/dev/sdb"
disk3 = ""
disk4 = ""
fstype = 0
raid_vendor = ""

Think this partition is on the nas-disk. See if I can get more info.

joes@film16-linux:~$ sudo mdadm --examine --scan /dev/sda1 /dev/sda2 /dev/sda3

ARRAY /dev/md0 UUID=1120c154:ee458961:c72e49a8:c467befb


joes@film16-linux:~$ sudo fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 63 273104 136521 82 Linux swap / Solaris
/dev/sda2 273105 546209 136552+ 83 Linux
/dev/sda3 546210 1953520064 976486927+ 83 Linux

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x63a924e1

Device Boot Start End Blocks Id System
/dev/sdb1 63 273104 136521 82 Linux swap / Solaris
/dev/sdb2 273105 546209 136552+ 83 Linux
/dev/sdb3 546210 3907024064 1953238927+ 83 Linux

Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xdc4da274

Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sdc2 206848 152115051 75954102 83 Linux

Disk /dev/sdd: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders, total 125045424 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffffffff

Device Boot Start End Blocks Id System
/dev/sdd1 * 63 125033894 62516916 7 HPFS/NTFS/exFAT

Continue searching and deriving extra info.
Tips speeding the search are welcome.
 
Upvote 0 Downvote
Thank you. First another one, don know if that is of any use.

joes@film16-linux:~$ sudo mdadm --examine /dev/sda
mdadm: /dev/sda is not attached to Intel(R) RAID controller.
mdadm: /dev/sda is not attached to Intel(R) RAID controller.
/dev/sda:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.0.00
Orig Family : 246f9a7e
Family : 246f9a7e
Generation : 000002cd
Attributes : All supported
UUID : 3270173f:054aff94:06bb56fc:89c2348e
Checksum : 8b25fdf6 correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1

Disk00 Serial : LB46Y49P5W82571M
State : active
Id : 00010000
Usable Size : 125040904 (59.62 GiB 64.02 GB)

[Volume0]:
UUID : 566c593d:e10cd185:0937f7d8:edac600b
RAID Level : 0
Members : 2
Slots : [UU]
Failed disk : 1
This Slot : 0
Array Size : 250081280 (119.25 GiB 128.04 GB)
Per Dev Size : 125040904 (59.62 GiB 64.02 GB)
Sector Offset : 0
Num Stripes : 488440
Chunk Size : 128 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Dirty State : clean

Disk01 Serial : 307YEA2M66XEWM6A
State : active
Id : 00040000
Usable Size : 125040904 (59.62 GiB 64.02 GB)

-----------------
Tried that one too - no luck.
joes@film16-linux:~$ sudo mdadm -E /dev/sda3
mdadm: cannot open /dev/sda3: No such file or directory

 
Upvote 0 Downvote
Some more info:
joes@film16-linux:~$ sudo blkid
[sudo] password for joes:
/dev/sda1: LABEL="SSD-60gyg" UUID="6E1CE86D1CE8322F" TYPE="ntfs"
/dev/sdb1: TYPE="swap"
/dev/sdb2: UUID="98f150d5-dfce-4572-8edf-aa830e9ad62d" TYPE="xfs"
/dev/sdb3: UUID="1120c154-ee45-8961-c72e-49a8c467befb" TYPE="linux_raid_member"
/dev/sdc1: TYPE="swap"
/dev/sdc2: UUID="7f51d39c-017c-4ac7-b36c-f101aef20dc9" TYPE="xfs"
/dev/sdc3: UUID="d95747d3-fd97-4840-aff6-40356a926d0d" TYPE="xfs"
/dev/sdd1: LABEL="Door systeem gereserveerd" UUID="A03CE83C3CE80EDA" TYPE="ntfs"
/dev/sdd2: UUID="5a5d8c3a-5039-45da-be93-9719a310a648" TYPE="ext3"

remark: the /dev/sda is a rather small ssd disk that I use for swapfiles to speed things up - not part of the array disk.

back to your advice...
searching for files I did get an error, having the choice between quit and report, I chose for report and the program hangs.
Will start again. Is there a kind of log at the end?
 
Upvote 0 Downvote
testdisk:
>Disk /dev/sda - 64 GB / 59 Gib - OCZ-VERTEX v1.10
CHS 7783 255 63 - sector size=512
>[proceed] [quit]
<p>
>[Intel] Intel/PC partition (has been detected)
<enter>
[ analyse ]
disk /dev/sda - 64 GB / 59 GiB - CHS 7783 255 63
current partition structure:
partition start end size in sectors
1 * HPFS - NTFS 0 1 1 7782 254 63 125033832 [SSD-60gyg]
> [ Quick Search ] [ Backup ]
<quick search> try to locate partition
structure: ok
{ quit ] [ deeper search ] [ write ]

Do not want to write partition structure to disk, since I do not know to which disk that will be; so did quit/go back to the menu for the moment.

[ Advanced ] Filesystem Utils
Not sure which one to choose. List looks interesting, but writes copies to somewhere. No idea if that is safe for the moment.




 
Upvote 0 Downvote
Did a new mdstat:
joes@film16-linux:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdb3[0](S)
976486848 blocks

md 127 is now an inactive sdb3 instead of sdba
the number of blocks is the same as in the first mdsat: 976486848 blocks
Maybe had a hickup...
But this shows that sda is not the one, as I already thought.
Back to sdb...
 
Upvote 0 Downvote
joes@film16-linux:~$ sudo mdadm -E /dev/sdb3
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.03
UUID : 1120c154:ee458961:c72e49a8:c467befb
Creation Time : Thu Jan 1 01:05:46 1970
Raid Level : raid1
Used Dev Size : 976486848 (931.25 GiB 999.92 GB)
Array Size : 976486848 (931.25 GiB 999.92 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Mon Feb 22 21:28:17 2016
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : c527268a - correct
Events : 126


Number Major Minor RaidDevice State
this 0 8 19 0 active sync /dev/sdb3

0 0 8 19 0 active sync /dev/sdb3
1 1 8 3 1 active sync
 
Upvote 0 Downvote
testdisk sdb:

Partition Start End Size in sectors
> 1 P Linux Swap 0 1 1 16 254 63 273042
2 P Linux 17 0 1 33 254 63 273105
3 P Linux 34 0 1 121600 254 63 1952973855

Looks better...
 
Upvote 0 Downvote
trying to list the files on the third partition I get the error:

Support for this filesystem hasn't been enable during compilation.

It looks like testdisk is not (yet) ready for reading xfs ?

 
Upvote 0 Downvote
That looks better. So now you could try: mdadm --assemble --force /dev/md0 /dev/sdb3

And if all goes well you should be able to mount /dev/md0 and see your data.

But I would look at it first with: testdisk /dev/sdb3
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom