Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
The steps I have to take are:
sudo modprobe nbd sudo ut listall sudo ut attach {DRIVE_ID_FROM_LISTALL} /dev/nbd0 sudo mount -t ext4 /mnt/sc101 /dev/nbd0
Line 1 adds a device driver to the kernel line 2 finds the drive's "id". You only need to run this once - the ID doesn't change line 3 "attaches" the drive to the system. line 4 mounts the block device at my chosen mount point.
I've added a line to FSTab to take care of line 4, but the problem is, I seem to need to do line 1 and line 3 after a reboot before I can mount it.
Q1: How can I make a modprobe "stick" to survive a reboot? Q2: Where should I execute line 3? Q3: Should I should manually mount there too, rather than using FSTab?
I'm attempting to use BackupPC to backup my files. This runs as a service, and requires that drive to be running to start.
Q4: Is there a way to conditionally start a service, dependant on whether the drive is present or not, or should I just let it attempt to auto-start and live with it failing if the drive's not there?
Any help much appreciated!
BTW, the reason I'm attempting to use BackupPC is because it "folds" identical files from multiple PCs into 1, i.e. it doesn't store multiple copies - i.e. it de-duplicates the backup, hopefully allowing me to backup multiple machines without buying loads of disks!
Cheers Steve
I neglected to say, I'm using Ubuntu 10.04 LTS Lucid Lynx Thanks Steve
steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
The steps I have to take are:
sudo modprobe nbd sudo ut listall sudo ut attach {DRIVE_ID_FROM_LISTALL} /dev/nbd0 sudo mount -t ext4 /mnt/sc101 /dev/nbd0
Line 1 adds a device driver to the kernel line 2 finds the drive's "id". You only need to run this once - the ID doesn't change line 3 "attaches" the drive to the system. line 4 mounts the block device at my chosen mount point.
I've added a line to FSTab to take care of line 4, but the problem is, I seem to need to do line 1 and line 3 after a reboot before I can mount it.
Q1: How can I make a modprobe "stick" to survive a reboot? Q2: Where should I execute line 3? Q3: Should I should manually mount there too, rather than using FSTab?
I'm attempting to use BackupPC to backup my files. This runs as a service, and requires that drive to be running to start.
Q4: Is there a way to conditionally start a service, dependant on whether the drive is present or not, or should I just let it attempt to auto-start and live with it failing if the drive's not there?
Any help much appreciated!
BTW, the reason I'm attempting to use BackupPC is because it "folds" identical files from multiple PCs into 1, i.e. it doesn't store multiple copies - i.e. it de-duplicates the backup, hopefully allowing me to backup multiple machines without buying loads of disks!
Cheers Steve
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
steve-ALUG@hst.me.uk wrote:
Q1: How can I make a modprobe "stick" to survive a reboot?
In Ubuntu 10.04 you should add the name of the module to the file /etc/modules for it to be loaded automatically at boot
Q2: Where should I execute line 3? Q3: Should I should manually mount there too, rather than using FSTab?
I came across this howto - its geared towards making GFS filesystems on the device (for clustered storage), but the init scripts and config files may allow you to mount the drive at boot:
http://www.dknss.com/data/sc101-nbd-init/sc101-gfs-howto/
Hope this helps a bit
Jim
On 19/08/10 09:37, Jim Rippon wrote:
In Ubuntu 10.04 you should add the name of the module to the file /etc/modules for it to be loaded automatically at boot [] I came across this howto - its geared towards making GFS filesystems on the device (for clustered storage), but the init scripts and config files may allow you to mount the drive at boot:
http://www.dknss.com/data/sc101-nbd-init/sc101-gfs-howto/
Hope this helps a bit
Jim
Thanks Jim, that helped. Thanks to all the others that helped too.
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
The steps I have to take are:
sudo modprobe nbd sudo ut listall sudo ut attach {DRIVE_ID_FROM_LISTALL} /dev/nbd0 sudo mount -t ext4 /mnt/sc101 /dev/nbd0
I bought one of those from a local cheapcycle offering.
I want to use a drive from an ex-Windows PC on it - a 250GB Western Digital drive but I'm not sure how I should partition/format it before stuffing it into the SC101.
Can anybody advise what I should do please? Perhaps I should add that I have plugged the drive into the Netgear but it just sits there for ages blinking the error (power) LED.
On 19/08/10 11:54, Chris Walker wrote:
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
The steps I have to take are:
sudo modprobe nbd sudo ut listall sudo ut attach {DRIVE_ID_FROM_LISTALL} /dev/nbd0 sudo mount -t ext4 /mnt/sc101 /dev/nbd0
I bought one of those from a local cheapcycle offering.
I want to use a drive from an ex-Windows PC on it - a 250GB Western Digital drive but I'm not sure how I should partition/format it before stuffing it into the SC101.
Can anybody advise what I should do please? Perhaps I should add that I have plugged the drive into the Netgear but it just sits there for ages blinking the error (power) LED.
Problem solved!
As I was sending this, the message from Jim Rippon came down so I'm now reading that.
Moral - don't be in so much of a hurry!
On 19/08/10 11:54, Chris Walker wrote:
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
The steps I have to take are:
sudo modprobe nbd sudo ut listall sudo ut attach {DRIVE_ID_FROM_LISTALL} /dev/nbd0 sudo mount -t ext4 /mnt/sc101 /dev/nbd0
I bought one of those from a local cheapcycle offering.
I want to use a drive from an ex-Windows PC on it - a 250GB Western Digital drive but I'm not sure how I should partition/format it before stuffing it into the SC101.
Can anybody advise what I should do please? Perhaps I should add that I have plugged the drive into the Netgear but it just sits there for ages blinking the error (power) LED.
I've given up with the drive and am currently fighting with it on an old PC.
So does anybody want a Netgear SC101 without drives but with the correct power supply?
I live just outside Norwich but if it would help, I come into Norwich quite often and could probably make one of the meetings at the Coach and Horses on Thorpe Road.
On 19 Aug 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
The steps I have to take are:
sudo modprobe nbd sudo ut listall sudo ut attach {DRIVE_ID_FROM_LISTALL} /dev/nbd0 sudo mount -t ext4 /mnt/sc101 /dev/nbd0
Line 1 adds a device driver to the kernel line 2 finds the drive's "id". You only need to run this once - the ID doesn't change line 3 "attaches" the drive to the system. line 4 mounts the block device at my chosen mount point.
I've added a line to FSTab to take care of line 4, but the problem is, I seem to need to do line 1 and line 3 after a reboot before I can mount it.
Q1: How can I make a modprobe "stick" to survive a reboot?
add it in /etc/modules
Q2: Where should I execute line 3?
Well, you want it to happen before the fstab comes up, so I'd be tempted to add a udev rule, as I'm assuming that a kernel event arrises after the modprobe that should be trappable to run a command for the attach... Either that or add a upstart job for it, should be simple enough it's only got to exec the attach, after all.
Q3: Should I should manually mount there too, rather than using FSTab?
Leaving it in fstab gives a fairly clear view of what you're expecting, so that's probably as good a place as any to be honest.
I'm attempting to use BackupPC to backup my files. This runs as a service, and requires that drive to be running to start.
Q4: Is there a way to conditionally start a service, dependant on whether the drive is present or not, or should I just let it attempt to auto-start and live with it failing if the drive's not there?
Well, if you wrote an upstart job to do the attach and mount, then you could get the backuppc job to rely on that having been run.
Any help much appreciated!
BTW, the reason I'm attempting to use BackupPC is because it "folds" identical files from multiple PCs into 1, i.e. it doesn't store multiple copies - i.e. it de-duplicates the backup, hopefully allowing me to backup multiple machines without buying loads of disks!
Personally I use dirvish, but that hasn't got quite such a pretty interface to play with, and doesn't squish identical files from multiple machines, but does just hard linking for the particular backup it's doing.
Cheers,
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
If it helps anyone, what I did was: Found a windows machine. Downloaded the latest windows driver and the latest firmware for the machine from:
http://kb.netgear.com/app/answers/detail/a_id/667
Installed the software on the Windows machine. Use the software to update the firmware. Use the software to create a partition on the drive on the drive. (As I recall, I had to "Assign a drive letter", which took me to the create a partition page. One the partition was created, I then option to "release a drive letter" (or whatever it was called)). Now finished with the windows machine; you can uninstall the software if required.
On Ubuntu, I downloaded and installed the .deb package from http://code.google.com/p/sc101-nbd/downloads/list
and following stuff from http://ubuntuforums.org/showthread.php?t=87480&page=2 I did
sudo ut listall <- lists the available partitions sudo modprobe nbd <- Inserts the driver module sudo ut attach [id] /dev/nbd0 <- Attaches the partition to /dev/nbd0 <- [id] is from the ut list results
On a whim, I decided to use ext4 rather than ext2
sudo mkfs.ext4 /dev/nbd0 <- formats the partition as ext4 sudo mount /dev/nbd0 /mnt/mountpoint <- Mounts the partition for use
I added ndb to the file /etc/modules so that ndb would be loaded on every boot.
I then used the info on this page: http://wiki.zeropain.com/index.php/SC101/Mount_Helper
I added an entry to my fstab file [id] /mnt/mountpoint ut _netdev,defaults,noatime,nodiratime,noexec 0 0
Where [id] is the drive's ID from "ut listall" The _netdev means that the drive is only mounted once the network is up. I added the noatime and nodiratime to speed up the drive; I'm not bothered about access times being recorded on this drive. I added noexec because nothing will be executed on this drive.
I then added the script from the zeropain webpage which handles the actual mounting.
Bob's then your uncle.
Hope this may help someone!
This page also provided useful information http://www.dknss.com/data/sc101-nbd-init/sc101-gfs-howto/
Cheers Steve
On 04/09/10 11:12, steve-ALUG@hst.me.uk wrote: [] And thanks to all that helped
Cheers Steve
On 04/09/10 11:12, steve-ALUG@hst.me.uk wrote:
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
I've been trying to mail steve about a SC101 but the mail has bounced.
The following message to steve-ALUG@hst.me.uk was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'relay not permitted'
This is the only way I can think of to bring this to his attention so apologies if I offend anybody.
On 04 Sep 18:01, Chris Walker wrote:
On 04/09/10 11:12, steve-ALUG@hst.me.uk wrote:
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
I've been trying to mail steve about a SC101 but the mail has bounced.
The following message to steve-ALUG@hst.me.uk was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'relay not permitted'
This is the only way I can think of to bring this to his attention so apologies if I offend anybody.
Looking at hst.me.uk's set of MX records, I'm scared... I didn't realise that there were still people with 4 MXs. Do you know which one of the MXs you hit?
On 04/09/10 18:50, Brett Parker wrote:
On 04 Sep 18:01, Chris Walker wrote:
On 04/09/10 11:12, steve-ALUG@hst.me.uk wrote:
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
I've been trying to mail steve about a SC101 but the mail has bounced.
The following message tosteve-ALUG@hst.me.uk was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'relay not permitted'
This is the only way I can think of to bring this to his attention so apologies if I offend anybody.
Looking at hst.me.uk's set of MX records, I'm scared... I didn't realise that there were still people with 4 MXs. Do you know which one of the MXs you hit?
The next bit of the message is this :-
Reporting-MTA: dns; out1.ip05ir2.opaltelecom.net
Final-Recipient: rfc822;steve-ALUG@hst.me.uk Action: failed Status: 5.0.0 (permanent failure) Remote-MTA: dns; [212.159.47.228] Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'relay not permitted' (delivery attempts: 0)
Does that help or would you like me to send copies of the headers?
On 04 Sep 19:02, Chris Walker wrote:
On 04/09/10 18:50, Brett Parker wrote:
On 04 Sep 18:01, Chris Walker wrote:
On 04/09/10 11:12, steve-ALUG@hst.me.uk wrote:
On 19/08/10 00:55, steve-ALUG@hst.me.uk wrote:
Hi Gurus!
I've been given a Netgear SC101 which I'm intending to use for backups. I found a post somewhere about how to mount it, and I have mounted it, or at least I thought I had until I rebooted and it was no-longer mounted.
I've been trying to mail steve about a SC101 but the mail has bounced.
The following message tosteve-ALUG@hst.me.uk was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'relay not permitted'
This is the only way I can think of to bring this to his attention so apologies if I offend anybody.
Looking at hst.me.uk's set of MX records, I'm scared... I didn't realise that there were still people with 4 MXs. Do you know which one of the MXs you hit?
The next bit of the message is this :-
Reporting-MTA: dns; out1.ip05ir2.opaltelecom.net
Final-Recipient: rfc822;steve-ALUG@hst.me.uk Action: failed Status: 5.0.0 (permanent failure) Remote-MTA: dns; [212.159.47.228] Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'relay not permitted' (delivery attempts: 0)
That's not the primary MX, and so I'd guess it's a badly setup secondary that should be removed from the list (it *is* set as the second MX, though, so you'd expect it to go right...)
On 05/09/10 01:44, Brett Parker wrote:
On 04 Sep 19:02, Chris Walker wrote:
On 04/09/10 18:50, Brett Parker wrote:
On 04 Sep 18:01, Chris Walker wrote:
On 04/09/10 11:12, steve-ALUG@hst.me.uk wrote:
I've been trying to mail steve about a SC101 but the mail has bounced.
The following message tosteve-ALUG@hst.me.uk was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'relay not permitted'
This is the only way I can think of to bring this to his attention so apologies if I offend anybody.
Hi! I'm back! Sorry, I had hardware issues so my server was down for a day, and I discovered that my secondary MX was bad too as you have spotted.
Looking at hst.me.uk's set of MX records, I'm scared... I didn't realise that there were still people with 4 MXs. Do you know which one of the MXs you hit?
Now reduced to 2!
Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'relay not permitted' (delivery attempts: 0)
That's not the primary MX, and so I'd guess it's a badly setup secondary that should be removed from the list (it *is* set as the second MX, though, so you'd expect it to go right...)
It has been corrected (hopefully)
Chris, feel free to try to email again! :-)
Cheers Steve
-
Brett Parker -
Chris Walker -
Jim Rippon -
steve-ALUG＠hst.me.uk